SP2a produces script errors

[Jason]

Hi all

After applying Project Server 2003 SP2a on two seperate Project 2003
servers, I get the following script errors after logging in as administrator
and downloading the new activex controls:

Microsoft JScript runtime error '800a138f'

'null' is null or not an object

/ProjectServer/Shell/Shell.asp, line 529

I have two Project application servers on virtual server instances, Windows
2003 SP0 and SP1 respectively, and the database is installed on a remote SQL
2000 server (which has Windows Server 2003 std with SP0). The same error
happens if I do this in a web browser locally on the project application
server, or remote on an XP or 2000 pro client.

Any idea why this would happen? Is anyone having the same problems as I am?

 

[tsheridan]

Jason,
I receive exactly the same error at the same spot during the login.
All components installed on one server. Windows Server 2003 SP1, SQL
2000 SP4, Analysis Services SP4, WSS SP2, & Project Server 2003 SP2a.

Any new info on this?
Thanks,

 

[tsheridan]

Fell prey to the ol' RTFM.
The fix was to follow the darn directions! Ran the cmd file under sa
on the ProjectServer database and it straightened everything out.
Has it right there on the download page
http://www.microsoft.com/downloads/...fd-2965-4faf-bd48-3cbcc5031e46&DisplayLang=en

Instructions
Upgrade the database
It is advised that you back up your database before applying any
updates. If you do not update your database, you may experience errors
when using Project Server 2003. For more information, see the Microsoft
Knowledge Base article (903093): You receive error messages when you
publish a plan or an assignment when you work with Project Server 2002
or with Project Server 2003.

Note: You must follow the steps below for each Microsoft SQL Server and
database.
Download the SQL patch, ProjectServer2003-KB887621-SQLFile-ENU.exe or
equivalent language from the bottom of this page.
Double-click on the file to extract the files to a temporary folder.
To apply the files, Osql.exe is required in the same directory from
where Upgdb112.cmd is run or in the system path. If you are running
Upgdb112.cmd directly on the machine where the database resides, this
file should already be present. It is also available on the Project
Server 2003 CD in the \support\database folder.
Run Upgdb112.cmd against the Project Server 2003 database. If the
database is a partitioned database, run the script against each of the
Project Server 2003 databases. Run Upgdb112.cmd from a command line
with the following parameters. To run from a command line, click Start

Run and type cmd in the dialog box and click OK.

Upgdb112.cmd <sql server name> <database name> <login> <password>

OR if using Microsoft Windows authentication to SQL Server as the
currently logged in user:

Upgdb112.cmd <sql server name> <database name>

 

[Jason]

Yes indeed, the fix was to follow the directions. Btw, if you come across
this article and have the same problem, it means that you haven't run the
update script for the database (you must run the script and the actual
service pack to complete the upgrade).