July 21, 2009 at 3:17 am
I have two sql servers on the network which I cannot connect through SQL Server Management Studio or profiler with the known username and passwords of ours (Although they are available on the network connections list). When I logon to the windows server I can see SQL Server Service Manager running on both and only system databases in the ms sql data directory. I am just trying to find out if this SQL Server Service Manager running for notting and if the ms sql is not used by any third party program so I can uninstall it from the windows server box.
Thanks a lot for any help.
Regards,
July 21, 2009 at 6:15 am
report any error log from sql server error log folder. You will find some error log in bootstrap folder. Go and find error log from event viewer and post them here.
-LK
July 21, 2009 at 9:39 am
2009-07-19 08:04:59.34 Server Microsoft SQL Server 2005 - 9.00.2047.00 (Intel X86)
Apr 14 2006 01:12:25
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
2009-07-19 08:04:59.35 Server (c) 2005 Microsoft Corporation.
2009-07-19 08:04:59.35 Server All rights reserved.
2009-07-19 08:04:59.35 Server Server process ID is 1720.
2009-07-19 08:04:59.35 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2009-07-19 08:04:59.37 Server This instance of SQL Server last reported using a process ID of 1592 at 19/07/2009 08:03:48 (local) 19/07/2009 07:03:48 (UTC). This is an informational message only; no user action is required.
2009-07-19 08:04:59.37 Server Registry startup parameters:
2009-07-19 08:04:59.42 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2009-07-19 08:04:59.42 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2009-07-19 08:04:59.42 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2009-07-19 08:04:59.49 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2009-07-19 08:04:59.49 Server Detected 4 CPUs. This is an informational message; no user action is required.
2009-07-19 08:05:00.20 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2009-07-19 08:05:00.90 Server Database mirroring has been enabled on this instance of SQL Server.
2009-07-19 08:05:01.12 spid5s Starting up database 'master'.
2009-07-19 08:05:01.56 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2009-07-19 08:05:01.82 spid5s SQL Trace ID 1 was started by login "sa".
2009-07-19 08:05:01.84 spid5s Starting up database 'mssqlsystemresource'.
2009-07-19 08:05:01.90 spid5s The resource database build version is 9.00.2047. This is an informational message only. No user action is required.
2009-07-19 08:05:02.29 spid8s Starting up database 'model'.
2009-07-19 08:05:02.29 spid5s Server name is 'WBCDRTS'. This is an informational message only. No user action is required.
2009-07-19 08:05:02.31 spid5s Starting up database 'msdb'.
2009-07-19 08:05:02.78 Server A self-generated certificate was successfully loaded for encryption.
2009-07-19 08:05:02.79 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2009-07-19 08:05:02.79 Server Server local connection provider is ready to accept connection on [ \\.\pipe\sql\query ].
2009-07-19 08:05:02.79 Server Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.
2009-07-19 08:05:02.81 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2009-07-19 08:05:00.37 spid8s Clearing tempdb database.
2009-07-19 08:05:00.86 spid8s Starting up database 'tempdb'.
2009-07-19 08:05:00.98 spid5s Recovery is complete. This is an informational message only. No user action is required.
2009-07-19 08:05:01.05 spid11s The Service Broker protocol transport is disabled or not configured.
2009-07-19 08:05:01.05 spid11s The Database Mirroring protocol transport is disabled or not configured.
2009-07-19 08:05:01.17 spid11s Service Broker manager has started.
2009-07-20 01:00:08.05 spid1s Server resumed execution after being idle 60874 seconds. Reason: timer event.
July 21, 2009 at 9:48 am
try connecting to them using SQL authentication mode instead of windows authentication with a valid credentials.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply