[Solved] WS-E 2.0 problem: "Creation time in the timestamp can not be in the future" [modified]
-
Hi! I'm calling on a webservice with WS-E 2.0 (because I need to use Dime), and the server returns this exception message:
Microsoft.Web.Services2.Security.SecurityFault: An error was discovered processing the <Security> header ---> System.Exception: Creation time in the timestamp can not be in the future.
I've allready checked that the clock on both machines are in sync (also the same timezone). I've also tried different combinations of setting the <timeToleranceInSeconds> and the <defaultTtlInSeconds> settings in both the clients app.config file and the servers web.config file. still gets me the same exception... Does anyone here have any suggestions on how to fix this? -- modified at 9:53 Thursday 15th June, 2006 Found it... While trying to fix this problem, I had inadvertenly cleared the Security collection of the SoapRequestHeader, so that the other two fixes didn't seem to work... Well, they did work, after removing that statement.