[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2304
  • Last Modified:

SCCM 2012 SMS_WSUS_SYNC_MANAGER Problem

I have a problem with SCCM 2012
I would like to mention that I am new to SCCM
I have a problem with SCCM 2012 WSUS sync. Let me try and explain what exactly happened SCCM 2012 was running on HYPER V machine on windows server 2012 because of space issue Hyper V machine where SCCM was running got paused and we could not re run the machine because there was no space available on physical server.
Then we decided to move the SCCM vhd file to another server since that there was lot of issues with SCCM I managed to resolve most of them but stuck with SCCM WSUS error cant seems to get around my head how to resolve the WSUS error (SMS_WSUS_SYNC_manager error)      
Initially Unser SITE STATUS Software update point was showing critical error status then I removed and re added SUP and WSUS role then critical error status changed to OK in SITE Status but under COMPONENT STATUS I am getting SMS_WSUS_SYNC_MANAGER status as critical hence software library is not showing any updates.
I am attaching the error message from Component status and wsyncmger.log
Help me resolve the issue .
SMS-WSUS-SYNC-MANAGER.txt
wsyncmgr.log.txt
0
SreenivasreddyRanabothu
Asked:
SreenivasreddyRanabothu
  • 2
1 Solution
 
Marten RuneCommented:
Youre database is most likely corrupt. The message "Microsoft SQL Server reported SQL message 605, severity 212" leeds me to:  http://technet.microsoft.com/en-us/library/aa258728(v=sql.80).aspx

The first thing you do is a backup. This way you can try the various options you have.

Your number one fix is to simply restore an older backup.
Do you have this. (Yeah problem solved, still read the sqlservercentral article)
If not. You're stuck with no easy fix for a corrupt database.

In all cases, you really should read this: http://www.sqlservercentral.com/articles/Corruption/65804/

The CHECKDB syntax is: DBCC CHECKDB (DatabaseName,REPAIR_FAST)
As an example.

If you don't have a good backup. Then AFTER you backed up your corrupt database. Try the REPAIR options in this order:
REPAIR_FAST
REPAIR_REBUILD
and the dreaded
REPAIR_ALLOW_DATA_LOSS
wich does what it says. It may leave you with a transactionally inconsistent database. But usable though.

Regards Marten
0
 
SreenivasreddyRanabothuAuthor Commented:
Dear Experts,

Issues was resolved.

Issue has arisen when we have moved the virtual machine from one Hyper-V host to another Hyper-V host. Since it was properly booting and was giving some errors as stated, we were caught up in resolving the issues one by one. However, finally one of our friend has suggested to combine the all VHDs created during the snapshot process and try. Surprisingly this trick worked.

Thank you very much for all those who have given a thought to this problem.
0
 
SreenivasreddyRanabothuAuthor Commented:
It worked.
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now