Script Error after SP2a install

[Chris T]

We have three isntance of Project Sever on our Pilot Server (one Dev, one
training and one Pre-prod) - they have a common code-base, but seperate
databases.

When SP2A was installed, all was well for our Dev instance, but the other
two both have script errors when PWA is accessed:

Microsoft JScript runtime error '800a138f'

'null' is null or not an object

/ProjectServer/Shell/Shell.asp, line 529

No errors came up in the SP2A install and the database is fine - MSP
connects fine and functions perfectly, as does the Dev instance that went in
first.

The only things different (that I am aware of!) about the two instances that
don't work are:
they aren't on the default port number, we set them up on the same server
but different ports
they have been edited using editsite since being first created

Any ideas?

 

[Marc S.]

Chris,

Although I'm having difficulties following your description on the
architecture the error sounds familiar to me. I think this is the message you
get when you installed SP2(a) for Project Server and the WSS template but not
yet for the database. Once you run the database update script to SP2 it
should work again.

Let us know, hope this helps...

Marc

 

[Chris T]

Marc - I don't think you have really got the gist of the issue actually.

I can confirm that the SP2A has been applied in full, and in the correct
order (i.e. DB first). Further, 2 PWA instances have errors, 1 is fine - they
all share the same base ASP code pool, so therefore, the code is the same in
all 3 PWA instances

regs, Chris

 

[Gary L. Chefetz [MVP]]

Chris:

Are you certain that the SQL script was run three times, once for each
database?