Error: "Exception! Error calling ParseLocalConnectionString"

Version 17

    Verified Product Versions

    Endpoint Manager 9.6Endpoint Manager 2016.xEndpoint Manager 2017.xEndpoint Manager 2018.x

    Exception! 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"

    or

    %LDMS_HOME%CoreDbUtil.exe 

     

    This communication works with SSL and Microsoft's Internet Information Services ( 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 CoreDbUtil.exe is unable to launch, let's proceed with some of the easier steps to correct this issue first.

     

    Solution #1 Ensure IIS is running

    For good measure, restart IIS using the following steps

     

    1. Open an elevated command line
    2. Type "iisreset" and hit enter

     

    You should see IIS stop (if started) and then start back up

     

    Solution #2 Check bindings in IIS for https / port 443

    Here are the steps to check the bindings on 443.

     

    1. On the Core Server open IIS manager
    2. Right-click on a Default Web Sie
    3. Select Edit Bindings...
      EditBinding.PNG
    4. Select the binding for https / 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 #3   Check Configure LANDESK Software Services and the Windows registry key HKLM\Software\LANDesk\ManagementSuite\Core\Connections\Local

    1. For this step, we will be checking the Windows Registry key to make sure it is not blank, and matches what is seen under “Configure LANDESK Software 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" or %LDMS_HOME%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 Database
    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. ( You must restart the services that use the database before your changes will take effect. )
      Successful.PNG
    4. Next we need to open Regedit then browse to:  HKLM\Software\LANDesk\ManagementSuite\Core\Connections\Local
    5. Make sure that the name of the Database, name of the Server, and User all match the information found in step 1
    6. Check to make sure that the value of IsNTLM is set to false

     

    localconnection.PNG

    Solution #4   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 IIScrypto. When you first launch the tool IIScrypto, everything might be grayed out. Double click on TLS 1.1 to enable it.

     

    isscrypto.PNG

    Click apply and then restart the Windows Server / Core Server. Now follow the same steps on the SQL Server. Once both Windows 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 #5 Check that IIS Application Pools are using the correct  .NET CLR Version.

     

    On the Core Server open IIS Manager. Application Pools should look as follows:

     

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

    Solution #7 Check if any proxy server is used in IE - Options - Connections