Jump to content


MaceUK

SCCM 2012 R2 and WSUS Server - console and remote server versions do not match

Recommended Posts

Hi

 

Wondering is anyone can help.

 

I have SCCM 2012 R2 running on Windows Server 2008 R2, and my WSUS server is running on Windows Server 2012 R2.

 

My wsus has been integrated and was working fine. However in the last week i can now see this message appearing in my WCM log ...

 

PublishApplication(8427071A-DA80-48C3-97DE-C9C528F73A2D) failed with error System.InvalidOperationException: Publishing operation failed because the console and remote server versions do not match.

 

Agreed they don't match but this was working previously and the servers were syncing successfully.

 

Has anyone else had this issue or knows of a fix.

 

Would be really appreciated.

 

Here is my full WCM log File...

 

Checking runtime v2.0.50727... SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:21:58 6720 (0x1A40)
Found supported assembly Microsoft.UpdateServices.Administration version 3.1.6001.1, file version 3.1.7600.256 SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:21:58 6720 (0x1A40)
Found supported assembly Microsoft.UpdateServices.BaseApi version 3.1.6001.1, file version 3.1.7600.256 SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:21:58 6720 (0x1A40)
Supported WSUS version found SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:21:58 6720 (0x1A40)
Attempting connection to WSUS server: WSUS2012.sovereign.org.uk, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:21:58 6720 (0x1A40)
Successfully connected to server: WSUS2012.sovereign.org.uk, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:21:59 6720 (0x1A40)
Verify Upstream Server settings on the Active WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:21:59 6720 (0x1A40)
No changes - WSUS Server settings are correctly configured and Upstream Server is set to Microsoft Update SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:21:59 6720 (0x1A40)
WSUS Server configuration has been updated. Updating Group Info. SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:21:59 6720 (0x1A40)
Updating Group Info for WSUS. SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:21:59 6720 (0x1A40)
Refreshing categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:21:59 6720 (0x1A40)
Attempting connection to WSUS server: WSUS2012.sovereign.org.uk, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:21:59 6720 (0x1A40)
Successfully connected to server: WSUS2012.sovereign.org.uk, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:21:59 6720 (0x1A40)
Successfully refreshed categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:23:46 6720 (0x1A40)
Attempting connection to WSUS server: WSUS2012.sovereign.org.uk, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:23:51 6720 (0x1A40)
Successfully connected to server: WSUS2012.sovereign.org.uk, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:23:51 6720 (0x1A40)
Attempting connection to WSUS server: WSUS2012.sovereign.org.uk, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:23:52 6720 (0x1A40)
Successfully connected to server: WSUS2012.sovereign.org.uk, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:23:52 6720 (0x1A40)
Attempting connection to WSUS server: WSUS2012.sovereign.org.uk, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:23:53 6720 (0x1A40)
Successfully connected to server: WSUS2012.sovereign.org.uk, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:23:53 6720 (0x1A40)
PublishApplication(8427071A-DA80-48C3-97DE-C9C528F73A2D) failed with error System.InvalidOperationException: Publishing operation failed because the console and remote server versions do not match.~~ at Microsoft.UpdateServices.Internal.BaseApi.Publisher.LoadPackageMetadata(String sdpFile)~~ at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetPublisher(String sdpFile)~~ at Microsoft.SystemsManagementServer.WSUS.WSUSServer.PublishApplication(String sPackageId, String sSDPFile, String sCabFile) SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:23:53 6720 (0x1A40)
ERROR: Failed to publish sms client to WSUS, error = 0x80131509 SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:23:53 6720 (0x1A40)
STATMSG: ID=6613 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=SCCMSVR.sovereign.org.uk SITE=SHA PID=4304 TID=6720 GMTDATE=Wed Jan 07 09:23:53.245 2015 ISTR0="8427071A-DA80-48C3-97DE-C9C528F73A2D" ISTR1="5.00.7958.1000" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:23:53 6720 (0x1A40)
Failed to publish client with error = 0x80131509 SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:23:53 6720 (0x1A40)
completed checking for client deployment SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:23:53 6720 (0x1A40)
HandleSMSClientPublication failed. SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:23:53 6720 (0x1A40)
Waiting for changes for 58 minutes SMS_WSUS_CONFIGURATION_MANAGER 07/01/2015 09:23:53 6720 (0x1A40)

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.