Messages and Codes

User authentication to the Client/Server Layer server failed.

Ensure that the user is valid in the configured environment and that the client version is newer or equal to the server version. If SSX is enabled, then check the SSX configuration of the Client/Server Layer server. Refer to the SSX log file for additional information.

The specified hostname cannot be found.

Use an existing hostname or an IP address of an existing host.

Task was executed with errors.

Action on this error depends on the type of the user-defined task. If you cannot resolve the problem, contact Software AG Global Support. Before you contact the support organization, prepare the following information: system and setup specifics; product error logs with exposed trace.

The System Management Hub client/server infrastructure uses non-secured communication.

none

SSX configuration change

none

The agent for the requested action has not been found.

The agent program does not have permissions to run.

Internal error.

You have enabled an old version of the agent program. For more information on the problem, set to "1" the New_StartAgent key in the CSLayer Server registry settings.

With Security enabled, the user has entered incorrect user name and/or password.

The CSLayer server is not running as a service on Windows.

The CSLayer server is not running with root rights on UNIX.

Check the security settings on the target machine and type again the user name and password.

CSLayer needs some special rights to execute a scheduled task. All neccessary rights and settings are explained in the official documentation.

Refer to the official documentation and set the right user privileges for the CSLayer server.

The server received an unknown command in the client's XML request.

Check the producer of the XML request. Use only the commands that are available for the server.

There is a syntax error in the command included in the client's XML request.

Check the syntax of the command that you want to include in the client's XML request.

The client's request includes a disabled command.

Check the server settings on the target machine.

The user's account does not have permissions to perform the requested action.

Check out the product's administrator list for users with administrator's rights.

The user does not have permissions to carry out the command.

Check out your user account for the assigned permissions.

Error occurred on CSLayer server.

Contact Software AG Global Support.

This is an internal error produced by the CSLayer server (argsrv).

The operating system has been overloaded. Check out the system configuration.

This is an internal error produced by the CSLayer server (argsrv) in the system call "write".

The write operation to a pipe for passing parameters to an agent failed. Try to continue or restart the server. If the error persists, contact your software supplier.

Failure to create a pipe for running the agent program is an internal error produced by the CSLayer server (argsrv).

Try to continue or restart the server. If the error persists, contact your software supplier.

Failure to redirect standard file descriptors is an internal error produced by the CSLayer server (argsrv).

The redirection failed in the 'dup' system call (UNIX). Try to continue or restart the server and if the error persists, contact your software supplier.

Failure to run the agent program is an internal error produced by the CSLayer server (argsrv).

Try to continue or restart the server and if the error persists, contact your software supplier.

The agent does not exist in the SMH installation on the target machine or the agent's path is not registered properly.

Check the product installation to see if the agent has been deleted or moved. Next, check the "Path" key of the agent in the SMH registry.

The agent program does not have permissions to run.

The agent program is being used by another process.

Check the permissions of the agent executable.

Check the running processes.

Failure to create child process is an internal error produced by the CSLayer server (argsrv) in the system call "fork".

Try to continue or restart the server and if the error persists, contact support.

Failure to run the agent is an internal error produced by the CSLayer server (argsrv) calling to API 'CreateProcess'.

Try to continue or re-start the server and if the error persists, contact support.

The agent program received a signal that it did not catch.

Check the agent. In most cases a patch for the specific agent will solve the problem.

Error duplicating handles is an internal error produced by the CSLayer server (argsrv) calling to API "DuplicateHandle".

Try to continue or restart the server. If the error persists, contact support.

This is an internal error produced by CSLayer server (argsrv) when attempting to initialize the Java Virtual Machine.

Check out the system settings.

Failed to create the JVM s an internal error produced by CSLayer server (argsrv) when attempting to initialize the Java Virtual Machine. The settings used for the JVM - jvm.dll (Windows), libjvm.sl (HP-UX), libjvm.so (other UNIX) - do not match the system configuration.

Check the system settings. Check the path and parameter settings.

Failure to initialize the Java bridge is an internal error produced by CSLayer server (argsrv) when attempting to initialize the Java bridge.

The settings used for the Java bridge - argjbr.dll (Windows), libargjbr.sl (HP-UX), libargjbr.so (other UNIX) - do not match the system configuration.

Check out the system settings, the path, and the parameter settings.

The support for Java agents has been disabled.

Enable the use of Java agents in the CSLayer server.

The agent class is not found because of incorrect agent's settings.

Check the agent settings including the agent class name and the classpath settings (global or product-specific registry settings).

The Java method is not found because the method's name or signature is incorrect.

Contact Software AG Global Support.

Java bridge error, agent-related problem. Java bridge error, agent-related problem.

Contact your software supplier

The client you are trying to connect to uses a newer version of the MIL server.

Upgrade the MIL server on your local host machine.

The agent returns an incorrect XML format.

Incorrect XML template used by the agent.

Incorrect XML template used by the Management Independent Layer server.

Client/Server Layer communication errors.

This is an internal generic error produced by the XML DOM library. Check the producer of the XML document. In most cases, a patch for the specific agent or a patch for the XML template file used will solve the problem.

The agent returns an incorrect XML format.

Incorrect XML template used by the agent.

Incorrect XML template used by the Management Independent Layer server.

This is an internal error produced by the XML DOM library. Check the producer of the XML document. In most cases, a patch for the specific agent or a patch for the XML template file used will solve the problem.

Operating system overloaded.

The agent returns an incorrect XML format.

Incorrect XML template used by the agent.

Incorrect XML template used by the Management Independent Layer server.

This is an internal error produced by the XML DOM library. Check the operating system and/or the producer of the XML document. In most cases, a patch for the specific agent or a patch for the XML template file used will solve the problem.

The agent returns an incorrect XML format.

Incorrect XML template used by the agent.

Incorrect XML template used by the Management Independent Layer server.

This is an internal error produced by the XML DOM library. Check the producer of the XML document. In most cases, a patch for the specific agent or a patch for the XML template file used will solve the problem.

Agent returns an XML document used to signal an error.

The error message provides the error description.

The agent returns an incorrect XML format.

Incorrect XML template used by the agent.

Incorrect XML template used by the Management Independent Layer server.

This is an internal error produced by the XML DOM library. Report the error to Software AG Global Support.

The agent returns an incorrect XML format.

Incorrect XML template used by the agent.

Incorrect XML template used by the Management Independent Layer server.

This is an internal error produced by the XML DOM library. Check the producer of the XML document. In most cases, a patch for the specific agent or a patch for the XML template file used will solve the problem.

Error in XML parser. Invalid DOM node.

Internal error. Contact Software AG Global Suppport.

OK

None.

Information message.

Use new command.

Information message.

None.

Command is deprecated.

Use new command.

Command is deprecated.

Use new command.

Information message.

None.

Job message localization failed.

Internal error. Contact Software AG Global Suppport.

No job record found for the specified ID.

Ensure that the job ID is correct.

On executing the job one or more alerts are rised.

Check the event log of the job and confirm the alerts.

A job can only be deleted if it is finished.

Wait for finalizing the job.

There is not enough memory for execution an action on argevsrv.

Stop the applications that are not currently needed to free some memory or restart the system.

The requested service is not available.

Check that the requested service is available and running.

The specified job was not found.

Check Product and Version.

Some of the jobs specified have unconfirmed warnings, errors or fatal errors. These need to be confirmed or ignored before the jobs can be deleted.

Check the jobs, confirm the individual alerts or confirm all alerts.

A job can only be deleted if the job is finished.

Wait for finalizing the job.

A job can only be deleted if the job is finished and all alerts are confirmed.

Confirm all alerts of the job.

A job with alert flags can only be deleted if the alerts are confirmed.

Check the job and confirm the alerts.

The request string is not in the product language resource library.

Check that the product is installed properly.

If the product has been upgraded, check that the upgrade completed successfully.

The language library requested by the product does not exist.

The language library requested by the product is incorrectly registered.

Check that the product is properly installed.

Check that the product is correctly registered with System Management Hub.

A product using System Management Hub has specified an incorrect (or invalid) product name or version.

This is an error generated by System Management Hub. Check the settings used by the product that reports the problem.

An error was detected while attempting to read the registry.

Check the installation. If the problems persist, contact Software AG Global Support.

Unknown error.

Contact Software AG Global Support.

Operating system is overloaded.

This is an internal error produced by the MIL server (argmlsrv). Check the system settings.

Session expired.

Authenticate on the system again.

Internal informative message, no error.

None.

This is an error produced by the transport library. In most cases, this is the TCP/IP driver library.

The server is not running or is not using the correct port.

Bad target URL or IP address.

Start the specific service and check the URL/IP settings and the port number

Check the settings of both Client/Server Layer Server and Management Independent Layer

This is an error produced by the TCP/IP driver library. The server is busy.

Retry the operation or log off and reconnect again later.

This is an error produced by the TCP/IP driver library. The specified server name is unknown or the DNS service is not available.

Check the system settings and the host lists.

Check if the DNS server is available.

This is an internal error produced by the TCP/IP driver library.

An internal TCP/IP error that indicates system overload.

Check the system settings

Close other applications using TCP/IP communication.

This is an internal error produced by the TCP/IP driver library.

An internal TCP/IP error that indicates system overload.

Check the system settings

Close other applications.

The specified server is not running or uses bad port settings.

This is an error produced by the TCP/IP driver library.

Check the system settings

Check if the specified server is running.

This is an internal error produced by the TCP/IP driver library.

TCP/IP communication errors.

Check the network settings.

On attempt to launch the Management Independent Layer Server or the CS Layer Server (System Management Hub Daemon) they were either already running or other applications are using the required socket.

No action is required if the servers are already running. Otherwise, terminate the application using the socket or configure the relevant System Management Hub server (if applicable).

This is an internal error produced by the TCP/IP driver library.

TCP/IP communication errors.

Check the network settings.

This is an internal error produced by the TCP/IP driver library.

TCP/IP communication errors.

Check the network settings.

The server was deactivated.

Restart the server and reconnect.

Operating system overloaded.

Close some applications and retry the operation.

Incorrect system settings.

Check the system and port settings.

Operating system error.

Check the operating system settings and the user account rights.

Cannot Initialize TCP/IP Connection on Windows

Internal communication error. Contact your system administrator.

Sending data over TCP/IP failed.

Internal communication error. Contact Software AG Global Support. Before you contact the support organization, prepare the following information: system and setup information; error logs with exposed traces.

Agent returns badly-formed XML.

Check the producer of the XML document. In most cases a patch for the specific agent or a patch for the XML template file used will solve the problem.

Receiving data over TCP/IP failed.

Internal communication error. Contact Software AG Global Support. Before you contact the support organization, prepare the following information: system and setup information; error logs with exposed traces.

Incomplete response or invalid protocol detected.

Internal communication error. Contact Software AG Global Support. Before you contact the support organization, prepare the following information: system and setup information; error logs with exposed traces.

Unknown error while getting the Client/Server Layer server response.

Internal communication error. Restart MIL and Client/Server Layer servers. If the problem persists, contact Software AG Global Support. Before you contact the support organization, prepare the following information: system and setup information; error logs with exposed traces.

Client/Server Layer server is not operating.

Ensure that the Client/Server Layer server is running and listening on the port specified in the connection settings. Ensure that the MIL server uses the right host and port of the running Client/Server Layer server. Check your firewall settings and restart the Client/Server Layer. If the problem persists, contact Software AG Global Support. Before you contact the support organization, prepare the following information: system and setup information; error logs with exposed traces.

This is an internal message and does not indicate an error. This message is provided for backward compatibility.

None.

The server was deactivated.

Restart the server and reconnect.

The agent returns an empty XML.

Check the producer of the XML document. In most cases, a patch for the specific agent or a patch for the XML template file in use solves the problem.

The agent returns incorrect XML format.

Check the producer of the XML document. In most cases, a patch for the specific agent or a patch for the XML template file in use solves the problem.

The agent did not finish its task in the given time interval.

Increase the agent timeout interval.

The agent returned XML that is larger than the maximum allowed size.

Make sure that the agent works properly or increase the maximum XML size that can be read.

Operating system overloaded.

This is an internal error produced by the XML parser. Check the system settings.

The agent returns an incorrect XML format.

Incorrect XML template used by the agent.

Incorrect XML template used by the Management Independent Layer server.

This is an internal error produced by the XML parser. Check the producer of the XML document. In most cases, a patch for the specific agent or a patch for the used XML template file will solve the problem.

Missing or corrupt agent.

The agent does not return an XML document.

The Client/Server Layer Server cannot start the agent.

XML template file not available.

Client/Server Layer communication errors.

This is an internal error produced by the XML parser. Check the producer of the XML document. In most cases, a patch for the specific agent or a patch for the XML template file used will solve the problem.

Put the Agent of the correct version for the platform in the correct location.

The agent returns an incorrect XML format.

Incorrect XML template used by the agent.

Incorrect XML template used by the Management Independent Layer server.

Check the producer of the XML document. In most cases, a patch for the specific agent or a patch for the XML template file used will solve the problem.

The agent returns an incorrect XML format.

Incorrect XML template used by the agent.

Incorrect XML template used by the Management Independent Layer server.

This is an internal error produced by the XML parser. Check the producer of the XML document. In most cases, a patch for the specific agent or a patch for the XML template file used will solve the problem.

The agent returns an incorrect XML format.

Incorrect XML template used by the agent.

Incorrect XML template used by the Management Independent Layer server.

This is an internal error produced by the XML parser. Check the producer of the XML document. In most cases, a patch for the specific agent or a patch for the XML template file used will solve the problem.

The agent returns an incorrect XML format.

Incorrect XML template used by the agent.

Incorrect XML template used by the Management Independent Layer server.

This is an internal error produced by the XML parser. Check the producer of the XML document. In most cases, a patch for the specific agent or a patch for the XML template file used will solve the problem.

The agent returns an incorrect XML format.

Incorrect XML template used by the agent.

Incorrect XML template used by the Management Independent Layer server.

This is an internal error produced by the XML parser. Check the producer of the XML document. In most cases, a patch for the specific agent or a patch for the XML template file used will solve the problem.

The agent returns an incorrect XML format.

Incorrect XML template used by the agent.

Incorrect XML template used by the Management Independent Layer server.

This is an internal error produced by the XML parser. Check the producer of the XML document. In most cases, a patch for the specific agent or a patch for the XML template file used will solve the problem.

Agent returns badly-formed XML.

Incorrect XML template used by the agent.

Incorrect XML template used by the Management Independent Layer server.

This is an internal error produced by the XML parser. Check the producer of the XML document. In most cases a patch for the specific agent or a patch for the XML template file used will solve the problem.

The agent returns an incorrect XML format.

Incorrect XML template used by the agent.

Incorrect XML template used by the Management Independent Layer server.

This is an internal error produced by the XML parser. Check the producer of the XML document. In most cases, a patch for the specific agent or a patch for the XML template file used will solve the problem.

The agent returns an incorrect XML format.

Incorrect XML template used by the agent.

Incorrect XML template used by the Management Independent Layer server.

This is an internal error produced by the XML parser. Check the producer of the XML document. In most cases, a patch for the specific agent or a patch for the XML template file used will solve the problem.

The agent returns an incorrect XML format.

Incorrect XML template used by the agent.

Incorrect XML template used by the Management Independent Layer server.

This is an internal error produced by the XML parser. Check the producer of the XML document. In most cases, a patch for the specific agent or a patch for the XML template file used will solve the problem.

The agent returns an incorrect XML format.

Incorrect XML template used by the agent.

Incorrect XML template used by the Management Independent Layer server.

This is an internal error produced by the XML parser. Check the producer of the XML document. In most cases, a patch for the specific agent or a patch for the XML template file used will solve the problem.

The agent returns an incorrect XML format.

Incorrect XML template used by the agent.

Incorrect XML template used by the Management Independent Layer server.

This is an internal error produced by the XML parser. Check the producer of the XML document. In most cases, a patch for the specific agent or a patch for the XML template file used will solve the problem.

The agent returns an incorrect XML format.

Incorrect XML template used by the agent.

Incorrect XML template used by the Management Independent Layer server.

This is an internal error produced by the XML parser. Check the producer of the XML document. In most cases, a patch for the specific agent or a patch for the XML template file used will solve the problem.

The agent returns an incorrect XML format.

Incorrect XML template used by the agent.

Incorrect XML template used by the Management Independent Layer server.

This is an internal error produced by the XML parser. Check the producer of the XML document. In most cases, a patch for the specific agent or a patch for the XML template file used will solve the problem. Only "ISO-8859-1" and "UTF-8" encoding is supported.

The agent returns an incorrect XML format.

Incorrect XML template used by the agent.

Incorrect XML template used by the Management Independent Layer server.

This is an internal error produced by the XML parser. Check the producer of the XML document. In most cases, a patch for the specific agent or a patch for the XML template file used will solve the problem. Only "ISO-8859-1" and "UTF-8" encoding is supported.

The agent returns an incorrect XML format.

Incorrect XML template used by the agent.

Incorrect XML template used by the Management Independent Layer server.

This is an internal error produced by the XML parser. Check the producer of the XML document. In most cases, a patch for the specific agent or a patch for the XML template file used will solve the problem.

The agent returns an incorrect XML format.

Incorrect XML template used by the agent.

Incorrect XML template used by the Management Independent Layer server.

This is an internal error produced by the XML parser. Check the producer of the XML document. In most cases, a patch for the specific agent or a patch for the XML template file used will solve the problem.