The GoTo Community is currently experiencing some technical issues affecting new posts and comments. You may need to reload the page you are on before you can post a comment. We are actively working with our service provider and apologize for the frustration.
Forum Discussion
Danny6
2 years agoNew Contributor
Error when connecting. (Error occurred error: 14094410:lib(20):func(148):reason(1040))
     Getting this error when connecting to a client.    So far only one member of my team can connect to this client but everyone else gets this error. 
- 2 years agoHere is the solution for computers showing this error due to an expired certificate: As admin, open the command prompt of my computer in LogMeIn Client 
 1. cd "C:\Program Files (x86)\LogMeIn\x64"
 2. cmd
 3. logmein.exe cert -createca "LogMeIn CA on %COMPUTERNAME%" -createsc "%COMPUTERNAME%"
 4. net stop LogMeIn && net start LogMeIn(Thank you Michal_orc ) Depending on where the computer is located, you may run into an error "Country too long". The problem is that Windows returns a 3-digit "sub-region-code" instead of the 2-character "alpha-2" country code. Check for example: https://github.com/lukes/ISO-3166-Countries-with-Regional-Codes/blob/master/all/all.csv To overcome on this problem you have to explicitly specify the 2-digit code of your country. So find the "alpha-2" code of your country in the table above and issue the following command in an administrator command prompt: "C:\Program Files (x86)\LogMeIn\x64\LogMeIn.exe" cert -createca "Default CA" "<alpha-2 code of your coutry>" -createsc For example if you are in Mexico, then issue the following command: "C:\Program Files (x86)\LogMeIn\x64\LogMeIn.exe" cert -createca "Default CA" "MX" -createsc On Mac the certificates are stored in files: - /Library/Application Support/LogMeIn/CA.pem - /Library/Application Support/LogMeIn/server_ex.pem First these files have to be deleted: - sudo rm /Library/Application Support/LogMeIn/CA.pem - sudo rm /Library/Application Support/LogMeIn/server_ex.pem Then restart the daemon: - sudo launchctl stop com.logmein.logmeinserver 
KateG
2 years agoGoTo Manager
Hi Danny6 Have you tried a full uninstallation of LMI including the registry keys?
If not can you Uninstall the affected computer, reboot the computer, install again, and test the connection?
Michal_orc
2 years agoActive Contributor
I have the same problems. I reinstall LMI; the issue still exists
but
I can login from LogMeIn Client to MainMenu.
I can't start Remote Control
I also noticed that the problem occurs more often on Windows 11
Unfortunately I don't have a solution yet
I send a message to HelpDesk, but I was unable to call