February 23, 2007 at 11:20 am
Hi,
I have a SQL Server 7 running, where the server service starts, but nobody can make a connection to the server (so the agent won't start either). I cannot use Enterprise Manager either because of same problem (cannot connect to server).
There are no errors in the event log (apart from the sqlagent not starting).
Any help/suggestions are very much appreciated.
February 23, 2007 at 1:49 pm
Have you seen the sql error logs? Can you post it?
The files are in the install folder, within LOG folder, open them with notepad. The most recent is ERRORLOG.
February 23, 2007 at 3:07 pm
Hi,
First of all thanks for reply. Here is the contents of the current errorlog file:
2007-02-23 16:51:58.10 kernel Microsoft SQL Server 7.00 - 7.00.1063 (Intel X86)
Apr 9 2002 14:18:16
Copyright (c) 1988-2002 Microsoft Corporation
Standard Edition on Windows NT 4.0 (Build 1381: Service Pack 6)
2007-02-23 16:51:58.10 kernel Copyright (C) 1988-1997 Microsoft Corporation.
2007-02-23 16:51:58.10 kernel All rights reserved.
2007-02-23 16:51:58.10 kernel Logging SQL Server messages in file 'f:\Mssql7\data\log\ERRORLOG'.
2007-02-23 16:51:58.14 kernel initconfig: Number of user connections limited to 32767.
2007-02-23 16:51:58.14 kernel SQL Server is starting at priority class 'high'(2 CPUs detected).
2007-02-23 16:51:58.17 kernel User Mode Scheduler configured for thread processing
2007-02-23 16:52:00.23 server Directory Size: 54105
2007-02-23 16:52:00.24 spid1 Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks
2007-02-23 16:52:00.24 kernel Attempting to initialize Distributed Transaction Coordinator.
2007-02-23 16:52:03.43 spid1 Starting up database 'master'.
2007-02-23 16:52:03.43 spid1 Opening file f:\Mssql7\data\data\master.mdf.
2007-02-23 16:52:03.43 spid1 Opening file f:\Mssql7\data\data\mastlog.ldf.
2007-02-23 16:52:03.49 spid1 Loading SQL Server's Unicode collation.
2007-02-23 16:52:03.51 spid1 Loading SQL Server's non-Unicode sort order and character set.
2007-02-23 16:52:03.54 spid1 5 transactions rolled forward in database 'master' (1).
2007-02-23 16:52:03.54 spid1 0 transactions rolled back in database 'master' (1).
2007-02-23 16:52:03.64 spid1 Starting up database 'model'.
2007-02-23 16:52:03.64 spid1 Opening file f:\Mssql7\data\DATA\model.mdf.
2007-02-23 16:52:03.65 spid1 Opening file f:\Mssql7\data\DATA\modellog.ldf.
2007-02-23 16:52:03.71 spid1 Clearing tempdb database.
2007-02-23 16:52:03.76 spid1 Creating file f:\Mssql7\data\DATA\TEMPDB.MDF.
2007-02-23 16:52:03.85 spid1 Closing file f:\Mssql7\data\DATA\TEMPDB.MDF.
2007-02-23 16:52:03.90 spid1 Creating file f:\Mssql7\data\DATA\TEMPLOG.LDF.
2007-02-23 16:52:04.01 spid1 Closing file f:\Mssql7\data\DATA\TEMPLOG.LDF.
2007-02-23 16:52:04.06 spid1 Opening file f:\Mssql7\data\DATA\TEMPDB.MDF.
2007-02-23 16:52:04.07 spid1 Opening file f:\Mssql7\data\DATA\TEMPLOG.LDF.
2007-02-23 16:52:04.34 spid1 Closing file f:\Mssql7\data\DATA\TEMPDB.MDF.
2007-02-23 16:52:04.35 spid1 Closing file f:\Mssql7\data\DATA\TEMPLOG.LDF.
2007-02-23 16:52:04.39 spid1 Starting up database 'tempdb'.
2007-02-23 16:52:04.39 spid1 Opening file f:\Mssql7\data\DATA\TEMPDB.MDF.
2007-02-23 16:52:04.39 spid1 Opening file f:\Mssql7\data\DATA\TEMPLOG.LDF.
2007-02-23 16:52:04.46 spid1 Server is unnamed.
2007-02-23 16:52:04.46 kernel Using 'SQLEVN70.DLL' version '7.00.1063'.
2007-02-23 16:52:04.46 kernel Using 'OPENDS60.DLL' version '7.00.00.1063'.
2007-02-23 16:52:04.46 ods Using 'SSNMPN70.DLL' version '7.0.694' to listen on '\\.\pipe\sql\query'.
2007-02-23 16:52:04.46 ods Using 'SSMSSO70.DLL' version '7.0.1063' to listen on '1433'.
2007-02-23 16:52:04.48 ods Using 'SSMSRP70.DLL' version '7.0.961' to listen on 'WGBEALF003'.
2007-02-23 16:52:04.59 spid6 Starting up database 'msdb'.
2007-02-23 16:52:04.59 spid6 Opening file f:\Mssql7\data\DATA\msdbdata.mdf.
2007-02-23 16:52:04.59 spid7 Starting up database 'DW_WH_DEV'.
2007-02-23 16:52:04.59 spid7 Opening file f:\Mssql7\data\data\DW_WH_DEV.mdf.
2007-02-23 16:52:04.62 spid8 Starting up database 'MSTR_MD'.
2007-02-23 16:52:04.62 spid8 Opening file f:\Mssql7\data\data\MSTR_MD_Data.MDF.
2007-02-23 16:52:04.64 spid9 Starting up database 'DW_SR2002_PROD'.
2007-02-23 16:52:04.64 spid9 Opening file f:\Mssql7\data\data\DW_SR2002_PROD_Data.MDF.
2007-02-23 16:52:04.67 spid6 Opening file f:\Mssql7\data\DATA\msdblog.ldf.
2007-02-23 16:52:04.73 spid8 Opening file G:\logs\MSTR_MD_Log.LDF.
2007-02-23 16:52:04.79 spid9 Opening file f:\Mssql7\data\data\DW_SR2002_PROD_Log.LDF.
2007-02-23 16:52:04.82 spid7 Opening file f:\Mssql7\data\data\DW_WH_DEV_log.ldf.
2007-02-23 16:52:07.82 spid1 Recovery complete.
2007-02-23 16:52:07.82 spid1 SQL Server's Unicode collation is:
2007-02-23 16:52:07.82 spid1 'English' (ID = 1033).
2007-02-23 16:52:07.82 spid1 comparison style = 196609.
2007-02-23 16:52:07.82 spid1 SQL Server's non-Unicode sort order is:
2007-02-23 16:52:07.82 spid1 'nocase_iso' (ID = 52).
2007-02-23 16:52:07.82 spid1 SQL Server's non-Unicode character set is:
2007-02-23 16:52:07.82 spid1 'iso_1' (ID = 1).
Hope this can give you a clue.
Thanks in advance
February 23, 2007 at 4:03 pm
What is the error when you try to connect?
Have you tried to connect from the server?
February 24, 2007 at 2:37 am
Hi,
Here's the error message I get when I try to manage the server in Enterprise Manager:
"A connection could not be established to <server>. - Login failed for user <user>.
Please verify SQL Server is running and check your SQL Server registration properties."
I can verify that SQL Server is running alright, and the security is set to mixed. The user account I am using is member of the domain admins group, so this user should have access to it.
I also tried an ODBC connection using a sql server user account, but result was the same. Every login fails. It is as if the logins table is empty....
February 24, 2007 at 9:14 am
... "The user account I am using is member of the domain admins group, so this user should have access to it." ...
that is not the case if you removed builtin\administrators !! Then you would have to give that user or that admin-user-group sysadmin privileges for sqlserver !
Try to connect using the sa sqllogin !
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
February 26, 2007 at 4:44 am
Try also a connection with osql through command prompt, just to verify that everything with EM ist OK
February 26, 2007 at 9:34 am
Hi,
First of all thanks for the help. Here's what happened today: users could log in again as if nothing had happened.
Since this is a server at a remote site that we've just begun to support, it is impossible for the moment to explain how this is possible, or what has happened over there. The remote site people thought I had fixed the problem, and I thought they had, but in fact nobody has done anything, it just started working again by itself.... This does require some further investigation, but anyway, thanks again for your support ! It is very much appreciated.
regards,
Koen
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply