Alt-PrintScreen causes problems v3.01

Disabled

Published 7 years ago

I was making some documentation and did an Alt-PrtScn on the Wayk Now window that was connected to a remote computer, it caused the following:

1. The remote computer that Wayk Now is connected to is un-responsive after Alt-PrtScn
2. The local computer freezes up for a few seconds
3. Disconnecting from the remote computer causes Wayk Now not to be able to re-connect to the remote computer
4. The remote computer has to be re-started in order to re-connect (not good considering it is remote)

This is with v3.01 Enterprise

All Comments (3)

Richard Markiewicz

Published 7 years ago

Hello

First of all, sorry for the inconvenience caused by the issue. I understand the inconvenience when you can't reconnect to your remote machine. So we would like to address this.

I have tried to reproduce the issue here, but I could not. Some more information would help me: are the local and remote computers both running Windows? Is the remote system using the unattended service?

A good first troubleshooting step would also be to try updating your Wayk installations to 3.0.3 (it's the current release available on wayk.devolutions.net).

Thanks very much,

Richard Markievicz

(user deleted)

Disabled

Published 7 years ago

The local system is a Windows 10 x64 v1803 and the remote system is Windows 2012 R2.

The remote system is running un-attended.

Del

Richard Markiewicz

Published 7 years ago

Hi Del

Thanks for the update. Unfortunately, I was still not able to reproduce the issue. Can you check the state of the following setting on the remote machine:

System Configuration (msconfig) > Boot > Advanced options > Debug

Can you enable logging on the remote system, and reproduce the issue once more, and send me the log?

The logs for the unattended service are different from the main application.

From an elevated command-prompt, you can enable the logs with the following command:
wayk-now config --global LoggingLevel 1

Otherwise, you can manually edit %ProgramData%\Wayk\WaykNow.cfg and change "LoggingLevel" to 1. Once the modification is done, you can restart the service (right-click Wayk Unattended Now Service in services.msc). Once it is running again with the logs enabled, reproduce the issue one last time, then collect the logs at the following location:

%ProgramData%\Wayk\logs\NowService.log

And send them to support@devolutions.net or post them here.

Thank you for your patience,

Richard Markievicz