Error: "Exception! Error calling ParseLocalConnectionString"

Version 10

    Verified Product Versions

    LANDESK Management Suite 9.6LANDESK Management Suite 2016.xLANDESK Endpoint Manager 2017.x

    Error: ParseLocalConnectionString Parameter name: local_connection_string

    Stuck while checking database pre-requisites

    Or error may occur any time the database is accessed via coredbutil.exe

     

    This document will cover a few different things that can contribute to getting this error message.


    The very first step to confirm this error message is to launch coredbutil.exe located here:

     

    "C:\Program Files\LANDesk\ManagementSuite\CoreDbUtil.exe" 

     

    This communication works with SSL and IIS to complete the connection.

    Here is the error message that you will most likely get while launching CoreDBUtil.exe

     

    coredbutilfailure.PNG

     

    Now that we have identified that the utility is unable to launch, let's proceed with some of the easier steps to correct this issue first.

     

    Solution #1 Check bindings in IIS for port 443.

    Here are the steps to check the bindings on 443.

     

    1. Open ISS manager
    2. Right-click on default sites.
    3. Select Edit bindings.
      EditBinding.PNG
    4. Select the binding for port 443 and then go to edit.
      443binding.PNG
    5. On the next screen, we will want to make sure that the hostname field is blank.

     

    Make sure that the SSL Cert is set to Secure Token Server

     

    Solution #2   Check Landesk Configure Services and the local Connection registry key.

    1. For this step, we will be checking the registry key to make sure it is not blank and, Matches what is seen under “Landesk Configure Services”

      Let's go ahead and launch “SvcCfg.exe”,   Usually you can launch this application by clicking on start then searching for Configure Services.     If your system is unable to find it, here is the full path:

      "C:\Program Files\LANDesk\ManagementSuite\SvcCfg.exe"
      ConfigureService.PNG
      Take note of the Server,  Username and Database.

      While we have Configure Services open,  we should test the login for the DB.

    2. Put a space after the password and then delete the space.
    3. Click apply.  Afterward, you should get a prompt telling you to restart the service if everything is accurate.
      Successful.PNG
    4. Next we need to open Regedit then browse to:  HKLM\Software\LANDesk\ManagementSuite\Connections\Local
    5. Make sure that the Database Name, Server, and User all match the information found in step 1.
    6. Check to make sure that IsNTLM is set to false.

     

    localconnection.PNG

    Solution #3   Check to make sure TLS 1.0/1.1 is enabled.

     

    The easiest way to enable TLS 1.0/1.1 is going to be with a tool named IIScrypto.

     

    Click here to download the tool.

     

    When you first launch the tool, everything might be grayed out.    Double click on TLS 1.1 to enable it.

     

    isscrypto.PNG

    Click apply and then restart the server.

     

    Now follow the same steps on the SQL server.

     

    Once both servers come back up, let's go ahead and try to launch Coredbutil.exe one more time.

     

    CoreDbutilSuccess.PNG

     

    If coredbutil.exe launched successfully, you should now be able to proceed with your upgrade or login.

     

     

    Solution #4   Check that IIS Application Pools are using the correct  .NET CLR Version.

     

    They should look as follows:

     

    Solution #5   Check that ISAPI and CGI Restrictions are allowed at the IIS Server level.