Corier push in 7.4.1 ERROR: SOAP header CourierSoapAuthentication was not understood. ?
Application Error
SOAP header CourierSoapAuthentication was not understood.
Error details
System.Web.Services.Protocols.SoapHeaderException: SOAP header CourierSoapAuthentication was not understood.
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Umbraco.Courier.RepositoryProviders.WebServiceProvider.RepositoryWebservice.CloseSession(String sessionKey)
at Umbraco.Courier.RepositoryProviders.CourierWebserviceRepositoryProvider.CloseSession(String sessionKey)
at Umbraco.Courier.RepositoryProviders.CourierWebserviceRepositoryProvider.Dispose(Boolean disposing)
at Umbraco.Courier.RepositoryProviders.CourierWebserviceRepositoryProvider.Dispose()
at Umbraco.Courier.Core.Common.Extensions.GlobalExtensions.DisposeIfDisposable(Object input)
at Umbraco.Courier.Core.Repository.Dispose(Boolean disposing)
at Umbraco.Courier.Core.Repository.Dispose()
at Umbraco.Courier.UI.Dialogs.CommitItem.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
the article asked to add following lines in system.web section of web.config and I did and I infact installed WSE 3.0 too. No luck. Could somebody put light on this?
We found the problem was incompatibility between two environment that were built using different version of the framework, or something like that anyway. When they shared exactly the same DLLs, there was no issue.
Corier push in 7.4.1 ERROR: SOAP header CourierSoapAuthentication was not understood. ?
Application Error
SOAP header CourierSoapAuthentication was not understood.
Error details
System.Web.Services.Protocols.SoapHeaderException: SOAP header CourierSoapAuthentication was not understood. at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Umbraco.Courier.RepositoryProviders.WebServiceProvider.RepositoryWebservice.CloseSession(String sessionKey) at Umbraco.Courier.RepositoryProviders.CourierWebserviceRepositoryProvider.CloseSession(String sessionKey) at Umbraco.Courier.RepositoryProviders.CourierWebserviceRepositoryProvider.Dispose(Boolean disposing) at Umbraco.Courier.RepositoryProviders.CourierWebserviceRepositoryProvider.Dispose() at Umbraco.Courier.Core.Common.Extensions.GlobalExtensions.DisposeIfDisposable(Object input) at Umbraco.Courier.Core.Repository.Dispose(Boolean disposing) at Umbraco.Courier.Core.Repository.Dispose() at Umbraco.Courier.UI.Dialogs.CommitItem.OnInit(EventArgs e) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
I also added based on below article
https://devnet.kentico.com/forums/f65/t34740/synchronization-staging-giving-soap-header-secu
the article asked to add following lines in system.web section of web.config and I did and I infact installed WSE 3.0 too. No luck. Could somebody put light on this?
Hello did you find any solution for this? I have the same issue.
We found the problem was incompatibility between two environment that were built using different version of the framework, or something like that anyway. When they shared exactly the same DLLs, there was no issue.
is working on a reply...