![]() If the registry keys are missing, or damaged, then Automation Manager will return an error on launch. In the System Protection tab, select System Restore. 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" On the Start menu search bar, type in ‘restore,’ and select the best match. Navigate or jump to the registry keypath below. In the Run dialog box, type regeditand hit Enter to open Registry Editor. at 32Error(Int32 errorCode, String str) at (String name) at (RegistryKey rk, String strValueName) at () at (String logFilePath, Int32 maxConcurrentJobs) Press Windows key Rto invoke the Run dialog. ![]() 15:05:00,831 INFO NCentralAutomation AgentImpl: Shutting down 15:05:08,941 INFO NCentralAutomation AgentImpl: Initializating AM 15:05:08,941 INFO NCentralAutomation AgentImpl: Current Culture 15:05:08,941 ERROR NCentralAutomation AgentImpl: AM initialization failed with the exception:The specified registry key does not exist. When Automation Manger executes, the following registry error appears in the AutomationManager.log file: 15:05:00,831 ERROR NCentralAutomation AgentImpl: *** ERROR: Automation Initialization failed.
0 Comments
Leave a Reply. |