02-09-2012 10:23 AM
This silly clock synchroniztion error is really delaying my project, what Timestamp is in the future?
It makes no sense, how do I fix this so I can proceed in development.?
SoapFault Object ( [message:protected] => An error was discovered processing the header ---> WSE065: Creation time of the timestamp is in the future. This typically indicates lack of synchronization between sender and receiver clocks. Make sure the clocks are synchronized or use the timeToleranceInSeconds element in the microsoft.web.services3 configuration section to adjust tolerance for lack of clock synchronization. [string:private] =>
02-09-2012 10:51 AM
The message means that the client clock is wrong. The timezone might be set incorrectly.
If the SOAP request is timestamped too far in the future or in the past, the server will reject it. We generally run into this error with mobile apps since folks don't always have their devices set to sync to network time.
09-13-2012 12:36 PM
I am also experiencing this.. and it just started recently.
I checked my computer's clock, my server's clock and both are accurate.
We are preparing for a major, time sensitive release and I am not able to continue testing without getting past sending an envelope.