Spooler Error 0x80004005 Reprise

[jwn]

I've been encountering the same old error many others have encountered. The
ubiquitous System Error 0x80004005. I've seen every post here, and every
response... I'm still looking for an answer. Running MSProject Server 2003
SP1 and I've applied the Hotfix.

I attempt to create a very simple project plan, add tasks, assign resources
(from the Enterprise Pool), then save and publish. That's when the spooler
jumps up and says "no way"... "not today". The project appears in Project
Center in PAW, but selecting that project I get the "no information to
display in this view" page. Sound familiar?

In the meantime the spooler is screamin' at me. But it isn't very helpful.
That's for sure (btw... why even have the silly spooler error window when it
doesn't tell you much of anything?)

The Spooler Message Type is: "Publish New and Changed Assignments"

From the Server's Event Log are the following (continual repeat of 1 warning
and 3 errors):

Event Type: Warning
Event Source: Microsoft Project Server Tracing Eventlog Provider
Event Category: None
Event ID: 1
Date: 9/28/2005
Time: 12:35:56 PM
User: NT AUTHORITY\LOCAL SERVICE
Computer: xxxxxxx
Description:
Component: ConnectSvc
File:
C:\Office\dev\project\WebClient\source\server\connectorsvc\connectorsvc.cpp
Line: 777
Description: <Description><![CDATA[Restarting listener for the connector
configured by 'SOFTWARE\Microsoft\Office\11.0\MS
Project\Services\Configuration\Connector\ProjectServer1']]></Description>
---------------------------------------------------------------
Event Type: Error
Event Source: MSSOAP
Event Category: Generic
Event ID: 16
Date: 9/28/2005
Time: 12:35:56 PM
User: N/A
Computer: xxxxxxx
Description:
Soap error: XML Parser failed at linenumber 0, lineposition 0, reason is:
Access is denied.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
---------------------------------------------------------------
Event Type: Error
Event Source: MSSOAP
Event Category: Generic
Event ID: 16
Date: 9/28/2005
Time: 12:35:56 PM
User: N/A
Computer: xxxxxxx
Description:
Soap error: Loading of the WSDL file failed.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
---------------------------------------------------------------
Event Type: Error
Event Source: MSSOAP
Event Category: Client
Event ID: 16
Date: 9/28/2005
Time: 12:35:56 PM
User: N/A
Computer: xxxxxxx
Description:
Soap error: One of the parameters supplied is invalid..

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
---------------------------------------------------------------

I don't really understand what the error messages are trying to say. They
(the 3 errors) refer to MSSOAP, XML and parameters not being valid. Access
denied?

What the heck?

So, please Microsoft... c'mon... we've spent tens of thousands of dollars on
WinServer, SharePoint, SQL Server and Project Server only to come to a
roadblock at the (seemingly) end of my quest. Can't you guys come up with an
answer to this question that keeps getting asked over and over?

Frustration level is gettin' pretty high out here in computerland.

I sure hope somebody answers this pretty quick... or better yet, give me a
call (and don't try to charge me $99 either... man, that's lame).

 

[Brian K - Project MVP]

I've been encountering the same old error many others have encountered. The
ubiquitous System Error 0x80004005. I've seen every post here, and every
response... I'm still looking for an answer. Running MSProject Server 2003
SP1 and I've applied the Hotfix.

I attempt to create a very simple project plan, add tasks, assign resources
(from the Enterprise Pool), then save and publish. That's when the spooler
jumps up and says "no way"... "not today". The project appears in Project
Center in PAW, but selecting that project I get the "no information to
display in this view" page. Sound familiar?

In the meantime the spooler is screamin' at me. But it isn't very helpful.
That's for sure (btw... why even have the silly spooler error window when
it
doesn't tell you much of anything?)

The Spooler Message Type is: "Publish New and Changed Assignments"

From the Server's Event Log are the following (continual repeat of 1
warning
and 3 errors):

Event Type: Warning
Event Source: Microsoft Project Server Tracing Eventlog Provider
Event Category: None
Event ID: 1
Date: 9/28/2005
Time: 12:35:56 PM
User: NT AUTHORITY\LOCAL SERVICE
Computer: xxxxxxx
Description:
Component: ConnectSvc
File:
C:\Office\dev\project\WebClient\source\server\connectorsvc\connectorsvc.cpp
Line: 777
Description: <Description><![CDATA[Restarting listener for the connector
configured by 'SOFTWARE\Microsoft\Office\11.0\MS
Project\Services\Configuration\Connector\ProjectServer1']]></Description>
---------------------------------------------------------------
Event Type: Error
Event Source: MSSOAP
Event Category: Generic
Event ID: 16
Date: 9/28/2005
Time: 12:35:56 PM
User: N/A
Computer: xxxxxxx
Description:
Soap error: XML Parser failed at linenumber 0, lineposition 0, reason is:
Access is denied.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
---------------------------------------------------------------
Event Type: Error
Event Source: MSSOAP
Event Category: Generic
Event ID: 16
Date: 9/28/2005
Time: 12:35:56 PM
User: N/A
Computer: xxxxxxx
Description:
Soap error: Loading of the WSDL file failed.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
---------------------------------------------------------------
Event Type: Error
Event Source: MSSOAP
Event Category: Client
Event ID: 16
Date: 9/28/2005
Time: 12:35:56 PM
User: N/A
Computer: xxxxxxx
Description:
Soap error: One of the parameters supplied is invalid..

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
---------------------------------------------------------------

I don't really understand what the error messages are trying to say. They
(the 3 errors) refer to MSSOAP, XML and parameters not being valid. Access
denied?

What the heck?

So, please Microsoft... c'mon... we've spent tens of thousands of dollars
on
WinServer, SharePoint, SQL Server and Project Server only to come to a
roadblock at the (seemingly) end of my quest. Can't you guys come up with
an
answer to this question that keeps getting asked over and over?

Frustration level is gettin' pretty high out here in computerland.

I sure hope somebody answers this pretty quick... or better yet, give me a
call (and don't try to charge me $99 either... man, that's lame).

I know that SP2 just released and specifically addresses this spooler error.

you can get it at http://www.microsoft.com/downloads

 

[jwn]

Thanks Brian. I got it yesterday and am in the process of dealing with both
the server and Project Pro versions.

And thanks for letting me vent. If the problem doesn't go away though,
prepare for another! ;^)

 

[Brian K - Project MVP]

Thanks Brian. I got it yesterday and am in the process of dealing with both
the server and Project Pro versions.

And thanks for letting me vent. If the problem doesn't go away though,
prepare for another! ;^)

Glad to see it moving forward.

And I did not 'let' you vent. You did all that before I came on.

Just be careful with too much of it. People tend to want to start to
ignore those that have too many "loud" things to say.

 

[jwn]

Well, sure, but after months of this stuff, just couldn't help myself.

In the meantime: I've installed SP2 to Project Server (2003) and to my
Project Pro and there's a problem. Both machines cannot continue to the PAW
as before. Attempting to navigate to the "http://servername/projectserver"
generates this on my PC:

Microsoft JScript runtime error '800a138f'

'null' is null or not an object

/ProjectServer/Shell/Shell.asp, line 529

Same sort of error appears in the browser on the server itself (except its
pointing to an Admin folder).

Now what?

 

[Gaurav Wason]

I did received the same error
'null' is null or not an object

/ProjectServer/Shell/Shell.asp, line 529

I had to reinstall SP2 on my database and restart the machine that did
solved my error. You can give it a try.

 

[jwn]

Thanks Gaurav.

I've rebooted both the server and my PC. Same problem (different folder
depending on the machine).

I'll try re-doing the SP (all 4 upgrades: i.e. Project Server, WSS, SQL and
Project Pro)

 

[jwn]

Can't "redo" or reapply the patches. I get the message (from both machines):

"This update has already been applied or is included in an update that has
already been applied."

Both machines were rebooted twice (just for the effect I guess).

So, if I can't go forward, and I can't go backwards (now), does anybody have
any more ideas?

 

[Gaurav Wason]

Just re-install the SQL sp2.

I did tried to re-install again and it did allowed me to re-install. Give it
a try.

 

[jwn]

Okay... not much happened. A command window blimped on then back off. Is
there supposed to more of a "light show" than that?

EXACTLY, what do you do to "reinstall" the SP2 to SQL? I double-click
"upgdb112.cmd" (in its folder location on the server) and then the CMD window
momentarily opens then immediately closes. That's all I see.

 

[Kevin Watson]

You need run the command from a command window where you have both the
upgdb112.cmd and the Osql.exe located in the same directory. See microsoft
directions for installing the service pack. Its spelled out there.

 

[jwn]

Yeah... that's exactly what I've done. (I have osql.exe in the same folder as
upgdb112.cmd) Refer to my previous message (above) as to what I don't see.

Is there anybody here who works for Microsoft? Specifically on Project
Server? Can't you call me direct? Can I call you? (without having to pay
those ridiculous prices after having paid over 10 grand for licences and
software, etc.)

206.607.5400 x5437 (I don't care that my number's publicly listed
here... I need some help.)

 

[Brian K - Project MVP]

Yeah... that's exactly what I've done. (I have osql.exe in the same folder
as
upgdb112.cmd) Refer to my previous message (above) as to what I don't
see.

Open PWA and hover over the Help menu. It will give you a tool tip with
some info including the last DB version. What number do you see there when
you do this?

 

[Gary L. Chefetz [MVP]]

JWN:

Did you run this at a C> prompt? Gurav is correct in advising you that
double clicking on cmd file does nothing. You must supply the proper command
line string including the destination server, database name, logon account
and password to run the command.

 

[jwn]

Hi Brian,

I tried to email you directly but no response (you may be done for the day).

I'm not 100% sure what you mean by "open PWA"... to me, that's where my
problem is. Trying to navigate to my "//server/projectserver" gives me this
error message:

Microsoft JScript runtime error '800a138f'
'null' is null or not an object
/ProjectServer/Shell/Shell.asp, line 529

Unless I'm missing something, I can't get to there from here.

 

[Brian K - Project MVP]

Hi Brian,

I tried to email you directly but no response (you may be done for the
day).

I think you really need to read the install instructions completely. you
posted here that you double clicked the cmd file. That is not how you run
that file. Doing so is the same as not running it at all. It must be run
from a command prompt with several parameters supplied. I think this is
the problem.

 

[jwn]

*** SOLUTION FOUND ***

Thanks to all who contributed here. My problem is solved, Project Server is
indeed back, up and running. I no longer have the spooler errors, and
resources do, in fact, publish to the server.

Did you run this at a C> prompt? Gurav is correct in advising you that
double clicking on cmd file does nothing. You must supply the proper command
line string including the destination server, database name, logon account
and password to run the command.

The short answer (for awhile) was "No". I wasn't "running" the .cmd file at
the C> prompt. That's the trick. So, for anybody who comes across this thread
in the future (and I'm sure there'll be some), when you get the Service Pack,
run the SQL patch from INSIDE a command window.

Here's what I finally did: ON THE SERVER RUNNING SQL SERVER, unzip the
upgdb112.cmd file (and other SQL patch files) into a temp directory (say:
C:\temp). I also copied the osql.exe into that same location.

Open a command window (i.e. Start/Run/"cmd"). Navigate to the above
directory (i.e. C:\temp). At the prompt type: upgdb112.cmd servername
projectDBname (supplying your specific server's name and SQL database name).

You can add a username and password (if you choose), but if you logged on to
your server with an account having appropriate rights, you can leave off
those parameters.

After specifying the command, press Enter. In my case, the command file ran
for about ten minutes (maybe a little less). Tons and tons of numbers, ">"
characters and messages fly by. Be patient, let it run, and when it's done
messages will inform you the upgrade is completed.

Following this patch process, run the other patches (i.e. apply SP2 to
Project Server and WSS).

All of this was accomplished with the existing projects still within the SQL
database. No harm was done to them. The resources could then be immediately
published via Project Pro and viewed in PWA.

Again, thanks to all for your perseverance and help. I will give credit
where credit is due. Thanks again.

 

[Nico Oosthuysen]

Heya jwn,

Just a quick note from my side and to be fair to everyone else here and
indeed MS themselves - MS do indeed provide extensive and complete
instructions for installing this service pack onto a project server
system at
http://www.microsoft.com/downloads/...FD-2965-4FAF-BD48-3CBCC5031E46&displaylang=en.


I have to admit also that the tone of your initial messages seemed to
suggest that the people active in these groups are somehow responsible
for the problems that you have been experiencing. The fact of the
matter is that these are public groups that are not staffed by MS
personnel, but indeed by volunteers who have experience with project
server and related technologies.

It might bode well to keep this in mind next time you request for
assistance

Nico