Microsoft Knowledge Base Email Alertz
All KB/RSS Links  |  Hot Kb!  |  New Kb!  |  Scott Cate  |  FAQ / KB  |  Web Hosting  |  Unsubscribe  

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

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.
Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

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

Article ID: 917401 - View products that this article applies to.

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" and "Installation ended prematurely"
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
(http://kbalertz.com/Feedback.aspx?kbNumber=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: "Could not connect to the OLAP server specified"
Back to the top | Give Feedback

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.
Back to the top | Give Feedback

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:
  1. Create the database.
    1. Start SQL Server Management Studio.
    2. In the Connect to Server dialog box, click Database Engine in the Server type box, and then click Connect.
    3. Right-click Databases, and then click New Database.
    4. 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.
    5. In the left pane of SQL Server Management Studio, expand Databases, right-click the database, and then click Properties.
    6. Under Select a page, click Options.
    7. In the Compatibility level box, click SQL Server 2000 (80), and then click OK.
    8. Exit SQL Server Management Studio.
  2. 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:
    1. Copy the Database folder from the Project Server 2003 CD to a location on the computer that is running SQL Server 2005.
    2. Run the script. The Setupdb.cmd script uses the following syntax:
      Setupdb.cmd SQLServerName DatabaseName UserName Password NOPAUSE
    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
    (http://office.microsoft.com/en-ca/assistance/HA011654021033.aspx)
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
Back to the top | Give Feedback

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
(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
(http://kbalertz.com/Feedback.aspx?kbNumber=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: "Could not connect to the OLAP server specified"
923803
(http://kbalertz.com/Feedback.aspx?kbNumber=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
Back to the top | Give Feedback

Properties

Article ID: 917401 - Last Review: September 18, 2011 - Revision: 5.0
APPLIES TO
  • Microsoft Office Project Server 2003, when used with:
    • Microsoft SQL Server 2005 Enterprise Edition
    • Microsoft SQL Server 2005 Standard Edition
Keywords: 
kbtshoot kbexpertiseinter kberrmsg kbsetup kbconfig kbprb KB917401
Back to the top | Give Feedback
        

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

roland Report As Irrelevant  
Written: 4/23/2006 10:15 PM
Easier way to do it without all the security issues you will get if you need to do it manually. Start setup, as soon as setup steps are finished (but prior to install) when setup asks to confirm the installation, make sure you have SQL Server 2005 opened and start install. Refresh the databases and as soon as you see ProjectServer database created, right click , option, change to SQL(80) compliant. All done. Because the SQL query that crashes the installation is quite late in the process of creating the database, you have sufficient time to change the SQL database before it crashes.



Copyright © 2002-2007 KBALERTZ.COM.  All Rights Reserved. Terms / Privacy. Discount ASP.NET Hosting