Spooler (0x80004005) ERROR SYSTEM

[Newbie]

Hello,

Project Server 2003
While I tried to publish my first assignements :
Collaborate / Publish / All information
I got the message : (0x80004005) ERROR SYSTEM

What's wrong ?
Thanks for help !

Newbie

 

[Sara - EPM]

Hi.

Your error could be a result of many things.

Do you have local resources in the project? Are project managers allowed to
publish with local resources? When publishing, can project managers create
PWA accounts?

If you look on your admin page in PWA, check your settings for the above
questions. I had this problem a while back because my pms do not have the
rights to create PWA accounts and when I publish projects with local
resources, the spooler was trying to create the account, hence the error.

Bottom line, check your admin page for what's on or off. Most likely, your
solution is where in permissions.

Sara

 

[Dev]

To add to Newbie's comment there is also a possibility that your client may
not be connected to the Project Server. You can check that out by opening
your project plan, click collaborate then click on collaboration option and
see if the Project Server URL is typed in correctly (click on the Test
Connection Button right next the URL box).

Let me know if you need more details on this.
Dev

 

[Newbie]

Hello Dev,

Thanks for your answer.
Yes, I checked the server URL and it is valid. So the problem is somewhere
else.
Thanks again,

Newbie

 

[Newbie]

Hello Sara,
Thanks for the detailed explanations.
But no, I have not any local resource in my projet. Anyway, where would be
the place in the Admin page where we could allow the project managers to
publish with local resources ?
Thanks for help,

Newbie

 

[Matthew Dunphy]

Hello Dev,

Thanks for your answer.
Yes, I checked the server URL and it is valid. So the problem is somewhere
else.
Thanks again,

Newbie

client option

 

[Matthew Dunphy]

I've been getting this error more and more lately. It's something that
I see has been addressed in some interim MS Fix that you specifically
have to request, but I'm really hoping a service pack will take care of
this incessant error, as it really screws things up. I can't seem to
nail down the problem. In one instance, the project was brand new, and
I simply created a copy of the project with a slightly different name
and everything was okay.

Now I've got two tasks in two separate projects that cannot be updated
because they both give the 80004005 error, and it's a bit maddening. I
have looked high and low for some simple solution to this before, now
that it's cropped up again I'm hoping someone has posted something
recently, but this is starting to get ridiculous.

 

[Denis in Brisbane]

Matthew
I was getting the 0x80004005 on a brand new database.
I discovered that even though I'm already running my PS2003 SP1, I still
need to run the upgdb111.exe referred to in the doco for SP1. Once I did
that the problem went away. Maybe that's your problem.
Denis

 

[Marcelo Margutti]

Hi Newbie,

This issue can occur if you try to use a Fully Qualified Domain Name (FQDM)
to connect to the Microsoft Office Project Server 2003 Web site. For example,
you use http://projects.projsvr2003.domain.com instead of
http://projsvr2003/ProjectServer

OR

Delete the resources from the assignments (tasks) and reassign them back.


Marcelo Margutti