Who is this article for?

Users who encounter the error when testing the service URL.

IT Administrator permissions are required to resolve the issue.

When testing the service URL in a Web browser you might see the error message "The service encountered an error.".  

This article explains how to resolve it.

1. Issue

It is standard practice to test system availability by opening the service URL in a browser.  This is a URL like http://server.domain.com/[instance name]/Service/TngService.svc.

If the test fails you might see the following error message:

The service encountered an error.
An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is: System.InvalidOperationException: An exception was thrown in a call to a policy export extension. Extension: System.ServiceModel.Channels.SymmetricSecurityBindingElement
Error: An exception was thrown in a call to a policy export extension.
Extension: System.ServiceModel.Channels.SymmetricSecurityBindingElement
Error: Specified argument was out of the range of valid values. Parameter name: suite ---- System.InvalidOperationException: An exception was thrown in a call to a policy export extension.
Extension: System.ServiceModel.Channels.SymmetricSecurityBindingElement Error: Specified argument was out of the range of valid values. Parameter name: suite ---- System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values.
Parameter name: suite

[..]

This can occur soon after a worker process recycle, which you can check for in the server's Event Viewer (System log, event ID 5074). 

In this case, it's possible for the test page to fail even though clients are able to connect. 

2. Solution

To troubleshoot the issue, first check if the application is functioning.

If the desktop client connects fine, there is nothing further to do and the test page should become available after a time.

If the desktop client is unable to connect and displays an error, restart the application pool and Robot service.

To restart these:

1. Log in to the application server.
2. Locate Service under the correct instance In IIS Manager.
3. Verify the name of the application pool used.
4. Restart that application pool.
5. Locate the Robot service In Windows Services (normally called ServerRobotPentanaPRD).
6. Restart the service.

You should then find that clients connect and the test page loads as normal.