J
Jennpenn07
Hi,
I have asked this question before and the responses I got were very helpful
and actualy resolved a different spooler error. However I am still getting
this one; SYSTEM ERROR (0x80004005).
I have two PMs working on seperate projects to which both have reported this
error. It appears when they accept time, save, or publish their projects. The
error doesn't prevent them from accepting time or saving, and it's occurance
is not consistant. Its very random.
I have ensured that there are no local resources on the project and that all
of the inactive resource's workgroup field were set to none. Thanks Chak that
resolved my 800040017 error.
Iv'e tried to apply the fix described in this microsoft article about the
FQDN. http://support.microsoft.com/kb/897771, but no luck
During my last post i was told that it could be caused by server
performance. therefore i rescheduled the OLAP update to begin earlier in the
am (12am) in order to make sure its not running during our operation hours.
For a minute there I thought the errors had stopped, but I was wrong. this
erorr is only appearing in the spooler, there are no errors in the event
viewer for client or server. Any thoughts????
I have asked this question before and the responses I got were very helpful
and actualy resolved a different spooler error. However I am still getting
this one; SYSTEM ERROR (0x80004005).
I have two PMs working on seperate projects to which both have reported this
error. It appears when they accept time, save, or publish their projects. The
error doesn't prevent them from accepting time or saving, and it's occurance
is not consistant. Its very random.
I have ensured that there are no local resources on the project and that all
of the inactive resource's workgroup field were set to none. Thanks Chak that
resolved my 800040017 error.
Iv'e tried to apply the fix described in this microsoft article about the
FQDN. http://support.microsoft.com/kb/897771, but no luck
During my last post i was told that it could be caused by server
performance. therefore i rescheduled the OLAP update to begin earlier in the
am (12am) in order to make sure its not running during our operation hours.
For a minute there I thought the errors had stopped, but I was wrong. this
erorr is only appearing in the spooler, there are no errors in the event
viewer for client or server. Any thoughts????