Forum Discussion
Hi chrisg750,
Can you provide more details about your issues using Ctrl+Alt+Delete? What operating systems are you connecting to, what happens or doesn't happen when you click the Ctrl+Alt+Delete button in the toolbar?
I cannot even find a CTRL-ALT-DEL on an unattended access connection. WHERE IS IT? GotoAssist 4 was fine until it randomly stopped creating sessions. It eventually creates one and works normally, but this is very frustrating!
- chrisg7503 years agoActive Contributor
If you hover over the the top toolbar you will see it. It doesn't work 3/4 of the time for me lately, but the button is there.
- chrisg7503 years agoActive Contributor
If you hover over the the top toolbar you will see it. It doesn't work 3/4 of the time for me lately, but the button is there.
- GlennD3 years agoGoTo Manager
Hi chrisg750,
Digging into this issue further, we have a primary and secondary method of passing the Ctrl+Alt+Delete to the client computer. If the Primary method fails the Secondary method is used. Please check for the following on the Unattended computers.
The first place to look is going to be this file GoToAssistUnattended.srv.log, you will find it in C:\Program Files (x86)\GoToAssist Remote Support Unattended\xxxxxxxxxxx\appdata
Primary method:
Search for CtrlAltDel message received, in case of error you will see:
"Primary CtrlAltDel injection failed with error code:" There should also be an error recorded in GoToAssistTools64/32.log in the same folder.Secondary method:
Check GoToAssistProcessChecker.srv.log for "Sending CtrlAltDel"
If this log is not present the command was unsuccessful, in this case one of these errors should be seen in GoToAssistUnattended.srv.log:
"Unable to open service control manager"
"Unable to open service"
"Sending service control message 128 failed, with error code"- chrisg7502 years agoActive ContributorHi GlennD thanks for the reply . Appreciate the response. And sorry for the late reply. Being service related would make sense. I will take some to look into this. I have a specific workstation that I MUST use v4 instead of v5 because of this exact issue. Never took the time to look into it as became too frustrating and time consuming. But I will definitely follow up soon. Thanks again.