August 4, 2009 at 12:17 am
Hi,
today morning when i logged in into my new bult sql server machine , if didnt allow me to login , as sql server screen got disaapered in less than 1 second .
then i tried from command prompt run>>sqlwb , but the result is SAME.
i also tried sql profiler and other tols like sql server aree configuration btu they are working FINE
i also installed one more instance ( that was my scheduled task for today's work) thinking that issue would be resolved but NO GOOD RESULTs
one strange thing is this , i can connect with it from local machine.
can anybody help me please ?
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
August 4, 2009 at 12:35 am
Hi,
Whenever you get any error you need to check two things.
1. Is there any error in sql error log.
2. Is there any error in windows event viewer.
Without this information I think its make difficult for others to help you in resolving the issue.
[font="Verdana"]Thanks
Chandra Mohan[/font]
August 4, 2009 at 12:51 am
When i checked EVENT VIEWER
i got the following error
FCB::Open failed: Could not open file D:\PROD\MSSQL.3\MSSQL\DATA\model.mdf for file number 1. OS error: 32(The process cannot access the file because it is being used by another process.).
Here PROD instance name
in SQl log :
SQL Server is now ready for client connections. This is an informational message; no user action is required.
2009-08-03 23:48:26.18 spid9s Clearing tempdb database.
2009-08-03 23:48:27.53 spid24s Starting up database 'DB_DBA'.
2009-08-03 23:48:27.53 spid19s Starting up database 'ECOMMERCE'.
2009-08-03 23:48:27.53 spid26s Starting up database 'TEMP_TABLE_DB1'.
2009-08-03 23:48:27.53 spid18s Starting up database 'DB_SURVEY'.
2009-08-03 23:48:27.53 spid25s Starting up database 'AspState'.
2009-08-03 23:48:27.53 spid27s Starting up database 'TEMP_TABLE_DB2'.
2009-08-03 23:48:27.53 spid16s Starting up database 'DB_RESPONDENT'.
2009-08-03 23:48:27.53 spid20s Starting up database 'ESS'.
2009-08-03 23:48:28.15 spid25s Error: 17207, Severity: 16, State: 1.
2009-08-03 23:48:28.15 spid25s FCB::Open: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'D:\PROD\MSSQL.3\MSSQL\DATA\AspState.mdf'. Diagnose and correct the operating system error, and retry the operation.
2009-08-03 23:48:28.21 spid25s Error: 17204, Severity: 16, State: 1.
2009-08-03 23:48:28.21 spid25s FCB::Open failed: Could not open file D:\PROD\MSSQL.3\MSSQL\DATA\AspState.mdf for file number 1. OS error: 2(The system cannot find the file specified.).
2009-08-03 23:48:28.26 spid25s Error: 5120, Severity: 16, State: 101.
2009-08-03 23:48:28.26 spid25s Unable to open the physical file "D:\PROD\MSSQL.3\MSSQL\DATA\AspState.mdf". Operating system error 2: "2(The system cannot find the file specified.)".
2009-08-03 23:48:28.74 spid25s Error: 17207, Severity: 16, State: 1.
2009-08-03 23:48:28.74 spid25s FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'D:\PROD\MSSQL.3\MSSQL\DATA\AspState_1.LDF'. Diagnose and correct the operating system error, and retry the operation.
2009-08-03 23:48:28.74 spid25s File activation failure. The physical file name "D:\PROD\MSSQL.3\MSSQL\DATA\AspState_1.LDF" may be incorrect.
2009-08-03 23:48:28.74 spid25s Starting up database 'ESS_ARCHIVE'.
2009-08-03 23:48:28.74 spid25s Error: 17207, Severity: 16, State: 1.
2009-08-03 23:48:28.74 spid25s FCB::Open: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'D:\PROD\MSSQL.3\MSSQL\DATA\ESS_ARCHIVE.mdf'. Diagnose and correct the operating system error, and retry the operation.
2009-08-03 23:48:28.74 spid25s Error: 17204, Severity: 16, State: 1.
2009-08-03 23:48:28.74 spid25s FCB::Open failed: Could not open file D:\PROD\MSSQL.3\MSSQL\DATA\ESS_ARCHIVE.mdf for file number 1. OS error: 2(The system cannot find the file specified.).
2009-08-03 23:48:28.74 spid25s Error: 5120, Severity: 16, State: 101.
2009-08-03 23:48:28.74 spid25s Unable to open the physical file "D:\PROD\MSSQL.3\MSSQL\DATA\ESS_ARCHIVE.mdf". Operating system error 2: "2(The system cannot find the file specified.)".
2009-08-03 23:48:28.76 spid25s Error: 17207, Severity: 16, State: 1.
2009-08-03 23:48:28.76 spid25s FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'D:\PROD\MSSQL.3\MSSQL\Data\ESS_ARCHIVE_7.ldf'. Diagnose and correct the operating system error, and retry the operation.
2009-08-03 23:48:28.76 spid25s File activation failure. The physical file name "D:\PROD\MSSQL.3\MSSQL\Data\ESS_ARCHIVE_7.ldf" may be incorrect.
2009-08-03 23:48:28.87 spid24s Analysis of database 'DB_DBA' (16) is 100% complete (approximately 0 seconds remain). This is an informational message only. No user action is required.
2009-08-03 23:48:33.07 spid9s Starting up database 'tempdb'.
2009-08-03 23:48:34.00 spid14s CHECKDB for database 'DB_PROD' finished without errors on 2007-12-27 05:21:09.400 (local time). This is an informational message only; no user action is required.
2009-08-03 23:48:44.18 spid5s Error: 8355, Severity: 16, State: 1.
2009-08-03 23:48:44.18 spid5s Server-level event notifications can not be delivered. Either Service Broker is disabled in msdb, or msdsb failed to start. Event notifications in other databases could be affected as well. Bring msdb online, or enable Service Broker.
2009-08-03 23:48:44.21 spid5s Recovery is complete. This is an informational message only. No user action is required.
2009-08-03 23:48:44.80 spid12s The Service Broker protocol transport is disabled or not configured.
2009-08-03 23:48:44.80 spid12s The Database Mirroring protocol transport is disabled or not configured.
2009-08-03 23:48:45.03 spid12s Service Broker manager has started.
2009-08-03 23:48:48.09 spid51 Using 'xpsqlbot.dll' version '2005.90.3042' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
2009-08-03 23:48:50.44 spid51 Using 'xpstar90.dll' version '2005.90.3310' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
2009-08-03 23:48:51.96 spid51 Using 'xplog70.dll' version '2005.90.3042' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
2009-08-04 00:00:06.18 spid16s This instance of SQL Server has been using a process ID of 1792 since 8/3/2009 11:48:44 PM (local) 8/3/2009 6:18:44 PM (UTC). This is an informational message only; no user action is required.
2009-08-04 10:36:49.37 Server SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.
2009-08-04 10:36:52.99 spid12s Service Broker manager has shut down.
2009-08-04 10:36:52.99 spid12s Error: 17054, Severity: 16, State: 1.
2009-08-04 10:36:52.99 spid12s The current event was not reported to the Windows Events log. Operating system error = 31(A device attached to the system is not functioning.). You may need to clear the Windows Events log if it is full.
2009-08-04 10:36:53.73 Server The connection has been lost with Microsoft Distributed Transaction Coordinator (MS DTC). Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) will begin once the connection is re-established. This is an informational message only. No user action is required.
2009-08-04 10:37:04.24 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
2009-08-04 10:37:04.56 Server The SQL Network Interface library could not deregister the Service Principal Name (SPN) for the SQL Server service. Error: 0x45b, state: 4. Administrator should deregister this SPN manually to avoid client authentication errors.
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
August 4, 2009 at 1:19 am
Hi,
As you can see there are lot of errors in the error log.
FCB::Open failed: Could not open file D:\PROD\MSSQL.3\MSSQL\DATA\model.mdf for file number 1. OS error: 32(The process cannot access the file because it is being used by another process.).
Can you check which process is using this.
2009-08-03 23:48:28.15 spid25s Error: 17207, Severity: 16, State: 1.
2009-08-03 23:48:28.15 spid25s FCB::Open: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'D:\PROD\MSSQL.3\MSSQL\DATA\AspState.mdf'. Diagnose and correct the operating system error, and retry the operation.
2009-08-03 23:48:28.21 spid25s Error: 17204, Severity: 16, State: 1.
2009-08-03 23:48:28.21 spid25s FCB::Open failed: Could not open file D:\PROD\MSSQL.3\MSSQL\DATA\AspState.mdf for file number 1. OS error: 2(The system cannot find the file specified.).
2009-08-03 23:48:28.26 spid25s Error: 5120, Severity: 16, State: 101.
2009-08-03 23:48:28.26 spid25s Unable to open the physical file "D:\PROD\MSSQL.3\MSSQL\DATA\AspState.mdf". Operating system error 2: "2(The system cannot find the file specified.)".
2009-08-03 23:48:28.74 spid25s Error: 17207, Severity: 16, State: 1.
2009-08-03 23:48:28.74 spid25s FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'D:\PROD\MSSQL.3\MSSQL\DATA\AspState_1.LDF'. Diagnose and correct the operating system error, and retry the operation.
2009-08-03 23:48:28.74 spid25s File activation failure. The physical file name "D:\PROD\MSSQL.3\MSSQL\DATA\AspState_1.LDF" may be incorrect.
2009-08-03 23:48:28.74 spid25s Starting up database 'ESS_ARCHIVE'.
2009-08-03 23:48:28.74 spid25s Error: 17207, Severity: 16, State: 1.
2009-08-03 23:48:28.74 spid25s FCB::Open: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'D:\PROD\MSSQL.3\MSSQL\DATA\ESS_ARCHIVE.mdf'. Diagnose and correct the operating system error, and retry the operation.
2009-08-03 23:48:28.74 spid25s Error: 17204, Severity: 16, State: 1.
2009-08-03 23:48:28.74 spid25s FCB::Open failed: Could not open file D:\PROD\MSSQL.3\MSSQL\DATA\ESS_ARCHIVE.mdf for file number 1. OS error: 2(The system cannot find the file specified.).
2009-08-03 23:48:28.74 spid25s Error: 5120, Severity: 16, State: 101.
2009-08-03 23:48:28.74 spid25s Unable to open the physical file "D:\PROD\MSSQL.3\MSSQL\DATA\ESS_ARCHIVE.mdf". Operating system error 2: "2(The system cannot find the file specified.)".
2009-08-03 23:48:28.76 spid25s Error: 17207, Severity: 16, State: 1.
2009-08-03 23:48:28.76 spid25s FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'D:\PROD\MSSQL.3\MSSQL\Data\ESS_ARCHIVE_7.ldf'. Diagnose and correct the operating system error, and retry the operation.
2009-08-03 23:48:28.76 spid25s File activation failure. The physical file name "D:\PROD\MSSQL.3\MSSQL\Data\ESS_ARCHIVE_7.ldf" may be incorrect.
From the error log either the sqlserverservice account does not have sufficient permissions on folder
for databases aspstate and ess_archive. Try to resolve this by giving sufficient permissions.
2009-08-04 10:36:52.99 spid12s The current event was not reported to the Windows Events log. Operating system error = 31(A device attached to the system is not functioning.). You may need to clear the Windows Events log if it is full.
Can you take backup of windows logs and clear the logs. Because as it indicates that the windows log is full any errors will not be logged which makes it impossible to trace and sort any issues and also there is a device related error try to check what is it.
2009-08-04 10:37:04.56 Server The SQL Network Interface library could not deregister the Service Principal Name (SPN) for the SQL Server service. Error: 0x45b, state: 4. Administrator should deregister this SPN manually to avoid client authentication errors.
And finally there is a SPN problem which might be blocking your connection.
Refer http://www.sqlservercentral.com/Forums/Topic622068-146-1.aspx#bm623115
And also check whether firewall is blocking your connectivity.
[font="Verdana"]Thanks
Chandra Mohan[/font]
August 4, 2009 at 2:39 am
Try to uninstall the SQL Server completely, reboot,re-install and reboot and then try to connect. This should resolve the problem.As your installation is not done perfectly or Corrupt.
Let SQL Server files use default C$ / drive itself for installing.
Cheers,
- Win.
" Have a great day "
August 4, 2009 at 2:57 am
Hi,
But keeping your files in C (which is a system drive) is not at all recommended.
[font="Verdana"]Thanks
Chandra Mohan[/font]
August 4, 2009 at 2:57 am
i will do that but how can this be done if we are working on any live server ???
is there any ways so that we can rectify these kinds of problem without removing the instances
permanently .
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
August 4, 2009 at 2:59 am
i m keeping my files in other drive
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
August 4, 2009 at 3:24 am
Hi,
Did you clear your windows log and resolve the SPN issue. We can go further into debugging this issue if you can do these two things.
[font="Verdana"]Thanks
Chandra Mohan[/font]
August 4, 2009 at 3:27 am
how can i clear event log ? i dont know the way
please assist
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
August 4, 2009 at 4:01 am
instead of clearing the log its better if you can increase the size of the log file
start->run
and type eventvwr and click on ok. Eventviewer window will open.
In the Eventviewer window right click on application and in the popup menu click on properties. In the properties window. Increase the maximum log size value.
Repeat the same steps for system and security also
[font="Verdana"]Thanks
Chandra Mohan[/font]
August 5, 2009 at 4:02 am
it seems the permission issues on ur folders, make service account as a local admin if it is not.
you said you installed another instance on that machine, please let me know what happend then, if the same then try to install another instance but change the directory.
thanks.
August 5, 2009 at 4:11 am
hi that problem has ben solved by re-installing the instance but caught with a new problem
please refer
below link , see if you can help me in this case
http://www.sqlservercentral.com/Forums/Topic765318-146-1.aspx
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
August 5, 2009 at 10:20 am
The errors look to me like a default instance of SQL server was installed, and then a named instance was installed, then you started seeing these isues when you were installing another named instance of SQL server.
Is this how all the instances of SQL server were installed on this Server?
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply