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.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-02-18 : 21:14:00
|
| Ian writes "We have a SQL Server 2000 (SP2) that has been running for 4 months without a reboot. Today we attempted to reboot the SQL Server service, but received the following error:17050 : initerrlog: Could not open error log file 'e:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'. Operating system error = 32(error not found).No read/write permissions have been changed on the directory or ERRORLOG file. We've had a look at the ERRORLOG file and nothing seems amiss.We've looked in SQL BOL and a number of reference books, but there's nothing for this particular error.Any ideas ???Thanks in advance" |
|
|
Spyder
SQLTeam Author
75 Posts |
Posted - 2002-02-19 : 02:38:15
|
Since the machine has been running so long since a reboot it might be worth checking to see if someone may have changed the account that the MSSQLSERVER service is running under -- if so, the new login does not take effect until you stop and restart the service and it is possible that this change could have been made and then not noticed until you rebooted the machine -- the account running the MSSQLSERVER service needs to have full access to the directory where the log resides. |
 |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2002-02-19 : 11:40:00
|
| Was the errorlog file being accessed while you tried to start the server? Also, check permissions on the SQL drive, as well as all the directories.HTH-Chad |
|
|
|
|
|
|
SQL Server startup