Content deployment error - Either the URL for the destination web application is not valid, or you do not have permissions to the Central Administration site on destination server farm
We have 2 identical MOSS 2007 sp2 (12.0.0.6520 ) server farms in our current environment. The staging server farm is behind our firewall, with an internet facing server farm in our DMZ. Last night when we attempted to create a new content deployment job, we received the following error when we click "Connect" when creating the content deployment job.------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------Either the URL for the destination Web application is not valid, or you do not have permissions to the Central Administration site on the destination server farm. Error details: The remote upload Web request failed.-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------We can successfully navigate to the Central Administration page on the receiving server from the staging server, using the same login information we enter into the following fields:Connect by using a different account, basic authentication, and enter the correct DMZ user name and password.The really strange thing is that we have another content deployment job using the same credentials as the one we attempted to create, and it works fine. We had a previous deployment job on the server that we deleted and gave the one last night the same name, but I doubt that could be causing the issue?Thanks any and all help.
February 26th, 2010 6:35pm

This looks more like its not finding the web application URL than an issue with credentials. Can you check if the destination URL does not have errors?
Free Windows Admin Tool Kit Click here and download it now
February 26th, 2010 7:19pm

Thank you, I will check on this. I failed to mention that we are using SSL encryption between the staging and DMZ servers. The new web application also uses https://, I found this in the trace logs:02/26/2010 01:16:01.20 w3wp.exe (0x34AC) 0x31F4 CMS Content Deployment 8nh5 Exception The remote upload Web request failed. 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... 02/26/2010 01:16:01.20* w3wp.exe (0x34AC) 0x31F4 CMS Content Deployment 8nh5 Exception ....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.runTryCode(Object userData) at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData) at System.Threading.ExecutionContext.Run(ExecutionContext ... 02/26/2010 01:16:01.20* w3wp.exe (0x34AC) 0x31F4 CMS Content Deployment 8nh5 Exception ...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.SharePoint.Publishing.Internal.Administration.ContentDeploymentRemoteImportSoapClient.GetVirtualServ... 02/26/2010 01:16:01.20* w3wp.exe (0x34AC) 0x31F4 CMS Content Deployment 8nh5 Exception ...ersInformation() at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentPath.GetVirtualServersInformation(String destinationAdminServerUrl, ICredentials credentials) at Microsoft.SharePoint.Publishing.Internal.CodeBehind.DeployPathPage.OnValidateDestinationAdminServerUrl(Object sender, ServerValidateEventArgs e)
February 26th, 2010 7:35pm

Because we had 1 ssl cert on 2 web applications, we where getting the error. We applied 2 separate certs and bound specific IP addresses to the web applications to resolve this error.
Free Windows Admin Tool Kit Click here and download it now
March 4th, 2010 10:17am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics