I know this has been posted alot but I want to know what people have
done to solve this issue, I am using WSE 3.0 and my webservice works
for about 100 clients but fails for about 2. They are about 5-10
minutes out of wack and I have tried syncing the workstations and this
works for a couple of hours before they resync with their domain
controllers (unfortunately I am not able to get to the domain
controllers of our clients networks). I have added this code to the
config:
<security>
<defaultTtlInSeconds>86400</defaultTtlInSeconds>
<timeToleranceInSeconds>86400</timeToleranceInSeconds>
</security>
but this still doesn't work. Somebody stated that they also added:
<tokenIssuer>
<autoIssueSecurityContextToken enabled="false"/>
</tokenIssuer>
But this isn't available in WSE 3.0, is there an equvalent that I am
missing?
Just in case this helps this is a stack trace:
WSE910: An error happened during the processing of a response message,
and you can find the error in the inner exception. You can also find
the response message in the Response property.:
at
Microsoft.Web.Services3.Xml.SoapEnvelopeReaderWrapper..ctor(SoapClientMessage
message, String messageContentType)
at
Microsoft.Web.Services3.WebServicesClientProtocol.GetReaderForMessage(SoapClientMessage
message, Int32 bufferSize)
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 ExtractLibrary.PMSExchangeService.PMSExchangeWse.Login()
at
ExtractLibrary.ExtractLibrary.ExtractJobs.RunServerTasks(AppSettings
currSettings):
Inner Exception:
An error was discovered processing the <Security> header:
at Microsoft.Web.Services3.Security.Utility.Timestamp.CheckValid()
at
Microsoft.Web.Services3.Security.Utility.Timestamp.LoadXml(XmlElement
element)
at
Microsoft.Web.Services3.Security.Utility.Timestamp..ctor(XmlElement
element)
at Microsoft.Web.Services3.Security.Security.LoadXml(XmlElement
element)
at
Microsoft.Web.Services3.Security.SecurityInputFilter.ProcessMessage(SoapEnvelope
envelope)
at
Microsoft.Web.Services3.Security.Wse2PipelinePolicy.LegacyFilterWrapper.ProcessMessage(SoapEnvelope
envelope)
at Microsoft.Web.Services3.Pipeline.ProcessInputMessage(SoapEnvelope
envelope)
at
Microsoft.Web.Services3.Xml.SoapEnvelopeReaderWrapper..ctor(SoapClientMessage
message, String messageContentType)
RyanS - 29 Nov 2006 00:11 GMT
Just as a side note, this error seems to be returned from the client
only when trying to access the webservice via a windows service, it
works fine while running it as a windows forms application.