Microsoft KB Archive/917401

= Error messages when you run the Setup program for Project Server 2003: &quot;Error 25624. Failed to execute SQL String&quot; and &quot;Installation ended prematurely&quot; =

Article ID: 917401

Article Last Modified on 3/19/2007

-

APPLIES TO

 Microsoft Office Project Server 2003, when used with:  Microsoft SQL Server 2005 Enterprise Edition

 Microsoft SQL Server 2005 Standard Edition 

-



SYMPTOMS
When you try to run the Setup program to install Microsoft Office Project Server 2003, and when you have chosen to point to a Microsoft SQL Server 2005 database, you may receive the following error message:

Error 25624. Failed to execute SQL String. (-2147217900 sp_addlogin ‘MSProjectServerUser’, ‘password’, ‘ProjectServer’ )

After you receive the first error message, you receive the following error message:

Error 25624. Failed to execute SQL String&quot; and &quot;Installation ended prematurely&quot;

Note Project Server 2003 can be installed to use a SQL Server 2005 database. However, the SQL Server 2005 database must be created outside the Project Server installation, and must be set to use SQL2000 compatibility mode.

For more information about how to create an OLAP cube in Project Server 2003 when a SQL Server 2005 database is used, click the following article number to view the article in the Microsoft Knowledge Base:

921116 Error message when you try to build an OLAP cube in a deployment of Project Server 2003 that uses SQL Server 2005 Analysis Services: &quot;Could not connect to the OLAP server specified&quot;



CAUSE
SQL Server 2005 was released after Project Server 2003. This issue occurs because the SQL scripts that are included with Project Server 2003 are incompatible with SQL Server 2005. The SQL scripts are used to create the database that is used by Project Server 2003. By default, the name of the database is ProjectServer.



WORKAROUND
To work around this issue, follow these steps:
 * 1) Before you install Project Server 2003, manually create the database on the computer that is running SQL Server 2005.
 * 2) Set the compatibility level of the database to the SQL Server 2000 (80) setting.
 * 3) Run the Setup program to install Project Server 2003.
 * 4) Connect to database by using the Connect to another existing database option on the Enter database server information page of the Setup program.

Create and configure the database that is used by Project Server 2003 on a computer that is running SQL Server 2005. To do this, follow these steps:  Create the database. <ol style="list-style-type: lower-alpha;"> Start SQL Server Management Studio.</li> In the Connect to Server dialog box, click Database Engine in the Server type box, and then click Connect.</li> Right-click Databases, and then click New Database.</li> In the New Database dialog box, type the name of the database in the Database name box. For example, type ProjectServer, and then click OK.</li> In the left pane of SQL Server Management Studio, expand Databases, right-click the database, and then click Properties.</li> Under Select a page, click Options.</li> In the Compatibility level box, click SQL Server 2000 (80), and then click OK.</li> Exit SQL Server Management Studio.</li></ol> </li> Run the Setupdb.cmd script. The Setupdb.cmd script is located in the \Support\Database folder of the Project Server 2003 CD. To use the Setupdb.cmd script, follow these steps: <ol style="list-style-type: lower-alpha;"> Copy the Database folder from the Project Server 2003 CD to a location on the computer that is running SQL Server 2005.</li> Run the script. The Setupdb.cmd script uses the following syntax:

Setupdb.cmd  NOPAUSE

</li></ol>

The Setupdb.cmd script creates the tables and roles that are required for Project Server 2003. For more information about how to use the Setupdb.cmd script, visit the following Microsoft Web site:

http://office.microsoft.com/en-ca/assistance/HA011654021033.aspx

</li></ol>

If you have an existing deployment of Project Server 2003, and you would like to move the database to a computer that is running SQL Server 2005, follow these steps:
 * 1) Restore the ProjectServer database to a SQL Server 2005 database.
 * 2) Set the compatibility level of the database.
 * 3) Use the Conninfo.exe tool to specify the connection information. The Conninfo.exe tool is located in the Project Server folder.

The following are examples of scripts that you can use to verify and to change the compatibility level of the database.

To verify the compatibility level of the database, use the following script. EXEC sp_dbcmptlevel DatabaseName Go To change the compatibility level of the database, use the following script. EXEC sp_dbcmptlevel DatabaseName, 80 Go

<div class="moreinformation_section">

MORE INFORMATION
For more information about how to install Project Server 2003, see the Microsoft Office Project Server 2003 Installation Guide. To obtain the Microsoft Office Project Server 2003 Installation Guide, visit the following Microsoft Web site:

http://www.microsoft.com/downloads/details.aspx?FamilyID=CA99B5E3-0478-4AC3-A230-C4F2D82096C1&displaylang=en

If you have an existing deployment of Project Server 2003, follow these steps:
 * 1) Restore the ProjectServer database to a SQL Server 2005 database.
 * 2) Set the compatibility level of the database.
 * 3) Use the Conninfo.exe tool to specify the connection information. The Conninfo.exe tool is located in the Project Server folder.

The following are examples of scripts that you can use to verify and to change the compatibility level of the database. To verify the compatibility level of the database, use the following script: EXEC sp_dbcmptlevel DatabaseName Go To change the compatibility level of the database, use the following script: EXEC sp_dbcmptlevel DatabaseName, 80 Go For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:

921116 Error message when you try to build an OLAP cube in a deployment of Project Server 2003 that uses SQL Server 2005 Analysis Services: &quot;Could not connect to the OLAP server specified&quot;

923803 Project Web Access does not correctly display Project Server 2003 custom field titles when you run Project Server 2003 on a server that is running SQL Server 2005

Additional query words: prj SQL2005

Keywords: kbtshoot kbexpertiseinter kberrmsg kbsetup kbconfig kbprb KB917401

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.