Error messages

Number

None

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.

None

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

Use one of the following responses:

• Use a BMC 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).

None

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).

Number

None

The URL used is invalid and the protocol (HTTP or HTTPS) cannot be determined. This usually occurs when BMC Atrium Orchestrator Development Studio tries to communicate with a target Web Service Definition Language (WSDL) either through the Web Services adapter or via the BMC Atrium Orchestrator Development Studio New Process from WSDL option.

Verify the URL used.

None

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”

BMC Atrium Orchestrator Development Studio does not have permission to access its components.

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).

None

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.

None

"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.

None

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.

None

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.

For a new installation of BMC Atrium Orchestrator
Development Studio that has never connected to
Grid Manager, this error can be ignored.

For an existing installation:

1. Verify that the $STUDIO_HOME\server directory
   exists.
2. Close BMC Atrium Orchestrator Development
   Studio.
3. Clear the contents of $STUDIO_HOME\config.
4. Launch BMC Atrium Orchestrator Development
   Studio.
5. Reconfigure the connection.
   
   For more information, see Knowledge Base
   article KA000074890 (Support logon required).

None

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

BMC Atrium Orchestrator Development Studio cannot find the directory that stores workflows that are loaded and edited in BMC Atrium Orchestrator Development Studio. This usually occurs if directories have been removed or renamed on the file system.

Reinstall BMC Atrium Orchestrator Development Studio
or recreate the directory.
The exact name of the folder can be found in the $STUDIO_HOME/config/management/
environments.xml file, in the id attribute for the <environment-name> element.

For example, given the following XML segment, the folder
to add is "ENV1-2012-02-17T125912Z":
<environment-name id="ENV1-2012-02-17T125912Z">
ENV1</environment-name>

None

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.

None

This error occurs for one of the following reasons:

• The JVM could not start because the system could not provide the amount of memory specified on the command line.
• BMC Atrium Orchestrator Development Studio did not find a Java version that it could use.

For the first reason for the error, free up memory on the system running BMC Atrium Orchestrator Development Studio or decrease the requested memory by modifying the Development Studio.ini file so that it uses less memory by replacing -Xmx768m with -Xmx512m and restarting BMC Atrium Orchestrator Development Studio.

For the second reason for the error, verify that BMC Atrium Orchestrator Development Studio has a valid Java version. On 64-bit computers, BMC Atrium Orchestrator Development Studio expects a 64-bit Java, and BMC Atrium Orchestrator Development Studio versions before 7.6.02 require a Java 6 JDK (not JRE).

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

None

The BMC Atrium Orchestrator server hosting the adapter might be set up to access the Internet via a proxy.

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).

None

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.

BMC Atrium Orchestrator Development Studio is relaunched when it is already running, which is not allowed. The secondary message varies.

Do not attempt to run the BMC Atrium Orchestrator Development Studio client twice.

None

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).

None

Unable to retrieve the module list
from the remote server.

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

Verify that the repository URL is correct and accessible by performing the following steps:

1. On the CDP, change the com.bmc.ao.REPOSITORY_URL parameter in the context.xml file, and then restart the CDP.
2. On the computer where BMC Atrium Orchestrator Development Studio is installed, with BMC Atrium Orchestrator Development Studio shut down, delete the .jms/disco folder.
3. Start BMC Atrium Orchestrator Development Studio and connect it to the CDP.

You can verify that you have used the new URL in the BMC Atrium Orchestrator Development Studio config/server.xml file.

Number

None

"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).

None

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 Access Manager.
• Download and install the appropriate 32-bit version of Java to support the 32-bit version of IE.