Error codes

Error code	Description	Possible causes	Solutions
201	Permission to access the file or directory is denied.	The process does not have the necessary permissions for accessing the file or directory.	Change the file or directory permissions to allow the process to access it.
202	The process cannot open the requested file.	The file is in the wrong directory. The process does not have permission to access the file.	Verify that the file is in the correct directory, and try again. Change the file permissions to allow the process to access it.
203	An error occurred while reading the file.	The process does not have permission to read the file.	Change the file permissions to allow the process to read the file.
204	An error occurred while writing to the file.	The process has read-only permission—it does not have permission to write to the file. The storage is full, and the system does not have enough room to write the changes to the file.	Change the file permissions to allow the process to write to the file. Clean up the storage, and then try again.
801	An error occurred while attempting to list an object of the given type.	No Location Service is available. No Smart Agent is running. The process is experiencing a communication problem.	Verify that a Location Service is available. See the VisiBroker ORB documentation for details. Start the Smart Agent using the osagent command. See the VisiBroker ORB documentation for details. Verify that all required processes are running, and all machines are up, and try again.

Error code

Description

Possible causes

Solutions

201

Permission to access the file or directory is denied.

The process does not have the necessary permissions for accessing the file or directory.

Change the file or directory permissions to allow the process to access it.

202

The process cannot open the requested file.

The file is in the wrong directory.

The process does not have permission to access the file.

Verify that the file is in the correct directory, and try again.

Change the file permissions to allow the process to access it.

203

An error occurred while reading the file.

The process does not have permission to read the file.

Change the file permissions to allow the process to read the file.

204

An error occurred while writing to the file.

The process has read-only permission—it does not have permission to write to the file.

The storage is full, and the system does not have enough room to write the changes to the file.

Change the file permissions to allow the process to write to the file.
Clean up the storage, and then try again.

801

An error occurred while attempting to list an object of the given type.

No Location Service is available.

No Smart Agent is running.

The process is experiencing a communication problem.

Verify that a Location Service is available. See the VisiBroker ORB documentation for details.

Start the Smart Agent using the osagent command. See the VisiBroker ORB documentation for details.

Verify that all required processes are running, and all machines are up, and try again.

Error code	Description	Possible causes	Solutions
4000	An instance of the VisiTransact Transaction Service was started successfully.	This is an informational message only.	This message requires no action.
4001	An instance of the VisiTransact Transaction Service is shutting down by request.	An administrator or other individual has shutdown the instance of the VisiTransact Transaction Service using either the vshutdown command, Ctrl+C, or the kill command.	This message requires no action.
4002	The instance of the VisiTransact Transaction Service is prepared to shutdown, but is waiting for outstanding transactions to enter the completion stage before exiting.	The request to shutdown the instance of the VisiTransact Transaction Service was issued without the -immediate argument, allowing the instance to let outstanding transactions enter the completion stage before exiting.	This message requires no action. If you want to shutdown an instance of the VisiTransact Transaction Service without allowing outstanding transactions to enter the completion stage, use the -immediate argument when issuing the vshutdown command.
4003	The instance of the VisiTransact Transaction Service is shutting down without waiting for outstanding transactions to enter the completion stage.	The request to shutdown the instance of the VisiTransact Transaction Service was issued with the -immediate argument, allowing the instance to shutdown without letting outstanding transactions enter the completion stage.	This message requires no action. If you want to shutdown an instance of the VisiTransact Transaction Service and allow outstanding transactions to enter the completion stage, issue the vshutdown command without the ‑immediate argument.
4004	A HeuristicHazard exception was raised by a Resource. For complete details on this exception, see the output of the heuristic log file.	A Resource made a heuristic decision and does not know the outcome of at least one relevant update.	There is a possible loss of data integrity. Look up the error in the heuristic log, and notify your database administrator of the transaction identifier. Your database administrator will need to locate this error on the Resource and correct any problems manually.
4005	A HeuristicCommit exception was raised by a Resource. For complete details on this exception, see the output of the heuristic log file.	A Resource made a heuristic decision to commit all relevant updates.	There is a possible loss of data integrity. Look up the error in the heuristic log, and notify your database administrator of the transaction identifier. Your database administrator will need to locate this error on the Resource and correct any problems manually.
4006	A HeuristicRollback exception was raised by a Resource. For complete details on this exception, see the output of the heuristic log file.	A Resource made a heuristic decision to rollback all relevant updates.	There is a possible loss of data integrity. Look up the error in the heuristic log, and notify your database administrator of the transaction identifier. Your database administrator will need to locate this error on the Resource and correct any problems manually.
4007	A HeuristicMixed exception was raised by a Resource. For complete details on this exception, see the output of the heuristic log file.	A Resource made a heuristic decision which differs from the outcome of the transaction. Some updates have been committed, others have been rolled back.	There is a possible loss of data integrity. Look up the error in the heuristic log, and notify your database administrator of the transaction identifier. Your database administrator will need to locate this error on the Resource and correct any problems manually.
4008	An exception was caught and ignored during the callback for a specific alarm (listed in the message).	This message could be thrown for various reasons, including running out of system resources.	Ignore this message.
4009	An internal application error occurred.	An internal module of VisiTransact Transaction Manager, used by several VisiTransact components, could not be initialized due to an unknown exception.	Contact Micro Focus Support.
4010	An internal application error occurred, as described in the message.	An internal module of VisiTransact Transaction Manager, used by several VisiTransact components, could not be initialized due to the exception listed in the message.	Contact Micro Focus Support.
4011	An exception occurred while parsing the initialization arguments listed in the message.	The wrong command-line arguments were entered when executing a VisiTransact command.	Verify the command-line arguments, and try again. See “Commands, utilities, arguments, and environment variables”.
4012	An exception occurred while parsing some initialization arguments, but it is unknown which arguments were incorrect.	The wrong command-line arguments were entered when executing a VisiTransact command.	Verify the command-line arguments, and try again. See “Commands, utilities, arguments, and environment variables”.
4014	An initialization failure (specified in the message) occurred while starting an instance of the VisiTransact Transaction Service.	The wrong configuration file was used, or incorrect values were entered for initialization parameters. An internal application error has occurred.	Verify you are using the correct configuration file, and are entering correct values for the initialization parameters. Contact Micro Focus Support.
4015	A runtime exception occurred within a running instance of the VisiTransact Transaction Service.	An internal application error has occurred.	Contact Micro Focus Support.
4016	The default transaction timeout has been changed to the value of the maximum transaction timeout.	The value of the default transaction timeout was higher than the value of the maximum transaction timeout.	Verify that you have coordinated your timeout settings between your applications and any command-line arguments you are using when starting instances of the VisiTransact Transaction Service.
4017	An invalid value was provided for the default transaction timeout. The timeout value was reset to 600 seconds.	When setting the default timeout value, a zero or a negative value was provided. The default timeout value must be at least 1 second.	When setting the default timeout value, make sure to set it to a value greater than or equal to 1 second. The recommended value is 600 seconds.
4018	An unexpected exception was received by the VisiTransact Transaction Service during transaction completion. The VisiTransact Transaction Service will retry transaction completion.	An internal application error has occurred.	Contact Micro Focus Support.
4019	An unexpected CORBA exception was received by the VisiTransact Transaction Service during transaction completion. The VisiTransact Transaction Service will retry transaction completion.	An internal application error has occurred.	Contact Micro Focus Support.

An instance of the VisiTransact Transaction Service was started successfully.

This is an informational message only.

This message requires no action.

4001

An instance of the VisiTransact Transaction Service is shutting down by request.

An administrator or other individual has shutdown the instance of the VisiTransact Transaction Service using either the vshutdown command, Ctrl+C, or the kill command.

This message requires no action.

4002

The instance of the VisiTransact Transaction Service is prepared to shutdown, but is waiting for outstanding transactions to enter the completion stage before exiting.

The request to shutdown the instance of the VisiTransact Transaction Service was issued without the -immediate argument, allowing the instance to let outstanding transactions enter the completion stage before exiting.

This message requires no action.

If you want to shutdown an instance of the VisiTransact Transaction Service without allowing outstanding transactions to enter the completion stage, use the -immediate argument when issuing the vshutdown command.

4003

The instance of the VisiTransact Transaction Service is shutting down without waiting for outstanding transactions to enter the completion stage.

The request to shutdown the instance of the VisiTransact Transaction Service was issued with the -immediate argument, allowing the instance to shutdown without letting outstanding transactions enter the completion stage.

This message requires no action.

If you want to shutdown an instance of the VisiTransact Transaction Service and allow outstanding transactions to enter the completion stage, issue the vshutdown command without the ‑immediate argument.

4004

A HeuristicHazard exception was raised by a Resource. For complete details on this exception, see the output of the heuristic log file.

A Resource made a heuristic decision and does not know the outcome of at least one relevant update.

There is a possible loss of data integrity. Look up the error in the heuristic log, and notify your database administrator of the transaction identifier. Your database administrator will need to locate this error on the Resource and correct any problems manually.

4005

A HeuristicCommit exception was raised by a Resource. For complete details on this exception, see the output of the heuristic log file.

A Resource made a heuristic decision to commit all relevant updates.

4006

A HeuristicRollback exception was raised by a Resource. For complete details on this exception, see the output of the heuristic log file.

A Resource made a heuristic decision to rollback all relevant updates.

4007

A HeuristicMixed exception was raised by a Resource. For complete details on this exception, see the output of the heuristic log file.

A Resource made a heuristic decision which differs from the outcome of the transaction. Some updates have been committed, others have been rolled back.

4008

An exception was caught and ignored during the callback for a specific alarm (listed in the message).

This message could be thrown for various reasons, including running out of system resources.

Ignore this message.

4009

An internal application error occurred.

An internal module of VisiTransact Transaction Manager, used by several VisiTransact components, could not be initialized due to an unknown exception.

Contact Micro Focus Support.

4010

An internal application error occurred, as described in the message.

An internal module of VisiTransact Transaction Manager, used by several VisiTransact components, could not be initialized due to the exception listed in the message.

Contact Micro Focus Support.

4011

An exception occurred while parsing the initialization arguments listed in the message.

The wrong command-line arguments were entered when executing a VisiTransact command.

Verify the command-line arguments, and try again. See “Commands, utilities, arguments, and environment variables”.

4012

An exception occurred while parsing some initialization arguments, but it is unknown which arguments were incorrect.

The wrong command-line arguments were entered when executing a VisiTransact command.

Verify the command-line arguments, and try again. See “Commands, utilities, arguments, and environment variables”.

4014

An initialization failure (specified in the message) occurred while starting an instance of the VisiTransact Transaction Service.

The wrong configuration file was used, or incorrect values were entered for initialization parameters.

An internal application error has occurred.

Verify you are using the correct configuration file, and are entering correct values for the initialization parameters.

Contact Micro Focus Support.

4015

A runtime exception occurred within a running instance of the VisiTransact Transaction Service.

An internal application error has occurred.

Contact Micro Focus Support.

4016

The default transaction timeout has been changed to the value of the maximum transaction timeout.

The value of the default transaction timeout was higher than the value of the maximum transaction timeout.

Verify that you have coordinated your timeout settings between your applications and any command-line arguments you are using when starting instances of the VisiTransact Transaction Service.

4017

An invalid value was provided for the default transaction timeout. The timeout value was reset to 600 seconds.

When setting the default timeout value, a zero or a negative value was provided. The default timeout value must be at least 1 second.

When setting the default timeout value, make sure to set it to a value greater than or equal to 1 second. The recommended value is 600 seconds.

4018

An unexpected exception was received by the VisiTransact Transaction Service during transaction completion. The VisiTransact Transaction Service will retry transaction completion.

An internal application error has occurred.

Contact Micro Focus Support.

4019

An unexpected CORBA exception was received by the VisiTransact Transaction Service during transaction completion. The VisiTransact Transaction Service will retry transaction completion.

An internal application error has occurred.

Contact Micro Focus Support.

Error code	Description	Possible causes	Solutions
6001	The Session Manager could not allocate the necessary memory.	Your system may have run out of memory.	Make memory available by increasing swap spaces and shutting down unnecessary processes.
6002	Profiles are incompatible because they are using different implementations of the Session Manager.	An application is attempting to use one profile which specifies the XA Session Manager for OCI in the same process with a profile which specifies the DirectConnect Session Manager for Oracle OCI.	Ensure that only one type of Oracle connection is used with the Session Manager in one process.
6003	The Session Manager could not load a necessary library.	The PATH or LIBRARY_PATH environment variables may not be set correctly, or the associated libraries may be missing.	Be sure to set environment variables correctly. If this does not correct the problem, you may need to reinstall VisiBroker VisiTransact and the VisiBroker ORB.
6004	The Session Manager could not locate a needed function symbol in the loaded library.	Not all required database libraries could be found. The loaded library file may be corrupted.	Verify that the PATH (Windows NT) and the LD_LIBRARY_PATH (Solaris) environment variables include the path to your database libraries. Check that the database client libraries are available. Reinstall the VisiBroker ORB and VisiBroker VisiTransact software.
6005	The Session Manager could not open a connection to the database.	The database may be unavailable. You may be using an invalid user name or password. The database software may not be correctly installed or configured.	Verify that the database is up and running. Check the Session Manager connection profile to verify that the database name, user name, and password are entered correctly. Verify that your database software is installed and configured correctly.
6006	An error occurred during the initialization phase of an attempt by the Session Manager to connect to the database.	The version of your database software is incompatible with the Session Manager.	Consult “XA Session Manager for Oracle OCI, version 9i Client” and “DirectConnect Session Manager for Oracle OCI, version 9i Client” to be sure that you are using the supported versions of the database software.
6007	A connection association error occurred when the Session Manager attempted to allocate a database connection.	The database server may be unavailable, or may be misconfigured. You may have used an invalid Coordinator when using non-ITS-managed transactions.	Check with the database administrator to ensure that the database server is up and running; check “XA Session Manager for Oracle OCI, version 9i Client” and “DirectConnect Session Manager for Oracle OCI, version 9i Client” for database configuration requirements. Be sure to use a valid Coordinator in any invocations of the getConnection() method.
6008	The limit on the maximum number of connections has been reached.	The maximum number of connections has been reached. The database server is overloaded.	Raise the limit for the maximum number of connections to this database. Reduce the load on the database server.
6009	Another thread already holds the connection to the database for this transaction.	You are using the DirectConnect Session Manager, and have attempted to connect to the database more than once for the transaction.	If you are using the Direct Connect Session Manager, be sure to use only one Connection object at a time for a transaction.
6010	The Session Manager could not retrieve the database's native connection handle from the XA libraries.	The version of your database software is incompatible with the Session Manager.	Consult “XA Session Manager for Oracle OCI, version 9i Client” and “DirectConnect Session Manager for Oracle OCI, version 9i Client” to be sure that you are using the supported versions of the database software.
6011	The thread that acquired the connection is not the same thread as the one currently trying to operate on it.	You may be trying to share a connection among threads.	See “XA Session Manager for Oracle OCI, version 9i Client” and “DirectConnect Session Manager for Oracle OCI, version 9i Client” for restrictions.
6012	The Session Manager could not register the Resource Director specified in the connection profile.	The Resource Director is not running at the specified OSAGENT_PORT. The name of the Resource Director is incorrectly specified in the connection profile.	Make sure that an instance of the Resource Director is running at the specified OSAGENT_PORT. See “Starting an XA Resource Director” on page 111. Verify that the name entered in the Resource Director Name field of the connection profile is correct. See , “Integrating VisiTransact with databases using the Session Manager” for instructions.
6013	A transaction context was not established when the connection was requested.	The transaction context did not exist when getConnection() was invoked because begin() was not called before it.	Make sure your program invokes begin() before calling getConnection().
6014	An invalid value was specified for the SMconnection_idle_timeout attribute.	A negative value was specified for SMconnection_idle_timeout.	Specify a positive value for this attribute.
6015	The Session Manager could not validate the explicit Coordinator used.	You are processing a transaction with explicit propagation, and passed a Coordinator object to the Session Manager for a transaction that rolled back already.	When processing a transaction with explicit propagation, you must ensure that the Coordinator object you pass is valid.
6016	An error occurred during the connection release process.	When the Session Manager was releasing the connection, the connection somehow became invalid—perhaps due to a database server crash.	Check that your database server process is still running.
6017	The Session Manager could not perform the requested disconnect from the database.	When the Session Manager was releasing the connection, the connection somehow became invalid—perhaps due to a database server crash.	Check that your database server process is still running.
6018	The Session Manager encountered an unknown attribute in the connection profile.	Perhaps you are using an older connection profile that is incompatible with this version of the Session Manager. The connection profile may be corrupted.	Recreate the connection profile using the VisiBroker Console. See , “Integrating VisiTransact with databases using the Session Manager.” Recreate the connection profile using the VisiBroker Console. (See above)
6019	A profile attribute that is necessary for obtaining a connection is not set.	The connection profile does not have a value for this connection attribute. The connection profile may be corrupted.	Use the VisiBroker Console to verify the settings in your connection profile. Recreate the connection profile using the VisiBroker Console.
6020	The infotype for an argument passed to the getInfo() method is invalid.	The getInfo() invocation in your program is passing an incorrect infotype.	See getInfo() in the VisiBroker for C++ API Reference for common infotypes accepted by the getInfo() method. See “XA Session Manager for Oracle OCI, version 9i Client” and “DirectConnect Session Manager for Oracle OCI, version 9i Client” for database-specific infotypes that are accepted.
6021	The hold() operation is not supported.	The application called hold() on a connection which does not support that operation.	Use isSupported() to determine connections for which this operation is valid.
6022	The connection profile name passed as an argument to a method invocation is invalid.	A method invocation in your application passes an invalid connection profile name (generally a null, or a string of 0 length).	Verify that the method uses a valid connection profile name. Also use the VisiBroker Console to verify that the connection profile is indeed set up.
6024	The Session Manager was unable to obtain a connection because it reached its maximum wait time for an available connection.	A deadlock has occurred between the current thread (which is requesting a connection) and another thread (which holds the requested connection). To resolve the deadlock, the current thread has been removed from the queue.	To optimize your code for deadlock avoidance, implement a retry loop that invokes getConnection() until it is successful. See “Data access using the Session Manager” for information.
6025	An invalid argument was passed at the command line.	A command-line argument may have been misspelled.	Verify the spelling of all command-line arguments. See “Commands, utilities, arguments, and environment variables”.
6026	An invalid value was specified for a command-line argument.	An invalid value was specified for a command-line argument.	Verify the valid values for all command-line arguments. See “Commands, utilities, arguments, and environment variables”.
6032	A commit has been attempted for this Resource, but has failed.	Illegal database operations were attempted during the commit, and the database rejected these operations.	See “XA Session Manager for Oracle OCI, version 9i Client” and “DirectConnect Session Manager for Oracle OCI, version 9i Client” for troubleshooting information about the Session Manager for your database.
6033	A rollback has been attempted on this Resource, but has failed.	Illegal database operations were attempted during the rollback, and the database rejected these operations.	See “XA Session Manager for Oracle OCI, version 9i Client” and “DirectConnect Session Manager for Oracle OCI, version 9i Client” for troubleshooting information about the Session Manager for your database.
6034	The error messages shown are native to the database you are using.	Native connection or transaction management calls to the database failed.	See “XA Session Manager for Oracle OCI, version 9i Client” and “DirectConnect Session Manager for Oracle OCI, version 9i Client” for troubleshooting information about the Session Manager for your database.
6035	An internal error occurred.	An internal application error has occurred in the Session Manager.	Contact Micro Focus Support.
6040	The Session Manager could not register a Resource with an instance of the VisiTransact Transaction Service.	An instance of the VisiTransact Transaction Service is not running at the specified OSAGENT_PORT.	Make sure that an instance of the VisiTransact Transaction Service is running at the specified OSAGENT_PORT.
6042	The specified Resource Director is unavailable.	An instance of the Resource Director is not running at the specified OSAGENT_PORT.	Make sure that an instance of the Resource Director is running at the specified OSAGENT_PORT.
6043	An error occurred during recovery.	The XA Resource Manager for the database is not running. The XA Resource Manager for the database experienced an error.	Make sure the database's XA Resource Manager is running and available. Check the database error log for a more specific indication of the error that occurred.
6046	The XA calls of the Session Manager have returned the error code listed in the message.	A database error occurred.	See “Problem determination” for troubleshooting tips.
6047	The Session Manager for Sybase CTLib has detected two connections with same LRM name, but different user names and passwords.	Two connection profiles in the same server process share the same database name, but have different passwords.	Create a new connection profile for one of these profiles that uses a different LRM. Modify your server process to use the new connection profile where appropriate.
6048	The connection profile has an unrecognized format.	Perhaps foreign files were written to the directory where the persistent store files are located, or the connection profile has been otherwise corrupted.	Recreate the connection profile using the VisiBroker Console.
6049	The Session Manager could not open the connection profile.	There could be a file permission problem.	Be sure that the file has the correct permissions.
6050	The Session Manager encountered an error while reading the connection profile.	Perhaps foreign files were written to the directory where the persistent store files are located, or the connection profile has been otherwise corrupted.	Recreate the connection profile using the VisiBroker Console.
6051	The Session Manager encountered an error while writing to the connection profile.	Perhaps the file or directory does not have the correct permissions. The disk is full, and the Session Manager cannot save the connection profile. You may have specified an incorrect path to the connection profile.	Be sure that the file and directory have the correct permissions. Free disk space so that the Session Manager can save the connection profile to disk. Be sure to specify the correct path.
6052	The specified path is invalid.	You may have specified an incorrect path to the connection profile.	Be sure to specify the correct path.
6053	The specified connection profile already exists.	You have tried to create a connection profile with a name that is already taken.	Choose a different name for this connection profile, or delete the other connection profile.
6054	The specified connection profile does not exist.	Perhaps you have misspelled the connection profile name.	Check that you have correctly specified the connection profile name.
6055	The connection profile could not be removed.	Perhaps the file or directory does not have the correct permissions.	Be sure that the file and directory have the correct permissions.
6056	The XA Resource Director was given an DirectConnect (non-XA) Session Manager connection profile.	You attempted to start an XA Resource Director with a connection profile created for the DirectConnect Session Manager.	Make sure to start the XA Resource Director with a connection profile that was created for the XA Session Manager.
6058	Previous hold() call has timed out; connection must be released.	The timeout value supplied to the hold() call has expired and the connection object may no longer be used.	Call release() on this connection and call getConnection() again if still required.

The Session Manager could not allocate the necessary memory.

Your system may have run out of memory.

Make memory available by increasing swap spaces and shutting down unnecessary processes.

6002

Profiles are incompatible because they are using different implementations of the Session Manager.

An application is attempting to use one profile which specifies the XA Session Manager for OCI in the same process with a profile which specifies the DirectConnect Session Manager for Oracle OCI.

Ensure that only one type of Oracle connection is used with the Session Manager in one process.

6003

The Session Manager could not load a necessary library.

The PATH or LIBRARY_PATH environment variables may not be set correctly, or the associated libraries may be missing.

Be sure to set environment variables correctly. If this does not correct the problem, you may need to reinstall VisiBroker VisiTransact and the VisiBroker ORB.

6004

The Session Manager could not locate a needed function symbol in the loaded library.

Not all required database libraries could be found.

The loaded library file may be corrupted.

Verify that the PATH (Windows NT) and the LD_LIBRARY_PATH (Solaris) environment variables include the path to your database libraries.

Check that the database client libraries are available.

Reinstall the VisiBroker ORB and VisiBroker VisiTransact software.

6005

The Session Manager could not open a connection to the database.

The database may be unavailable.

You may be using an invalid user name or password.

The database software may not be correctly installed or configured.

Verify that the database is up and running.

Check the Session Manager connection profile to verify that the database name, user name, and password are entered correctly.

Verify that your database software is installed and configured correctly.

6006

An error occurred during the initialization phase of an attempt by the Session Manager to connect to the database.

The version of your database software is incompatible with the Session Manager.

Consult “XA Session Manager for Oracle OCI, version 9i Client” and “DirectConnect Session Manager for Oracle OCI, version 9i Client” to be sure that you are using the supported versions of the database software.

6007

A connection association error occurred when the Session Manager attempted to allocate a database connection.

The database server may be unavailable, or may be misconfigured.

You may have used an invalid Coordinator when using non-ITS-managed transactions.

Check with the database administrator to ensure that the database server is up and running; check “XA Session Manager for Oracle OCI, version 9i Client” and “DirectConnect Session Manager for Oracle OCI, version 9i Client” for database configuration requirements.

Be sure to use a valid Coordinator in any invocations of the getConnection() method.

6008

The limit on the maximum number of connections has been reached.

The maximum number of connections has been reached.

The database server is overloaded.

Raise the limit for the maximum number of connections to this database.

Reduce the load on the database server.

6009

Another thread already holds the connection to the database for this transaction.

You are using the DirectConnect Session Manager, and have attempted to connect to the database more than once for the transaction.

If you are using the Direct Connect Session Manager, be sure to use only one Connection object at a time for a transaction.

6010

The Session Manager could not retrieve the database's native connection handle from the XA libraries.

The version of your database software is incompatible with the Session Manager.

6011

The thread that acquired the connection is not the same thread as the one currently trying to operate on it.

You may be trying to share a connection among threads.

See “XA Session Manager for Oracle OCI, version 9i Client” and “DirectConnect Session Manager for Oracle OCI, version 9i Client” for restrictions.

6012

The Session Manager could not register the Resource Director specified in the connection profile.

The Resource Director is not running at the specified OSAGENT_PORT.

The name of the Resource Director is incorrectly specified in the connection profile.

Make sure that an instance of the Resource Director is running at the specified OSAGENT_PORT. See “Starting an XA Resource Director” on page 111.

Verify that the name entered in the Resource Director Name field of the connection profile is correct. See , “Integrating VisiTransact with databases using the Session Manager” for instructions.

6013

A transaction context was not established when the connection was requested.

The transaction context did not exist when getConnection() was invoked because begin() was not called before it.

Make sure your program invokes begin() before calling getConnection().

6014

An invalid value was specified for the SMconnection_idle_timeout attribute.

A negative value was specified for SMconnection_idle_timeout.

Specify a positive value for this attribute.

6015

The Session Manager could not validate the explicit Coordinator used.

You are processing a transaction with explicit propagation, and passed a Coordinator object to the Session Manager for a transaction that rolled back already.

When processing a transaction with explicit propagation, you must ensure that the Coordinator object you pass is valid.

6016

An error occurred during the connection release process.

When the Session Manager was releasing the connection, the connection somehow became invalid—perhaps due to a database server crash.

Check that your database server process is still running.

6017

The Session Manager could not perform the requested disconnect from the database.

When the Session Manager was releasing the connection, the connection somehow became invalid—perhaps due to a database server crash.

Check that your database server process is still running.

6018

The Session Manager encountered an unknown attribute in the connection profile.

Perhaps you are using an older connection profile that is incompatible with this version of the Session Manager.

The connection profile may be corrupted.

Recreate the connection profile using the VisiBroker Console. See , “Integrating VisiTransact with databases using the Session Manager.”

Recreate the connection profile using the VisiBroker Console. (See above)

6019

A profile attribute that is necessary for obtaining a connection is not set.

The connection profile does not have a value for this connection attribute.

The connection profile may be corrupted.

Use the VisiBroker Console to verify the settings in your connection profile.

Recreate the connection profile using the VisiBroker Console.

6020

The infotype for an argument passed to the getInfo() method is invalid.

The getInfo() invocation in your program is passing an incorrect infotype.

See getInfo() in the VisiBroker for C++ API Reference for common infotypes accepted by the getInfo() method. See “XA Session Manager for Oracle OCI, version 9i Client” and “DirectConnect Session Manager for Oracle OCI, version 9i Client” for database-specific infotypes that are accepted.

6021

The hold() operation is not supported.

The application called hold() on a connection which does not support that operation.

Use isSupported() to determine connections for which this operation is valid.

6022

The connection profile name passed as an argument to a method invocation is invalid.

A method invocation in your application passes an invalid connection profile name (generally a null, or a string of 0 length).

Verify that the method uses a valid connection profile name. Also use the VisiBroker Console to verify that the connection profile is indeed set up.

6024

The Session Manager was unable to obtain a connection because it reached its maximum wait time for an available connection.

A deadlock has occurred between the current thread (which is requesting a connection) and another thread (which holds the requested connection). To resolve the deadlock, the current thread has been removed from the queue.

To optimize your code for deadlock avoidance, implement a retry loop that invokes getConnection() until it is successful. See “Data access using the Session Manager” for information.

6025

An invalid argument was passed at the command line.

A command-line argument may have been misspelled.

Verify the spelling of all command-line arguments. See “Commands, utilities, arguments, and environment variables”.

6026

An invalid value was specified for a command-line argument.

Verify the valid values for all command-line arguments. See “Commands, utilities, arguments, and environment variables”.

6032

A commit has been attempted for this Resource, but has failed.

Illegal database operations were attempted during the commit, and the database rejected these operations.

See “XA Session Manager for Oracle OCI, version 9i Client” and “DirectConnect Session Manager for Oracle OCI, version 9i Client” for troubleshooting information about the Session Manager for your database.

6033

A rollback has been attempted on this Resource, but has failed.

Illegal database operations were attempted during the rollback, and the database rejected these operations.

6034

The error messages shown are native to the database you are using.

Native connection or transaction management calls to the database failed.

6035

An internal error occurred.

An internal application error has occurred in the Session Manager.

Contact Micro Focus Support.

6040

The Session Manager could not register a Resource with an instance of the VisiTransact Transaction Service.

An instance of the VisiTransact Transaction Service is not running at the specified OSAGENT_PORT.

Make sure that an instance of the VisiTransact Transaction Service is running at the specified OSAGENT_PORT.

6042

The specified Resource Director is unavailable.

An instance of the Resource Director is not running at the specified OSAGENT_PORT.

Make sure that an instance of the Resource Director is running at the specified OSAGENT_PORT.

6043

An error occurred during recovery.

The XA Resource Manager for the database is not running.

The XA Resource Manager for the database experienced an error.

Make sure the database's XA Resource Manager is running and available.

Check the database error log for a more specific indication of the error that occurred.

6046

The XA calls of the Session Manager have returned the error code listed in the message.

A database error occurred.

See “Problem determination” for troubleshooting tips.

6047

The Session Manager for Sybase CTLib has detected two connections with same LRM name, but different user names and passwords.

Two connection profiles in the same server process share the same database name, but have different passwords.

Create a new connection profile for one of these profiles that uses a different LRM. Modify your server process to use the new connection profile where appropriate.

6048

The connection profile has an unrecognized format.

Perhaps foreign files were written to the directory where the persistent store files are located, or the connection profile has been otherwise corrupted.

Recreate the connection profile using the VisiBroker Console.

6049

The Session Manager could not open the connection profile.

There could be a file permission problem.

Be sure that the file has the correct permissions.

6050

The Session Manager encountered an error while reading the connection profile.

Perhaps foreign files were written to the directory where the persistent store files are located, or the connection profile has been otherwise corrupted.

Recreate the connection profile using the VisiBroker Console.

6051

The Session Manager encountered an error while writing to the connection profile.

Perhaps the file or directory does not have the correct permissions.

The disk is full, and the Session Manager cannot save the connection profile.

You may have specified an incorrect path to the connection profile.

Be sure that the file and directory have the correct permissions.

Free disk space so that the Session Manager can save the connection profile to disk.

Be sure to specify the correct path.

6052

The specified path is invalid.

You may have specified an incorrect path to the connection profile.

Be sure to specify the correct path.

6053

The specified connection profile already exists.

You have tried to create a connection profile with a name that is already taken.

Choose a different name for this connection profile, or delete the other connection profile.

6054

The specified connection profile does not exist.

Perhaps you have misspelled the connection profile name.

Check that you have correctly specified the connection profile name.

6055

The connection profile could not be removed.

Perhaps the file or directory does not have the correct permissions.

Be sure that the file and directory have the correct permissions.

6056

The XA Resource Director was given an DirectConnect (non-XA) Session Manager connection profile.

You attempted to start an XA Resource Director with a connection profile created for the DirectConnect Session Manager.

Make sure to start the XA Resource Director with a connection profile that was created for the XA Session Manager.

6058

Previous hold() call has timed out; connection must be released.

The timeout value supplied to the hold() call has expired and the connection object may no longer be used.

Call release() on this connection and call getConnection() again if still required.

Error code	Description	Possible causes	Solutions
8001	An internal error occurred in the logger module. See the message log for details.	See the error text in the message log.	If you cannot resolve this error from the error text displayed in the message log, contact Micro Focus Support.

An internal error occurred in the logger module. See the message log for details.

See the error text in the message log.

If you cannot resolve this error from the error text displayed in the message log, contact Micro Focus Support.