Error installing SP1 on Project Server 2003

[Mark]

When attempting to apply SP1 to Project Server 2003 I get "Update cannot be
applied."

I found that there is a log that gives some errors but it did not really
help. Anybody else have this problem?

first log

Starting the log on 11/12/2004 at 14:07:43...
Loading the resource .dll...
Reading the settings...
The settings are:
IsNormalUpdate=1
AdminUsesShortFilenames=1
AdminPath=""
MessageTitle="Microsoft Office Project Server 2003 Service Pack 1"
CopyFilesToRerun=1
ShowSuccessDialog=1
RebootInQuietMode=0
RunSetupWatson=1
RequireAllPatchesNeeded=0
RequireAllProductsAtMinVersion=0
MinProductVersion=""
MinMsiVersion="2.0"
UpgradeMsi=1
MsiUpgradeURL="http://go.microsoft.com/fwlink/?LinkId=20610"
OHotfixLogLevel="v"
MsiLogLevel="v"
OHotfixUILevel="n"
MsiUILevel="n"
FeatureToCheck=""
Making sure only this instance of the bootstrapper is running...
Making sure the environment is okay for patching...
Getting the patches...
Getting the products to patch...
Seeing if patch
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\IXP000.TMP\ProjectServer2003-KB837241-FullFile-ENU.msp is needed...
Product {91320409-6000-11D3-8CFE-0150048383C9}: Not installed.
Cannot patch.
Product {90320409-6000-11D3-8CFE-0150048383C9} Microsoft Office
Project Server 2003 Version 11.0.5614.0: Needs patch.
Applying the patches...
Applying patches to product {90320409-6000-11D3-8CFE-0150048383C9} Microsoft
Office Project Server 2003...
Applying patch
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\IXP000.TMP\ProjectServer2003-KB837241-FullFile-ENU.msp...
Command line:
PATCH="C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\IXP000.TMP\ProjectServer2003-KB837241-FullFile-ENU.msp" REBOOT=ReallySuppress
The update failed.
Finished processing the update on 11/12/2004 at 14:07:54.
Encountered error 1603 while updating.
FindError result: failed
Error 1603 not ok to report to Setup Watson.


Errors in detailed log include

DEBUG: Error 2746: Transform 1TTo1U invalid for package
C:\WINDOWS\Installer\16041f6c.msi. Expected product
{91320409-6000-11D3-8CFE-0150048383C9}, found product
{90320409-6000-11D3-8CFE-0150048383C9}.
1: 2746 2: 1TTo1U 3: C:\WINDOWS\Installer\16041f6c.msi 4:
{91320409-6000-11D3-8CFE-0150048383C9} 5:
{90320409-6000-11D3-8CFE-0150048383C9}

MSI (s) (CC:28): Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI112.tmp, Entrypoint: GetUserAccounts
GetUserAccounts: ...Using SQL authentication.
GetUserAccounts: ....coinit
GetUserAccounts: ....getting webvroot
GetUserAccounts: ....got webvroot
GetUserAccounts: ....multibytetowidechar
GetUserAccounts: ....opening the key
GetUserAccounts: ....failed openkey
GetUserAccounts: Error: Failed to OpenKey.

 

[KnightFall1]

Check out this URL for downloading and installing the Project Server 2003 SP1:

http://www.microsoft.com/downloads/...62-d534-4f17-ab08-7c9b790c5b15&displaylang=en

On this URL it mentions that there is a SQL update file
(ProjectServer2003-KB837241-SQLFile-ENU.exe) that must be applied prior to
installation of SP1 for Project Server 2003. Did you install the update prior
on the server that houses your SQL Server database for Project Server 2003
prior to attempting to install Project Server 2003 SP1? If not, you will need
to do this first.

 

[Mark]

Thanks for the reply.

I did apply the SQL patch and it appeared to update correctly.

 

[KnightFall1]

Check your permissions to make sure those are correct as well. I'm assuming
you are logged onto the Project Server 2003 box with Administrator privileges
but what privileges do your logged-on network account have to the actual
Project Server 2003 database on the SQL Server (assuming the database is
residing on a seperate server).

At the end of the log you attached it mentioned that SQL authentication was
attempting to be performed and failure to perform an operation. Basically a
check is being performed to ensure you have the adequate level of access to
perform this upgrade. Different issue but even when I performed backups of
WSS sites used by Project Server 2003 I needed to have adequate permissions
to the Project Server 2003 database itself. Try having the DBA temporarily
bump up your privileges on your NT ID to the Project Server database while
you are performing the upgrade. The other option is to temporarily log onto
the Project Server box with the domain account you originally setup during
the installation of Project Server 2003 and then run the upgrade file. This
account should also have appropriate permissions to the Project Server
database.