Skip to main content

Synchronization problem with sccm 2012 with remote wsus 3.0 SP2

When SCCM 2012 is integrated with remote WSUS 3.0 SP2 server, synchronization problems occured. In the wsyncmgr log file there are some logs about the problem. Log files are under Program Files\Microsoft Configuration Manager\Logs folder.

Performing sync on retry schedule  $$<SMS_WSUS_SYNC_MANAGER><05-10-2012 14:10:05.829-180><thread=3452 (0xD7C)>
STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=wssccm01 SITE=DFG PID=1684 TID=3452 GMTDATE=Thu May 10 11:10:05.831 2012 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_WSUS_SYNC_MANAGER><05-10-2012 14:10:05.831-180><thread=3452 (0xD7C)>
Sync failed: WSUS server not configured. Please refer to WCM.log for configuration error details.. Source: CWSyncMgr::DoSync  $$<SMS_WSUS_SYNC_MANAGER><05-10-2012 14:15:05.922-180><thread=3452 (0xD7C)>
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=wssccm01 SITE=DFG PID=1684 TID=3452 GMTDATE=Thu May 10 11:15:05.924 2012 ISTR0="CWSyncMgr::DoSync" ISTR1="WSUS server not configured. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_WSUS_SYNC_MANAGER><05-10-2012 14:15:05.925-180><thread=3452 (0xD7C)>
Sync failed. Will retry in 60 minutes  $$<SMS_WSUS_SYNC_MANAGER><05-10-2012 14:15:05.945-180><thread=3452 (0xD7C)>
Setting sync alert to active state on site DFG  $$<SMS_WSUS_SYNC_MANAGER><05-10-2012 14:15:05.947-180><thread=3452 (0xD7C)>

On the SCCM server, i installed WSUS Admin console only. After that synchronization problem solved. Logs look normal.

Synchronizing WSUS server WSSCWUS $$<SMS_WSUS_SYNC_MANAGER><05-10-2012 14:24:35.496-180><thread=3452 (0xD7C)>
Using account wsusadm to connect to WSUS Server  $$<SMS_WSUS_SYNC_MANAGER><05-10-2012 14:24:35.510-180><thread=3452 (0xD7C)>
Synchronizing WSUS server wsscwus ...  $$<SMS_WSUS_SYNC_MANAGER><05-10-2012 14:24:35.622-180><thread=3844 (0xF04)>
sync: Starting WSUS synchronization  $$<SMS_WSUS_SYNC_MANAGER><05-10-2012 14:24:35.626-180><thread=3844 (0xF04)>
sync: WSUS synchronizing categories  $$<SMS_WSUS_SYNC_MANAGER><05-10-2012 14:24:39.155-180><thread=3844 (0xF04)>
sync: WSUS synchronizing updates  $$<SMS_WSUS_SYNC_MANAGER><05-10-2012 14:24:43.436-180><thread=3844 (0xF04)>
sync: WSUS synchronizing updates, processed 901 out of 7264 items (12%), ETA in 00:07:03  $$<SMS_WSUS_SYNC_MANAGER><05-10-2012 14:25:44.370-180><thread=3844 (0xF04)>
sync: WSUS synchronizing updates, processed 1340 out of 7264 items (18%), ETA in 00:08:50  $$<SMS_WSUS_SYNC_MANAGER><05-10-2012 14:26:44.421-180><thread=3844 (0xF04)>
sync: WSUS synchronizing updates, processed 1563 out of 7264 items (21%), ETA in 00:11:18  $$<SMS_WSUS_SYNC_MANAGER><05-10-2012 14:27:49.723-180><thread=3844 (0xF04)>
sync: WSUS synchronizing updates, processed 1843 out of 7264 items (25%), ETA in 00:12:03  $$<SMS_WSUS_SYNC_MANAGER><05-10-2012 14:28:50.168-180><thread=3844 (0xF04)>
sync: WSUS synchronizing updates, processed 2230 out of 7264 items (30%), ETA in 00:11:33  $$<SMS_WSUS_SYNC_MANAGER><05-10-2012 14:29:50.770-180><thread=3844 (0xF04)>
sync: WSUS synchronizing updates, processed 2663 out of 7264 items (36%), ETA in 00:10:35  $$<SMS_WSUS_SYNC_MANAGER><05-10-2012 14:30:51.668-180><thread=3844 (0xF04)>
sync: WSUS synchronizing updates, processed 3119 out of 7264 items (42%), ETA in 00:09:30  $$<SMS_WSUS_SYNC_MANAGER><05-10-2012 14:31:53.256-180><thread=3844 (0xF04)>
sync: WSUS synchronizing updates, processed 3490 out of 7264 items (48%), ETA in 00:08:49  $$<SMS_WSUS_SYNC_MANAGER><05-10-2012 14:32:53.990-180><thread=3844 (0xF04)>
sync: WSUS synchronizing updates, processed 4083 out of 7264 items (56%), ETA in 00:07:09  $$<SMS_WSUS_SYNC_MANAGER><05-10-2012 14:33:54.567-180><thread=3844 (0xF04)>
sync: WSUS synchronizing updates, processed 4681 out of 7264 items (64%), ETA in 00:05:37  $$<SMS_WSUS_SYNC_MANAGER><05-10-2012 14:34:54.925-180><thread=3844 (0xF04)>
sync: WSUS synchronizing updates, processed 5252 out of 7264 items (72%), ETA in 00:04:17  $$<SMS_WSUS_SYNC_MANAGER><05-10-2012 14:35:55.315-180><thread=3844 (0xF04)>
sync: WSUS synchronizing updates, processed 5851 out of 7264 items (80%), ETA in 00:02:56  $$<SMS_WSUS_SYNC_MANAGER><05-10-2012 14:36:55.800-180><thread=3844 (0xF04)>
sync: WSUS synchronizing updates, processed 6395 out of 7264 items (88%), ETA in 00:01:47  $$<SMS_WSUS_SYNC_MANAGER><05-10-2012 14:37:56.525-180><thread=3844 (0xF04)>
sync: WSUS synchronizing updates, processed 6892 out of 7264 items (94%), ETA in 00:00:46  $$<SMS_WSUS_SYNC_MANAGER><05-10-2012 14:38:57.236-180><thread=3844 (0xF04)>
sync: WSUS synchronizing updates, processed 7264 out of 7264 items (100%)  $$<SMS_WSUS_SYNC_MANAGER><05-10-2012 14:39:30.104-180><thread=3844 (0xF04)>
Done synchronizing WSUS Server wsscwus $$<SMS_WSUS_SYNC_MANAGER><05-10-2012 14:39:30.107-180><thread=3844 (0xF04)>

Comments

Popular posts from this blog

Creating Multiple VLANs over Bonding Interfaces with Proper Routing on a Centos Linux Host

In this post, I am going to explain configuring multiple VLANs on a bond interface. First and foremost, I would like to describe the environment and give details of the infrastructure. The server has 4 Ethernet links to a layer 3 switch with names: enp3s0f0, enp3s0f1, enp4s0f0, enp4s0f1 There are two bond interfaces both configured as active-backup bond0, bond1 enp4s0f0 and enp4s0f1 interfaces are bonded as bond0. Bond0 is for making ssh connections and management only so corresponding switch ports are not configured in trunk mode. enp3s0f0 and enp3s0f1 interfaces are bonded as bond1. Bond1 is for data and corresponding switch ports are configured in trunk mode. Bond0 is the default gateway for the server and has IP address 10.1.10.11 Bond1 has three subinterfaces with VLAN 4, 36, 41. IP addresses are 10.1.3.11, 10.1.35.11, 10.1.40.11 respectively. Proper communication with other servers on the network we should use routing tables. There are three

Sending Jboss Server Logs to Logstash Using Filebeat with Multiline Support

In addition to sending system logs to logstash, it is possible to add a prospector section to the filebeat.yml for jboss server logs. Sometimes jboss server.log has single events made up from several lines of messages. In such cases Filebeat should be configured for a multiline prospector. Filebeat takes lines do not start with a date pattern (look at pattern in the multiline section "^[[:digit:]]{4}-[[:digit:]]{2}-[[:digit:]]{2}" and negate section is set to true ) and combines them with the previous line that starts with a date pattern. server.log file excerpt where DatePattern: yyyy-MM-dd-HH and ConversionPattern: %d %-5p [%c] %m%n Logstash filter: