krisnparker
asked on
MMC has detected an error in a snap in sbs 2008 wsus
Hi everyone,
I have an SBS 2008 R2 server in a small business which suddenly reported failed backups.
After a while I stopped the VSS service which then started the backups working again, but somewhat haphazardly.
BUT after stopping VSS service, for some reason WSUS stopped working. I have tried to use the Microsoft Technet article referred to by some queries in EE, entitled "Repair Windows Update Server Services. Latest update March 24 2009."
1) I cant delete the old WSUS directory because it reports that the folder is being used by another program.
2) If I cut and paste the command line command in an elevated cmd prompt. it seems to do something for about 5 secs then stop. Not the 10 mins referred to in the article.
3) if I then try to open the windows server update services plug in, I get the "MMC has detected an error in the snap in."
I am now at my wit's end and need some help desperately.
BTW: I generally do the administrative work remotely via VPN and remote desktop, because I am some distance away from the server.
Could this fact affect the ability to delete files etc?
Because there appear to be multiple problems with both the backup and the WSUS, I presume the SQL database is corrupt or something equally sinister, so how do I go back to first principles and solve the problem?
Please help.....
Kind regards
Chris
I have an SBS 2008 R2 server in a small business which suddenly reported failed backups.
After a while I stopped the VSS service which then started the backups working again, but somewhat haphazardly.
BUT after stopping VSS service, for some reason WSUS stopped working. I have tried to use the Microsoft Technet article referred to by some queries in EE, entitled "Repair Windows Update Server Services. Latest update March 24 2009."
1) I cant delete the old WSUS directory because it reports that the folder is being used by another program.
2) If I cut and paste the command line command in an elevated cmd prompt. it seems to do something for about 5 secs then stop. Not the 10 mins referred to in the article.
3) if I then try to open the windows server update services plug in, I get the "MMC has detected an error in the snap in."
I am now at my wit's end and need some help desperately.
BTW: I generally do the administrative work remotely via VPN and remote desktop, because I am some distance away from the server.
Could this fact affect the ability to delete files etc?
Because there appear to be multiple problems with both the backup and the WSUS, I presume the SQL database is corrupt or something equally sinister, so how do I go back to first principles and solve the problem?
Please help.....
Kind regards
Chris
ASKER
I have done the VSS admin list writers in an elevated cmd, and the last time I did it there were no errors. I will do it again with the service started and stopped. The only other remediation I did was to try to delete the WSUS folder as specified in the article by MICROSOFT.
Thanks for at least a response!
Much appreciated.
Thanks for at least a response!
Much appreciated.
ASKER
Please see the VSSadmin list writers list attached. as you can see there's no errors. I would like to change the points on the question, but can't see how to?
Help...
vss-admin-list.txt
Help...
vss-admin-list.txt
So you stopped the VSS services in an attempt to remediate backup failures? What prompted you do to so? Were there any clues in the backup history or in the event logs?
ASKER
It was one of the temporary solutions proposed in this forum, just to get backups happening, which was my main concern. Then the server reported that WSUS wasn't working. It seemed to be working on the server but not the clients. There was a continual failure on the server to update to the latest WSUS (v3??), which is what led me to check the client updates and saw the WSUS problem.
Thanks a lot for your help. I feel a bit helpless being in a remote spot in Australia. The difference in time zones doesn't help.
Thanks a lot for your help. I feel a bit helpless being in a remote spot in Australia. The difference in time zones doesn't help.
Because no one else is helping, I'm guessing the solution is not apparent from the information given. I know it is not to me. Can you please check your event viewer - windows logs for error conditions that might be relevant, then drill down to the details in the applications and services logs and the others in the lower half?
Event-Viewer.JPG
Event-Viewer.JPG
ASKER
Will do ASAP
ASKER
I think you have got me to the problem. the solution is another issue.
It appears that the Database is full. See JPG attached.
I have searched for a way to fix it but none of the solutions seem to have the same configuration and tools as this server.
I have also attached a picture of the SQL programs on the server, and the configuration snap in.
I have little or no experience with SQL and would really appreciate a step by step as to how to fix the data base.
Kind regards
Chris
eventlog.jpg
It appears that the Database is full. See JPG attached.
I have searched for a way to fix it but none of the solutions seem to have the same configuration and tools as this server.
I have also attached a picture of the SQL programs on the server, and the configuration snap in.
I have little or no experience with SQL and would really appreciate a step by step as to how to fix the data base.
Kind regards
Chris
eventlog.jpg
ASKER
ASKER
I have actually mangaged to fix it myself.
What I did was through a difficult process to delete a number of entries in the Database. I found that on one day for an hour, a number of the same errors occurred. About 2.5 gig worth. Considering that the whole Database was allowed a Max of 4 gig, it swamped the Database and it basically stopped working. After deleting I then found that a whole bunch of permissions were wrong and spent an hour setting the permissions as they should be.
I think from memory the date these errors occurred was the 16/05/2014. They never occurred again after that. I cannot remember the error code, but 3302 rings a bell!
I still have a slight problem with the WSUS, but am in the process of reinstalling it. At least the add in works and the console and the server as a whole is stable.
I am a bit disappointed with the response from EE but it forced me to delve into the guts of SQL and I learned a lot!
What I did was through a difficult process to delete a number of entries in the Database. I found that on one day for an hour, a number of the same errors occurred. About 2.5 gig worth. Considering that the whole Database was allowed a Max of 4 gig, it swamped the Database and it basically stopped working. After deleting I then found that a whole bunch of permissions were wrong and spent an hour setting the permissions as they should be.
I think from memory the date these errors occurred was the 16/05/2014. They never occurred again after that. I cannot remember the error code, but 3302 rings a bell!
I still have a slight problem with the WSUS, but am in the process of reinstalling it. At least the add in works and the console and the server as a whole is stable.
I am a bit disappointed with the response from EE but it forced me to delve into the guts of SQL and I learned a lot!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
Besides stopping the VSS have you done anything else to remediate?
There are a bazillion articles already on repairing VSS, including many on this forum. Have you looked at/tried any of them? Start by "vssadmin list writers" from an elevated command prompt. Check for any error conditions and let us know.