Jobos Posted October 19, 2007 Report Posted October 19, 2007 Over the summer holiday we installed SQL2005 and ran it alongside SQL2000. All seemed ok. Last Wednesday I got round to uninstalling the old SQL2000 that wasn’t needed anymore. All went ok but today I have checked the server application logs and it is a sea of red! The error is from SQLBrowser and gives the error ‘The SQL configuration for SQL is inaccessible or invalid’ Event ID 1. Any ideas?
tech_guy Posted October 19, 2007 Report Posted October 19, 2007 Erm, I think you're supposed to run SQL2000 alongside SQL2005 until the November Sims.Net upgrade. Might be wrong on this though.
Jobos Posted October 19, 2007 Author Report Posted October 19, 2007 I was told to leave it for a month then uninstall it...
tech_guy Posted October 19, 2007 Report Posted October 19, 2007 That's what they've told us originally but then they said to leave it on 'as it won't do any harm'... Found this..... Anonymous (Last update 7/12/2006): In my case, this event occurred after the SQL Server 2000 databases had been deleted from the same box where SQL Server 2005 was installed as well. The SQL Browser service is part of the SQL Server 2005 and it was still looking for them. After a reboot, the error was gone.
Jobos Posted October 21, 2007 Author Report Posted October 21, 2007 Thanks. Looks like the same info I found. A reboot has stopped the error so it looks like it's fixed
PhilNeal Posted October 21, 2007 Report Posted October 21, 2007 SQL 2000 and 2005 can co-exist because SIMS might not be the only application using one or the other.
Jobos Posted October 21, 2007 Author Report Posted October 21, 2007 Quite… but it would be interesting to know how much resources are being used by unused services such as SQL2000 that are just sitting there?
DMcCoy Posted October 21, 2007 Report Posted October 21, 2007 I was cautious and deleted mine 10 mins after testing the 2005 instance
Oops_my_bad Posted October 21, 2007 Report Posted October 21, 2007 I was cautious and deleted mine 10 mins after testing the 2005 instance Same here Except it wasn't until I deleted it I found it was also hosting the backupexec job stuff
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now