You are viewing limited content. For full access, please sign in.

Question

Question

"An error has occurred while starting web scanning WSE910"

asked on September 16, 2016

My client is getting an error when clicking on the LFscanning button in web access, I have tried a repair and synchronized the time in windows, but it still comes up. Has any one else experienced this issue? The user is on web access 9.1.1.545, and LFScanning 9.1.1.482 :

"Error:
Exception has been thrown by the target of an invocation.

    ResponseProcessingException:
    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.

        SecurityFault:
        Message Expired

            Exception:
            WSE066: Timestamp is expired. This indicates a stale message but may also be caused by 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."

0 0

Answer

APPROVED ANSWER SELECTED ANSWER
replied on September 21, 2016

Did you synchronize the time on the server too?

2 0

Replies

replied on September 19, 2016

Does the issue occur if you login with a different windows/LF account on the same machine?

Does it occur on other machines or is the issue machine specific?

0 0
replied on September 20, 2016

After some testing it seems the issue is local to the computer. Any user that uses it is subject to the error.

0 0
replied on September 21, 2016

Check the system time on the machine.  If possible, set the system time to synchronize with a valid, known outside source.  Then try scanning again.

0 0
replied on September 21, 2016

I tried that already and it still gives me the error. I synchronized with time.windows.com but it didn't make a difference.

0 0
APPROVED ANSWER SELECTED ANSWER
replied on September 21, 2016

Did you synchronize the time on the server too?

2 0
replied on September 23, 2016

After synchronizing on the server the error has gone away. Thanks for the help!

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.