Run-time Server Errors

This topic elaborates on some of the error messages that are displayed by the Runtime Service for Screens. Several of the Runtime Service errors are the result of corrupted files. To recreate the files, the Runtime Service must be reinitialized.

If you're running Runtime Service for Screens as an application, error messages are displayed in the console window. If you're running the service as a Windows service or a Unix daemon, the error messages are recorded in the log file.

Choose a message in this list to see an explanation:

Error Messages

com.attachmate.datastream.ReadTimeoutException (100033)
-or-
com.attachmate.nav.samtng.ResourceException (400000)

A variety of situations can cause this message to be displayed. Most commonly, this error occurs if the host displays an unrecognized screen while a task is running.

As stated in the message, this problem can occur for a variety of reasons. For example,

java.io.FileNotFoundException

One of the files required by the Runtime Service, ConfigTree.db, was moved or deleted after the session pool was configured. You can either copy the file back to its original location, or reinitialize the Runtime Service to recreate the file.

If this error message is displayed and you do not have the original file, you can reinitialize the Runtime Service. This will recreate the ConfigTree.db and .data files required by the Runtime Service.

com.attachmate.common.cfgserver.system.CfgserverException (300000)

The Runtime Service cannot download the NavMap (NavMapName) from the MCS server. This may be because the NavMap's read-only attribute has been set on the run-time computer, or because the NavMap does not exist on the MCS server. If the file exists, check its attributes; otherwise, to make the NavMap available, you'll need to publish your project from Task Builder to MCS.

Before it can run your application, the Runtime Service needs access to the NavMap that is associated with your session pool. The NavMap is downloaded from MCS (Management & Control Services) when the session pool is started.

If this error is displayed, and the NavMap is not available on the MCS server, you may need to republish your project from Task Builder. If the NavMap is already available on the MCS server, make sure that the version of the NavMap that is on the run-time computer is not marked read-only. If neither of these is the case, you may need to recreate your session pool.

com.attachmate.common.cfgserver.system.CfgserverException (300003)

Either the file ConfigTree.db or one of the internal data files (.data extension) has been corrupted. This may be because a file was manually altered. These files are required by the Runtime Service. To recreate the files, the Runtime Service must be reinitialized.

If one of these error messages is displayed, the Runtime Service must be reinitialized. This will recreate the ConfigTree.db and .data files required by the Runtime Service.

java.net.BindException

The Runtime Service cannot establish itself as an RMI remote server on port (PortNumber). This error usually indicates that another application is listening for network traffic on that port.

You can avoid this error by:

After being restarted, the Runtime Service should be able to successfully bind itself to the specified port.

com.attachmate.common.cfgserver.system.CfgserverException (300001)

The session pool named (SessionPoolName) cannot be found. This could be because the requested session pool name is different from the NavMap name or because the session pool has not been configured. It could also occur if internal files required by the Runtime Service have been changed or cannot be found in the expected location.

When an application starts, it requests a host connection from a session pool you configured in MCS. If this error is displayed, and the session pool exists, check to make sure that the session pool name matches the name of the associated NavMap; or, if you want to use a name that does not match the NavMap name, configure the task to use the non-standard session pool name. If the session pool does not exist, configure a new session pool in MCS.

If neither of these issues appears to be the problem, you may need to reinitialize the Runtime Service to recreate its internal files.

com.attachmate.nav.samtng.ResourceException (400001)

There is a problem connecting to or logging in to the host. Either the host is down, or the login failed because of an incorrect username/password combination or because that user is already logged in. You may need to specify a different username or password, or change the username and password options in the pool configuration.

Check that the host is running and that you can make a connection. If you need to make changes to the pool configuration, you can do so in MCS.

NavException Messages

NavException messages may be displayed alone or in combination with other messages. This is usually because a single issue can cause a problem in more than one area. For example, mismatched naming between the session pool and the NavMap creates a problem when the application connects through the Runtime Service and when the Runtime Service attempts to access a session pool. It can result in the generation of two or more separate error messages (com.attachmate.common.cfgserver.system.CfgserverException (300001), NavException (300001)).

Note The number in parentheses after the message is not actually displayed. It has been added in the online help for identification purposes.

com.attachmate.nav.engine.NavException (300001)

The session pool named (SessionPoolName) cannot be found. This could be because the requested session pool name is different from the NavMap name or because the session pool has not been configured. It could also occur if internal files required by the Runtime Service have been changed or cannot be found in the expected location.

The com.attachmate.nav.engine.NavException (300001) and com.attachmate.common.cfgserver.system.CfgserverException (300001) error messages are the same, resulting from the same error. com.attachmate.nav.engine.NavException (300001) originates from the client, while com.attachmate.common.cfgserver.system.CfgserverException (300001) originates from the Runtime Service.

When an application starts, it requests a host connection from a session pool you configured in MCS. If this error is displayed, and the session pool exists, check to make sure that the session pool name matches the name of the associated NavMap; or, if you want to use a name that does not match the NavMap name, configure the task to use the non-standard session pool name. If the session pool does not exist, configure a new session pool in MCS.

com.attachmate.nav.engine.NavException (200018)

The application could not connect to the Runtime Service.

This message is most often the result of a network or hardware configuration problem.

Related Topics
Bullet Synapta Services Builder, Overview
Bullet Configuring Your Run-time Environment, Overview
Bullet Reinitializing the Runtime Service
  Attachmate