This topic describes problems you can encounter when using Operations Sentinel. Click a specific problem to view possible solutions.
Problems
An attempt to start an Operations Sentinel client application fails because the Operations Sentinel Server services are not running.
On the Operations Sentinel server Start menu, point to Programs, Unisys Operations Sentinel x.y.z, Administrative Tools, and then click Status of Server Services.
If the display shows that Operations Sentinel services are not running, click Start Server Services from the Administrative Tools submenu. After a short time, a window appears that gives the result of the attempt to start the service. If the status reported in the window says that either the OS 2200 Console services or the Operations Sentinel services failed to start, then click Start Server Services again. Note that starting and stopping the Operations Sentinel services might take a few minutes.
An attempt to start or stop the Operations Sentinel Server services fails.
You must have the administrator privilege to start or stop Operations Sentinel Server services on the Operations Sentinel server.
To change the Operations Sentinel Server services account and password
On the Start menu, point to Programs, Unisys Operations Sentinel x.y.z, Administrative Tools, and then click Change Server Service Account.
Enter the correct service account and password, and reenter the password for confirmation.
An attempt to start an Operations Sentinel client application fails due to security problems.
Ensure your user account has access to the Operations Sentinel server. Your user account must be a member of the SPO Users or SPO Administrators Windows group on the server.
See the Operations Sentinel Administration and Configuration Guide for more information about security aspects of Operations Sentinel.
An attempt to open an OS 2200 console window with a specific view fails.
This typically happens if the name of the view is incorrect or a view with that name has not been defined. Check the value of the OS 2200 View propertyfor the OS 2200 console to verify that the name of the view is correct.
SP-AMS is not automating a connected system.
Possible explanations are:
No SP-AMS database is active. You see the following icon on the status bar of Operations Sentinel Console: . To correct this problem you must activate an SP-AMS database. On the Tools menu in Operations Sentinel Console , point to Automation Control and then click Activate.
For an MCP system, a valid usercode and password were not submitted to the MCP system, or the Operations Sentinel MCP Agent is not running on the MCP system. To correct this problem you must start the Operations Sentinel MCP Agent on the MCP system. See the Operations Sentinel Interface for ClearPath MCP Installation and Configuration Guide for more information.
An error occurs when you try to launch Server Sentinel from Operations Sentinel Console.
When you try to launch Server Sentinel from Operations Sentinel Console and an error occurs, a dialog box appears telling you to look in the Windows Application Event Log for more detailed information. As a supplement to this information, the Unisys Customer Support Center might ask you to set some environment variables to trace the launch of Server Sentinel from Operations Sentinel Console.
Use the following instructions to turn on tracing for Server Sentinel on an Operations Sentinel Console workstation.
Perform this procedure only after consulting with the Unisys Customer Support Center. Extra system resources are required once tracing is turned on, so it is recommended that you use this procedure only for debugging.
Double-click the My Computer icon.
Double-click the Control Panel icon.
Double-click the System icon.
The System Properties window opens.
Click the Advanced tab, and then click the Environment Variables button.
Click New in the System Variables pane of the Environment Variables window.
The New System Variable dialog box appears.
Type SPOLAUNCHWINEXE_DBG in the Variable Name field.
Type on in the Variable Value field.
Server Sentinel does not start.
On the Service Processor, click Start, point to Settings, and click Control Panel.
The Control Panel dialog box appears.
Double-click Administrative Tools.
The Administrative Tools dialog box appears.
Double-click Services.
The Services dialog box appears.
Look for the SC Server service.
If it is not running, right-click the SC Server service and click Start on the shortcut menu that appears.
If the SC Server service is not installed, you need to reinstall the plateau software.
If you need to report any problem or technical question, please submit a Service Request (CONTACT) or a User Communication Form (UCF) with supporting materials.