SMS Server 6703 - SMS WSUS Synchronization Failed

Hi,
i am getting the following error on SCCM server,
"on 3/6/2011 12:00:00 PM component SMS_WSUS_SYNC_MANAGER on computer "ComputerName" reported: SMS WSUS Synchronization failed. Message: WSUS server not configured. Source: CWSyncMgr::DoSync. The operating system
reported error 2147500037: Unspecified error " with message ID 6703
i have SCCM server and WSUS server, it was working suddenly it started behaving as above.
i have check all SUP configuration, Proxy Settings, and all related.
why it is unable to sync with WSUS server, any idea ?\
Regards

Hi Owais,
I've found a few more posts with the same error you mentioned.
Problems Synchronizing System Center Configuration Manager Software Updates "SMS WSUS Synchronization Failed":
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Systems_Management_Server/Q_24025939.html
which mentions: Found a useful tip that solved this problem for me in a SCCM/WSUS installation on the same server. It all comes down to removing the FQDN in the SUP role. Do this by removing the SUP role and reinstalling it. Uncheck the FQDN checkbox and
it works (at least it did in my case).
WSUS Error:
http://social.technet.microsoft.com/Forums/en-US/configmgrsum/thread/98c8b384-7e15-4143-820f-ff165ec7623e
WSUS SERVER not configured (Error 6703):
http://www.myitforum.com/forums/tm.aspx?high=&m=179760&mpage=1#179760
which mentions: I have check Automatic Detect Setting and I have filled proxy address and it works !!!!
Regards, Henk
My ConfigMgr blog: http://henkhoogendoorn.blogspot.com Follow me on Twitter: @henkhoogendoorn

Similar Messages

SCCM WSUS Synchronization fails with error 0x80131904

With no reason the software update point in SCCM 2012 CU3 fails to synchronize update from the local installed WSUS service. I have checked the WSUS Sync manager log and what I have got is in the image below. I have tried to uninstall and the WSUS service
and reinstalled it but no success. I have also used the clean up option from the WSUS console and no success yet.
From the log below I am quite sure that if I can force the removal or clean up those updates that are failing to get saved the SCCM Update point synchronization might be able to fully synchronize. I hope someone can help me out. Thanks in advance.
Event view error - 2148734208
Wsyncmgr.log

I need WCM.log for investigation. Please upload this file to Skydrive and post the link here.
Juke Chou
TechNet Community Support

SCCM 2012 and WSUS Synchronization error. Message ID: 6703.

Hi,
I am facing issues with synchronising updates in WSUS server with SUP in SCCM 2012. I am using web proxy, which has full access to all microsoft update websites. I have configures SUP for both intranet and internet clinets. I am posting some logs below
that may help to resolve the issue:-
wsyncmgr.log-
Synchronizing WSUS server SCCMSERVER.domain.com SMS_WSUS_SYNC_MANAGER 11/1/2012 11:56:35 AM 3824 (0x0EF0)
sync: Starting WSUS synchronization SMS_WSUS_SYNC_MANAGER 11/1/2012 11:56:35 AM 6368 (0x18E0)
Sync failed: UssCommunicationError: WebException: The remote name could not be resolved: 'www.update.microsoft.com'~~at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context). Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS SMS_WSUS_SYNC_MANAGER 11/1/2012
11:58:04 AM 3824 (0x0EF0)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=CDCTIBCMSCCM.India.TCS.com SITE=I1P PID=2648 TID=3824 GMTDATE=Thu Nov 01 06:28:04.549 2012 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS"
ISTR1="UssCommunicationError: WebException: The remote name could not be resolved: 'www.update.microsoft.com'~~at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9=""
NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 11/1/2012 11:58:04 AM 3824 (0x0EF0)
Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER 11/1/2012 11:58:04 AM 3824 (0x0EF0)
WCM.log-
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001 SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:05 AM 4016 (0x0FB0)
The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.7600.226) SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:05 AM 4016 (0x0FB0)
Successfully connected to server: SCCMSERVER.domain.com, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:05 AM 4016 (0x0FB0)
Verify Upstream Server settings on the Active WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:05 AM 4016 (0x0FB0)
WSUS Server settings are correctly configured and Upstream Server is set to Microsoft Update SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:05 AM 4016 (0x0FB0)
Successfully connected to server: SCCMSERVER.domain.com, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:05 AM 4016 (0x0FB0)
Successfully got update categories from WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:16 AM 4016 (0x0FB0)
Successfully connected to server: SCCMSERVER.domain.com, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:16 AM 4016 (0x0FB0)
Successfully got update classifications from WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:16 AM 4016 (0x0FB0)
Successfully connected to server: SCCMSERVER.domain.com, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:16 AM 4016 (0x0FB0)
Successfully got update languages from WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:16 AM 4016 (0x0FB0)
Successfully connected to server: SCCMSERVER.domain.com, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:21 AM 4016 (0x0FB0)
Subscribed Update Categories <?xml version="1.0" ?>~~<Categories>~~ <Id>1403f223-a63f-f572-82ba-c92391218055</Id>~~ <Id>041e4f9f-3a3d-4f58-8b2f-5e6fe95c4591</Id>~~ <Id>84f5f325-30d7-41c4-81d1-87a0e6535b66</Id>~~ <Id>bfe5b177-a086-47a0-b102-097e4fa1f807</Id>~~ <Id>8c3fcc84-7410-4a95-8b89-a166a0190486</Id>~~ <Id>cb263e3f-6c5a-4b71-88fa-1706f9549f51</Id>~~ <Id>5312e4f1-6372-442d-aeb2-15f2132c9bd7</Id>~~ <Id>7f44c2a7-bc36-470b-be3b-c01b6dc5dd4e</Id>~~ <Id>dbf57a08-0d5a-46ff-b30c-7715eb9498e9</Id>~~ <Id>fdfe8200-9d98-44ba-a12a-772282bf60ef</Id>~~ <Id>ec9aaca2-f868-4f06-b201-fb8eefd84cef</Id>~~ <Id>ba0ae9cc-5f01-40b4-ac3f-50192b5d6aaf</Id>~~ <Id>90e135fb-ef48-4ad0-afb5-10c4ceb4ed16</Id>~~ <Id>26997d30-08ce-4f25-b2de-699c36a8033a</Id>~~ <Id>a4bedb1d-a809-4f63-9b49-3fe31967b6d0</Id>~~ <Id>4cb6ebd5-e38a-4826-9f76-1416a6f563b0</Id>~~ <Id>558f4bc3-4827-49e1-accf-ea79fd72d4c9</Id>~~ <Id>6964aab4-c5b5-43bd-a17d-ffb4346a8e1d</Id>~~</Categories> SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012
11:52:21 AM 4016 (0x0FB0)
Subscribed Update Classifications <?xml version="1.0" ?>~~<Classifications>~~ <Id>e6cf1350-c01b-414d-a61f-263d14d133b4</Id>~~ <Id>0fa1201d-4330-4fa8-8ae9-b877473b6441</Id>~~ <Id>28bc880e-0592-4cbf-8f95-c79b17911d5f</Id>~~ <Id>cd5ffd1e-e932-4e3a-bf74-18bf0b1bbd83</Id>~~</Classifications> SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012
11:52:22 AM 4016 (0x0FB0)
WSUSCtrl.log-
WSUS registry key change notification triggered. SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.0.6000.273, Major Version = 0x30000, Minor Version = 0x17700111 SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001 SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.7600.226) SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
System.Net.WebException: The request failed with HTTP status 403: Forbidden.~~ at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~ at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()~~
at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber) SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
Failed to set WSUS Local Configuration. Will retry configuration. SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
Waiting for changes for 57 minutes SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
Urgent Help Appreciated.
Thanks,
Deepak

STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=CDCTIBCMSCCM.India.TCS.com SITE=I1P PID=2648 TID=3824 GMTDATE=Thu Nov 01 06:28:04.549 2012 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS"
ISTR1="UssCommunicationError: WebException: The remote name could not be resolved: 'www.update.microsoft.com'~~at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7=""
ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 11/1/2012 11:58:04 AM 3824 (0x0EF0)
System.Net.WebException: The request failed with HTTP status 403: Forbidden.~~ at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~ at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()~~
at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber) SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
Those errors are unrelated to ConfigMgr. The first one is a name resolution error; the second one tells that the servers is not allowed to connect to the proxy.
Torsten Meringer | http://www.mssccmfaq.de

Is there anyway to integrate sms server with Peoplesoft 8.52

Hii,
My client asked me about SMS Server Integration with Peoplesoft 8.52 .. so please advice me, is this achievable? if yes then provide me some assistance
thankss

You have 2 choices, replace 2nd disk with a CDROM drive or perform a network install from a JumpStart server on the same subnet.

Urgent: ColdFusion SMS Server

I developed my application locally on my laptop and it worked
fine. But when I moved it online for real world testing, I find
that the SMS Server though running is not receiving the data being
sent. my other SMS Server nowSMS however is receiving.
I have two options now. Either to get the Coldfusion Server
to work or find a way to get coldfusion to integrate with other SMS
Servers. The problem is that I can hardly find any resource to help
me either debug the ColdFusion SMS Server problem or figure out how
to make Coldfusion work with another server as its event gateway.
Attached is an example of how I ammended the cfg file that
comes with Coldfusion, with the aim of making it work with a real
world SMSC.
I will appreciate any insight into how to solve my problem.
TIA

I developed my application locally on my laptop and it worked
fine. But when I moved it online for real world testing, I find
that the SMS Server though running is not receiving the data being
sent. my other SMS Server nowSMS however is receiving.
I have two options now. Either to get the Coldfusion Server
to work or find a way to get coldfusion to integrate with other SMS
Servers. The problem is that I can hardly find any resource to help
me either debug the ColdFusion SMS Server problem or figure out how
to make Coldfusion work with another server as its event gateway.
Attached is an example of how I ammended the cfg file that
comes with Coldfusion, with the aim of making it work with a real
world SMSC.
I will appreciate any insight into how to solve my problem.
TIA

UltraLiteJ Error[-857]: Synchronization failed due to an error on the server

Hi,
I have been trying to sync with a syncronization group, In SUP 2.2 and android.
But my android eclipse log cat shows...
Caused by: com.ianywhere.ultralitejni12.implementation.JniException: UltraLiteJ Error[-857]: Synchronization failed due to an error on the server: [-10225] Message: Failure occurred while executing user supplied code
and my SCC logs
shows this type error info,
{"_op":"C","level":5,"code":412,"eisCode":"9502","message":"java.sql.SQLException:SQL Anywhere Error -638: Right truncation of string data","component":"NFAApp_QASDB","entityKey":null,"operation":"synchronize","requestId":null,"timestamp":"2014-04-21 11:50:15.997","messageId":0,"_rc":0}
I have prepared my mbo for SQL store procedure. Please help me!
Thank you.

Hi Prashant,
Please mark this Discussion with a Correct Answer and Helpful Answer where appropriate. See http://scn.sap.com/community/support/blog/2013/04/03/how-to-close-a-discussion-and-why Even if you discovered the solution without any outside contributions, it helps others to understand what the solution turned out to be.
Regards, Mike
SAP Customer Experience Group - CEG

SMS from SAP (via another SMS server)

Hi Frnds,
I have one requirement like i have to create one abap program for sending SMS.
Port is opened in Quality and production. I wanted to know how to create a program to access the SMS server or to say to update a table with the records(to send as SMS) in SMS server.
I searched in already existing threads, but I wasnt able to workout.
Thanks.

Hi Grace
Refer below threads
http://help.sap.com/SAPHELP_NWPI71/helpdata/EN/af/73563c1e734f0fe10000000a114084/content.htm
Re: SMS through ABAP
Re: Help Urgent : Invoking SMS Web Services Using ABAP FM HTTP_POST
Regards,
Syf

Can i design a virtual sms server?

hi... i dont know how sms server run exactly. I will send a message to virtual server and it takes this sms and interpreted it then sms server send answer with SMS to message sender. Firstly user send sms to server, then server interpret it(server must use database to interpret), then server send sms to user. Is there any sms server as virtual that provides this system ? Or, are there any tactics for me? thankx

Hi Broad Arrow builders,
99jon is right.
However, that is assuming you already know the dimensions (99jon rightly describes setting the dimensions in advance) of the logo in advance, and you're going to use the logo you need for one specific use only. A logo you make in Photoshop Elements may not always remain clear and legible when you scale it up or down. I say that because logos will, generally, find their way into lots of places - letterheads, banners, T-shirt emblems, and other places. You might need different sizes for different needs.
You might want to use a vector graphics tool like Illustrator for logo design.
Phew! Okay - temporary fix - PSE 11 will work great! Permanent fix - for multiple designs and dimensions - you might need a different tool.
Cheers,
David

SMS Server not receiving from SMSC

Using the gateway configuration file that comes with
Colfusion 8, I re-configured the file to read as it is now
(attached). Unfortunately when test is sent to my phone number, it
is not received for processing in Coldfusion. I downloaded nowSMS
and set it up as well. The NowSMS server is receiving alright. So I
am wondering what is up with the Coldfusion SMS Server and Secondly
how would I be able to make Coldfusion work with the nowSMS server?
# SMSGateway configuration file
# Test server config
# This is the IP address of SMSC
ip-address=190.4.64.43
# Port to bind to
port=7710
# Your system id
system-id=test
# Your password
password=testSMS
# The source address for this client
source-ton=1
source-npi=1
# This is a made-up address
source-address=00447700081736
# The address range this smpp client will serve
# Generally the same as your source address
addr-ton=1
addr-npi=1
address-range=00447700081736
# Message sending rate; how many messages per second is the
# gateway allowed to send to your service provider.
# This can be a decimal (i.e. 0.1). 0 is unlimited.
# The default is 100 messages per second.
message-rate=100.0
# The mode of the gateway; Either synchronous or asynchronous
# In synchronous mode the gateway will wait for the response
# from the server when sending a message and the
SendGatewayMessage()
# CFML function will return the SMS messageID of the message
# or an empty string if their is an error. In asynchronous
mode,
# the gateway will not wait for a response and the SMS
messageID
# will NOT be returned from SendGatewayMessage().
# The default is synchronous.
mode=synchronous
# Should the gateway retry delivery on Network Errors?
# If a network error occurs while trying to deliver a
message,
# should the message be queued for delivery when the gateway
# is able to re-bind to the SMSC. This is useful if the
gateway
# is in asynchronous mode, where no error status is returned
from
# the CFML SendGatewayMessage() function.
# The default is no.
network-retry=no
# Should the gateway retry delievery on Transient Errors?
# If an error is returned from the SMSC that indicates
# the message may be able to be delivered in the future,
# should the gateway attemp to resend send the message?
# This is useful if the gateway is in asynchronous mode,
# where no error status is returned from the CFML
# SendGatewayMessage() function.
# The default is no.
transient-retry=no
# Everything below here is usually OK.
# The function in the Gateway CFC which the is called
# when an incoming message arrives.
cfc-method=onIncomingMessage
# The default destination address info
destination-ton=1
destination-npi=1
# You can't have a default destination
# destination-address=
# The service type can be empty or one of
# the following values:
# CMT, CPT, VMN, VMA, WAP or USSD
# service-type=
# From the spec:
# Identifies the type of system requesting the bind.
# This may enable SMSC responses which are
# particular to a given type of ESME.
system-type=SMPP
# The receive timeout is a timeout for trying to receive a
message
# from the SMSC. If you want go to infinite wait until a PDU
# is received, set the receive-timeout to -1.
# The value is in seconds. The default is 30 seconds.
receive-timeout=10
# The ping interval is how often the SMS Gateway will send an
# EnquireLink PDU to the server to verify the health of the
connection.
# The value is in seconds. The default is 60 seconds.
ping-interval=60
# The number of connection attempts the gateway will make
until it gives up.
# Use -1 to retry until connected. The default is -1 (try
forever).
retries=-1
# Connection retry interval; how long to wait between
connection attemps.
# The value is in seconds. The default is 10 seconds.
retry-interval=10

Why don't you just use Coldfusion's built-in gateway,
together with the SMS client simulator. The simulator is at
{CF_HOME}/bin/SMSClient.bat

SCCM 2012 on Server 2012 and WSUS 3.0 SP2 on Server 2008

We are installing SCCM 2012 SP1 fresh into our development environment - the primary site server and the database (SQL 2012) are both being installed on Server 2012.
We have an existing WSUS box on a Windows 2008 (not R2) server - the WSUS server version is 3.2.7600.256. We have set this up as the software update point.
For the purposes of this discussion, these are the server names (obviously obfuscated):
Primary site server: sccm.domain.local
Database server: sccmdb.domain.local
WSUS server: wsus.domain.local
On the primary SCCM server, I've installed the WSUS user interface (Install-WindowsFeature -Name UpdateServices-UI), in order to work with the remote WSUS server.
Updates synchronization appears to be working fine, but when I try to setup client distribution via SUP, I'm getting the following error in the Application event log:
Log Name:      Application
Source:        SMS Server
Date:          8/6/2013 11:03:11 AM
Event ID:      6613
Task Category: SMS_WSUS_CONFIGURATION_MANAGER
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      sccm.domain.local
Description:
On 8/6/2013 11:03:11 AM, component SMS_WSUS_CONFIGURATION_MANAGER on computer sccm.domain.local reported: WSUS Configuration Manager failed to publish client boot-strapper package "9D5353E5-DA80-48C3-97DE-C9C528F73A2D" with version "5.00.7804.1000"
to the Software Updates Point.
As well as this in the WMC.log:
PublishApplication(9D5353E5-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><08-06-2013
11:03:11.787+240><thread=3704 (0xE78)>
ERROR: Failed to publish sms client to WSUS, error = 0x80131509 $$<SMS_WSUS_CONFIGURATION_MANAGER><08-06-2013 11:03:11.803+240><thread=3704 (0xE78)>
It would seem obvious that this is because of a mismatch in versions between the WSUS server version on wsus.domain.local, compared to the UpdateServices UI on sccm.domain.local.
Is there a way around this, without having to upgrade the WSUS server to Server 2012?
Thanks for any thoughts you may have!

Not really. As mentioned though, even the separate WSUS server is probably overkill. In ConfigMgr, WSUS is used to handle the update catalog and that's it. Clients do *not* report status to the WSUS instance and do *not* download updates from the WSUS instance.
No management is ever done in WSUS.
So, in reality, once a month, clients connect to WSUS to download the delta update catalog (delta compared to what they currently have) which usually comes out to about a few hundred KB (yes KB, not MB) -- this download is done via BITS. The server also
syncs the catalog from the WSUS instance, via the SUP, in a similar fashion. If you are using SCEP, the frequency will be greater, but the deltas will be much smaller.
EULAs, as needed, are also stored in WSUS and accessed by clients -- these are also quite small only a select few updates requires them.
That's it. Standing up a dedicated WSUS instance means having a server sitting there doing almost nothing else.
If you are concerned about load on the site server, then you should create a separate site system that contains the MP, SUP (and WSUS instance), and DP. Then, for HA purposes, you can simply build a second site system with these three roles also and HA will
essentially be automatic (from a client functionality perspective).
Jason | http://blog.configmgrftw.com

Server 2012 R2 WSUS not synchronizing

So I am testing out a new WSUS server on Server 2012 R2.
This has been working fine for a few weeks and downloading updates from MS with no problems.
However from the 8th December on-wards it now fails.
I checked to see if any updates had been installed on the 7th and there was one so I uninstalled it but still the same problem.
The error is as follows:
WebException: The request was aborted: Could not create SSL/TLS secure channel.
at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)
at Microsoft.UpdateServices.ServerSync.ServerSyncCompressionProxy.GetWebResponse(WebRequest webRequest)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetAuthConfig()
at Microsoft.UpdateServices.ServerSync.ServerSyncLib.InternetGetServerAuthConfig(ServerSyncProxy proxy, WebServiceCommunicationHelper webServiceHelper)
at Microsoft.UpdateServices.ServerSync.ServerSyncLib.Authenticate(AuthorizationManager authorizationManager, Boolean checkExpiration, ServerSyncProxy proxy, Cookie cookie, WebServiceCommunicationHelper webServiceHelper)
at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.SyncConfigUpdatesFromUSS()
at Microsoft.UpdateServices.Serve
Anyone any ideas what this is and why it has suddenly stopped working?
Regards,
Rob

The update removed was KB3011780.
There were some issues with the original release of this update. A revision was published on Nov 18, 2014. You might check to be sure that the latest revision is approved. Possibly the server had installed the earlier revision?
As for the SSL part... no idea. This is not something we have setup or changed.
My apologies. I confused the issue here. This is the logfile attempting to synchronize with Microsoft, and it does use SSL for that task.
There are only a few reasons why this SSL connection would fail:
Something is now interfering with the connection. (Is the WSUS server configured to use a proxy server?)
The WSUS Server is missing a required certificate to authenticate the Microsoft certificate chain.
Note also that the installation of MS14-066 changed the priority order of the ciphers used for SSL/TLS connections, so if there are intermediary devices, make sure they also support the use of those ciphers.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

WSUS Keeps failing on SCCM 2012 R2

Hello all
I am hoping I could get some help with this strange issue:
I am trying to install WSUS on my sccm server prior to the software update point. This what I have done so far:<o:p></o:p>
In server manger I select to install the WSUS role>Click next (I notice there is a feature option to install Windows internal database)
I unchecked this option because I am using my existing sql server for the WSUS instance. I cant seem to find anything that say tells me that when installing sccm 2012 on Windows Server 2012 and you are using the sql database instance for WSUS to do xyz. In
my case as mentioned before unchecked the Windows Internal Database Feature. Then under Roles Services there are three option: WID Database, WSUS Services, Database. I chose WSUS Services and Database. On the next page I defined my source for the downloads,
then the next page DB Instance I entered the instance of the sql server which in my case is also on my sccm 2012 server VMSCCM is the name> Click Check Connection and that was successfully connected to the server. <o:p></o:p>
So here is where everything goes wrong. I then select to install everything at the confirmation page. reboot the server<o:p></o:p>
once rebooted I open server manager and there is message that says Launch post - installation configuration. I then get the following error "Post-deployment
configuration failed see log below is a image for the log located in c:\users\username\appdata\local\temp\tmpFC3D\
<o:p></o:p>
<o:p></o:p>
Phil Balderos

I had similar issues with the WSUS integration with ConfigMgr 2012 R2. I also have the WSUS DB hosted on the same SQL instance where ConfigMgr 2012 installs it's database.
I found WSUS would not function correctly until I added the SYSTEM account to the WSUS Administrators group under Local Users and Groups:
Hope this helps! :-)
Reference Article -->
http://technet.microsoft.com/en-us/library/gg712696.aspx
Look under Plan for WSUS Installation heading. You can also add
NT AUTHORITY\SYSTEM account as a user for the WSUS database (SUSDB) and configure a minimum of the webService database role membership as an alternative to the above
Hello again,
How would I add this account. When I go into th WSUS admin group on the local machines I cannot search for the this type of account. It returns nothing.
Thanks
Phil Balderos

Stopped server while running full synchronization of SQL MA

Hi Everyone,
I am currently facing an issue in the Sync server where the Full Sync is showing "Stopped server" while running Full Synchronization of SQL MA and this is not happending regularly as it is showing the error message 3 times if it runs 10 times in
a week and rest 7 times its running fine.
What could be the reason why this is occuring?
Your response will be highly appreciated
Thanks,
Aman

Hi Nosh,
My first profiler is FI & FS then i am running FS in which i am facing this issue of stopped server and second thing is that the above thing is running absolutly fine with ILM but in FIM its shwoing this error and this error is not permanent as
it is failing two times then third time it is running perfectly.
Please suggest
Thanks,
Aman

WSUS 6 upstream server will support WSUS 3 SP2 downstream server or not

In our company WSUS upstream server operating system is windows 2012 r2. I would like to know can we install downstream server in windows 2008 r2 (WSUS 3.0 sp2) it will download approved patches from upstream server.
WSUS 6 upstream server will support WSUS 3.0 SP2 downstream or not?

No post-installation instruction in the KB article.
Then you should READ the article again. Let me help:
How to apply this update
We recommend that you synchronize all WSUS servers after you apply this update. If you have a hierarchy of WSUS servers, apply this update, and then synchronize your servers from the top of the hierarchy on down. To synchronize your servers in this manner,
follow these steps:
Note Before computers that are running Windows 8 or Windows Server 2012 can be updated by WSUS 3.2 servers, you must complete these steps.
Start the process with WSUS 3.0 SP2 that synchronizes with Microsoft Update.
Apply this update.
Start a synchronization.
Wait for the synchronization to succeed.
Repeat steps 2 through 4 for each WSUS 3.0 SP2 server that synchronizes to the server that you just updated.
Known issues with this update
If you have Windows 8 or Windows Server 2012 clients that synchronized with WSUS 3SP2 before you applied this update, wait for the update to be applied to the WSUS servers, and then follow these steps:
On the affected client, open cmd.exe in elevated mode
Type the following commands. Make sure that you press Enter after you type each command:
Net stop wuauserv
rd /s %windir%\softwaredistribution\
Net start wuauserv
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

When synchronization fails to create a backup, iTunes gives an error.

When synchronization fails to create a backup, iTunes gives an error.
iPhone 4, OS 5, Windows XP S3, iTunes 10. ITunes was moving a few times. Please help me.

When synchronization fails to create a backup, iTunes gives an error.
iPhone 4, OS 5, Windows XP S3, iTunes 10. ITunes was moving a few times. Please help me.

SMS Server 6703 - SMS WSUS Synchronization Failed

Similar Messages

Maybe you are looking for