Solutions

PVCS Version Manager Server Admin shows error IIS Configuration Query Failed



ID:    S143510
Published:    31 August 2021

Operating System(s)

  • All Windows

Product(s)

  • PVCS Version Manager
 

Description

The PVCS Version Manager Server Admin utiltiy (vpadmin.exe) shows error IIS Configuration Query Failed:
 
 
Pressing Click for details yields one of these errors:
 
  • PowerShell script execution failed: & : File C:\Program Files (x86)\Micro Focus\vm\common\bin\win64\PvcsConfigureIIS.ps1 cannot be loaded because running scripts is disabled
    on this system
    . For more information, see about_Execution_Policies at http://go.microsoft.com/fwlink/?LinkID=135170.
    At line:1 char:2
    + &'C:\Program Files (x86)\Micro Focus\vm\common\bin\win64\PvcsConfigureIIS.ps1' -Operation ...
    +  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : SecurityError: (:) [], PSSecurityException
        + FullyQualifiedErrorId : UnauthorizedAccess
    .
     
  • PowerShell script execution failed: & : File C:\Program Files (x86)\Micro Focus\vm\common\bin\win64\PvcsConfigureIIS.ps1 cannot be loaded. The file
    C:\Program Files (x86)\Micro Focus\vm\common\bin\win64\PvcsConfigureIIS.ps1 is not digitally signed. You cannot run this script on the
    current system. For more information about running scripts and setting execution policy, see about_Execution_Policies
    at http://go.microsoft.com/fwlink/?LinkID=135170.
    At line:1 char:2
    + &'C:\Program Files (x86)\Micro Focus\vm\common\bin\win64\PvcsConfigureIIS.ps1' -Operation ...
    +  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : SecurityError: (:) [], PSSecurityException
        + FullyQualifiedErrorId : UnauthorizedAccess
    .
     

Resolution

This error typically indicates Group Policy either disabled PowerShell script execution on this machine, or restricted it to run signed scripts only (Execution Policy is set to Allow only signed scripts).
 
To solve this, open the Group Policy Editor (gpedit.msc), navigate to Computer Configuration | Administrative Templates | Windows Components | Windows PowerShell and edit Turn On Script Execution.
 
Change the value shown there to either Not Configured or Enabled with Execution Policy Allow local scripts and remote signed scripts:
 
 
If your account does not permit you to make this change, ask IT to make the adjustment for you.

 


Rate this Solution

Find Answers

Type a question or describe what you are looking for below

My Recent Searches

Welcome kb sso

Additional Assistance

  • Submit a Case Online
  • FAQs