S
Shane
It appears that the OLAP cube building process has stalled in our Project
Server 2003. Is there a way to kill the process?
Shane
Server 2003. Is there a way to kill the process?
Shane
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
S
Steve Sanderlin
It appears that the OLAP cube building process has stalled in our Project
Server 2003. Is there a way to kill the process?
Shane
When you say it has "stalled", what exactly do you mean? What are you
seeing that leads you to believe that this has occured? Can you please
post some error messages and/or symptoms you are seeing?
S
Shane
The cube usually takes 2 hours or less to run. When you start the cube, it
says under 'Current Cube Status': "The cube building process was initiated on
....". Ours started at 12:04am on 6/8/07. When the process finishes, the
status message indicates such. At the time of my first submission (1:00 PM),
the message hadn't changed. Now it's been the weekend and the message still
hasn't changed.
Thx,
Shane
says under 'Current Cube Status': "The cube building process was initiated on
....". Ours started at 12:04am on 6/8/07. When the process finishes, the
status message indicates such. At the time of my first submission (1:00 PM),
the message hadn't changed. Now it's been the weekend and the message still
hasn't changed.
Thx,
Shane
S
Steve Sanderlin
The cube usually takes 2 hours or less to run. When you start the cube, it
says under 'Current Cube Status': "The cube building process was initiated on
...". Ours started at 12:04am on 6/8/07. When the process finishes, the
status message indicates such. At the time of my first submission (1:00 PM),
the message hadn't changed. Now it's been the weekend and the message still
hasn't changed.
Thx,
Shane
Are there any errors in the application log of the Analysis Services,
SQL Server, or Project Server system?
Try attaching the SQL Profiler to your Project Server's DB server...
is there activity going on in the CUBE tables?
D
Dave
I work with Shane, there are no errors in the logs on the sql server, on
project server there are various errors. Seems to be the same errors that
just repeat:
Component: PjMsgHlr
File: C:\Office\devsp\project\WebClient\source\server\pjmsghlr\MsgHandler.cpp
Line: 588
Error Number: 0x8c040017
Description: <Description><![CDATA[Assert Detected. The error code was also
included.]]></Description>
Component: PjMsgHlr
File: C:\Office\devsp\project\WebClient\source\server\pjmsghlr\updatedb.cpp
Line: 516
Error Number: 0x8c040017
Description: <Description><![CDATA[Assert Detected. The error code was also
included.]]></Description>
Component: PjMsgHlr
File: C:\Office\devsp\project\WebClient\source\server\pjmsghlr\updatedb.cpp
Line: 2318
Error Number: 0x8c040017
Description: <Description><![CDATA[Assert Detected. The error code was also
included.]]></Description>
Component: PjMsgHlr
File: C:\Office\devsp\project\WebClient\source\server\pjmsghlr\updatedb.cpp
Line: 2318
Error Number: 0x8c040017
Description: <Description><![CDATA[Assert Detected. The error code was also
included.]]></Description>
Component: PjMsgHlr
File: C:\Office\devsp\project\WebClient\source\server\pjmsghlr\MsgHandler.cpp
Line: 1100
Error Number: 0x8c040017
Description: <Description><![CDATA[Assert Detected. The error code was also
included.]]></Description>
These appear often in the error logs on the project server. The only error
around the time the cube build was initiated is this:
Component: PCSViews
File: ViewsDrop.cls
Line: -1
Error Number: 0x5
Description: <Description><![CDATA[Error Information: Invalid procedure call
or argument
Additional Information: An error occured processing the following view :-
<ViewsDropData><ProjectData><EntProjectName><![CDATA[TRD 0004-04-01
DOCA.Published]
]></EntProjectName><EntProjectID>36</EntProjectID></ProjectData><OrgGuid>projectserver</OrgGuid><ProjectID>108</ProjectID><BasePath>projectserver</BasePath><TimeStamp>2007-06-08T12:35:26</TimeStamp></ViewsDropData>
]]></Description>
I believe this is from using a dash in the project name so I generally
disregard this error.
Any ideas on the other errors? We're also seeing Project web access not
updating after a project has been published/updated.
Thanks,
Dave
project server there are various errors. Seems to be the same errors that
just repeat:
Component: PjMsgHlr
File: C:\Office\devsp\project\WebClient\source\server\pjmsghlr\MsgHandler.cpp
Line: 588
Error Number: 0x8c040017
Description: <Description><![CDATA[Assert Detected. The error code was also
included.]]></Description>
Component: PjMsgHlr
File: C:\Office\devsp\project\WebClient\source\server\pjmsghlr\updatedb.cpp
Line: 516
Error Number: 0x8c040017
Description: <Description><![CDATA[Assert Detected. The error code was also
included.]]></Description>
Component: PjMsgHlr
File: C:\Office\devsp\project\WebClient\source\server\pjmsghlr\updatedb.cpp
Line: 2318
Error Number: 0x8c040017
Description: <Description><![CDATA[Assert Detected. The error code was also
included.]]></Description>
Component: PjMsgHlr
File: C:\Office\devsp\project\WebClient\source\server\pjmsghlr\updatedb.cpp
Line: 2318
Error Number: 0x8c040017
Description: <Description><![CDATA[Assert Detected. The error code was also
included.]]></Description>
Component: PjMsgHlr
File: C:\Office\devsp\project\WebClient\source\server\pjmsghlr\MsgHandler.cpp
Line: 1100
Error Number: 0x8c040017
Description: <Description><![CDATA[Assert Detected. The error code was also
included.]]></Description>
These appear often in the error logs on the project server. The only error
around the time the cube build was initiated is this:
Component: PCSViews
File: ViewsDrop.cls
Line: -1
Error Number: 0x5
Description: <Description><![CDATA[Error Information: Invalid procedure call
or argument
Additional Information: An error occured processing the following view :-
<ViewsDropData><ProjectData><EntProjectName><![CDATA[TRD 0004-04-01
DOCA.Published]
]></EntProjectName><EntProjectID>36</EntProjectID></ProjectData><OrgGuid>projectserver</OrgGuid><ProjectID>108</ProjectID><BasePath>projectserver</BasePath><TimeStamp>2007-06-08T12:35:26</TimeStamp></ViewsDropData>
]]></Description>
I believe this is from using a dash in the project name so I generally
disregard this error.
Any ideas on the other errors? We're also seeing Project web access not
updating after a project has been published/updated.
Thanks,
Dave
B
Brian Tkatch
I work with Shane, there are no errors in the logs on the sql server, on
project server there are various errors. Seems to be the same errors that
just repeat:
Component: PjMsgHlr
File: C:\Office\devsp\project\WebClient\source\server\pjmsghlr\MsgHandler.cpp
Line: 588
Error Number: 0x8c040017
Description: <Description><![CDATA[Assert Detected. The error code was also
included.]]></Description>
Component: PjMsgHlr
File: C:\Office\devsp\project\WebClient\source\server\pjmsghlr\updatedb.cpp
Line: 516
Error Number: 0x8c040017
Description: <Description><![CDATA[Assert Detected. The error code was also
included.]]></Description>
Component: PjMsgHlr
File: C:\Office\devsp\project\WebClient\source\server\pjmsghlr\updatedb.cpp
Line: 2318
Error Number: 0x8c040017
Description: <Description><![CDATA[Assert Detected. The error code was also
included.]]></Description>
Component: PjMsgHlr
File: C:\Office\devsp\project\WebClient\source\server\pjmsghlr\updatedb.cpp
Line: 2318
Error Number: 0x8c040017
Description: <Description><![CDATA[Assert Detected. The error code was also
included.]]></Description>
Component: PjMsgHlr
File: C:\Office\devsp\project\WebClient\source\server\pjmsghlr\MsgHandler.cpp
Line: 1100
Error Number: 0x8c040017
Description: <Description><![CDATA[Assert Detected. The error code was also
included.]]></Description>
These appear often in the error logs on the project server. The only error
around the time the cube build was initiated is this:
Component: PCSViews
File: ViewsDrop.cls
Line: -1
Error Number: 0x5
Description: <Description><![CDATA[Error Information: Invalid procedure call
or argument
Additional Information: An error occured processing the following view :-
<ViewsDropData><ProjectData><EntProjectName><![CDATA[TRD 0004-04-01
DOCA.Published]
]></EntProjectName><EntProjectID>36</EntProjectID></ProjectData><OrgGuid>projectserver</OrgGuid><ProjectID>108</ProjectID><BasePath>projectserver</BasePath><TimeStamp>2007-06-08T12:35:26</TimeStamp></ViewsDropData>
]]></Description>
I believe this is from using a dash in the project name so I generally
disregard this error.
Any ideas on the other errors? We're also seeing Project web access not
updating after a project has been published/updated.
Thanks,
Dave
Are there any errors in the application log of the Analysis Services,
SQL Server, or Project Server system?
Try attaching the SQL Profiler to your Project Server's DB server...
is there activity going on in the CUBE tables?
Were there any errors on the database server?
B.
S
Steve Sanderlin
I work with Shane, there are no errors in the logs on the sql server, on
project server there are various errors. Seems to be the same errors that
just repeat:Component: PjMsgHlr
File: C:\Office\devsp\project\WebClient\source\server\pjmsghlr\MsgHandler.cpp
Line: 588
Error Number: 0x8c040017
Description: <Description><![CDATA[Assert Detected. The error code was also
included.]]></Description>Component: PjMsgHlr
File: C:\Office\devsp\project\WebClient\source\server\pjmsghlr\updatedb.cpp
Line: 516
Error Number: 0x8c040017
Description: <Description><![CDATA[Assert Detected. The error code was also
included.]]></Description>
Component: PjMsgHlr
File: C:\Office\devsp\project\WebClient\source\server\pjmsghlr\updatedb.cpp
Line: 2318
Error Number: 0x8c040017
Description: <Description><![CDATA[Assert Detected. The error code was also
included.]]></Description>Component: PjMsgHlr
File: C:\Office\devsp\project\WebClient\source\server\pjmsghlr\updatedb.cpp
Line: 2318
Error Number: 0x8c040017
Description: <Description><![CDATA[Assert Detected. The error code was also
included.]]></Description>Component: PjMsgHlr
File: C:\Office\devsp\project\WebClient\source\server\pjmsghlr\MsgHandler.cpp
Line: 1100
Error Number: 0x8c040017
Description: <Description><![CDATA[Assert Detected. The error code was also
included.]]></Description>These appear often in the error logs on the project server. The only error
around the time the cube build was initiated is this:Component: PCSViews
File: ViewsDrop.cls
Line: -1
Error Number: 0x5
Description: <Description><![CDATA[Error Information: Invalid procedure call
or argument
Additional Information: An error occured processing the following view :-
<ViewsDropData><ProjectData><EntProjectName><![CDATA[TRD 0004-04-01
DOCA.Published]
]></EntProjectName><EntProjectID>36</EntProjectID></ProjectData><OrgGuid>projectserver</OrgGuid><ProjectID>108</ProjectID><BasePath>projectserver</BasePath><TimeStamp>2007-06-08T12:35:26</TimeStamp></ViewsDropData>
]]></Description>I believe this is from using a dash in the project name so I generally
disregard this error.Any ideas on the other errors? We're also seeing Project web access not
updating after a project has been published/updated.
Were there any errors on the database server?
B.
Yeah, or wherever Analysis Services is running... Next step is to test
the profiler...
D
Dave
No errors on the DB server, Analysis Services not reporting errors either.
Steve Sanderlin said:I work with Shane, there are no errors in the logs on the sql server, on
project server there are various errors. Seems to be the same errors that
just repeat:Component: PjMsgHlr
File: C:\Office\devsp\project\WebClient\source\server\pjmsghlr\MsgHandler.cpp
Line: 588
Error Number: 0x8c040017
Description: <Description><![CDATA[Assert Detected. The error code was also
included.]]></Description>Component: PjMsgHlr
File: C:\Office\devsp\project\WebClient\source\server\pjmsghlr\updatedb.cpp
Line: 516
Error Number: 0x8c040017
Description: <Description><![CDATA[Assert Detected. The error code was also
included.]]></Description>
Component: PjMsgHlr
File: C:\Office\devsp\project\WebClient\source\server\pjmsghlr\updatedb.cpp
Line: 2318
Error Number: 0x8c040017
Description: <Description><![CDATA[Assert Detected. The error code was also
included.]]></Description>Component: PjMsgHlr
File: C:\Office\devsp\project\WebClient\source\server\pjmsghlr\updatedb.cpp
Line: 2318
Error Number: 0x8c040017
Description: <Description><![CDATA[Assert Detected. The error code was also
included.]]></Description>Component: PjMsgHlr
File: C:\Office\devsp\project\WebClient\source\server\pjmsghlr\MsgHandler.cpp
Line: 1100
Error Number: 0x8c040017
Description: <Description><![CDATA[Assert Detected. The error code was also
included.]]></Description>These appear often in the error logs on the project server. The only error
around the time the cube build was initiated is this:Component: PCSViews
File: ViewsDrop.cls
Line: -1
Error Number: 0x5
Description: <Description><![CDATA[Error Information: Invalid procedure call
or argument
Additional Information: An error occured processing the following view :-
<ViewsDropData><ProjectData><EntProjectName><![CDATA[TRD 0004-04-01
DOCA.Published]
]></EntProjectName><EntProjectID>36</EntProjectID></ProjectData><OrgGuid>projectserver</OrgGuid><ProjectID>108</ProjectID><BasePath>projectserver</BasePath><TimeStamp>2007-06-08T12:35:26</TimeStamp></ViewsDropData>
]]></Description>I believe this is from using a dash in the project name so I generally
disregard this error.Any ideas on the other errors? We're also seeing Project web access not
updating after a project has been published/updated.
Are there any errors in the application log of the Analysis Services,
SQL Server, or Project Server system?Try attaching the SQL Profiler to your Project Server's DB server...
is there activity going on in the CUBE tables?
Were there any errors on the database server?
B.
Yeah, or wherever Analysis Services is running... Next step is to test
the profiler...
S
Steve Sanderlin
No errors on the DB server, Analysis Services not reporting errors either.
Steve Sanderlin said:On Mon, 11 Jun 2007 11:24:02 -0700, Dave
I work with Shane, there are no errors in the logs on the sql server, on
project server there are various errors. Seems to be the same errors that
just repeat:
Component: PjMsgHlr
File: C:\Office\devsp\project\WebClient\source\server\pjmsghlr\MsgHandler.cpp
Line: 588
Error Number: 0x8c040017
Description: <Description><![CDATA[Assert Detected. The error code was also
included.]]></Description>
Component: PjMsgHlr
File: C:\Office\devsp\project\WebClient\source\server\pjmsghlr\updatedb.cpp
Line: 516
Error Number: 0x8c040017
Description: <Description><![CDATA[Assert Detected. The error code was also
included.]]></Description>
Component: PjMsgHlr
File: C:\Office\devsp\project\WebClient\source\server\pjmsghlr\updatedb.cpp
Line: 2318
Error Number: 0x8c040017
Description: <Description><![CDATA[Assert Detected. The error code was also
included.]]></Description>
Component: PjMsgHlr
File: C:\Office\devsp\project\WebClient\source\server\pjmsghlr\updatedb.cpp
Line: 2318
Error Number: 0x8c040017
Description: <Description><![CDATA[Assert Detected. The error code was also
included.]]></Description>
Component: PjMsgHlr
File: C:\Office\devsp\project\WebClient\source\server\pjmsghlr\MsgHandler.cpp
Line: 1100
Error Number: 0x8c040017
Description: <Description><![CDATA[Assert Detected. The error code was also
included.]]></Description>
These appear often in the error logs on the project server. The only error
around the time the cube build was initiated is this:
Component: PCSViews
File: ViewsDrop.cls
Line: -1
Error Number: 0x5
Description: <Description><![CDATA[Error Information: Invalid procedure call
or argument
Additional Information: An error occured processing the following view :-
<ViewsDropData><ProjectData><EntProjectName><![CDATA[TRD 0004-04-01
DOCA.Published]
]></EntProjectName><EntProjectID>36</EntProjectID></ProjectData><OrgGuid>projectserver</OrgGuid><ProjectID>108</ProjectID><BasePath>projectserver</BasePath><TimeStamp>2007-06-08T12:35:26</TimeStamp></ViewsDropData>
]]></Description>
I believe this is from using a dash in the project name so I generally
disregard this error.
Any ideas on the other errors? We're also seeing Project web access not
updating after a project has been published/updated.
Thanks,
Dave
Are there any errors in the application log of the Analysis Services,
SQL Server, or Project Server system?
Try attaching the SQL Profiler to your Project Server's DB server...
is there activity going on in the CUBE tables?
Were there any errors on the database server?
B.Yeah, or wherever Analysis Services is running... Next step is to test
the profiler...
I have seen instances where special characters in Project or Resource
names will cause the cube not to build... This could be your issue.
Try attaching the Profiler and kicking off the build again, looking
for errors, timeouts, etc.
G
Gary L. Chefetz [MVP]
Dave:
The errors ending in "17" are caused by local resources in the project plans
that do not have their workgroup setting set to "none." Have your PMs change
this value for each local resource and the errors will clear up.
The OLAP cube build likely never started. The typical scenario here is that
the OLAP identity account you use for COM+ has become disabled or had a
password change. Try rerunning COM+ tool to re-establish the identity. First
make sure that the account is active in AD.
--
Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com
The errors ending in "17" are caused by local resources in the project plans
that do not have their workgroup setting set to "none." Have your PMs change
this value for each local resource and the errors will clear up.
The OLAP cube build likely never started. The typical scenario here is that
the OLAP identity account you use for COM+ has become disabled or had a
password change. Try rerunning COM+ tool to re-establish the identity. First
make sure that the account is active in AD.
--
Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com
No errors on the DB server, Analysis Services not reporting errors either.
Steve Sanderlin said:On Mon, 11 Jun 2007 11:24:02 -0700, Dave
I work with Shane, there are no errors in the logs on the sql server,
on
project server there are various errors. Seems to be the same errors
that
just repeat:
Component: PjMsgHlr
File:
C:\Office\devsp\project\WebClient\source\server\pjmsghlr\MsgHandler.cpp
Line: 588
Error Number: 0x8c040017
Description: <Description><![CDATA[Assert Detected. The error code was
also
included.]]></Description>
Component: PjMsgHlr
File:
C:\Office\devsp\project\WebClient\source\server\pjmsghlr\updatedb.cpp
Line: 516
Error Number: 0x8c040017
Description: <Description><![CDATA[Assert Detected. The error code was
also
included.]]></Description>
Component: PjMsgHlr
File:
C:\Office\devsp\project\WebClient\source\server\pjmsghlr\updatedb.cpp
Line: 2318
Error Number: 0x8c040017
Description: <Description><![CDATA[Assert Detected. The error code was
also
included.]]></Description>
Component: PjMsgHlr
File:
C:\Office\devsp\project\WebClient\source\server\pjmsghlr\updatedb.cpp
Line: 2318
Error Number: 0x8c040017
Description: <Description><![CDATA[Assert Detected. The error code was
also
included.]]></Description>
Component: PjMsgHlr
File:
C:\Office\devsp\project\WebClient\source\server\pjmsghlr\MsgHandler.cpp
Line: 1100
Error Number: 0x8c040017
Description: <Description><![CDATA[Assert Detected. The error code was
also
included.]]></Description>
These appear often in the error logs on the project server. The only
error
around the time the cube build was initiated is this:
Component: PCSViews
File: ViewsDrop.cls
Line: -1
Error Number: 0x5
Description: <Description><![CDATA[Error Information: Invalid
procedure call
or argument
Additional Information: An error occured processing the following view
:-
<ViewsDropData><ProjectData><EntProjectName><![CDATA[TRD 0004-04-01
DOCA.Published]
]></EntProjectName><EntProjectID>36</EntProjectID></ProjectData><OrgGuid>projectserver</OrgGuid><ProjectID>108</ProjectID><BasePath>projectserver</BasePath><TimeStamp>2007-06-08T12:35:26</TimeStamp></ViewsDropData>
]]></Description>
I believe this is from using a dash in the project name so I generally
disregard this error.
Any ideas on the other errors? We're also seeing Project web access
not
updating after a project has been published/updated.
Thanks,
Dave
Are there any errors in the application log of the Analysis
Services,
SQL Server, or Project Server system?
Try attaching the SQL Profiler to your Project Server's DB server...
is there activity going on in the CUBE tables?
Were there any errors on the database server?
B.
Yeah, or wherever Analysis Services is running... Next step is to test
the profiler...
D
Dave
Gary,
Thanks for the info on these errors,we will check with the PMs and see if
they are using local resources.
Any idea what the following codes would indicate?
Component: PjBusObj
File:
C:\Office\devsp\project\WebClient\source\server\pjbusobj\PjTaskBusObj.cpp
Line: 3557
Error Number: 0x8c04004b
Description: <Description><![CDATA[Assert Detected for Virtual Root
'projectserver'. The error code was also included.]]></Description>
Component: PjQuery
File:
C:\Office\devsp\project\WebClient\source\server\pjquery\PjGenericQuery.cpp
Line: 881
Error Number: 0x80004005
Description: <Description><![CDATA[Assert Detected for Virtual Root
'projectserver'. The error code was also included.]]></Description>
I mostly see 0x80004005, 0x8c040012, 0x80040e14 and 0x8c040017 in the error
logs on the project server.
I will check the service accounts and make sure they aren't locked/password
expired.
Thanks for the info on these errors,we will check with the PMs and see if
they are using local resources.
Any idea what the following codes would indicate?
Component: PjBusObj
File:
C:\Office\devsp\project\WebClient\source\server\pjbusobj\PjTaskBusObj.cpp
Line: 3557
Error Number: 0x8c04004b
Description: <Description><![CDATA[Assert Detected for Virtual Root
'projectserver'. The error code was also included.]]></Description>
Component: PjQuery
File:
C:\Office\devsp\project\WebClient\source\server\pjquery\PjGenericQuery.cpp
Line: 881
Error Number: 0x80004005
Description: <Description><![CDATA[Assert Detected for Virtual Root
'projectserver'. The error code was also included.]]></Description>
I mostly see 0x80004005, 0x8c040012, 0x80040e14 and 0x8c040017 in the error
logs on the project server.
I will check the service accounts and make sure they aren't locked/password
expired.
S
Steve Sanderlin
Gary,
Thanks for the info on these errors,we will check with the PMs and see if
they are using local resources.
Any idea what the following codes would indicate?
Component: PjBusObj
File:
C:\Office\devsp\project\WebClient\source\server\pjbusobj\PjTaskBusObj.cpp
Line: 3557
Error Number: 0x8c04004b
Description: <Description><![CDATA[Assert Detected for Virtual Root
'projectserver'. The error code was also included.]]></Description>
Component: PjQuery
File:
C:\Office\devsp\project\WebClient\source\server\pjquery\PjGenericQuery.cpp
Line: 881
Error Number: 0x80004005
Description: <Description><![CDATA[Assert Detected for Virtual Root
'projectserver'. The error code was also included.]]></Description>
I mostly see 0x80004005, 0x8c040012, 0x80040e14 and 0x8c040017 in the error
logs on the project server.
I will check the service accounts and make sure they aren't locked/password
expired.
Gary L. Chefetz said:Dave:The errors ending in "17" are caused by local resources in the project plans
that do not have their workgroup setting set to "none." Have your PMs change
this value for each local resource and the errors will clear up.
I would echo Gary's advice that you re-establish the COM+ identity and
make sure the account did not have its password change, expire, or the
account was disabled.
As for the other errors:
0x8c040012 indicates that a particular resource is inactive... the
only info I can find on this is from 2002 - http://support.microsoft.com/kb/840574
0x80004005 shows when Viewdrop permissions are incorrect -
http://support.microsoft.com/kb/328249
0x80040e14 indicates that a timestamp in the MSP_WEB_PROJECTS table is
incorrect - http://support.microsoft.com/kb/889500
0x8C040017 indicates that a local resource is in use and an account is
attempting to be created on the project server by a user that does not
have permission to do so - http://support.microsoft.com/kb/843088
C
Crook
Hi,
Bottom Line: for us cube build failures are typically caused by out of
memory conditions resulting from a memory leak in the Project Server Views
Notification Service. This problem is remedied by restarting the Project
Server Views Notification Service using the following instructions pasted
from http://support.microsoft.com/kb/899482/en-us:
WORKAROUND
To work around this issue, stop and then restart the Project Server Views
Notification Service on each server that is running the Project Server Views
Notification Service. The files that are currently in the ViewDrop folder
will be processed when the service is restarted.
To stop and then restart the Project Server Views Notification Service,
follow these steps: 1. Click Start, point to Administrative Tools, and then
click Services.
2. Right-click Project Server Views Notification Service, and then
click Stop.
3. Right-click Project Server Views Notification Service, and then
click Start.
4. Repeat these steps two times to make sure that the service is
restarted.
Note If you suspect that the Project Server Views Notification Service is
not responding or that the Project Server Views Notification Service is
processing a task, run a task-killing tool before you restart the Project
Server Views Notification Service.
I check the View Drop folder before restarting the service to ensure there
are no jobs in process.
Resetting the Project Server Views Notification Service has fixed our cube
build problem in all instances except 2. In those instances, I had to
delete the cubes and then let PS03 rebuild them from scratch. In those
cases, I received the following error, "The cube scheduled to be built on
month/day/year at 3:00 AM failed. (-2147221492) Unable to save object. The
object has been modified by another application."
Now, having said all that, the diagnoses provided are accurate, and we have
been subject to them all, especially 0x8C040017 - Local resource cannot be
created. For us these problems led to cube build failure by causing memory
leaks on the server.
BTW, our fix for the -17 errors is to ask our PMs to set the workgroup for
local resources to "none". The workgroup is populated with "default" when
the local resource is created. (hat tip to the MS Project Experts folks, I
got the fix for -17 errors from them in another thread on this list).
I really feel for you in this.
Hope this helps,
Crook
Bottom Line: for us cube build failures are typically caused by out of
memory conditions resulting from a memory leak in the Project Server Views
Notification Service. This problem is remedied by restarting the Project
Server Views Notification Service using the following instructions pasted
from http://support.microsoft.com/kb/899482/en-us:
WORKAROUND
To work around this issue, stop and then restart the Project Server Views
Notification Service on each server that is running the Project Server Views
Notification Service. The files that are currently in the ViewDrop folder
will be processed when the service is restarted.
To stop and then restart the Project Server Views Notification Service,
follow these steps: 1. Click Start, point to Administrative Tools, and then
click Services.
2. Right-click Project Server Views Notification Service, and then
click Stop.
3. Right-click Project Server Views Notification Service, and then
click Start.
4. Repeat these steps two times to make sure that the service is
restarted.
Note If you suspect that the Project Server Views Notification Service is
not responding or that the Project Server Views Notification Service is
processing a task, run a task-killing tool before you restart the Project
Server Views Notification Service.
I check the View Drop folder before restarting the service to ensure there
are no jobs in process.
Resetting the Project Server Views Notification Service has fixed our cube
build problem in all instances except 2. In those instances, I had to
delete the cubes and then let PS03 rebuild them from scratch. In those
cases, I received the following error, "The cube scheduled to be built on
month/day/year at 3:00 AM failed. (-2147221492) Unable to save object. The
object has been modified by another application."
Now, having said all that, the diagnoses provided are accurate, and we have
been subject to them all, especially 0x8C040017 - Local resource cannot be
created. For us these problems led to cube build failure by causing memory
leaks on the server.
BTW, our fix for the -17 errors is to ask our PMs to set the workgroup for
local resources to "none". The workgroup is populated with "default" when
the local resource is created. (hat tip to the MS Project Experts folks, I
got the fix for -17 errors from them in another thread on this list).
I really feel for you in this.
Hope this helps,
Crook
Steve Sanderlin said:Gary,
Thanks for the info on these errors,we will check with the PMs and see if
they are using local resources.
Any idea what the following codes would indicate?
Component: PjBusObj
File:
C:\Office\devsp\project\WebClient\source\server\pjbusobj\PjTaskBusObj.cpp
Line: 3557
Error Number: 0x8c04004b
Description: <Description><![CDATA[Assert Detected for Virtual Root
'projectserver'. The error code was also included.]]></Description>
Component: PjQuery
File:
C:\Office\devsp\project\WebClient\source\server\pjquery\PjGenericQuery.cpp
Line: 881
Error Number: 0x80004005
Description: <Description><![CDATA[Assert Detected for Virtual Root
'projectserver'. The error code was also included.]]></Description>
I mostly see 0x80004005, 0x8c040012, 0x80040e14 and 0x8c040017 in the
error
logs on the project server.
I will check the service accounts and make sure they aren't
locked/password
expired.
Gary L. Chefetz said:Dave:The errors ending in "17" are caused by local resources in the project
plans
that do not have their workgroup setting set to "none." Have your PMs
change
this value for each local resource and the errors will clear up.
I would echo Gary's advice that you re-establish the COM+ identity and
make sure the account did not have its password change, expire, or the
account was disabled.
As for the other errors:
0x8c040012 indicates that a particular resource is inactive... the
only info I can find on this is from 2002 -
http://support.microsoft.com/kb/840574
0x80004005 shows when Viewdrop permissions are incorrect -
http://support.microsoft.com/kb/328249
0x80040e14 indicates that a timestamp in the MSP_WEB_PROJECTS table is
incorrect - http://support.microsoft.com/kb/889500
0x8C040017 indicates that a local resource is in use and an account is
attempting to be created on the project server by a user that does not
have permission to do so - http://support.microsoft.com/kb/843088
G
Gary L. Chefetz [MVP]
Steve:
Excellent reply. I'd add that the e14 errors also appear when duplicate
assignments are in the database and the 4005 errors occur not only for view
drop issues, but other authentication problems as well.
--
Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com
Excellent reply. I'd add that the e14 errors also appear when duplicate
assignments are in the database and the 4005 errors occur not only for view
drop issues, but other authentication problems as well.
--
Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com
Steve Sanderlin said:Gary,
Thanks for the info on these errors,we will check with the PMs and see if
they are using local resources.
Any idea what the following codes would indicate?
Component: PjBusObj
File:
C:\Office\devsp\project\WebClient\source\server\pjbusobj\PjTaskBusObj.cpp
Line: 3557
Error Number: 0x8c04004b
Description: <Description><![CDATA[Assert Detected for Virtual Root
'projectserver'. The error code was also included.]]></Description>
Component: PjQuery
File:
C:\Office\devsp\project\WebClient\source\server\pjquery\PjGenericQuery.cpp
Line: 881
Error Number: 0x80004005
Description: <Description><![CDATA[Assert Detected for Virtual Root
'projectserver'. The error code was also included.]]></Description>
I mostly see 0x80004005, 0x8c040012, 0x80040e14 and 0x8c040017 in the
error
logs on the project server.
I will check the service accounts and make sure they aren't
locked/password
expired.
Gary L. Chefetz said:Dave:The errors ending in "17" are caused by local resources in the project
plans
that do not have their workgroup setting set to "none." Have your PMs
change
this value for each local resource and the errors will clear up.
I would echo Gary's advice that you re-establish the COM+ identity and
make sure the account did not have its password change, expire, or the
account was disabled.
As for the other errors:
0x8c040012 indicates that a particular resource is inactive... the
only info I can find on this is from 2002 -
http://support.microsoft.com/kb/840574
0x80004005 shows when Viewdrop permissions are incorrect -
http://support.microsoft.com/kb/328249
0x80040e14 indicates that a timestamp in the MSP_WEB_PROJECTS table is
incorrect - http://support.microsoft.com/kb/889500
0x8C040017 indicates that a local resource is in use and an account is
attempting to be created on the project server by a user that does not
have permission to do so - http://support.microsoft.com/kb/843088