Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 SQL SERVER 6.5 Connecting Trouble

Author  Topic 

AskSQLTeam
Ask SQLTeam Question

0 Posts

Posted - 2004-05-13 : 08:15:52
Carlos Contessi writes " We´re using MS SQL 6.5 RUNNING NT SERVER 4.0
Problem:
: A CONNECTION COULD NOT BE ESTABLISHED TO SERVIDOR_II - [DB-LIBRARY] UNABLED TO CONECCT: SQL SERVER IS UNAVAIBLE OR DOES NOT EXIST. SPECIFIED SQL SERVER NOT FOUND.
02/03/2004 09:41:44 AM MSSQLServer Error Kernel 17055 N/A SERVIDOR_II Mesg 18491 : Unable to start due to invalid serial number.

02/03/2004 09:41:44 AM MSSQLServer Información Kernel 17055 N/A SERVIDOR_II Mesg 17026 : Using 'SQLEVN60.DLL' version '6.00.000'.

02/03/2004 09:41:43 AM MSSQLServer Información Server 17055 N/A SERVIDOR_II Mesg 18109 : Recovery dbid 3 ckpt (338,0) oldest tran=(339,0)

02/03/2004 09:41:43 AM MSSQLServer Información Server 17055 N/A SERVIDOR_II Mesg 18109 : Recovery dbid 1 ckpt (7958,34) oldest tran=(7958,0)

02/03/2004 09:41:42 AM SQLExecutive Información Service Control 101 N/A SERVIDOR_II SQLExecutive Service successfully started
02/03/2004 09:41:40 AM MSSQLServer Información Kernel 17055 N/A SERVIDOR_II Mesg 17162 : SQL Server is starting at priority class 'normal' with dataserver serialization turned on (1 CPU detected).

02/03/2004 09:41:40 AM MSSQLServer Información Kernel 17055 N/A SERVIDOR_II Mesg 17119 : initconfig: number of server processes reduced to 9

02/03/2004 09:41:40 AM MSSQLServer Información Kernel 17055 N/A SERVIDOR_II Mesg 17117 : initconfig: number of user connections reduced to 0
02/03/2004 09:41:37 AM MSDTC Información SVC 4097 N/A SERVIDOR_II Microsoft DTC has started.
02/03/2004 09:41:37 AM MSDTC Información CM 4156 N/A SERVIDOR_II Debug string message: ProcID=0x78 Protocols On :24."

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2004-05-13 : 13:09:05
So does this happen upon connecting to the server or starting the service? Check to make sure the service is started. Do you have backups for your databases? You might have a corrupted installation.

Tara
Go to Top of Page
   

- Advertisement -