heckle Posted January 23, 2013 Posted January 23, 2013 Setup: Server 2012 Data Center 64bit SQL 2012 SP1 SCCM 2012 SP1 We have the SCCM SP1 and SQL 2012 SP1 installed on Server 2012 Datacenter. Everything is setup and "talking". However when we try to setup a Software Update Server (on the same box) WSUS will not work. It does not download any updates and is talking to the SQL 2012 database. The WSUS Role was installed after SQL and before SCCM. So it should all be talking properly but it is not. We are currently at a dead end on figuring out what to do next and looking for any tips or suggestions. Thanks.
FN-GM Posted January 23, 2013 Posted January 23, 2013 What did you do you come to conclusion its not working? Can you throw as much detail as possible please? THanks
heckle Posted January 23, 2013 Author Posted January 23, 2013 The WSUS service would not start. It would not start downloading any updates. When I get to work in the morning I can try to get some log files to post. Any log specifically I should look for?
Gatt Posted January 24, 2013 Posted January 24, 2013 SCCM should handle all the WSUS stuff once the role is instlalled and you have configured the role and the components Role : \Administration\Overview\Site Configuration\Servers and Site System Roles Component: \Administration\Overview\Site Configuration\Sites - Configure Site Components on the ribbon -> Software Update Point. Once these are configured, it should just be a case of going to the Software Updates branch and running a full Sync. Are you using HTTP or HTTPS for WSUS? (Some extra configuration of WSUS might be needed for SSL Is WSUS on the same server or its own? What does it say under \Monitoring\Overview\Software Update Point Synchronization Status ? If you can get us the wsyncmgr.log we can take a look and see if there is anything obvious.
heckle Posted January 24, 2013 Author Posted January 24, 2013 (edited) Here is a snip of the bottom part of the wsyncmgr.log Found 1 SUPs $$<01-24-2013 07:00:02.290+300> Found active SUP SDE-SCCM930 from SCF File.~ $$<01-24-2013 07:00:02.305+300> DB Server not detected for SUP SDE-SCCM930 from SCF File. skipping.~ $$<01-24-2013 07:00:02.305+300> Sync failed: WSUS update source not found on site P30. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource $$<01-24-2013 07:00:02.321+300> STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=SDE-SCCM930 SITE=P30 PID=3948 TID=6884 GMTDATE=Thu Jan 24 12:00:02.321 2013 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found on site P30. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<01-24-2013 07:00:02.321+300> Sync failed. Will retry in 60 minutes $$<01-24-2013 07:00:02.336+300> Setting sync alert to active state on site P30 $$<01-24-2013 07:00:02.336+300> Sync time: 0d00h00m00s $$<01-24-2013 07:00:02.352+300> Wakeup for a polling cycle $$<01-24-2013 08:00:02.575+300> Starting Sync $$<01-24-2013 08:00:02.590+300> Performing sync on retry schedule $$<01-24-2013 08:00:02.606+300> Read SUPs from SCF for SDE-SCCM930.exec.ds.state.ct.us $$<01-24-2013 08:00:02.606+300> Found 1 SUPs $$<01-24-2013 08:00:02.622+300> Found active SUP SDE-SCCM930 from SCF File.~ $$<01-24-2013 08:00:02.637+300> DB Server not detected for SUP SDE-SCCM930 from SCF File. skipping.~ $$<01-24-2013 08:00:02.637+300> Sync failed: WSUS update source not found on site P30. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource $$<01-24-2013 08:00:02.653+300> STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=SDE-SCCM930 SITE=P30 PID=3948 TID=6884 GMTDATE=Thu Jan 24 13:00:02.653 2013 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found on site P30. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<01-24-2013 08:00:02.653+300> Sync failed. Will retry in 60 minutes $$<01-24-2013 08:00:02.669+300> Setting sync alert to active state on site P30 $$<01-24-2013 08:00:02.669+300> Sync time: 0d00h00m00s $$<01-24-2013 08:00:02.669+300> Wakeup for a polling cycle $$<01-24-2013 09:00:02.863+300> Starting Sync $$<01-24-2013 09:00:02.878+300> Performing sync on retry schedule $$<01-24-2013 09:00:02.894+300> Read SUPs from SCF for SDE-SCCM930 $$<01-24-2013 09:00:02.894+300> Found 1 SUPs $$<01-24-2013 09:00:02.909+300> Found active SUP SDE-SCCM930 from SCF File.~ $$<01-24-2013 09:00:02.909+300> DB Server not detected for SUP SDE-SCCM930 from SCF File. skipping.~ $$<01-24-2013 09:00:02.925+300> Sync failed: WSUS update source not found on site P30. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource $$<01-24-2013 09:00:02.925+300> STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=SDE-SCCM930.exec.ds.state.ct.us SITE=P30 PID=3948 TID=6884 GMTDATE=Thu Jan 24 14:00:02.941 2013 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found on site P30. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<01-24-2013 09:00:02.941+300> Sync failed. Will retry in 60 minutes $$<01-24-2013 09:00:02.941+300> Setting sync alert to active state on site P30 $$<01-24-2013 09:00:02.956+300> Sync time: 0d00h00m00s $$<01-24-2013 09:00:02.956+300> Edited January 24, 2013 by heckle
heckle Posted January 24, 2013 Author Posted January 24, 2013 When we installed the software, it prompted for us to install the ADK which we did. We selected all the options. Party of that was to install SQLExpress. Could that have caused some problem?
Gatt Posted January 24, 2013 Posted January 24, 2013 Looking at the log I'm seeing this error: DB Server not detected for SUP SDE-SCCM930 from SCF File. skipping. Sync failed: WSUS update source not found on site P30. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource What DB is the WSUS using? is it installed on SQL 2012 What version of WSUS (3.0 SP2 or the newer version with Server 2012?) **I don't have 2012 setup yet so not sure of any pitfalls with it...** It might be worth removing the WSUS role from SCCM and un-installing WSUS too.
heckle Posted January 24, 2013 Author Posted January 24, 2013 Looking at the log I'm seeing this error: DB Server not detected for SUP SDE-SCCM930 from SCF File. skipping. Sync failed: WSUS update source not found on site P30. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource What DB is the WSUS using? is it installed on SQL 2012 What version of WSUS (3.0 SP2 or the newer version with Server 2012?) **I don't have 2012 setup yet so not sure of any pitfalls with it...** It might be worth removing the WSUS role from SCCM and un-installing WSUS too. Which version? Whatever version that was installed automatically when we installed the role. So it is probably the newer version. I am nto sure what DB it is using. We just went with the defaults. I did find this in the WCM.log Set DBServerName property in SCF to 'SDE-SCCM930.exec.ds.state.ct.us\MICROSOFT##WID' on this site for SDE-SCCM930.exec.ds.state.ct.us.~ $$<01-23-2013 12:45:08.557+300>
Gatt Posted January 24, 2013 Posted January 24, 2013 Which version? Whatever version that was installed automatically when we installed the role. So it is probably the newer version. I am nto sure what DB it is using. We just went with the defaults. I did find this in the WCM.log Set DBServerName property in SCF to 'SDE-SCCM930.exec.ds.state.ct.us\MICROSOFT##WID' on this site for SDE-SCCM930.exec.ds.state.ct.us.~ $$<01-23-2013 12:45:08.557+300> Ok, looks like its running on the Windows Internal Database then. Only 2 options I can think of are to remove WSUS and the SUP role from SCCM and either reinstall it as above with Windows Internal DB or use SQL for its DB Or, build a separate WSUS server runniing 2008 r2 (WSUS 3.0 SP2 + Hotfixes)
heckle Posted January 25, 2013 Author Posted January 25, 2013 Thanks Gatt. I think tomorrow I will remove WSUS and SUP then reinstall it and try to have it use SQL. If that fails, I will just end up doing a format and reinstall. Ok, looks like its running on the Windows Internal Database then. Only 2 options I can think of are to remove WSUS and the SUP role from SCCM and either reinstall it as above with Windows Internal DB or use SQL for its DB Or, build a separate WSUS server runniing 2008 r2 (WSUS 3.0 SP2 + Hotfixes)
Gatt Posted January 25, 2013 Posted January 25, 2013 Thanks Gatt. I think tomorrow I will remove WSUS and SUP then reinstall it and try to have it use SQL. If that fails, I will just end up doing a format and reinstall. Let me know how you get on
heckle Posted January 25, 2013 Author Posted January 25, 2013 I removed the SUP and WSUS. But I could not get the WID to remove. In the process of a reload right now.
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