Error 25623: Failed to connect to SQL Server

[Mark Steele]

All,

I am attempting to install MS Project Server 2003 and am receiving the
following error during install "25623: Failed to connect to SQL Server"

My configuration is as follows:

- Windows Server 2003 Standard Edition Service Pack 1 running in an ESX VM
- 512MB RAM, 20GB Disk
- installed MSDE 2.0A
- installed IIS
- installed SharePoint Services

This is a small, standalone installation used specifically to collaborate on
one or two project plans.

I have verified the database is running in Mixed Mode via the registry and
have set the installation to use Windows Authentication Mode.

The installation has been tough to say the least and now I am stuck at this
point.

Any help would be appreciated.

 

[Kevin W Flanagan]

Microsoft does not support ESX VM for Project Server deployments. You can
use Virtual PC from Micorosft.

 

[Mark Steele]

On 8/14/06 11:14 PM, in article
(e-mail address removed), "Kevin W Flanagan"

Microsoft does not support ESX VM for Project Server deployments. You can
use Virtual PC from Micorosft.

Kevin - are you stating that the reason I am getting this error is BECAUSE I
have deployed the Project Server inside a VMWare VM? Or are you simply
stating that Microsoft says they don't support it?

Virtual PC is not a viable solution - it is not server or enterprise grade.

I am running multiple other Microsoft VM's on the ESX platform - including
Windows 2003, SQL Server, Exchange, etc.

 

[Kevin W Flanagan]

I'm saying that Micorosft will not support anything other than VPC.

 

[Rolly Perreaux]

All,

I am attempting to install MS Project Server 2003 and am receiving the
following error during install "25623: Failed to connect to SQL Server"

My configuration is as follows:

- Windows Server 2003 Standard Edition Service Pack 1 running in an ESX VM
- 512MB RAM, 20GB Disk
- installed MSDE 2.0A
- installed IIS
- installed SharePoint Services

This is a small, standalone installation used specifically to collaborate on
one or two project plans.

I have verified the database is running in Mixed Mode via the registry and
have set the installation to use Windows Authentication Mode.

The installation has been tough to say the least and now I am stuck at this
point.

Any help would be appreciated.

Hi Mark,

Here's the steps to installing Project Server 2003 using MSDE

First un-install your copy of MSDE from your VM

Then download Microsoft SQL Server 2000 Service Pack 4 at:
http://www.microsoft.com/downloads/details.aspx?familyid=8E2DFC8D-C20E-
4446-99A9-B7F0213F8BC5&displaylang=en

At the bottom of the page click Download for the file:
SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE

NOTE:
Service Pack 4 of MSDE can also do a clean install of MSDE

Double click SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE to extract the files
needed. It will create a new folder called SQL2KSP4.

Then, re-intall MSDE but using the following command line:
C:\SQL2KSP4\msde\setup.exe sapwd=<strong_pwd> securitymode=sql
disablenetworkprotocols=0 INSTANCENAME="ProjectDB"

After it finishes, it might ask you to reboot, just click Cancel and go
to Services and start your new SQL instance. It should be listed as
MSSQL$PROJECTDB.

Next, install Project Server 2003. When you get to the "Enter database
server information" dialog box, in the Database server box, type
<servername>\ProjectDB and click Next.

....and now you're on your way

BTW, just remember what Kevin said about VMware being unsupported

Good Luck and let us know how it turns out!

--
Rolly Perreaux, PMP, MCSE
Project Server Trainer/Consultant

TriMagna Corporation
Microsoft Gold Partner
http://www.trimagna.com

 

[Rolly Perreaux]

I'm saying that Micorosft will not support anything other than VPC.

....and Virtual Server

The beauty is that they are both FREE

Cheers,

--
Rolly Perreaux, PMP, MCSE
Project Server Trainer/Consultant

TriMagna Corporation
Microsoft Gold Partner
http://www.trimagna.com

 

[Mark Steele]

On 8/15/06 9:18 AM, in article
(e-mail address removed), "Rolly Perreaux"

Hi Mark,

Here's the steps to installing Project Server 2003 using MSDE

First un-install your copy of MSDE from your VM

Then download Microsoft SQL Server 2000 Service Pack 4 at:
http://www.microsoft.com/downloads/details.aspx?familyid=8E2DFC8D-C20E-
4446-99A9-B7F0213F8BC5&displaylang=en

At the bottom of the page click Download for the file:
SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE

NOTE:
Service Pack 4 of MSDE can also do a clean install of MSDE

Double click SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE to extract the files
needed. It will create a new folder called SQL2KSP4.

Then, re-intall MSDE but using the following command line:
C:\SQL2KSP4\msde\setup.exe sapwd=<strong_pwd> securitymode=sql
disablenetworkprotocols=0 INSTANCENAME="ProjectDB"

After it finishes, it might ask you to reboot, just click Cancel and go
to Services and start your new SQL instance. It should be listed as
MSSQL$PROJECTDB.

Next, install Project Server 2003. When you get to the "Enter database
server information" dialog box, in the Database server box, type
<servername>\ProjectDB and click Next.

...and now you're on your way


BTW, just remember what Kevin said about VMware being unsupported

Good Luck and let us know how it turns out!

Trying that now - thanks!

BTW - do you know if SQLServer 2005 Express would work as well?

 

[Kevin W Flanagan]

Not sure about 2005 express, but I do know that 2005 does not work with 2003.
You will need to wait until 2007 comes out

 

[Mark Steele]

On 8/15/06 12:11 PM, in article C1076A62.17B8D%[email protected], "Mark

On 8/15/06 9:18 AM, in article
(e-mail address removed), "Rolly Perreaux"


Trying that now - thanks!

BTW - do you know if SQLServer 2005 Express would work as well?

Success!

 

[Rolly Perreaux]

Actually that's not true

Please review the following KB article:
http://support.microsoft.com/kb/917401/en-us

The key here is that the Project Server database needs to be created
first, then change the compatibility level to SQL Server 2000, and then
when installing Project Server select the "Connect to database" option.

Cheers,

--
Rolly Perreaux, PMP, MCSE
Project Server Trainer/Consultant

TriMagna Corporation
Microsoft Gold Partner
http://www.trimagna.com

 

[Rolly Perreaux]

Congratulations Mark!
Let the fun and games begin

Good Luck,

--
Rolly Perreaux, PMP, MCSE
Project Server Trainer/Consultant

TriMagna Corporation
Microsoft Gold Partner
http://www.trimagna.com

 

[Rolly Perreaux]

I haven't tried it with SQL Server 2005 Express, but if you read the
following KB Article I'm sure you will be able to figure it out what you
need to do from the command line.

http://support.microsoft.com/kb/917401/en-us\

However, I did find another article that you might be interested in
reading:

Upgrading MSDE 2000 to SQL Server 2005 Express
http://www.microsoft.com/technet/prodtechnol/sql/2005/msde2sqlexpress.ms
px

Good Luck!

--
Rolly Perreaux, PMP, MCSE
Project Server Trainer/Consultant

TriMagna Corporation
Microsoft Gold Partner
http://www.trimagna.com

 

[Kevin W Flanagan]

Yes, but you do not gain any functionality this way and any customizations
you have created will have to be rewritten as well. Does this really make
any sense?

 

[Rolly Perreaux]

Hi Keven,

Actually it does. You're assuming that the only database in SQL Server
2005 is the Project Server database. A lot of enterprise operations use
SQL Server 2005 for other database applications and it's typical that
the Administration of SQL Server is done by a DBA and not a Project
Server Administrator. It's also one of the reasons why SQL Server is the
first Project Server component to be off-loaded onto it's own server.
(along with Analysis Services)

If you use Sharepoint Services, there's at least another 2 more
databases right there that can use SQL Server 2005 functionality.

Just remember that the compatibility level is set on the database, not
the SQL Server 2000 server.

Cheers,

--
Rolly Perreaux, PMP, MCSE
Project Server Trainer/Consultant

TriMagna Corporation
Microsoft Gold Partner
http://www.trimagna.com

 

[Gary L. Chefetz [MVP]]

Rolly:

I'm landing on the side of don't do it when comes to running Project Server
2003 on SQL 2005. The incompatibilities are in the process of being
addressed, but as far as I can see, they haven't all been identified, let
alone addressed. So, for the more cautious among us, I strongly recommend
staying away from this combination.

 

[Rolly Perreaux]

Hi Gary,

Actually Project Server 2003 on SQL 2005 is fully supported by
Microsoft. But you still have to use Analysis Services 2000 for Porfolio
Analysis

"Microsoft Office Project Server 2003 can be installed to use a
Microsoft SQL Server 2005 database. However, the SQL Server 2005
database must be created outside the Project Server installation and set
to use SQL2000 compatibility mode. Currently, you must use Analysis
Services 2000 with Project Server 2003 to enable the Portfolio Analysis
feature that uses the data in an Analysis Services 2000 OLAP cube"

http://support.microsoft.com/kb/917401/en-us

So if an Administrator has the luxury of having it's own SQL server for
Project Server, then I would probably agree. But that's typically not
the case in large enterprises.

YMMV

Cheers,

--
Rolly Perreaux, PMP, MCSE
Project Server Trainer/Consultant

TriMagna Corporation
Microsoft Gold Partner
http://www.trimagna.com

 

[Gary L. Chefetz [MVP]]

Rolly:

Actually, there's now a fix available for the OLAP issues, however, like I
said in my previous post, it's fairly obvious that there are remaining
incompatibilities which haven't been addressed. Why go there?

 

[Rolly Perreaux]

Hi Gary,

Which "incompatibilities that haven't been addressed" and which fix for
OLAP issues are you referring too?

Cheers,

--
Rolly Perreaux, PMP, MCSE
Project Server Trainer/Consultant

TriMagna Corporation
Microsoft Gold Partner
http://www.trimagna.com

 

[Gary L. Chefetz [MVP]]

There's something funky going on with custom field name display which has
been reported a number of times. This is just hitting the radar. There may
be more. As for the OLAP fix, see:
http://support.microsoft.com/kb/921115/en-us