talksr Posted May 30, 2022 Posted May 30, 2022 Hi there, We have a WSUS server which is constantly crashing. After spending a considerable amount of time trying everything already covered on these forums, it just wouldn't work, so we have uninstalled it, cleared all previous files and now we are trying to re-install. Rather than use WID, we are trying to use SQL. We are unable to proceed through the WSUS installer as it can't connect to our local SQL server instance. If I try and connect to SQL Server Management Studio, I am getting errors stating that the server was not found when trying to connect to \\server\SQLEXPRESS I have not changed any default instance names for SQL and it was showing SQLEXPRESS before I removed WSUS. If I open SQL Server Configuration Manager, this is what I am seeing: Can anyone tell me what I can do to rectify this. The server has Backup Excel which is what the two names are at the top of the list. I don't really want to mess the backups up. Thanks in advance.
Steve21 Posted May 30, 2022 Posted May 30, 2022 (edited) Have you actually installed a separate SQL instance? As that's only showing the BKUPEXEC instance, and you're trying to connect to SQLEXPRESS which would by why it's erroring You'd need to run the SQL Express installer and set that up as a separate one if you didn't want to mix the same instance between both items (Edit - As a side note, it shouldn't mess anything up by just adding a new SQL database into the current instance, so that's another option, but honestly both will work fine for something so small) Steve Edited May 30, 2022 by Steve21 1
talksr Posted May 31, 2022 Author Posted May 31, 2022 Have you actually installed a separate SQL instance? As that's only showing the BKUPEXEC instance, and you're trying to connect to SQLEXPRESS which would by why it's erroring You'd need to run the SQL Express installer and set that up as a separate one if you didn't want to mix the same instance between both items (Edit - As a side note, it shouldn't mess anything up by just adding a new SQL database into the current instance, so that's another option, but honestly both will work fine for something so small) Steve I had not, thanks for the tips, I have never messed around with SQL. I re-ran the installer and added it back in. All working perfectly now. Thanks very much:D
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