August 22, 2010 at 1:08 am
Hey Guys
i am at loss, im getting the following error message on one of our SQL Servers sitting on a clustered SQL environment, this error has only started popping up over the last 5 hours but logs the error every couple of seconds in the event log,
initerrlog: Could not open error log file 'T:\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
Operating system error = 21(error not found).
any ideas? as to how to resovle it?
Nothing has changed server like i said only started these error 5 6 hours ago
August 22, 2010 at 2:01 am
As per this page, error code 21 = 'The device is not ready.'. Can the node running the SQL Server instance access the T:\ path?
SQL BAK Explorer - read SQL Server backup file details without SQL Server.
Supports backup files created with SQL Server 2005 up to SQL Server 2017.
August 22, 2010 at 2:08 am
Hey Ray
thanks for the reply mate 🙂
Yes its the strangest thing im on the active node now and i can access the path perfectly ive checked permissions ect no luck?
SQL itself is writtening to the error log if i check through management studio
Thanks in advance
August 22, 2010 at 3:56 am
If the SQL Server instance is already writing to the error log successfully, but still raises that error in the event log, it's mighty strange. Sorry, I'm out of ideas.
SQL BAK Explorer - read SQL Server backup file details without SQL Server.
Supports backup files created with SQL Server 2005 up to SQL Server 2017.
August 22, 2010 at 7:06 am
twebster-856509 (8/22/2010)
Hey Guysi am at loss, im getting the following error message on one of our SQL Servers sitting on a clustered SQL environment, this error has only started popping up over the last 5 hours but logs the error every couple of seconds in the event log,
initerrlog: Could not open error log file 'T:\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
Operating system error = 21(error not found).
any ideas? as to how to resovle it?
Nothing has changed server like i said only started these error 5 6 hours ago
Seems something is wrong with the errorlog.
Try cycling the error log:
EXEC sp_cycle_errorlog ;
GO
HTH,
Cheers !
______________________________________________________________________________________________________________________________________________________________________________________
HTH !
Kin
MCTS : 2005, 2008
Active SQL Server Community Contributor 🙂
August 22, 2010 at 9:35 pm
Agree with Ray. The device was not ready when you received this message. Try running xp_cmdshell 'dir T:\' when you receive this error message. This will confirm if SQL Server is able to access this drive or not. If it is able to access this file, check if the ERRORLOG file is in use by some other application like Anti virus, Tape backup etc.
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
August 23, 2010 at 6:58 am
Only thing you forgot is to make sure xp_cmdshell is enabled?
August 23, 2010 at 7:04 am
Is the T: Drive set as a dependency of SQL Server in the Cluster Group?
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply