June 25, 2004 at 8:52 am
I attempted to change the location of the SQL Server error logs for a 2000 named instance by changing the -e startup parameter to reflect a different path. After making the change, starting the MSSQL service for the instance results in the service message "The MSSQL$SQL2000 service on Local Computer started then stopped. Some services stop automatically if they have no work to do, for example, the Perrformance Logs and Alert service." I am unable to successfully start and access this instance. Can anyone help?
June 25, 2004 at 12:09 pm
Did you change any other parameters?
Like the -d?
June 25, 2004 at 12:30 pm
No, I only changed the -e parameter.
June 25, 2004 at 12:51 pm
Have you tried changing it back?
Steve (not Jones)
June 25, 2004 at 2:16 pm
When I attempt to look at server properties thru EM with the service stopped, it tries to start the service but it give me a 'server not found or access denied' message because I believe the service starts and immediately stops.
June 25, 2004 at 3:37 pm
Go into Control Panel, Administrative Tools, Services, find the MSSQLSERVER service, right click, select properties, then you should be able to modify the startup parameters.
Steve
June 25, 2004 at 3:51 pm
I tried that. I get the same message "The MSSQL$SQL2000 service on Local Computer started then stopped. Some services stop automatically if they have no work to do, for example, the Perrformance Logs and Alert service."
June 25, 2004 at 8:49 pm
Try to modify the registry to change it back and see what is going to happen and post back.
June 25, 2004 at 9:37 pm
Hi, you have spent so much time trying to fix your problem, I would by this time probably re-install. Since your SQL Server is stopped anyway, copy out (save ) DATA folder containing your and system databases and if you backed up something to Bakup folder, copy it out too. Also if you created your databases in some other locations, save them too. Uninstall SQL Server named instance, install again with exactly same installation options and names like you did the first time. Stop SQL Server instance. Move somewhere NEW DATA directory. Replace it with original DATA directory. See if it works. If not, stop SQL Server instance again, replace Master database files with the fresh ones from the second installation. Start SQL server instance. Attach all your databases.
Yelena
Regards,Yelena Varsha
June 28, 2004 at 8:47 am
Try starting sql server from the command line not as a service with the -c option
sqlservr -c.
If it still doesn't start, start it with -e option and provide the alternate error log location. Once it starts, you can go to enterprise manager and should be able to change the location.
If it doesn't start, post the error on the newsgroup.
the sqlservr.exe shoudl be under \mssql\binn directory.
June 28, 2004 at 9:11 am
When I tried starting sql server from the command line, I got a message that my 'Sql server installation is either corrupt or has been tampered with'. I'm throwing in the towel and re-installing.
Thanks everyone for all your help!
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply