WSUS 3.0 SQL Error.

I recently updated some firmware on a Dell PE which is our WSUS 3.0SP2 server, and now am getting the following error:

The SQL Server VSS Writer service failed to start due to the following error:
This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem.

When I run the console to connect to WSUS, I also get the following error:

Resolve Partial Assembly failed for Microsoft.VC80.ATL. Reference error message: The referenced assembly is not installed on your system.

I do not use a full version of SQL Server, just what WSUS installs.  Any ideas on how to correct this without re-installing WSUS?
ECO_RVAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

neubdaCommented:
Sorry, don't know much about wsus but you should go after the visual c error message. Did you try to install the Microsoft Visual C++ 2008 Redistributable Package ?
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=9b2da534-3e03-4391-8a4d-074b9f2bc1bf
0
ECO_RVAuthor Commented:
I thought about the Visual C error, and I tried it as per your suggestion which DID indeed get rid of the second error, but not the first.  Thanks for helping with a piece of the problem!  Now I just need to get an answer for the SQL server VSS writer.
0
DonNetwork AdministratorCommented:
Windows Internal Database is the database that gets installed by WSUS  
Run the workaround mentioned here
 
http://support.microsoft.com/kb/929665
To work around this issue, repair Windows Internal Database. To do this, run the following command line at a command prompt:
 Msiexec /i SSEE_10.msi CALLERID=OCSetup.exe REINSTALL=ALL REINSTALLMODE=omus /qn REBOOT=ReallySupress /l*v <Log_File_Path>
0
Protecting & Securing Your Critical Data

Considering 93 percent of companies file for bankruptcy within 12 months of a disaster that blocked access to their data for 10 days or more, planning for the worst is just smart business. Learn how Acronis Backup integrates security at every stage

arnoldCommented:
Does this server have any other application?
Check the services for a service that has a defined user credential set for the logon as.
This might be the issue.
What version of sql do you have?  Were all applicable patches/updates applied?

I suspect that the sql 2005 with visual studio 2008 visual C error might be part of the issue.
0
DonNetwork AdministratorCommented:
here's better steps on how to do that
1. At a command prompt, move to the folder where the WSUSSetup.exe file is located.
2. Type the following command, and then press ENTER: WSUSsetup.exe /x
  This command extracts the files into the current directory.
3.  Type the following command, and then press ENTER: cd wyukon
4. Type the following command, and then press ENTER:
 msiexec /i SSEE_10.msi CALLERID=OCSetup.exe REINSTALL=ALL REINSTALLMODE=omus /qn REBOOT=ReallySupress /l*v logfile_name
Note In this step, logfile_name represents the name of the log file. For example, you can use "Output.log."
5.  Start the Services snap-in.
6. Start the Windows Internal Database (MICROSOFT ##SSEE) service.
 
extracted from http://support.microsoft.com/kb/940194
 
0
ECO_RVAuthor Commented:
Thanks for the ideas dstewartjr, unfortunately neither suggestion worked.  I still get error listed above and the SQL Server VSS writer service will not start.  I am also still getting the side by side errors listed above when I reboot, so I guess the C++ redistributable did not fix the second issue after all.  The SQL Server VSS writer service logs on with the local system account and I tried a few others to see if it was a password issue, but no luck.

Arnold, I am not using SQL other than the VSS writer which was installed with WSUS 3.0.
0
DonNetwork AdministratorCommented:
Try running the sqlwriter.msi installer to see if it repairs
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ECO_RVAuthor Commented:
That was the fix.  Once I ran the sqlwriter and rebooted, all was fine.  Thanks for the help!
0
DonNetwork AdministratorCommented:
Glad to help
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server Apps

From novice to tech pro — start learning today.