durango099
asked on
SBS 2003 wsus / mssql$microsoft##ssee
Hi Experts-
Have a good one going here...
While attempting to resolve a WSUS 3.0 SP1 issue, a admin started the MS technet blog post about removing manually all of WSUS dated 5 Nov 2008, without knowing what the internal windows database does with SBS. I will run down what he did to this point:
Ran the Windows Installer Cleanup Utility pulling out WSUS and MICROSOFT##SSEE
Ran "net stop mssql$microsoft##ssee
Ran "sc delete mssql$microsoft##ssee
removed some registery keys
Noticed the sharepoint files in the \%windir%\SYSMSI\SSEE\MSSQ L\DATA dir and stopped
Good news is this:
1. Server has not been restarted
2. He backed up the registery before making any changes
3. Did not delete any files (so he says)
Can any or all of this be undone?
if so, how can I remount the internal database?
Currently in management studio the sbs\microsoft##ssee database is a white ball not running as well as wsus. The other sql databases are running.
The wsus did not uninstall correctly either as the attempt to install WSUS 3.0 SP2 reported an error that another database existed.
Thanks
Have a good one going here...
While attempting to resolve a WSUS 3.0 SP1 issue, a admin started the MS technet blog post about removing manually all of WSUS dated 5 Nov 2008, without knowing what the internal windows database does with SBS. I will run down what he did to this point:
Ran the Windows Installer Cleanup Utility pulling out WSUS and MICROSOFT##SSEE
Ran "net stop mssql$microsoft##ssee
Ran "sc delete mssql$microsoft##ssee
removed some registery keys
Noticed the sharepoint files in the \%windir%\SYSMSI\SSEE\MSSQ
Good news is this:
1. Server has not been restarted
2. He backed up the registery before making any changes
3. Did not delete any files (so he says)
Can any or all of this be undone?
if so, how can I remount the internal database?
Currently in management studio the sbs\microsoft##ssee database is a white ball not running as well as wsus. The other sql databases are running.
The wsus did not uninstall correctly either as the attempt to install WSUS 3.0 SP2 reported an error that another database existed.
Thanks
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
By reinstall, you are talking about wsus 3.0 SP2?
ASKER
the current config, they do not use the companyweb site. A different instance of sharepoint is being used and is working. So can I ignore the sharepoint suggestion?
"By reinstall, you are talking about wsus 3.0 SP2?"
yes
"the current config, they do not use the companyweb site. A different instance of sharepoint is being used and is working. So can I ignore the sharepoint suggestion?"
yes, we'll tackle if need be
yes
"the current config, they do not use the companyweb site. A different instance of sharepoint is being used and is working. So can I ignore the sharepoint suggestion?"
yes, we'll tackle if need be
ASKER
Thanks, I will do this after everyone leaves tonight and report the findings.
ASKER
Error running the 32bit command:
Windows Installer: This action is only valid for products that are currently installed
So it appears that the Windows Installer Cleanup did part of the work, but not all. I tried again to install WSUS and it fails saying that it is installed already.
Windows Installer: This action is only valid for products that are currently installed
So it appears that the Windows Installer Cleanup did part of the work, but not all. I tried again to install WSUS and it fails saying that it is installed already.
Are there any errors in your eventvwr under Application(WSUS related) ?
Have you tried opening the WSUS console ?
Have you tried opening the WSUS console ?
ASKER
when opening wsus, it said it could not connect to the server
in sql, the server is not running and will not start
in sql, the server is not running and will not start
Eventvwr errors?
Could you post your WSUSSetup.log ?
http://technet.microsoft.com/en-us/library/cc708547(WS.10).aspx
Could you post your WSUSSetup.log ?
http://technet.microsoft.com/en-us/library/cc708547(WS.10).aspx
ASKER
Here is the app log file...it's UGLY
ASKER
I could not upload the evt file, so I added .txt and here it is.
app-3-18-11.evt.txt
app-3-18-11.evt.txt
Wasnt asking for you to upload application log, I meant for you upload wsussetup.log
Is you server 32 or 64 bit?
At this point I would reinstall both WSUS and Sharepoint.
How to manually remove all of WSUS
http://blogs.technet.com/b/sus/archive/2008/11/05/how-to-manually-remove-all-of-wsus.aspx
I would also uninstall IIS/ASP.NET and reinstall these as well
This would be alot easier than trying to troubleshoot a botched uninstall/reinstall.
If you have a Server backup prior to this, you try that first.
Is you server 32 or 64 bit?
At this point I would reinstall both WSUS and Sharepoint.
How to manually remove all of WSUS
http://blogs.technet.com/b/sus/archive/2008/11/05/how-to-manually-remove-all-of-wsus.aspx
I would also uninstall IIS/ASP.NET and reinstall these as well
This would be alot easier than trying to troubleshoot a botched uninstall/reinstall.
If you have a Server backup prior to this, you try that first.
ASKER
Here is the wsussetup log
WSUSSetup.log
WSUSSetup.log
ASKER
That is the same technet blog post that started this...Thankfully, the admin stopped when he noticed the sql data directory also had the current used sharepoint database. That is the point that he stopped and called :)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Should I install the 2008 report viewer even though this is SBS2003?
After setting the auth on sql, what is the next step?
Thanks
After setting the auth on sql, what is the next step?
Thanks
Yes, 2008 only refers to the version
"After setting the auth on sql, what is the next step?"
Try to install WSUS again
Try to install WSUS again
ASKER
The auth setting is already there for the base <servername> database, though I can not check on the WSUS and MICROSOFT##SSEE databases as they will not start.
The report viewer installed okay, so try the WSUS install again anyway?
The report viewer installed okay, so try the WSUS install again anyway?
yes, then go over the WSUSsetup.log to review for any errors
ASKER
It stopped at what seems like a simple error now, saying that the WSUS database exists already and that I should move or delete the old database from \Windows\SYSMSI\SSEE\MSSQL .2005\MSSQ L\DATA
Do you know which files I should rename or delete from the data directory?
Do you know which files I should rename or delete from the data directory?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I've had to do this in the past
data.bmp
data.bmp
ASKER
I just need to make sure it will not kill the sharepoint database on :8081
ASKER
The WSUS failed again with the 0x80070643 error showing in the wsussetup log.
It did however install the internal database and it is not running.
I double checked the sysadmin settings in server roles and it is checked.
It did however install the internal database and it is not running.
I double checked the sysadmin settings in server roles and it is checked.
ASKER
I am currently installing updates and will attempt the WSUS install after they complete. Was a pretty long list of updates to be completed.
Thanks
Thanks
ASKER
After installing the Windows Updates, the WSUS install proceeded correctly.
Thanks for all your extra effort on this question...too bad there is not a bonus points system in place to award you for the time this took.
Thanks
Thanks for all your extra effort on this question...too bad there is not a bonus points system in place to award you for the time this took.
Thanks
Glad to help, I take more pride in being able to help than accumalating the points.
http://support.microsoft.com/kb/829114