The GoTo Community is currently experiencing some technical issues affecting new posts and comments. We are actively working with our service provider and apologize for the frustration.

Forum Discussion

Danny6's avatar
Danny6
New Contributor
2 years ago
Solved

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.
  • GlennD's avatar
    GlennD
    2 years ago

    Here 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 

     

GlennD's avatar
GlennD
GoTo Manager
2 years ago

Michal_orc Please email the log file to gotoservice at logmein dot com

 

GlennD's avatar
GlennD
GoTo Manager
2 years ago

Michal_orc Danny6  I checked with Support and after reviewing another customer's log files it was suggested that reinstalling the LMI SSL Certificate may be the solution. Can you please try the following on one of your affected PCs?

  1. Launch command prompt (as administrator)
  2. Change directory to “C:\program files\logmein\x86” if it's a 32 bit OS or "C:\program files (x86)\logmein\x64" if its 64 bit.
  3. Issue the command :
    logmein.exe cert -createca "LogMeIn CA on %COMPUTERNAME%" -createsc "%COMPUTERNAME%"
  4. Turn off / on LogMeIn from the system tray icon.
    If all goes well, the following should appear in the registry:
    HKLM\Software\LogMeIn\v5\Net
    Key (Dword) CertificateIDEx. Each value will have a bunch of gibberish
    HKLM\Software\LogMeIn\v5\WebSvc
    Key (Dword) HostCertIDSent and HostCertSent. Each value will have a bunch of gibberish
  5. Try connecting again

 

  • vrajm's avatar
    vrajm
    Active Contributor
    7 months ago

    i don't see HostCertSent
    I am running LMI on Win XP SP3

  • Hemantrathore02's avatar
    Hemantrathore02
    New Contributor
    2 years ago

    Hi Glean,

     

    I'm happy to report that the solution you provided is working perfectly fine. However, I was wondering why this issue is happening throughout the whole company. Is there a way to apply the solution to all computers at once? Also, is it mandatory to apply the fix? While the issue is manageable for one or two systems, it could become a major problem if it affects all of the company's host computers.

     

    Thanks.

    • GlennD's avatar
      GlennD
      GoTo Manager
      2 years ago

      Hi Hemantrathore02, to date this issue was only being reported for minority of individual systems, this is why we have not released a new client build requiring everyone to update their clients.  

       

      • dlorite's avatar
        dlorite
        Visitor
        2 years ago

        Hi GlennD 

         

        What you say is not true, our company has 606 computers with logmein as of today and it is failing in all of them.

        You should give us a solution that does not consist of repairing computer by computer. This is creating a lot of inconvenience for us.

         

        Thank you

  • Michal_orc's avatar
    Michal_orc
    Active Contributor
    2 years ago

    If I need to do the entire procedure remotely, I do

     

    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

     

    GlennD Your solution works
    Thank you

    • GlennD's avatar
      GlennD
      GoTo Manager
      2 years ago

      Thank you Michal_orc for reporting back. We have a ticket opened with the Prod team and I will make a note that this was successful.

       

  • erdemtopcu's avatar
    erdemtopcu
    Visitor
    2 years ago

    Hi

    After the update numbered 4.1.0.15428 (Mar 14, 2024) was installed on our host computers, we are unable to establish remote connections.

    We kindly request your urgent support regarding this matter.