Polycom CX600 The connection was closed before TLS negotiation completed

Hello guys,
I'm trying to login with cx600 at a remote location on a SBA SBA but the log is showing the following message
The connection was closed before TLS negotiation completed .
Did the remote peer accept our certificate ?
scenario :
Offline CA : OfflineIssueCA
Subordinate CA : DomainIssueCA
AD DOMAIN : domain.local
SIP DOMAIN : domainA.com
SIP DOMAIN : domainB.com
Pool: pool01.domain.local
SBA : mysba.domain.local
SBA Certificate :
SN : mysba.domain.local
SAN : sip.domainA.com
SAN : sip.domainB.com
DNS :
sip.domainA.com => ip of mysba.domain.local
_sipinternaltls._tcp.domainA.com => sip.domainA.com
DHCP :
option offer 120 mysba.domain.local
option offer 43 https://pool01.domain.local:443/CertProv/CertProvisioningService.svc
Checking the log LPE I see the following error most often :
ERROR :: :: OUTGOING_TRANSACTION OnRequestConnectionConnectComplete - connection failed error 80ee0065
And the SBA log SIPStack :
The connection was closed before TLS negotiation completed .
Did the remote peer accept our certificate ?
I believe that the phone is not downloading the chain of private certificate :
? = © K € ª Æ DUCD_LOG_INFO : 28/05/2014 | 04:50:30 Aries : 05/28/2014 | 04:50:30.885
C4000A : 5C02336 :: INFO :: CCertInstaller LdapGetValsfromMesg : AddRootCerttoStore ( DER .
) succeeded hr = 0x0
ROMK € Yi DUCD_LOG_ERROR : ? 28/05/2014 | 04:50:30 Aries : 28/05/2014
| 04:50:30.886 C4000A : 5C02336 CLogOnManager :: ERROR :: HandleCertEvent : CertInstaller gave callback with Error
code = 5
Æ D | K € kHžDUCD_LOG_INFO : ? 28/05/2014 | 04:50:30 Aries :
05/28/2014 | 04:50:30.907 C4000A : 5C02336 :: INFO :: CCertInstaller AddSingleCerttoStore : Adding Single Certificate Successful
= © K € OžDUCD_LOG_INFO : 05/28/2014 | 04:50:30 Aries : 05/28/2014 |
04:50:30.908 C4000A : 5C02336 :: INFO :: CCertInstaller LdapGetValsfromMesg : AddRootCerttoStore ( . RSP) succeeded
hr = 0x0
ROMK € mSžDUCD_LOG_ERROR : 05/28/2014 | 04:50:30 Aries :
28/05/2014 | 04:50:30.908 C4000A : 5C02336 CLogOnManager :: ERROR :: HandleCertEvent : CertInstaller gave callback with Error code = 5
: O | K € øËžDUCD_LOG_INFO : 28/05/2014 | 04:50:30 Aries : 28/05/2014
| 04:50:30.928 C4000A : 5C02336 :: INFO :: CCertInstaller AddSingleCerttoStore : Adding Single Certificate Successful
= © K € ¥ ÒžDUCD_LOG_INFO : 28/05/2014 | 04:50:30 Aries : 28/05/2014
| 04:50:30.929 C4000A : 5C02336 :: INFO :: CCertInstaller LdapGetValsfromMesg : AddRootCerttoStore ( . RSP) succeeded
hr = 0x0
ROMK € ñÖžDUCD_LOG_ERROR : 05/28/2014 | 04:50:30 Aries :
05/28/2014 | 04:50:30.930 C4000A : 5C02336 CLogOnManager :: ERROR :: HandleCertEvent : CertInstaller gave callback with Error code = 5
: O | K € OŸDUCD_LOG_INFO : 28/05/2014 | 04:50:30 Aries : 05/28/2014
| 04:50:30.950 C4000A : 5C02336 :: INFO :: CCertInstaller AddSingleCerttoStore : Adding Single Certificate Successful
= © K € UŸDUCD_LOG_INFO : 05/28/2014 | 04:50:30 Aries : 28/05/2014
| 04:50:30.951 C4000A : 5C02336 :: INFO :: CCertInstaller LdapGetValsfromMesg : AddRootCerttoStore ( . RSP) succeeded hr
= 0x0
rom € ¸ ¶ K tŸDUCD_LOG_INFO : 28/05/2014 | 04:50:30
Aries : 28/05/2014 | 04:50:30.956 C4000A : 5520002 :: INFO :: CLogOnManager OnCertStatusEvent : Received notification from CertInstaller with state
= 0x5
G_ck € ™ zŸDUCD_LOG_INFO : 28/05/2014 | 04:50:30
Aries : 05/28/2014 | 04:50:30.957 C4000A : 5520002 :: INFO :: CCertStateImplementor HandleCertEvents : Received Status event from CertInstaller event from
cert installer
4th K € | ŸDUCD_LOG_INFO : 28/05/2014 | 04:50:30 Aries : 05/28/2014
| 04:50:30.957 C4000A : 5520002 :: INFO :: CLogOnScreen OnCertInstallerStateChange : OnCertInstallerStateChange status = 5
Robson Hasselhoff - Follow me @Robk9e

Log in below to connect sip.domainA.com:
�é�K€®ËÃ.UCD_LOG_INFO: 05/28/2014|07:28:56 Uccapi: 05/28/2014|07:28:56.693 5510002:5520002 INFO :: SockMgr: Create New Connection:DestName:(sip.domainA.com)DestPort:(5061)Transport:(2)httpTunnel:(0)TLS RemotePrincipalName:(sip.domainA.com)
� (0¯�K€ãÃ.UCD_LOG_INFO: 05/28/2014|07:28:56 Uccapi: 05/28/2014|07:28:56.696 5510002:5520002 INFO :: CSIPCompressor::Initialize - Compression setting 1, threshold 128000, timeout 5000
�)Ì�K€™óÃ.UCD_LOG_INFO: 05/28/2014|07:28:56 Uccapi: 05/28/2014|07:28:56.699 5510002:5520002 INFO :: CSIPAsyncSocket::Connect 00CCD6A0 connecting(async) window 7003B800 socket:00000F8D DestAddr:10.145.53.115:5061
�¬�K€ºaÄ.UCD_LOG_ERROR: 05/28/2014|07:28:56 Uccapi: 05/28/2014|07:28:56.717 5510002:56A000A ERROR :: SECURE_SOCKET: negotiation failed: 80090327, principal name: [sip.domainA.com]
�Ù�K€!fÄ.UCD_LOG_ERROR: 05/28/2014|07:28:56 Uccapi: 05/28/2014|07:28:56.718 5510002:5520002 ERROR :: CSIPTransportLayerSecurity::OnTlsNegotiationComplete (ccd720) failed with 0x80ee0065. Raising OnConnect with the same error
�p.e—�K€¶hÄ.UCD_LOG_ERROR: 05/28/2014|07:28:56 Uccapi: 05/28/2014|07:28:56.718 5510002:5520002 ERROR :: CSIPClientConnection::OnConnect (80ee0065) this: 00CCD540
�0Ï�K€£jÄ.UCD_LOG_INFO: 05/28/2014|07:28:56 Uccapi: 05/28/2014|07:28:56.719 5510002:5520002 INFO :: SIP_MSG_PROCESSOR::OnRequestConnectionConnectComplete - Enter this: 00CCC1E0, callid=(null), ErrorCode: 0x80ee0065
�i�K€ýkÄ.UCD_LOG_ERROR: 05/28/2014|07:28:56 Uccapi: 05/28/2014|07:28:56.719 5510002:5520002 ERROR :: Releasing connection and notifying transactions
�t t©�K€RmÄ.UCD_LOG_ERROR: 05/28/2014|07:28:56 Uccapi: 05/28/2014|07:28:56.719 5510002:5520002 ERROR :: SIP_MSG_PROCESSOR::NotifyRequestConnectionConnectComplete - Error: 80ee0065
�ca ¹�K€pˆÄ.UCD_LOG_ERROR: 05/28/2014|07:28:56 Uccapi: 05/28/2014|07:28:56.724 5510002:5520002 ERROR :: OUTGOING_TRANSACTION::OnRequestConnectionConnectComplete - connection failed error 80ee0065
�07:~�K€Ö‰Ä.UCD_LOG_INFO: 05/28/2014|07:28:56 Uccapi: 05/28/2014|07:28:56.724 5510002:5520002 INFO :: REGISTER_CONTEXT:State (4) => (5)
�CC—�K€X‹Ä.UCD_LOG_INFO: 05/28/2014|07:28:56 Uccapi: 05/28/2014|07:28:56.724 5510002:5520002 INFO :: REGISTER_CONTEXT(ccc1e0) SetAndNotify Recv(6) at State (5)
�c~�K€¿ŽÄ.UCD_LOG_INFO: 05/28/2014|07:28:56 Uccapi: 05/28/2014|07:28:56.724 5510002:5520002 INFO :: REGISTER_CONTEXT:State (5) => (6)
�nez�K€ Ä.UCD_LOG_INFO: 05/28/2014|07:28:56 Uccapi: 05/28/2014|07:28:56.725 5510002:5520002 INFO :: SIP_REGISTER:State (1) => (0)
�72–�K€ª”Ä.UCD_LOG_INFO: 05/28/2014|07:28:56 Uccapi: 05/28/2014|07:28:56.726 5510002:5520002 INFO :: Function: CUccServiceOperationManager::DisableServManager
� Ž�K€º–Ä.UCD_LOG_INFO: 05/28/2014|07:28:56 Uccapi: 05/28/2014|07:28:56.726 5510002:5520002 INFO :: Function: CUccServerEndpoint::UpdateEndpointState
� 0“�K€ãšÄ.UCD_LOG_ERROR: 05/28/2014|07:28:56 Uccapi: 05/28/2014|07:28:56.726 5510002:5520002 ERROR :: HRESULT API failed: 80ee0061 = hr. DisableServManager
�O«�K€nœÄ.UCD_LOG_INFO: 05/28/2014|07:28:56 Uccapi: 05/28/2014|07:28:56.727 5510002:5520002 INFO :: CUccDnsResolverManager::Stop MR-INFO - [00CC7C10] DNS resolver manager stopped
�5y�K€µŸÄ.UCD_LOG_INFO: 05/28/2014|07:28:56 Uccapi: 05/28/2014|07:28:56.728 5510002:5520002 INFO :: ~Out trxn corr-id (00CCD000)
�= hç�K€Ä¥Ä.UCD_LOG_ERROR: 05/28/2014|07:28:56 Aries: 05/28/2014|07:28:56.728 5510002:5520002 ERROR :: WriteLogonSessionAssertionTrace: NModel::CEasyUccContext::Get[133] - ASSERTION FAILURE: IUccContext::get_Property() failed!. hr=0x80ee0058
�tç�K€˜§Ä.UCD_LOG_ERROR: 05/28/2014|07:28:56 Aries: 05/28/2014|07:28:56.729 5510002:5520002 ERROR :: WriteLogonSessionAssertionTrace: NModel::CEasyUccContext::Get[133] - ASSERTION FAILURE: IUccContext::get_Property() failed!. hr=0x80ee0058
�5ç�K€T©Ä.UCD_LOG_ERROR: 05/28/2014|07:28:56 Aries: 05/28/2014|07:28:56.729 5510002:5520002 ERROR :: WriteLogonSessionAssertionTrace: NModel::CEasyUccContext::Get[133] - ASSERTION FAILURE: IUccContext::get_Property() failed!. hr=0x80ee0058
�Rç�K€«Ä.UCD_LOG_ERROR: 05/28/2014|07:28:56 Aries: 05/28/2014|07:28:56.729 5510002:5520002 ERROR :: WriteLogonSessionAssertionTrace: NModel::CEasyUccContext::Get[101] - ASSERTION FAILURE: IUccContext::get_Property() failed!. hr=0x80ee0058
�5¶�K€m¯Ä.UCD_LOG_ERROR: 05/28/2014|07:28:56 Aries: 05/28/2014|07:28:56.730 5510002:5520002 ERROR :: NModel::CBaseLogonSession::OnEnable: Logon failed with UCCP status/diag code 0x80ee0065/0
� :K€m·Ä.UCD_LOG_INFO: 05/28/2014|07:28:56 Aries: 05/28/2014|07:28:56.731 5510002:5520002 INFO :: NModel::CManagedCredential::SetResult: Logon success state 0 reported by user id=0 (adjusted=0) on CManagedCredential[SPECIFIC this=00AD1E40, domain=intranet.local,
userName=robson.carvalho]
�et¶�K€ÙºÄ.UCD_LOG_ERROR: 05/28/2014|07:28:56 Aries: 05/28/2014|07:28:56.732 5510002:5520002 ERROR :: CServerConfigModel::LoadValue: UCCP object is not received yet. groupIndex=0, hr=80ee0061
�esÈ�K€%½Ä.UCD_LOG_INFO: 05/28/2014|07:28:56 Aries: 05/28/2014|07:28:56.732 5510002:5520002 INFO :: NModel::CLogonServerStatistic::SetResult: CLogonServerStatistic::SetResult sip.domainA.com:5061/3 0x80ee0065
�¼�K€AÀÄ.UCD_LOG_INFO: 05/28/2014|07:28:56 Aries: 05/28/2014|07:28:56.733 5510002:5520002 INFO :: NModel::CLogonServerStatistic::ClearDedicatedServer: CLogonServerStatistic::ClearDedicatedServer
�©�K€ÅÉÄ.UCD_LOG_INFO: 05/28/2014|07:28:56 Aries: 05/28/2014|07:28:56.734 5510002:5520002 INFO :: NModel::CBaseLogonSession::DeactivateRecoveryMode: Recovery mode switched off
�) f|�K€¦ÌÄ.UCD_LOG_INFO: 05/28/2014|07:28:56 Uccapi: 05/28/2014|07:28:56.735 5510002:5520002 INFO :: Function: CUccEndpoint::Disable
�©�K€&ÑÄ.UCD_LOG_INFO: 05/28/2014|07:28:56 Aries: 05/28/2014|07:28:56.736 5510002:5520002 INFO :: NModel::CBaseLogonSession::DeactivateRecoveryMode: Recovery mode switched off
�07:ª�K€ËÙÄ.UCD_LOG_INFO: 05/28/2014|07:28:56 Aries: 05/28/2014|07:28:56.737 5510002:5520002 INFO :: CCallManager::OnEvent: CCallManager::OnEvent - Received logon-session event 0.
�=0ñ�K€PÜÄ.UCD_LOG_INFO: 05/28/2014|07:28:56 Aries: 05/28/2014|07:28:56.737 5510002:5520002 INFO :: NModel::CComponentLifecycleManager::NotifyComponentStateChanged: CLM received state change event of component 'LogonSession', reporting state STOPPED
�jecÎ�K€dÞÄ.UCD_LOG_ERROR: 05/28/2014|07:28:56 Aries: 05/28/2014|07:28:56.738 5510002:5520002 ERROR :: NModel::CComponentDetails::SetStatusInfo: Component LogonSession reports error code 0x80ee0065 (no auto-recovery)
�:S2K€æñÄ.UCD_LOG_INFO: 05/28/2014|07:28:56 Aries: 05/28/2014|07:28:56.739 5510002:5520002 INFO :: NModel::CBaseLogonSession::OnEnable:
Received server response:
   status/diag code=0x80ee0065/0
   clientVersionCheckResult=0
   upgradeUrl=
   authWebServiceBaseUrl=
   currentAuthMode=0
   supportedAuthModes=0
   isTlsDskSupported=0
   Reporting credential success 80ee0065
   Reporting server success 80ee0065
   updatedServerName=sip.domainA.com:5061
   updatedTransportMode=3
   isClientVersionCheckError=0
   isServerVersionCheckError=0
   isConnectionError=1
   isRootCertError=0
   isAuthError=0
   isTlsDskError=0
   isKerberosError=1
   isUserCredError=0
   isProxyCredError=0
   isErrorWithCache=0
   isNtlmMismatch=0
   isServerCertInvalid=1
   shouldResetAllowedAuthModes=0
   current allowedAuthModes=12
   new allowedAuthModes=0
No further alternate server available or SVF/CVF error!
   autoRetryByErrorCode=1
   withRescheduleHint=0
   withAutoRetrials=0
   Login failed with permanent error or no auto-retrials
   Recovery mode switched off
   newState=LOGGED_OUT
Robson Hasselhoff - Follow me @Robk9e

Similar Messages

SQL Service Broker 2012: the connection was closed by the remote end, or an error occurred while receiving data: '64(The specified network name is no longer available.)'

Anyone can help with the below issue please? Much appreciated.
We have about 2k+ messages in sys.transmission_queue
Telnet to the ports 4022 is working fine.
Network connectivity has been ruled out.
The firewalls are OFF.
We also explicitly provided the permissions to the service account on Server A and Server B to the Service broker end points.
GRANT
CONNECT ON
ENDPOINT <broker> <domain\serviceaccount>
Currently for troubleshooting purposes, the DR node is also out of the Availability Group, which means that we right now have only one replica the server is now a traditional cluster.
Important thing to note is when a SQL Server service is restarted, all the messages in the sys.transmission queue is cleared immediately. After about 30-40 minutes, the errors are continued to be seen with the below
The
connection was
closed by the
remote end,
or an
error occurred while
receiving data:
'64(The specified network name is no longer available.)'

We were able to narrow down the issue to an irrelevant IP coming into play during the data transfer. We tried ssbdiagnose runtime and found this error:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>SSBDIAGNOSE -E RUNTIME -ID 54F03D35-1A94-48D2-8144-5A9D24B24520 Connect to -S <SourceServer> -d <SourceDB> Connect To -S <DestinationServer> -d <DestinationDB>
Microsoft SQL Server 11.0.2100.60
Service Broker Diagnostic Utility
An internal exception occurred: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
P 29830 Could not find the connection to the SQL Server that
corresponds to the routing address tcp://XX.XXX.XXX.199:4022. Ensure the tool is connected to this server to allow investigation of runtime events
The IP that corresponds to routing address is no where configured within the SSB. We are yet unsure why this IP is being referred despite not being configured anywhere. We identified that this IP belongs to one of nodes other SQL Server cluster, which has
no direct relation to the source server. We failed over that irrelevant SQL Server cluster and made another node active and to our surprise, the data from sys.transmission_queue started flowing. Even today we are able to reproduce the issue, if we bring
back this node [XX.XXX.XXX.199] as active. Since, its a high business activity period, we are not investigating further until we get an approved downtime to find the root cause of it.
When we get a approved downtime, we will bring the node [XX.XXX.XXX.199] as active and we will be running Network Monitor, Process Monitor and the SSB Diagnose all in parallel to capture the process/program that is accessing the irrelevant IP.
Once, we are able to nail down the root cause, I will share more information.

WSUS sync fails with "Webexception the underlying connection was closed. The connection was closed unexpectedly"

While I have my WSUS integrated with SCCM. I think this error has nothing to do with SCCM, so I put it here in the WSUS forum. On one of my networks, the nightly WSUS sync worked until two weeks ago. I've made no progress in fixing it. Ocassionally it'll
say the sync was successful (about 1 in 15 attempts). I keep getting "WebException: The underlying connection was closed. The connection was closed unexpectedly. at System.WebServices.Protocols.WebClientProtocol.GetWebResponse(WebRequest
request) at System.WebServices.Protocols.GetWebResponse(WebRequest request) at MicroSoft.UpdateServices.ServerSync.ServerSyncCompressionProxy.GetWebResponse(WebRequest webrequest) at System.Web.Services.Protocols.SoapHttpClientProtocol.(Invoke StringMethodName,Object[]
Parameters) at Microsoft.UpdateServices.ServerSync.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetRevisionIdList(Cookie cookie, ServerSyncFilter filter) at Microsoft.Update.Services.ServerSync.CatalogSyncAgentCore.WebserviceGetRevisionIdList(ServerSyncFilter
filter, Boolean isConfigData), at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.SyncConfigUpdatesfromUSS() at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)"
Our enterprise has it's own WSUS server we have to sync from. The problem may be at that end, not mine. A sync will start and will fail about 4 minutes later. Our network guy watched the traffic leave our compound but saw only a trickle of traffic coming
back. Any ideas?
Ben JohnsonWY

Hi,
Please try this fix below first:
FIX: Intermittent "Underlying connection was closed" error message when you call a Web service from ASP.NET
http://support.microsoft.com/kb/819450
I guess you are maintaining a downstream server. If it isn’t a replica server, please try to sync with Microsoft update.
Hope this helps.

VISUAL STUDIO ONLINE Unable to read data from the transport connection: The connection was closed.

Can anyone explain why I've suddenly started getting this error on one file in my projects?
Visual Studio is 2013 Premium Update 4
The file that's failing ins 14,140KB in size.

Hi s6521d,
For this problem, you can try the following methods to check if the issue can be resolved. And elaborate more details if the issue still exist.
1. Do a get latest and then have a check if your team project works fine
2. Clean team foundation cache and sign out your credentials then reconnect to the team project
3. Have a try on other machines to see if it only occurs on your environment
4. Confrm whether the workspace you're using is server workspace and the file is locked. If yes, unlock the file. If the file was changed, you can also revert to a former changeset to check if the error still exist
5. Check event logs to see if there any useful information
Best regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

WSUS Sync is not working Sync failed: UssCommunicationError: WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. --- System.Security.Authentication.AuthenticationException: The remote

I know there are loads of posts with same issue and most of them were related to proxy and connectivity .
This was case for me as well (few months back). Now the same error is back. But I've confirmed that FW ports and proxy are fine this time around.
server is configured on http port 80
ERROR
Sync failed: UssCommunicationError: WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid
according to the validation procedure.~~at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request). Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WSyncAction.WSyncAction.SyncWSUS
I've checked proxy server connectivity. I'm able browse following site from WSUS server
http://catalog.update.microsoft.com/v7/site/Home.aspx?sku=wsus&version=3.2.7600.226&protocol=1.8
I did telnet proxy server on the particular port (8080) and that is also fine.
I've doubt on certificates, any idea which are the certificates which we need to look? And if certificate is expired then (my guess) we won't be able open the above mentioned windows update catalog site?
Any tips appreciated !
Anoop C Nair (My Blog www.AnoopCNair.com)
- Twitter @anoopmannur -
FaceBook Forum For SCCM

Hi Lawrence ! - Many thanks for looking into this thread and replying. Appreciate your help.
Your reply ("SSL is enabled/configured, and the certificate being used is invalid
(or the cert does not exist or cannot be obtained), or the SSL connection could not be established.") is very helpful.
I've already tested CONTENT DOWNLOAD and it's working fine. WSUS Sync was also working fine for years with proxy server configured on port (8080) and WSUS server on port 80.
My Guess (this is my best guess ;)) is this something to do with Firewall or Proxy side configuration rather than WSUS. However, I'm not finding a way to prove this to proxy/firewall team. From their perspective all the required port communication open and
proxy server is also reachable. More over we're able to access internet (Microsoft Update Catalog site) over same port (8080).
Any other hints where I can prove them it's a sure shot problem from their side.
Thanks again !!
Anoop C Nair (My Blog www.AnoopCNair.com)
- Twitter @anoopmannur -
FaceBook Forum For SCCM

SSRS Report Server Could not establish connection. The underlying connection was closed. Could not establish trust relationship for the SSL/TLS Secure channel

Hi
Had to un-install and then re-install MS SQL Server 2012 with SSRS.
After we re-installed we are able to get to the Web Services page but not the Report Server page and get the above error message. We need to use SSL and when we bind the cert in RS Configuration Manager it says it does this successfully on the WebServices
tab. We also do a similar exercise on the ReportServer page.
Any help warmly welcomed :D
Thanks

Hi Rich Whight,
According to your description, after you re-installed SQL Server 2012 with SSRS, you are able to access Web Service URL, but when you tried to access Report Manager URL, the error occurred: The underlying connection was closed. Could not establish trust
relationship for the SSL/TLS Secure channel.
The issue may be caused when the certificate isn't installed correctly in the trusted root for the local computer. To verify and install the certificate, Please refer to the steps blow:
In RsReportServer.config file(default location: C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer), change the “SecureConnectionLevel” element value from 0 to 3.
Add correct value to <UrlRoot> element.
Add the same value to the <ReportServerUrl> element as step2.
Go to Microsoft management Console, add the certificate which you use to access the report server under “Trusted Root Certification Authorities”.
For more information about SSL configuration and Managing Trusted Root Certificates, please refer to the following documents:
http://blogs.msdn.com/b/mariae/archive/2007/12/12/ssl-configuration-and-reporting-services.aspx
http://technet.microsoft.com/en-us/library/cc754841.aspx
If you have any more questions, please feel free to ask.
Best Regards,
Wendy Fu

The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.

I tried to redeem a digital download copy of a movie and was presented the following error:
The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
Any guesses on what it is and how to resolve it?
Thanks

Hi
Abhilash Francis,
Could you tell us your scenario? What's your project? Is it a WCF service?
Looks like this is not a code issue.
Just from the error information,
it seems that you do not configure the service certificate very well so as to Server was unable to process request.
I am not completely sure what the real scenario is, but it might be a problem of that It is a WCF services application, please check these following articles to configure the service certificate.
If not, please feel free to let me know.
How to: Configure an IIS-hosted WCF service with SSL
Could not establish trust
relationship for the SSL/TLS secure channel
Hope this helps.
Best regards,
Kristin
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

SSRS Reporting manages goes down frequently. ERROR: The underlying connection was closed: An unexpected error occurred on a send.

We have been experiencing issues with SSRS over the past 5 weeks, the service goes down frequently. And it comes up only on reboot of the server.
We had also disabled the On Access scan in Mcafee.
The service is in use for about two years, and the below error started occuring over the last few days. Please advise on this.
ui!ReportManager_0-2!24e8!08/14/2014-18:13:45:: e ERROR: The underlying connection was closed: An unexpected error occurred on a send.
ui!ReportManager_0-2!24e8!08/14/2014-18:13:45:: e ERROR: HTTP status code --> 500
-------Details--------
System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException:
An existing connection was forcibly closed by the remote host
   at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
   at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   --- End of inner exception stack trace ---
   at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.ConnectStream.WriteHeaders(Boolean async)
   --- End of inner exception stack trace ---
   at Microsoft.SqlServer.ReportingServices2005.RSConnection.GetSecureMethods()
   at Microsoft.ReportingServices.UI.Global.RSWebServiceWrapper.GetSecureMethods()
   at Microsoft.SqlServer.ReportingServices2005.RSConnection.IsSecureMethod(String methodname)
   at Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection()
   at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
   at Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel level)
   at Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object sender, EventArgs args)
   at System.EventHandler.Invoke(Object sender, EventArgs e)
   at System.Web.UI.Control.OnInit(EventArgs e)
   at System.Web.UI.Page.OnInit(EventArgs e)
   at System.Web.UI.Control.InitRecursive(Control namingContainer)
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
ui!ReportManager_0-2!24e8!08/14/2014-18:13:46:: e ERROR: Exception in ShowErrorPage: System.Threading.ThreadAbortException: Thread was being aborted.
   at System.Threading.Thread.AbortInternal()
   at System.Threading.Thread.Abort(Object stateInfo)
   at System.Web.HttpResponse.End()
   at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
   at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String errMsg) at    at System.Threading.Thread.AbortInternal()
   at System.Threading.Thread.Abort(Object stateInfo)
   at System.Web.HttpResponse.End()
   at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
   at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String errMsg)
library!ReportServer_0-1!1c90!08/14/2014-18:13:51:: Call to ListParentsAction(/Data Sources).
library!ReportServer_0-1!1c90!08/14/2014-18:13:51:: Call to ListParentsAction(/Data Sources).
library!ReportServer_0-1!1c90!08/14/2014-18:13:51:: Call to ListChildrenAction(/Data Sources, False).
webserver!ReportServer_0-1!1c90!08/14/2014-18:13:51:: i INFO: Processed folder '/Data Sources'
library!ReportServer_0-1!68c!08/14/2014-18:13:56:: Call to GetItemTypeAction(/).
library!ReportServer_0-1!68c!08/14/2014-18:13:56:: Call to ListParentsAction(/).
library!ReportServer_0-1!68c!08/14/2014-18:13:56:: Call to ListChildrenAction(/, False).
webserver!ReportServer_0-1!68c!08/14/2014-18:13:56:: i INFO: Processed folder '/'

Hi SThiyag,
Based on your error message, it may be related to the “SecureConnectionLevel” in the RSReportServer.config file. Please go to C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer, use Notepad to open the RSReportServer.config,
modify <Add Key="SecureConnectionLevel" Value="0"/>, change the value into "1" or "2".
(Note: Please backup the file before modify it.)
Acceptable values are:
3 Most secure—Use SSL for absolutely everything.
2 Secure—Use SSL for rendering and methods that pass credentials but don't insist on it for all SOAP calls.
1 Basic Security—Accepts http but rejects any calls that might be involved in the passing of credentials.
0 Least Secure—Don't use SSL at all
Here is a blog for error message "The underlying connection was closed...", please refer to the link below:
http://blogs.msdn.com/b/engelsr/archive/2005/11/29/the-underlying-connection-was-closed.aspx
If you have any question, please feel free to ask.
Best Regards,
Simon Hou

Register-SPWorkflowService error: The underlying connection was closed

I have a three server workflow manager farm. I'm using hardware load balancing across the three servers. I've associated a hostname in DNS with the VIP on the NLB.
When I run Register-SPWorkflowService and point at the hostname for the -WorkflowHostUri parameter, I get the error:
Register-SPWorkflowService The underlying connection was closed An unexpected error occurred on a receive.
If I put that URL into a browser on the SP machine where I'm running this cmdlt, it responds with the correct XML. So I know that the NLB is routing regular http requests to my machines in the quorum.
Also, if I use the actual machine name of one of the three machines in the workflow manager quorum, the cmdlt works.
I know very little about NLB hardware. Is there something I need to tell the guys configuring the NLB to do so that the connection doesn't close?

Yes, I actually had done that before using a host file entry to replace the DNS mapping from the NLB VIP to the IP of one of the machines in the WFM quorum. It worked from the standpoint of registering and SharePoint shows that the farm is "connected". However,
when I go to create an SP 2013 workflow, it still only shows 2010 workflows in the dropdown (in SPD.)
I also put Fiddler on the SharePoint machine that I'm using to register the WFM quorum to SharePoint. It shows that when the register cmdlt is executed, several calls to the
/SharePoint/ web service endpoint are made, initially getting a 401 asking for an authentication, and then after creds are passed, getting a 200. But then a call to
/SharePoint/$Activities is called and a 401 occurs twice, after which the registration cmdlt fails.

Wsus Sync Failed. WebException: The underlying connection was closed: An unexpected error occurred on a send. --- System.IO.IOException: Received an unexpected EOF or 0 bytes from the transport stream.

Hi I have installed wsus 3 sp2 on a win 2008 R2 Sp1
before the installation , I have updated the windows
I can open easily browse internet , but when I try to configure synchronization .but it fails.
No firewall , no proxy ............. I am behind a nat.
Wsus version is 3.2.7600.256.
I have searched and searched .....
Can any body help me
WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Received an unexpected EOF or 0 bytes from the transport stream.
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

Hi
yes . it is alloweded.
Nat rule permits any ip traffic . No problem with https...
also my windows is fully updated.
here is my netstat -an , maybe usefull.
TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
TCP    0.0.0.0:8530           0.0.0.0:0              LISTENING
TCP    0.0.0.0:8531           0.0.0.0:0              LISTENING
TCP    0.0.0.0:47001          0.0.0.0:0              LISTENING
TCP    0.0.0.0:49152          0.0.0.0:0              LISTENING
TCP    0.0.0.0:49153          0.0.0.0:0              LISTENING
TCP    0.0.0.0:49154          0.0.0.0:0              LISTENING
TCP    0.0.0.0:49155          0.0.0.0:0              LISTENING
TCP    0.0.0.0:49156          0.0.0.0:0              LISTENING
TCP    --------------------:139       0.0.0.0:0              LISTENING
TCP    --------------------:8530      172.16.2.201:53317     ESTABLISHED
TCP    --------------------:49362     23.65.244.185:443      ESTABLISHED
TCP    --------------------:49363     23.65.244.185:443      ESTABLISHED
TCP    --------------------:49367     23.65.244.185:443      ESTABLISHED
TCP    --------------------:49377     23.65.244.185:443      ESTABLISHED
TCP    --------------------:49414     131.253.34.141:443     ESTABLISHED
TCP    --------------------:49416     216.239.32.20:80       ESTABLISHED
TCP    --------------------:49417     216.239.32.20:80       ESTABLISHED
TCP    --------------------:49418     173.194.70.113:80      ESTABLISHED
TCP    --------------------:49419     173.194.70.113:80      ESTABLISHED
TCP    --------------------:49420     65.52.103.78:80        ESTABLISHED
TCP    --------------------:49421     65.52.103.78:80        ESTABLISHED
TCP    --------------------:49424     88.221.93.31:80        ESTABLISHED
TCP    --------------------:49425     88.221.93.30:80        ESTABLISHED
TCP    --------------------:49426     88.221.93.30:80        ESTABLISHED
TCP    --------------------:49427     88.221.93.31:80        ESTABLISHED
TCP    --------------------:49428     88.221.93.31:80        ESTABLISHED
TCP    --------------------:49429     88.221.93.31:80        ESTABLISHED
TCP    --------------------:49430     88.221.93.30:80        ESTABLISHED
TCP    --------------------:49431     88.221.93.30:80        ESTABLISHED
TCP    --------------------:49432     88.221.93.31:80        ESTABLISHED
TCP    --------------------:49433     88.221.93.31:80        ESTABLISHED
TCP    --------------------:49434     88.221.93.30:80        ESTABLISHED
TCP    --------------------:49435     88.221.93.31:80        ESTABLISHED
TCP    --------------------:49436     88.221.93.30:80        ESTABLISHED
TCP    --------------------:49437     88.221.93.30:80        ESTABLISHED
TCP    --------------------:49438     88.221.93.30:80        ESTABLISHED
TCP    --------------------:49439     88.221.93.30:80        ESTABLISHED
TCP    --------------------:49440     88.221.93.31:80        ESTABLISHED
TCP    --------------------:49441     88.221.93.30:80        ESTABLISHED
TCP    --------------------:49442     88.221.93.30:80        ESTABLISHED
TCP    --------------------:49443     88.221.93.54:80        ESTABLISHED
TCP    --------------------:49444     88.221.93.54:80        ESTABLISHED
TCP    --------------------:49445     88.221.93.63:80        ESTABLISHED
TCP    --------------------:49446     88.221.93.63:80        ESTABLISHED
TCP    --------------------:49447     88.221.93.63:80        ESTABLISHED
TCP    --------------------:49448     88.221.93.63:80        ESTABLISHED
TCP    --------------------:49449     88.221.93.63:80        ESTABLISHED
TCP    --------------------:49450     88.221.93.31:80        ESTABLISHED
TCP    --------------------:49451     88.221.93.31:80        ESTABLISHED
TCP    --------------------:49453     88.221.93.30:80        ESTABLISHED
TCP    --------------------:49456     65.55.58.184:80        ESTABLISHED
TCP    --------------------:49457     65.55.58.184:80        ESTABLISHED
TCP    --------------------:49460     131.253.34.142:80      ESTABLISHED
TCP    --------------------:49461     131.253.34.142:80      ESTABLISHED
TCP    --------------------:49462     65.52.103.78:80        ESTABLISHED
TCP    --------------------:49463     65.52.103.78:80        ESTABLISHED
TCP    --------------------:49464     63.251.85.33:80        ESTABLISHED
TCP    --------------------:49466     131.253.40.50:80       ESTABLISHED
TCP    --------------------:49467     131.253.40.50:80       ESTABLISHED

URGENT - The underlying connection was closed: An unexpected error occurred on a send

Hello,
We have a web app that works with Ping Federate SSO. The code that was working fine suddenly stopped working with this error message.
Code: httpResponse = (HttpWebResponse)httpRequest.GetResponse()
Error: The underlying connection was closed: An unexpected error occurred on a send
We have tried everything to try to make it work. Made sure TLS is enabled, review the logs from both sides. Nothing seemed to work. I read on the net that there appears to be some known bug with the .net framework.
This is our prodcution code and our customers are currently impacted by this issue and we need to get the SSO working again.
I'd appreciate if you can email me how we can go about resolving this issue. BTW, I also made sure have the correct certificate through IIS bind.
regards,
Ilanko
[email protected]
206.931.9442

Hello Ilanko,
It seems that you could access the application source code, if so, I suggest that you could check this
blog to debug the GetResponse() method to find the exact caused code line.
For this exception, here I find some related information which might be helpful:
You receive one or more error messages when you try to make an HTTP request in an application that is built on the .NET Framework 1.1 Service Pack 1
A blog which contains a summary for this exception and provides various workarounds:
http://blogs.msdn.com/b/engelsr/archive/2005/11/29/the-underlying-connection-was-closed.aspx
If your application is calling a web service, you could check this hotfix to see if your environment are met:
https://support.microsoft.com/kb/819450
If not, you could post a hotfix request with your environment description to:
https://support2.microsoft.com/contactus/emailcontact.aspx?scid=sw;%5BLN%5D;1422
Regards.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

The underlying connection was closed: An unexpected error occurred on a send.

Fala ae galera.
tive problemas ao publicar meu primeiro report, exibe o seguinte erro: The underlying connection was closed: An unexpected error occurred on a send.
Configurações IIS

Hello,
Based on the error message, the issue may be related to the “SecureConnectionLevel” in the RSReportServer.config file. When we use HTTP protocol, the value of the “SecureConnectionLevel” attribute should be 0. Usually, we change the value to “1” or “2” only
when we configure the Report Server for Secure Sockets Layer (SSL) connections.
Reference:
http://msdn.microsoft.com/en-us/library/ms157273(v=sql.105).aspx
Please refer to the following steps try to resolve the issue:
1. Use Notepad to open the RSReportServer.config. By default, in SSRS 2012, it is located in: C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer
(Note: Please backup the file before modify it.)
2. Search for “SecureConnectionLevel” and make sure its value is set to 0. It looks like this:
<Add Key="SecureConnectionLevel" Value="0"/>
There is a blog about “The underlying connection was closed…" error message, you can refer to it.
http://blogs.msdn.com/b/engelsr/archive/2005/11/29/the-underlying-connection-was-closed.aspx
Regards,
Alisa Tang
Alisa Tang
TechNet Community Support

The underlying connection was closed: Could not establish trust

The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
Please checkout the following code. I am just trying to login on to the web service. I have imported the certificate from IE by going to the Ondemand website.
I am using C# VS 2005
public static String Login(String loginUrlString, String userName, String password)
string p = null;
try
ServicePointManager.ServerCertificateValidationCallback = new System.Net.Security.RemoteCertificateValidationCallback(MyCertValidationCb);
HttpWebRequest myRequest = (HttpWebRequest)WebRequest.Create(loginUrlString);
HttpWebResponse myResponse;
myRequest.Method = "GET";
myRequest.Headers["UserName"] = userName;
myRequest.Headers["Password"] = password;
myRequest.AllowAutoRedirect = true;
myRequest.CookieContainer = new CookieContainer();
myRequest.ClientCertificates.Add(X509Certificate.CreateFromCertFile(@"c:\a.cer"));
// Return the response.
myResponse = (HttpWebResponse)myRequest.GetResponse();
// retrieve session id
char[] sep = { ';' };
String[] headers = myResponse.Headers["Set-Cookie"].Split(sep);
for (int i = 0; i <= headers.Length - 1; i++)
if (headers.StartsWith("JSESSIONID"))
sep[0] = '=';
SessionID = headers[i].Split(sep)[1];
break;
myResponse.Close();
p = sep.ToString();
catch (Exception e)
MessageBox.Show(e.Message);
return p;
public static bool MyCertValidationCb(
object sender,
X509Certificate certificate,
X509Chain chain,
SslPolicyErrors sslPolicyErrors)
if ((sslPolicyErrors & SslPolicyErrors.RemoteCertificateChainErrors)
== SslPolicyErrors.RemoteCertificateChainErrors)
return false;
else if ((sslPolicyErrors & SslPolicyErrors.RemoteCertificateNameMismatch)
== SslPolicyErrors.RemoteCertificateNameMismatch)
Zone z;
z = Zone.CreateFromUrl(((HttpWebRequest)sender).RequestUri.ToString());
if (z.SecurityZone == System.Security.SecurityZone.Intranet
|| z.SecurityZone == System.Security.SecurityZone.MyComputer)
return true;
return false;
return false;

Hi
Abhilash Francis,
Could you tell us your scenario? What's your project? Is it a WCF service?
Looks like this is not a code issue.
Just from the error information,
it seems that you do not configure the service certificate very well so as to Server was unable to process request.
I am not completely sure what the real scenario is, but it might be a problem of that It is a WCF services application, please check these following articles to configure the service certificate.
If not, please feel free to let me know.
How to: Configure an IIS-hosted WCF service with SSL
Could not establish trust
relationship for the SSL/TLS secure channel
Hope this helps.
Best regards,
Kristin
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

The underlying connection was closed error FIM 2010

I have a fresh installation of FIM 2010 R2. After installation I am able to see FIM portal through account used for installation.
however in evenvwr I am continously getting below error. During instllation EXCHANGE team provided the address 'outlook.company.in' as the address and I selected
all option like SSL and pooling on installation screen.
Below error seems related with Exchagne but I am not able to undserstand what should I demand from exchange team.
Kindly suggest.
Error
System.Web.Services: System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according
to the validation procedure.
   at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception)
   at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
   at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.ConnectStream.WriteHeaders(Boolean async)
   --- End of inner exception stack trace ---
   at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
   at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at Microsoft.ResourceManagement.WebServices.Mail.Exchange.ExchangeServiceBinding.FindItem(FindItemType FindItem1)
   at Microsoft.ResourceManagement.WebServices.Mail.Exchange.MailChannel.ExchangeMailChannelListener`1.ExchangeMailListener.<OnPollTimerExpired>b__0(Boolean findUnreadItems)
   at Microsoft.ResourceManagement.WebServices.Mail.Exchange.MailChannel.ExchangeMailChannelListener`1.ExchangeMailListener.OnPollTimerExpired(Object state)
Thanks,
Mann

Hello,
You have to connect to the EWS (Exchange Web service: https://mailserver/ews/exchange.asmx) with the FIMService account to get the certificate of EWS.
http://technet.microsoft.com/en-us/library/ff512686%28v=ws.10%29.aspx
Regards,
Sylvain

The underlying connection was closed: An unexpected error occurred on a receive..Exception.Message - while executing powershell command for sharepoint online site

" +The underlying connection was closed: An unexpected error occurred on a receive..Exception.Message " OR sometimes
"The remote server returned an error: (503) Server Unavailable..Exception.Message"
Getting exception above when performing various operation (site coll creating, group creation, adding users to group) for sharepoint online (Office 365) site using powershell script.
I want to create 3500 site collections using PS script. In-between getting above exception so it will skip one site collection creating and working again. for eg. after creating 11 site coll, script will through above exception and so 12th site coll will
not be create but working fine from 13 and so on...

Remote server seems working to me...any additional check?
if problem with remote server then may be loop to create site provisioning should not start again..Right?
any idea?

Polycom CX600 The connection was closed before TLS negotiation completed

Similar Messages

Maybe you are looking for