cubernaut

Microsoft Visual C++ Runtime Library Runtime Error

42 posts in this topic

I get this error when I try to run Synergy.exe:

"This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information."

 

I get the error with Synergy versions 1.8.4, 1.8.7 and 1.8.8.

Has anybody else encountered this problem?

Is there a known solution?

synergy_error.png

Share this post


Link to post
Share on other sites

Have you tried rebooting your machine already?

Share this post


Link to post
Share on other sites

Can you try uninstalling it then reboot machine. Re-install after the reboot.

Share this post


Link to post
Share on other sites

I installed v1.9.0-rc3.

The error does not occur anymore, but the main window takes about 40 seconds to appear.

The client does not connect to the server (Connection was refused).

Server log:

[2017-05-22T22:20:01] INFO: connecting to service...

[2017-05-22T22:20:48] INFO: connection established

[2017-05-22T22:18:43] DEBUG1: registered event type ISocketEvents::disconnected as 14

[2017-05-22T22:18:43] DEBUG: ipc client disconnected

[2017-05-22T22:18:43] DEBUG: ipc client proxy removed, connected=0

[2017-05-22T22:20:01] DEBUG: accepted ipc client connection

[2017-05-22T22:20:48] DEBUG: start ipc handle data

[2017-05-22T22:20:48] DEBUG: ipc read: IHEL

[2017-05-22T22:20:48] DEBUG2: readf(%1i)

[2017-05-22T22:20:48] DEBUG2: readf: read 1 byte integer: 1 (0x1)

[2017-05-22T22:20:48] DEBUG: finished ipc handle data

[2017-05-22T22:20:48] DEBUG: ipc hello, type=gui

[2017-05-22T22:20:48] INFO: watchdog status: error

Share this post


Link to post
Share on other sites

I followed the instructions with no success.

I installed 1.9.0 on the client (Win7 64bit) as well, but it has 50% CPU usage, so that won't work for me.

Share this post


Link to post
Share on other sites

Can you post a screenshot of both machine's Synergy interface?

Share this post


Link to post
Share on other sites

So it successfully connected now, right? Can you set the logging level back to Info? This will lessen the CPU usage.

Share this post


Link to post
Share on other sites

Are you familiar with the interface?

I suppose it states that it connected to the SERVICE, not to the SERVER...

The clients log level is set to info, but that has no effect on the CPU usasge. 50% CPU usage is an indicator for an error and should not result from a high logging level.

 

Share this post


Link to post
Share on other sites

Due to the installation of 1.9.0 on the client I now have a new problem. The synergy service can't be stopped and is taking all the CPU time of one processor.

I can't even uninstall this version, because the uninstall routine is unable to stop the service and fails.

Share this post


Link to post
Share on other sites

The service can NOT be stopped, how should I disconnect?

What do you mean?

How should that help?

Share this post


Link to post
Share on other sites

I was able to uninstall the hanging 1.9.0 version on the client by manually disabling the service and rebooting. That way the service was not started and the uninstall routine worked...

To sum up the situation:

1.9.0 is running with long delays on the Win 10 server.

1.8.8 is running on the Win 7 client.

A connection cannot be established. The server log:

[2017-05-23T16:29:40] INFO: starting server
[2017-05-23T16:29:42] INFO: config file: C:/Users/Philip Groß/AppData/Local/Temp/Synergy.l15048
[2017-05-23T16:29:42] INFO: log level: INFO
[2017-05-23T16:29:44] ERROR: ipc connection error, remote host closed
[2017-05-23T16:29:45] INFO: connecting to service...
[2017-05-23T16:29:45] INFO: connection established
[2017-05-23T16:29:44] ERROR: invalid ipc message
[2017-05-23T16:29:44] DEBUG: ipc disconnect, closing stream
[2017-05-23T16:29:44] DEBUG: finished ipc handle data
[2017-05-23T16:29:44] DEBUG: start ipc handle data
[2017-05-23T16:29:44] DEBUG: finished ipc handle data
[2017-05-23T16:29:44] DEBUG: ipc client proxy removed, connected=0
[2017-05-23T16:29:44] DEBUG: empty command, elevate=1
[2017-05-23T16:29:44] INFO: service command updated
[2017-05-23T16:29:45] DEBUG: accepted ipc client connection
[2017-05-23T16:29:45] DEBUG: start ipc handle data
[2017-05-23T16:29:45] DEBUG: ipc read: IHEL
[2017-05-23T16:29:45] DEBUG2: readf(%1i)
[2017-05-23T16:29:45] DEBUG2: readf: read 1 byte integer: 1 (0x1)
[2017-05-23T16:29:45] DEBUG: finished ipc handle data
[2017-05-23T16:29:45] DEBUG: ipc hello, type=gui
[2017-05-23T16:29:45] INFO: watchdog status: error

 

Share this post


Link to post
Share on other sites

Can you try pinging the client machine from the server machine (and vice versa) ?

Share this post


Link to post
Share on other sites

Yes, that works.

Synergy has worked in the exact same setup for years, only since I updated to 1.8.8 the problem arose.

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now