SP2a errors remain

[J Burford Fields]

It looks like SP2a took. I'm seeing build 11.2.2005.1801.15 in PWA.

The first indication I had was that a user had to accept a license
agreement and download components. My own download of components
failed due to browser security settings until I fired up Project Pro
and accepted the server certificates (something I have to do each time
I start Project Pro).

The bad news is that the errors I had hoped to see go away are still
there.

When I try to remove the inactive flag from a resource and save it, I
get...
"Project Server was unable to process the request. An invalid node
name parameter was specified..."

When I open one file, I get: "An exception occurred in project server.
Project server encoutnered a problem with this error code: 9573

Then the message about out of sync actuals and "Do you want to
overwrite from PWA." If I say yes, I get the Problem Restart screen.
I sent the problem to Microsoft and am back at a screen for more
information describing upgrades. I have a call into the techs to make
sure my Office configuration has the latest patches and updates. Was
this SP suppose to be applied against clients as well???

Sorry for the core dump, but I think that's all the issues so far.

 

[Gary L. Chefetz [MVP]]

JB:

You should apply SP2 for the client at the same time, although Microsoft
doesn't state that this is an absolute requirement. IMO, it is. The fact
that you see the correct build number means that msi file was correctly
applied. It doesn't verify that your SQL upgrade ran correctly, for which
all indicators suggest that it didn't.

 

[J Burford Fields]

Thanks, Gary. I would be insane supporting this if it weren't for you.
I'll continue to prosecute this. -- J

 

[J Burford Fields]

Gary,

You mean that Office XP SP2 should be applied, not that we should apply
the Project Professional service pack against the client, right?

J

 

[Gary L. Chefetz [MVP]]

JB:

I meant that when you apply SP2a for Project Server, you should be applying
SP2 for the Project client. Nothing in my previous posts talks about Win XP.

 

[J Burford Fields]

Thanks. I was looking for 2a for the client.

JB:

I meant that when you apply SP2a for Project Server, you should be applying
SP2 for the Project client. Nothing in my previous posts talks about Win XP.

 

[Gary L. Chefetz [MVP]]

That one didn't need the "a" designation as it wasn't recalled.<g>

 

[J Burford Fields]

Ha!

I was beginning to think anything without the 'a' was suspect.

All the troubles seem to have gone away except for error code 9573, at
this point.

Life is suddenly much more promising. I don't want to count how many
weeks I've come to work wondering if there would still be employment at
the end of the week!

J

 

[J Burford Fields]

Short lived pleasure. One of the customer project managers who had not
yet updated project professional with sp2, ran into errors and
terminated the program. It now appears that we have tasks in PWA that
no longer appear in Project Professional. Also, some new database
error messages in the log. People are charging time to tasks over
which I no longer have a lot of control! The good news may be that the
project with those errors ends soon.