RE: Status Report Notification

Tech-Archive recommends: Fix windows errors by optimizing your registry

{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\f0\fs20 Hi Jay,
\par
\par Just a followup on this post. I am wondering if you have any questions or concerns about this issue. If you need further assistance, please do not hesitate to let me know.
\par
\par Hope this helps!
\par
\par Sincerely,
\par
\par Dana Brash
\par Microsoft Online Partner Support
\par
\par When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue.
\par =====================================================
\par Business-Critical Phone Support (BCPS) provides you with technical phone support at no charge during critical LAN outages or "business down" situations. This benefit is available 24 hours a day, 7 days a week to all Microsoft technology partners in the United States and Canada.
\par
\par This and other support options are available here:
\par BCPS: https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
\par Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/
\par
\par If you are outside the United States, please visit our International Support page: http://support.microsoft.com/common/international.aspx.
\par =====================================================
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par
\par
\par \pard\li720 --------------------
\par Thread-Topic: Status Report Notification
\par thread-index: AcX1D5Pe/egHfcTLQGaT70KxrgoNBQ==
\par X-WBNR-Posting-Host: 204.4.13.72
\par From: =?Utf-8?B?SmF5?= <fjm@xxxxxxxxxxxxxx>
\par References: <F2952271-793A-4E44-98C8-9A98F7BD3E7F@xxxxxxxxxxxxx> <zUuCfE23FHA.1172@xxxxxxxxxxxxxxxxxxxxx> <6A85A105-8483-4120-9D5A-D02635737904@xxxxxxxxxxxxx> <uUGYxU04FHA.1172@xxxxxxxxxxxxxxxxxxxxx> <CA670D32-1662-4DDF-AF9E-6008FB78C24E@xxxxxxxxxxxxx> <n1ivSzo5FHA.2672@xxxxxxxxxxxxxxxxxxxxx>
\par Subject: RE: Status Report Notification
\par Date: Tue, 29 Nov 2005 10:06:10 -0800
\par Lines: 313
\par Message-ID: <0CAB8EAF-27D7-43D6-81E9-823797F33807@xxxxxxxxxxxxx>
\par MIME-Version: 1.0
\par Content-Type: text/plain;
\par \tab charset="Utf-8"
\par Content-Transfer-Encoding: 7bit
\par X-Newsreader: Microsoft CDO for Windows 2000
\par Content-Class: urn:content-classes:message
\par Importance: normal
\par Priority: normal
\par X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
\par Newsgroups: microsoft.public.sharepoint.teamservices
\par NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
\par Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
\par Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sharepoint.teamservices:22808
\par X-Tomcat-NG: microsoft.public.sharepoint.teamservices
\par
\par To answer your first question, I deleted the report over a year ago using PWA.
\par
\par I ran the query again and found that both entries show the
\par WREPORT_IS_ENABLED field set to 0. I'm not sure where to go from here. I
\par deleted the report properly and the table has the proper value. Is there a
\par table which schedules or hold the notifications perhaps we can remove this
\par entry from there.
\par --
\par Jay, MCP
\par
\par
\par ""Dana Brash"" wrote:
\par
\par > Hi Jay,
\par >
\par > Please do not delete these records from the database, we just needed to
\par > have a peek at what's there. ANY direct manipulation (adding, deleting,
\par > modifying) of the data for ProjectServer is ALWAYS a last ditch effort.
\par >
\par > Please also tell me exactly HOW you deleted the status report originally.
\par > What were the exact steps that you followed?
\par >
\par > I understand that when you run the query:
\par >
\par > Use ProjectServer
\par > Go
\par > select * from MSP_WEB_STATUS_REPORTS
\par >
\par > You see two records.
\par >
\par > Locate the status report in question in the WREPORT_NAME field then check
\par > the WREPORT_IS_ENABLED field and confirm whether it's 0 or 1.
\par >
\par > IF the WREPORT_IS_ENABLED field is 0, it's been deleted, if 1 it's still
\par > active. If the 'deleted' report is showing as 1, we can first check to
\par > make the setting in PWA.
\par >
\par > 1) PWA > Status Reports
\par > 2) Delete a status report so your team members no longer have to respond to
\par > it
\par > 3) Select the correct WREPORT_NAME from the dropdown
\par > 4) Click OK twice.
\par >
\par > This will update the WREPORT_IS_ENABLED field to 0, and you should no
\par > longer receive notifications.
\par >
\par > If for some reason you are not able to perform the above steps in PWA, then
\par > you may consider manually updating the record in the database. Again, this
\par > is a last resort, and a bigger concern is how did the problem happen like
\par > this.
\par >
\par > update msp_web_status_reports set wreport_is_enabled=1 where wreport_name =
\par > '<your report name here>'
\par >
\par > Please note that when you delete 'status reports' in the PWA Clean up
\par > Project Server database page, you are only deleting submitted reports, not
\par > the actual request.
\par >
\par > Please let me know if this helps.
\par >
\par > Best,
\par > Dana
\par >
\par > Dana Brash [MSFT]
\par >
\par > When responding to posts, please "Reply to Group" via your newsreader so
\par > that others may learn and benefit from your issue.
\par > =====================================================
\par > This posting is provided "AS IS" with no warranties, and confers no rights.
\par >
\par >
\par > --------------------
\par > Thread-Topic: Status Report Notification
\par > thread-index: AcXmMwQvg5XY/82eQSq0KX4QZClOhw==
\par > X-WBNR-Posting-Host: 204.4.13.72
\par > From: =?Utf-8?B?SmF5?= <fjm@xxxxxxxxxxxxxx>
\par > References: <F2952271-793A-4E44-98C8-9A98F7BD3E7F@xxxxxxxxxxxxx>
\par > <zUuCfE23FHA.1172@xxxxxxxxxxxxxxxxxxxxx>
\par > <6A85A105-8483-4120-9D5A-D02635737904@xxxxxxxxxxxxx>
\par > <uUGYxU04FHA.1172@xxxxxxxxxxxxxxxxxxxxx>
\par > Subject: RE: Status Report Notification
\par > Date: Thu, 10 Nov 2005 12:12:03 -0800
\par > Lines: 281
\par > Message-ID: <CA670D32-1662-4DDF-AF9E-6008FB78C24E@xxxxxxxxxxxxx>
\par > MIME-Version: 1.0
\par > Content-Type: text/plain;
\par > \tab charset="Utf-8"
\par > Content-Transfer-Encoding: 7bit
\par > X-Newsreader: Microsoft CDO for Windows 2000
\par > Content-Class: urn:content-classes:message
\par > Importance: normal
\par > Priority: normal
\par > X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
\par > Newsgroups: microsoft.public.sharepoint.teamservices
\par > NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
\par > Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
\par > Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sharepoint.teamservices:22763
\par > X-Tomcat-NG: microsoft.public.sharepoint.teamservices
\par >
\par > I've run the query and the report has two entries in the table. Can I
\par > simply
\par > delete the two entries to resolve the problem?
\par > --
\par > Jay, MCP
\par >
\par >
\par > ""Dana Brash"" wrote:
\par >
\par > > Hello Jay,
\par > >
\par > > Please let me know what you find with running the query and looking into
\par > > the other potential environmental issues I mentioned previously.
\par > >
\par > > As this is really a Project question, I'm unsure as to why you would be
\par > > directed to post in the SharePoint newsgroup, particularly as you have a
\par > > way to the correct newsgroup (starting from non-managed). I would like
\par > to
\par > > follow up with the specific case where you were told to post to this
\par > group.
\par > > If possible, could you tell me the NG, initial post date, and subject
\par > line
\par > > of the thread where you were given this information?
\par > >
\par > > Also, if you use Outlook Express, or another direct newsgroup reader, you
\par > > should be able to go directly to the public newgroups at
\par > > microsoft.public.... Using IE, you can also directly access all Office
\par > > newsgroups at
\par > > http://www.microsoft.com/office/community/en-us/default.mspx?d=1,
\par > including
\par > > the groups for Project and Project Server.
\par > >
\par > > microsoft.public.project.server can be accessed directly here:
\par > >
\par > http://www.microsoft.com/office/community/en-us/default.mspx?dg=microsoft.pu
\par > > blic.project.server&lang=en&cr=US
\par > >
\par > > Please let me know as you get more information. I look forward to
\par > hearing
\par > > back from you.
\par > >
\par > > Best,
\par > > Dana
\par > >
\par > > Dana Brash [MSFT]
\par > >
\par > > When responding to posts, please "Reply to Group" via your newsreader so
\par > > that others may learn and benefit from your issue.
\par > > =====================================================
\par > > This posting is provided "AS IS" with no warranties, and confers no
\par > rights.
\par > >
\par > >
\par > > --------------------
\par > > Thread-Topic: Status Report Notification
\par > > thread-index: AcXhfdkcHm4JM/E0SvOOWDyQQhFo4w==
\par > > X-WBNR-Posting-Host: 204.4.13.72
\par > > From: =?Utf-8?B?SmF5?= <fjm@xxxxxxxxxxxxxx>
\par > > References: <F2952271-793A-4E44-98C8-9A98F7BD3E7F@xxxxxxxxxxxxx>
\par > > <zUuCfE23FHA.1172@xxxxxxxxxxxxxxxxxxxxx>
\par > > Subject: RE: Status Report Notification
\par > > Date: Fri, 4 Nov 2005 12:25:07 -0800
\par > > Lines: 190
\par > > Message-ID: <6A85A105-8483-4120-9D5A-D02635737904@xxxxxxxxxxxxx>
\par > > MIME-Version: 1.0
\par > > Content-Type: text/plain;
\par > > \tab charset="Utf-8"
\par > > Content-Transfer-Encoding: 7bit
\par > > X-Newsreader: Microsoft CDO for Windows 2000
\par > > Content-Class: urn:content-classes:message
\par > > Importance: normal
\par > > Priority: normal
\par > > X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
\par > > Newsgroups: microsoft.public.sharepoint.teamservices
\par > > NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
\par > > Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
\par > > Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sharepoint.teamservices:3535
\par > > X-Tomcat-NG: microsoft.public.sharepoint.teamservices
\par > >
\par > > I run the query you suggested to see that it was deleted from the table.
\par > > SP1
\par > > has been installed since it was released in 2004 and the client SP1 was
\par > > slipstreamed into our Project Pro image so all users are running that as
\par > > well. I have a feeling I'll find that the report wasn't actually removed
\par > > from the table.
\par > >
\par > > I'll let you know what I find.... thank you for following up.
\par > >
\par > > As far as the NG is concerned I'm accessing them from
\par > >
\par > http://www.microsoft.com/technet/community/newsgroups/managed/dgbrowser/en-u
\par > >
\par > s/default.mspx?dg=microsoft.public.sharepoint.teamservices&mid=c50653dc-3097
\par > > -4026-9ae1-df42271cf7aa
\par > > which has an expanding menu on the left, none of the project news groups
\par > > show
\par > > there. If you start from the Non-managed newsgroups link then you are
\par > able
\par > > to see the Project groups. It's very strange. I reported this to the NG
\par > > managers some time ago and it's still not resolved. They stated I should
\par > > post on the Sharepoint groups even though this issue is not Sharepoint
\par > > related.
\par > > --
\par > > Jay, MCP
\par > >
\par > >
\par > > ""Dana Brash"" wrote:
\par > >
\par > > > Hi Jay,
\par > > >
\par > > > Thanks for looking for the Project newsgroups. It's interesting that
\par > > > you're not able to see the microsoft.public.project or
\par > > > microsoft.public.project.server newsgroups, though I'm sure your
\par > support
\par > > > case will manage to get that sorted out. Regardless, I'm happy to work
\par > > > with you here on this problem.
\par > > >
\par > > > From your post, my understanding of this issue is: a user is receiving
\par > > > reminders to submit status reports that have been deleted. If this is
\par > > not
\par > > > correct, please feel free to let me know.
\par > > >
\par > > > I'd like to confirm that you've got the latest updates installed for
\par > the
\par > > > system. There are some known issues with SP2 for Project Server at
\par > this
\par > > > point related to RBS, so I am recommending that users continue with SP1
\par > > > until these issues are resolved.Please apply both server and client
\par > > service
\par > > > packs and retest the problem. You can find more information here:
\par > > >
\par > > > Description of Project Server 2003 Service Pack 1
\par > > > http://support.microsoft.com/?id=837241
\par > > >
\par > > > Please see the "Determine whether the service pack is installed " link
\par > in
\par > > > the above article for information about determining the version and the
\par > > > build number of Project Server 2003 that is installed on the server.
\par > > > For the SQL installation of Project Server SP1, confirm that the
\par > correct
\par > > > .sql files are installed on the system.
\par > > >
\par > > > SP1 should display something along the lines of 11.1.2004.0.1707.15.
\par > > >
\par > > > Project Server 2003 SP1:
\par > > >
\par > >
\par > http://www.microsoft.com/downloads/details.aspx?familyid=5dea5862-d534-4f17-
\par > > > ab08-7c9b790c5b15&displaylang=en
\par > > >
\par > > > Project 2003 SP1:
\par > > >
\par > >
\par > http://www.microsoft.com/downloads/details.aspx?familyid=1b04c073-e58f-4f42-
\par > > > b76d-6b565a45cdc3&displaylang=en
\par > > >
\par > > > If you would like to check the database to see whether the status
\par > report
\par > > is
\par > > > still in the dataset, you can try the below query in Query Analyzer:
\par > > >
\par > > > Please run the below query to confirm that the status report has truly
\par > > been
\par > > > deleted:
\par > > >
\par > > > Use ProjectServer
\par > > > Go
\par > > > select * from MSP_WEB_STATUS_REPORTS
\par > > >
\par > > > You can review the WREPORT_NAME field for the name of the deleted
\par > status
\par > > > report.
\par > > >
\par > > > ** NOTE: This programming example is provided for illustration only,
\par > > > without warranty either expressed or implied, including, but not
\par > limited
\par > > > to, the implied warranties of merchantability and/or fitness for a
\par > > > particular purpose. This assumes that you are familiar with the
\par > > programming
\par > > > language being demonstrated and the tools used to create and debug
\par > > > procedures. Microsoft support professionals can help explain the
\par > > > functionality of a particular procedure, but they will not modify these
\par > > > examples to provide added functionality or construct procedures to meet
\par > > > your specific needs. If you have limited programming experience, you
\par > may
\par > > > want to contact a Microsoft Certified Partner or the Microsoft
\par > fee-based
\par > > > consulting line at (800) 936-5200. For more information about Microsoft
\par > > > Certified Partners, please visit the following Microsoft Web site: \tab
\par > > > http://www.microsoft.com/partner/referral/
\par > > >
\par > > > For more information about the support options that are available and
\par > > > about how to contact Microsoft, visit the following Microsoft Web site:
\par > > > http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS
\par > > >
\par > > > I would like to check a couple of obvious thing with you. I noticed a
\par > > > similar case, where both the Support Engineer and the contact on the
\par > > > customer side were very experienced and savvy. After about a month of
\par > > > working on the problem and trying numerous things, it turned out to be
\par > an
\par > > > old copy of the database running on a testing server that was sending
\par > the
\par > > > reminders. So, I'd like to make sure we're not running into something
\par > > > obvious like that. =)
\par > > >
\par > > > Another case had the users reporting that the reminders were from a
\par > > deleted
\par > > > status report, but the report showed up in the PWA > Status reports >
\par > > > Status reports archive list. Please have the user confirm in PWA that
\par > > the
\par > > > status report in question is not in this list.
\par > > >
\par > > > I believe that this problem should be resolved by either applying
\par > Service
\par \pard
\par
\par }