WinRM related errors are seen when browsing through the Server Configuration Portal

Version 2

    Verified Product Versions

    AppSense Management Center 10.0AppSense Management Center 10.1AppSense Environment Manager 10.0AppSense Environment Manager 10.1

    Introduction

     

    When performing certain actions within the Server Configuration Portal (SCP) such as creating a new database connection or viewing the initial "UWM Summary" page, you may see errors similar to the following:

     

                   WinRM SCP error.png

    Connecting to remote server JR-V10 failed with the following error message : The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see the about_Remote_Troubleshooting Help topic.

    If you check in the "Applications and Services Logs > Microsoft > Windows > Windows Remote Management" event log you will also see an error similar to the following:

    Error 08/09/2017 12:57:58 Windows Remote Management 142 Response handling

    WSMan operation CreateShell failed, error code 2150858770

    Detail

     

    These errors can be seen when the following Group Policy is set to lock down WinRM:

    Computer Configuration > Policies > Administrative Templates > Windows Components > Windows Remote Management (WinRM) > WinRM Service

     

    To confirm whether this policy will be affecting you, run the "winrm e winrm/config/listener" command from an administrative command prompt:

                   winrm config.png

    If the "ListeningOn" value is set to "null" then the policy will be affecting the SCP.

     

    To exclude the server running the SCP from this policy, you will need to update the policy with an IPv4 filter for both the loopback address and the address of the server, for example if the server address is "10.70.21.218":

    127.0.0.1-127.0.0.1, 10.70.21.218-10.70.21.218

    NOTE: Even if you are only entering a single IP address here, you need to specify it as a range as seen above.

    Once this policy has been applied to the server, run the "winrm e winrm/config/listener" command again and the "ListeningOn" value should now show you both of the IP addresses added to the policy:

                   winrm config.png

    At this point, you should no longer see errors within the SCP.