Automation Manager returns a registry error on launch

Last Modified

Mon Mar 11 14:46 GMT 2019

Description

When Automation Manger executes, the following registry error appears in the AutomationManager.log file:

[49] 2017-10-09 15:05:00,831 ERROR NCentralAutomation AgentImpl: *** ERROR: Automation Initialization failed. [49] 2017-10-09 15:05:00,831 INFO NCentralAutomation AgentImpl: Shutting down [87] 2017-10-09 15:05:08,941 INFO NCentralAutomation AgentImpl: Initializating AM [87] 2017-10-09 15:05:08,941 INFO NCentralAutomation AgentImpl: Current Culture [ en-US ] [87] 2017-10-09 15:05:08,941 ERROR NCentralAutomation AgentImpl: AM initialization failed with the exception:The specified registry key does not exist. at Microsoft.Win32.RegistryKey.Win32Error(Int32 errorCode, String str) at Microsoft.Win32.RegistryKey.GetValueKind(String name) at PolicyExecutor.RegistryHelper.ReadRegistryString(RegistryKey rk, String strValueName) at PolicyExecutor.Utils.PowerShellUtils.FindLatestInstalledPSVersion() at NCentralAutomation.AgentImpl.InitializeInternal(String logFilePath, Int32 maxConcurrentJobs)

On launch, Automation Manager looks for the following PowerShell registry entries:

"HKLM\SOFTWARE\WOW6432Node\Microsoft\PowerShell\1\PowerShellEngine\PowerShellVersion" "HKLM\SOFTWARE\Microsoft\PowerShell\1\PowerShellEngine\PowerShellVersion"

If the registry keys are missing, or damaged, then Automation Manager will return an error on launch.

Environment

• N-able N-central
  

Solution

1. Check for Windows Corruption
   1. Check for Windows corruption by running the DISM or System Update Readiness tool. https://support.microsoft.com/en-us/kb/947821
   2. From an administrator command line, execute: SFC /scannow.
2. Remove & Re-install PowerShell
   1. Navigate to Control Panel > Programs and Features.
   2. Click on Turn Windows features on or off.
   3. Remove the check mark from Windows PowerShell.
   4. Click Ok.
   5. Click on Turn Windows features on or off.
   6. Re-Check Windows PowerShell.