We have to servers that sync using sync-wdserver, this has worked fine up until now. Recently we got an SSL certificate for a site hosted on those servers, it was initially installed via iis 8 on both servers however it was later removed and the SSL installed on the load balancer instead. Since this occurred, the two servers are unable to sync in the regular fashion, the following error occurs on the slave:
User:
Client IP: private ip here
Content-Type: application/msdeploy
Version: 9.0.0.0
MSDeploy.VersionMin: 7.1.600.0
MSDeploy.VersionMax: 9.0.1955.0
MSDeploy.Method: Sync
MSDeploy.RequestId: 8f1de4f4-9d33-41b1-abd2-045c2907f894
MSDeploy.RequestCulture: en-US
MSDeploy.RequestUICulture: en-US
ServerVersion: 9.0.1763.0
Skip: objectName="^configProtectedData$"
Provider: webServer, Path:
A tracing deployment agent exception occurred that was propagated to the client. Request ID '8f1de4f4-9d33-41b1-abd2-045c2907f894'. Request Timestamp: '3/31/2017 12:18:20 PM'. Error Details:
System.Runtime.InteropServices.COMException (0x80070520): A specified logon session does not exist. It may already have been terminated. (Exception from HRESULT: 0x80070520)
at Microsoft.Web.Deployment.AxNative.NativeMethods.HttpSetSslConfiguration(String binding, String hash, String appId, String storeName, Int32 certCheckMode, Int32 freshnessTime, Int32 urlRetrievalTimeout, String ctlIdentifier, String ctlStoreName, Int32 flags)
at Microsoft.Web.Deployment.HttpCertCommitableItem.ApplyConfiguration()
at Microsoft.Web.Deployment.HttpCertCommitableItem.CommitChanges(DeploymentCommitContext commitContext)
at Microsoft.Web.Deployment.DeploymentCommitContext.CommitChanges(DeploymentSyncOptions syncOptions, DeploymentBaseContext baseContext)
at Microsoft.Web.Deployment.DeploymentObject.SyncToInternal(DeploymentObject destObject, DeploymentSyncOptions syncOptions, PayloadTable payloadTable, ContentRootTable contentRootTable, Nullable`1 syncPassId, String syncSessionId)
at Microsoft.Web.Deployment.DeploymentAgent.HandleSync(DeploymentAgentAsyncData asyncData, Nullable`1 passId)
at Microsoft.Web.Deployment.DeploymentAgent.HandleRequestWorker(DeploymentAgentAsyncData asyncData)
at Microsoft.Web.Deployment.DeploymentAgent.HandleRequest(DeploymentAgentAsyncData asyncData)
It seems some broken certificate somewhere is causing an issue, when I run the sync-wdserver from powershell on the master I notice the following warning before the logon error above also appears below this warning:
WARNNING: skipping source cert ("some hash appears here") because of rule skipinvalidsource. No certificate found in store My with has "same hash as above"
I assume the issue is related to the SSL certificates that were installed and removed, somewhere an issue has been caused. Can anyone clarify what the problem is and if possible how to resolve it so we are able to sync the servers successfully again?