Error messages

An internal error occurred while
handling adapter request.

An adapter fails to return information to the running process.

Check the grid.log file for a more detailed error message.

For licensing reasons, the Remedy Action Request (AR) System server prevents a user from accessing the same server instance from multiple client systems. This error occurs when a Remedy AR System adapter uses logon credentials that are concurrently used by other adapters or Remedy AR System clients running on other systems.

Use one of the following responses:

• Use a Remedy AR
  System logon credential that
  is a member of the Administrator group and does not have this restriction.
• Use the adapter on only one
  peer or use multiple adapters
  with multiple user accounts
  by using the peer-mapping
  feature of the adapter.
  
  For more information,
  see Knowledge Base article KA000074301 (Support logon ID required).

A specified logon session does not exist.
It may already have been terminated.

The Windows Command adapter tries to log on.

Verify that the logon credentials used for the connection have
"Log on as a service" rights.

For more information, see Knowledge Base article KB000074301 (Support logon ID required).

Verify the URL used.

Could not create the view Plug-in
“com.bmc.ao.ui.studio.plugin” was unable to
instantiate class “com.bmc.ao.ui.studio.
eclipse.views.StudioView”

Right-click the BMC Atrium Orchestrator
Development Studio Studio.exe file,
select the Security tab, and then select the
Run As Administrator option.

For more information, see Knowledge Base article
KA000095210 (Support logon required).

The process generation failure is due to failure of the Web Service Definition Language (WSDL) to meet Java standards, specifically, the limit of 255 for method arguments.

Determine the problematic type definition in
the WSDL and reduce the number of arguments
to fewer than 255.

"Server returned no modules. Either no modules
have been activated on the server, or you currently do
not have access to any processes in any active modules."

Either the user does not have permission to any modules or no content has been installed in the Repository.

Verify that the user is a member of a role that has
access to the modules and that content exists in
the Repository.

This message occurs when you save a process that has a Switch statement with an extra or empty port.

Verify that all the Switch statements have the correct
number of ports (the small triangles to the right of the
Switch activity) and that all the ports have a condition
associated with them.

The attempt to clear the existing grid
configuration failed. The existing configuration
has been preserved.

The $STUDIO_HOME\server or server.xml file does not exist.

Starting Dev Studio fails with message "Could
not find environment directory"

The two systems in question, the adapter and the remote server, do not match the accepted SSH protocol.

Verify that the remote device has the SSH2 protocol enabled.

Some adapters do not support proxy servers. If you receive this message, verify that the peer has direct access to the Internet without going through a proxy server.

For more information, see Knowledge Base article KA000068507 (Support logon required).

Error while multiple users try to logon to
Development Studio at the same time:
The attempt to clear the existing grid
configuration failed. The existing configuration
may have been partially removed. Directories or
files which couldn't be removed may need to be
manually removed.

performCommand() SSH Client is not connected!.
Serious internal error!!,

The server where the command is being executed by using the SSH adapter requires a prompt.

Specify the <prompt> element when it is required by the target host.

For more information, see Knowledge Base article KA000064176 (Support logon required).

Unable to retrieve the module list
from the remote server.

The peer cannot access the Repository. This can occur when server names change.

"There must be at least one Case in the Switch
activity" when loading Atrium Orchestrator module.

There is a Switch statement in the module with no cases for one of the following reasons:

• The module had a rule that was deleted. Adding a rule adds a <switch /> element to the rules.xml file with cases for the rules, but deleting the rules removes the cases and leaves the empty <switch />.
• There is a Switch statement in the workflow with missing case information.

In the first case, modify the rules.xml file to remove the stand-alone <switch /> statement.

In the second case, review workflows to verify that all the Switch statements are properly configured with at least one default and one case.

For more information, see Knowledge Base article KA000083935 (Support logon required).

Error: Java Not Enabled. Java must be enabled
for BMC Help to run.

You see this error on Windows x64 systems where the default web browser (typically used for web shortcuts) is the 32-bit version of Windows Internet Explorer (iexplore.exe, or IE).

Use either of the following responses:

• Use the 64-bit version of IE when accessing Grid Manager or the authentication service.
• Download and install the appropriate 32-bit version of Java to support the 32-bit version of IE.