SQL Server(Tough one)

[gioannou]

Hi again...
I'm looking for experienced(or anyone who knows)users of SQL Server 2000.

One of our customers runs windows 2003 SBS sp1 and tries to install sql server 2000 Standard Edition(which is needed for one of our company's applications to run - Yeap, we support that as well).This version doesn't run on this OS unless Sql server 2K SP3 or latest is installed.Without Sp3 installed the sql service cannot start.However, installation is supposed to end.In a finished installation sp3 can be applied and the service CAN start and everything goes fine.
On this certain occasion the install cannot end.On the installation log file I can see that everything is copied fine.However, the final lines are as follows:

Starting Service ...

Greek_CI_AI

-m -Q -T4022 -T3659

Connecting to Server ...

driver={sql server};server=SERVER;UID=<login>;PWD=<password>;database=master

[Microsoft][ODBC SQL Server Driver]Client unable to establish connection

[Microsoft][ODBC SQL Server Driver]Unable to load communication module. Driver has not been correctly installed.

driver={sql server};server=SERVER;UID=<login>;PWD=<password>;database=master

[Microsoft][ODBC SQL Server Driver]Client unable to establish connection

[Microsoft][ODBC SQL Server Driver]Unable to load communication module. Driver has not been correctly installed.

driver={sql server};server=SERVER;UID=<login>;PWD=<password>;database=master

[Microsoft][ODBC SQL Server Driver]Client unable to establish connection

[Microsoft][ODBC SQL Server Driver]Unable to load communication module. Driver has not been correctly installed.

SQL Server configuration failed.

###############################################################################

13:20:44 Process Exit Code: (-1)
13:21:22 Setup failed to configure the server. Refer to the server error logs and C:\WINDOWS\sqlstp.log for more information.
13:21:23 Action CleanUpInstall:
13:21:23 C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\SqlSetup\Bin\scm.exe -Silent 1 -Action 4 -Service SQLSERVERAGENT
13:21:23 Process Exit Code: (1060) The specified service does not exist as an installed service.

13:21:23 C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\SqlSetup\Bin\scm.exe -Silent 1 -Action 4 -Service MSSQLSERVER
13:21:23 Process Exit Code: (0)
13:21:23 StatsGenerate returned: 2
13:21:23 StatsGenerate (0x0,0x1,0xf000,0x100,1033,303,0x0,0x1,0,0,0
13:21:23 StatsGenerate -1,Administrator)
13:21:23 Installation Failed.


And the installation rolls back.
I should mention that the troubleshoot process is made by phone...
In a normal case the service cannot be started.In this case it seems like the service cannot even be installed.That's why the install process rolls back.
I couldn't find anything helpful in any specialized forum I checked.Norton 2005 Antivirus installed but it shouldn't mean anything cause the same occurs with the Antivirus uninstalled.OS fully updated.
I've checked the ODBC driver needed for the SQL to run, it's listed in the registry and it exists on the path specified.Tried to re-register it by regsvr32 yet I get the message that the dllregisterserver entry point was not found which means that the file specified is not a valid .dll file(BTW same s*** happens on my machine which runs xp but everything works just fine)
Same goes for the file ntwdblib.dll which is the client part of SQL Server.
It's a long shot I just wonder if anyone came accross this situation(Ok, it's not that usual and it is rather speciallized)or any ideas whatsoever.

Thanx in advance

[LindaHewitt]

Gioannou,

You wrote:

I'm looking for experienced(or anyone who knows)users of SQL Server 2000.

One of our customers runs windows 2003 SBS sp1 and tries to install sql server 2000 Standard Edition(which is needed for one of our company's applications to run - Yeap, we support that as well).This version doesn't run on this OS unless Sql server 2K SP3 or latest is installed.Without Sp3 installed the sql service cannot start.

I am confused. The original version of Small Business Server 2003 included SQL Server 2000, so why are you trying to install it again? This should have been installed as part of the original installation.

Microsoft has released an update R2 which contains SQL Server 2005. Below is an URL, which shows everything that is included in the SBS 2003 R2 version. The primary upgrades are to .NET Framework 2.0, Visual Studio 2005, and SQL Server 2005. Most of these updates reduce the development time required but if your client is not very experienced, then I would recommend staying with the original SBS 2003 but apply all of the Microsoft updates.

The URL below is for the R2 version of SBS 2003 and its shows all of its components. The major benefit of SBS for the small business is that this is a very cost effective way to obtain all of this software.

http://download.microsoft.com/downlo....Datasheet.pdf

I hope this helps. Please keep us posted.

Cheers,

Linda

[gioannou]

Hi there...back after the weekend!
Actually we don't officialy support SQL Server 2005 yet...
Most of our customers still use MSDE 7.0 since there are many standalone installations of our programs.
As it seems there is no current installation of SQL 2K on the machine.To be honest I haven't come up with a situation where it is already installed on SBS.
Are u sure it's 2k server that you are talking about and not MSDE 2K?

[LindaHewitt]

I am absolutely sure that it is SQL Server 2000 standard edition and not MSDE.

Just look at the R2 components link. That link does not say MSDE. As for their original SSBS 2003 CDs for confirmation.

FYI ... Microsoft tweaks each of these server programs, so that they are limited to how large a business can use SBS. Microsoft's objective is to get small to medium size business used to Microsoft integration, so that when these business require it, they will upgrade to the individual standard versions. This also makes the migration process much simplier.

http://www.itjungle.com/two/two052505-story02.html

http://www.smallbizserver.net/ This link verifies that it is SQL Server 2000, which is included in SBS.

http://www.microsoft.com/windowsserv...s/default.mspx

Here is the Google search that I used.

http://www.google.com/search?sourcei...ess+Server+sp1

Is it possible that the SP1 update process was not completed correctly? Or maybe SBS was not installed correctly.

UPDATE:

I just did some additional Google searches and discovered that there are multiple versions of SBS 2003 and that the standard edition does not include SQL Server 2000 but the premium edition does include SQL Server 2000. Because this product is heavily subsidized and limited to maximum number of processers and users, if you are trying to install a regular version of SQL Server 2000, then the problem that you are having is caused because there is an incompatibility here.

If this is the case, the solution is for your client to upgrade to the premium edition.

Here are some additional links, so that you can continue to do the research.

http://www.microsoft.com/windowsserv...s/default.mspx

SQL Server is not included in standard edition

http://en.wikipedia.org/wiki/Windows_Server_2003

Cheers,

Linda

[gioannou]

Yeah well, the link shows the components of SBS R2 which indeed contains sql 2005 but I'm not sure which version of SBS the client runs.Actually I wasn't aware of the R2 version.The thing is, when we went through the installed programs(I repeat by phone)we couldn't see any SQL installation either of 2K or 2005.So we start from scratch...Thx for the info.

Oh, and by the link u suggested I see that sql 2K is included it the Premium Edition of SBS not in Standard Edition


FYI...I didn't see all of your updates!

[LindaHewitt]

FYI ... I have updated my previous post with additional information.

Linda

[gioannou]

Enough with the edits...
Small Business, Premium, Standard, Web, Enterprise, Datacenter, Compute Cluster...yak!
The thing is, our usual procedure in this occasion is what I described in the first place.Install SBS then Sp1 for SBS then SQL 2K, then SP3 or 4 for SQL.
He's bringing the machine over this week anyway I'll have a better view of the situation.

[gioannou]

OK, solved that one...
The problem is that the file dbnetlib.dll which contains the communication modules(protocols)for the client/server communication was missing from the windows installation(specifically the WINDOWS folder)
Copied the file to its location and everything worked fine.
Thx Linda for your interest