Quantcast
Channel: Ivanti User Community : All Content - Installation
Viewing all articles
Browse latest Browse all 524

CoreDbUtil Error During 9.6 Service Pack Installation

$
0
0

Issue

 

Upgrading the LDMS Core fails, and gives prompt:

 

Note:the popup may be hidden behind other windows. If the upgrade appears frozen, move the windows on the screen around to reveal the popup.

 

Login for user failed: {username}

1-prompt.png

 

Cause

 

In some cases, the ldcryptoconfig.xml file is missing or corrupted from the Keys directory on the Core Server (C:\Program Files\LANDesk\Shared Files\Keys) which causes the upgrade to fail.

 

 

Solution


  • Keep clicking Ok on the "Login Failed for user..." box until you get to a screen that you can click cancel. You may need to move the screen multiple times to click Ok to move forward. Go ahead and cancel the upgrade.

2-errored.png

 

  • Rename theldcryptoconfig.xmlfile in\Program Files\LANDesk\SharedFiles\Keysfolder (if this file does not exist move to the next step)
  • In all programs, please click on LANDESK ->LANDESK Configure Services and re-enter your database information.
  • In the registry key (HKEY_LOCAL_MACHINE\SOFTWARE\LANDesk\ManagementSuite\Core\Connections\Local) rename the PWD Scheme
  • In the registry key (HKEY_LOCAL_MACHINE\SOFTWARE\LANDesk\ManagementSuite\Core\Connections\Local) rename the password
  • In the registry key (HKEY_LOCAL_MACHINE\SOFTWARE\LANDesk\ManagementSuite\Core\Connections\Local) rename the PWD Encrypt
  • InHKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\LANDesk\ManagementSuite\Core_x86\Connections\Localmake sure the user and password values match the values in the 64 bit registry key(HKEY_LOCAL_MACHINE\SOFTWARE\LANDesk ManagementSuite\Core\Connections\Local) if they don't match you will get an error that the password does not match. (if these keys do not exist move on to the next step)
  • Run each of the following commands separately from anELEVATED COMMAND PROMPT. (The default paths are listed below. Please change the path if you extracted the service pack to a different location)


(NOTE: THERE HAVE BEEN NUMEROUS CALLS BECAUSE OF PEOPLE TYPING IN THE COMMANDS WRONG. PLEASE COPY AND PASTE THE COMMANDS BELOW- THIS EXAMPLE IS FOR SP1 TO FIX SP2 REPLACE SP1 PATH WITH APPROPRIATE SP2 PATHS):

 

 

  • "C:\LANDesk_Patches\LD960-SP1-Core\Updates\1\image\ldcryptoconfigutil.exe" /symmKeySize=256 /symmAlgorithmid=AES /symmBlockMode=CBC
    • You can confirm this is successful by browsing to Program Files\LANDesk\SharedFiles\Keys and verify a new ldcryptoconfig.xml has been created.
  • "C:\LANDesk_Patches\LD960-SP1-Core\Updates\1\image\LANDESK.DataServices.PasswordPromotion.exe" /promote
  • "C:\LANDesk_Patches\LD960-SP1-Core\Updates\1\image\LANDESK.DataServices.PasswordPromotion.exe" /validate (If the promoted password doesn't match conduct the following)
  • "C:\LANDesk_Patches\LD960-SP1-Core\Updates\1\image\LANDESK.DataServices.PasswordPromotion.exe" /demote
  • "C:\LANDesk_Patches\LD960-SP1-Core\Updates\1\image\LANDESK.DataServices.PasswordPromotion.exe" /validate (If the promoted password doesn't match repeat the above steps - starting with renaming the ldcryptoconfig.xml file)
  • "C:\LANDesk_Patches\LD960-SP1-Core\Updates\1\image\LANDESK.DataServices.PasswordPromotion.exe" /commit

These will give an error if they fail to run.


  • Reboot the core, and then restart the install.
  • If the steps above do not work, please get to the screen where you can cancel the installation, and then contact support.


Note: This issue could also occurwhile upgrading from 9.5 SPx to 9.6


Viewing all articles
Browse latest Browse all 524

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>