Gary:
I found a lot of error messages in the application event log. The most
interesting are:
Event Type: Warning
Event Source: Microsoft Project Server Tracing Eventlog Provider
Event Category: None
Event ID: 1
Date: 2005-01-16
Time: 00:01:16
User: NT AUTHORITY\LOCAL SERVICE
Computer: VIEG12YA
Description:
Component: Unknown Component Name
File: C:\Office\dev\project\WebClient\source\server\pjnpesvc\PjNpeSvc.cpp
Line: 147
Error Number: 0x80020009
Description: <Description><![CDATA[Cube Processing Failed]]></Description>
Event Type: Error
Event Source: Microsoft Project Server Tracing Eventlog Provider
Event Category: None
Event ID: 2
Date: 2005-01-16
Time: 00:01:16
User: NT AUTHORITY\LOCAL SERVICE
Computer: VIEG12YA
Description:
File: C:\Office\dev\project\WebClient\source\utility\pjadorsutil2.cpp
Line: 1691
Error Number: 0x80004005
Description: <Description><![CDATA[Assert Detected. The error code was also
included.]]></Description>
___________________________________
Component: Microsoft OLE DB Provider for SQL Server
Description: <Description><![CDATA[Die in der Anmeldung 'ProjectServer6717'
angeforderte Datenbank kann nicht geöffnet werden. Fehler bei der
Anmeldung.]]></Description>
"Translation: CDATA[The in the registation `ProjectServer6717` demanded
database could not be opened. Error in registation."
Event Type: Error
Event Source: Microsoft Project Server Tracing Eventlog Provider
Event Category: None
Event ID: 2
Date: 2005-01-16
Time: 00:01:16
User: NT AUTHORITY\LOCAL SERVICE
Computer: VIEG12YA
Description:
Component: PjQuery
File: C:\Office\dev\project\WebClient\source\server\pjquery\CnxCookie.cpp
Line: 150
Error Number: 0x80004005
Description: <Description><![CDATA[Assert Detected for Virtual Root
'ProjectServer'. The error code was also included.]]></Description>
I also found some other warnings and errors:
Event Type: Warning
Event Source: Active Server Pages
Event Category: None
Event ID: 9
Date: 2005-01-13
Time: 07:45:43
User: N/A
Computer: VIEG12YA
Description:
Warning: IIS log failed to write entry, Script timed out. The maximum
amount of time for a script to execute was exceeded. You can change this
limit by specifying a new value for the property Server.ScriptTimeout or by
changing the value in the IIS administration tools..
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1053
Date: 2005-01-13
Time: 14:59:03
User: NT AUTHORITY\SYSTEM
Computer: VIEG12YA
Description:
Windows cannot determine the user or computer name. (Not enough storage is
available to complete this operation. ). Group Policy processing aborted.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
If you need further information for analysing the problem let me know.
Thanks for your help!
Oliver
Gary L. Chefetz (MVP) said:
Oliver:
Ok then, you have a problem. What are you willing to share with us to help
you fix it? Do you see errors in the application event log? Things like
that?
--
Gary L. Chefetz, MVP
"We wrote the books on Project Server"
http://www.msprojectexperts.com
-
Hi to all of you!
My question to this problem: Has this suggestion to solve the problem been
succsessfully?
We have the same problem but the reason seems not to be the xml-files.
Maybe you can help us.
Oliver
:
Hi Vanessa
Normally, this issue occurs when the XML request is stuck at Project
Server
services. At this time, I suggest you try the
following steps for troubleshooting.
1. Avoid users to access Project Server.
2. On the Project Server computer, go to the ViewDrop folder. By
default, it
is at:
Program Files\Microsoft Office Project Server 2003\BIN\VIEWDROP
3. Check if there is any XML files within this folder. If there is, move
all
of them to a temporary folder.
4. Restart the Microsoft Project Server Views Notification Service. If
possible, please restart other Project Server services
also.
5. Try manually updating the cube again to check the results.
6. If the cube is updated successfully, you may put the XML files back
to
the ViewDrop folder one by one. It should
disappear in the folder after a few seconds. In case it does not
disappear,
please move it out and place others.
Regarding the second issue, I suggest you check it again after the cube
is
successfully updated. In case this behavior
persists, would you please create a new Portfolio Analyzer view to see
if
the same behavior appears?
Best Regards
Kelvin Kirby
Technology Associates
www.techassoc.com
:
The OLAP cube is built daily and was working fine (sort of...) until
recently.
Now the build initialises but never completes. Can anyone suggest
what the
problem could be?
As a seperate issue, my Project Analyser view seems to display
different
(lower) Actual Work figures compared to those in Resource Usage view.
Timesheet summaries are also incomplete. Very frustrating...
Help much appreciated!