After the upgrade to ProSolution 9.2, I found that the tasks we ran which used PowerShell with the ProSolution Worker Service failed with the following error message:<\/p>\n\n\n\n
Error: – System.Management.Automation.Runspaces.PSSnapInException: An error occurred when loading the system Windows PowerShell Snap-Ins. Please contact Microsoft Support Services. —> System.Management.Automation.PSArgumentException: Unable to access Windows PowerShell PowerShellEngine registry information.<\/strong><\/p>\n\n\n\n at System.Management.Automation.PSSnapInReader.GetPSEngineKey(String psVersion)<\/strong><\/p>\n\n\n\n at System.Management.Automation.PSSnapInReader.ReadRegistryInfo(Version& assemblyVersion, String& publicKeyToken, String& culture, String& architecture, String& applicationBase, Version& psVersion)<\/strong><\/p>\n\n\n\n at System.Management.Automation.PSSnapInReader.ReadEnginePSSnapIns()<\/strong><\/p>\n\n\n\n at System.Management.Automation.Runspaces.MshConsoleInfo.CreateDefaultConfiguration()<\/strong><\/p>\n\n\n\n — End of inner exception stack trace —<\/strong><\/p>\n\n\n\n at System.Management.Automation.Runspaces.MshConsoleInfo.CreateDefaultConfiguration()<\/strong><\/p>\n\n\n\n at System.Management.Automation.Runspaces.RunspaceConfigForSingleShell.CreateDefaultConfiguration()<\/strong><\/p>\n\n\n\n at System.Management.Automation.Runspaces.RunspaceFactory.CreateRunspace(PSHost host)<\/strong><\/p>\n\n\n\n at System.Management.Automation.Runspaces.RunspaceFactory.CreateRunspace()<\/strong><\/p>\n\n\n\n at CompassCC.CCCSystem.CCCWindowsService.CCCScriptExecutor.CreateOpenDefaultRunSpace()<\/strong><\/p>\n\n\n\n at CompassCC.CCCSystem.CCCWindowsService.CCCScriptExecutor.ExecutePowerShellScript(String strScript)<\/strong><\/p>\n\n\n\n The first thought was a dodgy script, so I checked and made a test script containing something simple like changing directory, but even this failed, with the same error as shown above. I could run the script manually from the PowerShell prompt on the server so I knew that PowerShell was working fine on the server.<\/p>\n\n\n\n It appeared that the problem was to do with Powershell 3.0 not being installed, after installing PowerShell 3.0 onto the server from: http:\/\/www.microsoft.com\/en-us\/download\/details.aspx?id=34595<\/a><\/p>\n\n\n\n Windows Server 2008 R2 SP1 64-bit versions: Windows6.1-KB2506143-x64.msu<\/strong><\/p>\n\n\n\n Then reboot the server to complete the installation.<\/p>\n\n\n\n Now to verify that the PowerShell version is correct run the following commands from a PowerShell console:<\/p>\n\n\n\n PS H:\\> Set-Location variable:<\/strong><\/p>\n\n\n\n PS H:\\> Get-ChildItem<\/strong><\/p>\n\n\n\n Then to show the version:<\/p>\n\n\n\n PS H:\\> $Host.Version<\/strong><\/p>\n\n\n\n Now once this was done I testing running the tasks from within ProSolution and they worked fine.<\/p>\n","protected":false},"excerpt":{"rendered":" After the upgrade to ProSolution 9.2, I found that the tasks we ran which used PowerShell with the ProSolution Worker Service failed with the following error message: Error: – System.Management.Automation.Runspaces.PSSnapInException: An error occurred when loading the system Windows PowerShell Snap-Ins. Please contact Microsoft Support Services. —> System.Management.Automation.PSArgumentException: Unable to access Windows PowerShell PowerShellEngine registry information. … Read more<\/a><\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[],"class_list":["post-250","post","type-post","status-publish","format-standard","hentry","category-general"],"_links":{"self":[{"href":"https:\/\/geekmungus.co.uk\/index.php?rest_route=\/wp\/v2\/posts\/250","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/geekmungus.co.uk\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/geekmungus.co.uk\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/geekmungus.co.uk\/index.php?rest_route=\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/geekmungus.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=250"}],"version-history":[{"count":1,"href":"https:\/\/geekmungus.co.uk\/index.php?rest_route=\/wp\/v2\/posts\/250\/revisions"}],"predecessor-version":[{"id":1492,"href":"https:\/\/geekmungus.co.uk\/index.php?rest_route=\/wp\/v2\/posts\/250\/revisions\/1492"}],"wp:attachment":[{"href":"https:\/\/geekmungus.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=250"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/geekmungus.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=250"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/geekmungus.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=250"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}