This appendix lists error messages and their meanings, and it provides suggested actions to correct the problem identified in the message. Use this appendix with Chapter 11, Handling synchronization problems to identify and correct problems.
DSYA000E | Invalid or missing JDKpath environment variable encountered in file dsysetenv.bat. |
Explanation: The specified file contains an invalid or missing environment variable.
User Response: Modify the specified file and correct the specified environment variable to contain a valid path.
DSYA001E | Invalid or missing JSDKpath environment variable encountered in file dsysetenv.bat. |
Explanation: The specified file contains an invalid or missing environment variable.
User Response: Modify the specified file and correct the specified environment variable to contain a valid path.
DSYC100E | Failed to open Config DB |
Explanation: The Sync Client could not open the configuration database. The configuration database may be missing, write-protected, locked by another application, or corrupted.
User Response: Check the access right of the configuration file, have the Sync Server administrator reset the user, and try again. If problems persist, contact IBM software support.
DSYC101E | Failed to open Misc DB |
Explanation: The Sync Client could not open the configuration database. The configuration database may be missing, write-protected, locked by another application, or corrupted.
User Response: Check the access right of the configuration file, have the Sync Server administrator reset the user, and try again. If problems persist, contact IBM software support.
DSYC102E | Failed to open File DB |
Explanation: The Sync Client could not open the configuration database. The configuration database may be missing, write-protected, locked by another application, or corrupted.
User Response: Check the access right of the configuration file, have the Sync Server administrator reset the user, and try again. If problems persist, contact IBM software support.
DSYC103E | Unexpected sync mode |
Explanation: The Sync Client has encountered unexpected internal information while synchronizing configuration information.
User Response: Have the Sync Server administrator reset the user and try again. If problems persist, contact IBM software support.
DSYC104E | String is too long |
Explanation: The Sync Client has encountered unexpected internal information.
User Response: Have the Sync Server administrator reset the user and try again. If problems persist, contact IBM software support.
DSYC105E | Unexpected message format |
Explanation: The Sync Client has encountered unexpected internal information during configuration synchronization.
User Response: Have the Sync Server Administrator reset the user and try again. If problems persist, contact IBM software support.
DSYC106W | Failed to remove file: 'filename' |
Explanation: The Sync Client could not remove the specified file. Note that 'filename' may be truncated.
User Response: Make sure the file is not write-protected, or locked by another application.
DSYC107E | Server reported invalid user or password |
Explanation: The provided username/password doesn't match any registered user on the Sync Server.
User Response: Make sure that the username and password are entered correctly, and try again. If problems persist, contact the Sync Server administrator.
DSYC108E | Server reported user or device not enabled |
Explanation: The user has not been enabled to synchronize by the Sync Server administrator.
User Response: Make sure that the username is entered correctly, and have the Sync Server administrator enable and reset the user, and try again. If problems persist, contact the Sync Server administrator.
DSYC109E | Server reported invalid device ID |
Explanation: An invalid device ID was sent to the Sync Server.
User Response: Contact the Sync Server administrator.
DSYC110E | Server failed to register this client |
Explanation: The Sync Server had problems registering the user.
User Response: Contact the Sync Server administrator.
DSYC111E | Server failed to register this device |
Explanation: The Sync Server had problems registering the device. It could be because that the Sync Client has changed its user information, and thus doesn't match the registered user information at the Sync Server.
User Response: Have the Sync Server Administrator reset the new user, and try again. If problems persist, contact the Sync Server administrator.
DSYC112E | Server reported this device is not registered to this client |
Explanation: The Sync Server had problems registering the device to this user.
User Response: Contact the Sync Server administrator.
DSYC113E | Server reported new client must be enabled first |
Explanation: An invalid username was sent by the Sync Client to the Sync Server, or the user has not been enabled by the Sync Server administrator.
User Response: Make sure that the username is entered correctly, and try again. If problems persist, contact the Sync Server administrator.
DSYC114E | Server encountered an unexpected error |
Explanation: The Sync Server could not synchronize this user.
User Response: Contact the Sync Server administrator.
DSYC115E | Failed to allocate work buffer for config synchronization |
Explanation: The Sync Client could not allocate sufficient memory as work buffer for configuration synchronization.
User Response: The device could be low on available memory. Quit some unused applications, and try again. If problems persist, consult the DB2 Everyplace database engine documentation or contact IBM software support.
DSYC200E | Config Adapter not already loaded |
Explanation: The Sync Client could not load the configuration adapter.
User Response: Make sure the config adapter library has been properly loaded onto the device and try again. Check with your Sync Server administrator for the library file name to look for.
DSYC201E | Failed to find file entry with given ID |
Explanation: The Sync Client detected inconsistent data in its configuration database.
User Response: Have the Sync Server administrator reset the user and try again. If problems persist, contact IBM software support.
DSYC202E | Unexpected empty temp file |
Explanation: The Sync Client detected problems with a file subscription.
User Response: Have the Sync Server administrator reset the user and try again. If problems persist, contact IBM software support.
DSYC203E | Failed to create target file |
Explanation: The Sync Client detected problems creating a file.
User Response: Check the target filename with the administrator and make sure the Sync Client has permission to create it, or it is not being used by another application. Have the Sync Server administrator reset the user and try again. If problems persist, contact IBM software support.
DSYC204E | Failed to remove target file |
Explanation: The Sync Client detected problems removing a file.
User Response: Check the target filename with the administrator and make sure the Sync Client has permission to delete, or it is not being used by another application. Have the Sync Server administrator reset the user and try again. If problems persist, contact IBM software support.
DSYC205E | Failed to create temp file |
Explanation: The Sync Client detected problems creating a temporary file.
User Response: Have the Sync Server administrator reset the user and try again. If problems persist, contact IBM software support.
DSYC206E | Failed to empty temp file |
Explanation: The Sync Client was unable to empty a temporary file
User Response: Have the Sync Server administrator reset the user and try again. If problems persist, contact IBM software support.
DSYC207E | Invalid file format |
Explanation: The Sync Client received unexpected file subscription data from the Sync Server.
User Response: Have the Sync Server administrator reset the user and try again. If problems persist, contact IBM software support.
DSYC208E | Temp file state inconsistent with current message # |
Explanation: The Sync Client received unexpected file subscription data from the Sync Server.
User Response: Have the Sync Server administrator reset the user and try again. If problems persist, contact IBM software support.
DSYC209E | Failed writing to target file |
Explanation: The Sync Client detected problems writing to the target file.
User Response: Check the target filename with the administrator and make sure the Sync Client has permission to modify, or it is not being used by another application. Have the Sync Server administrator reset the user and try again. If problems persist, contact IBM software support.
DSYC210W | Failed to remove temp file |
Explanation: The Sync Client detected problems removing a temporary file.
User Response: Have the Sync Server administrator reset the user and try again. If problems persist, contact IBM software support.
DSYC211E | Unexpected empty target file |
Explanation: The Sync Client received unexpected empty file subscription data from the Sync Server.
User Response: Check the target filename with the administrator and make sure it does exist on the server and is not empty. Have the Sync Server administrator reset the user and try again. If problems persist, contact IBM software support.
DSYC300E | Failed to open adapter: <adapter name> |
Explanation: The Sync Client could not open the adapter library after use.
User Response: Check that the library for 'adapter name' is present on the device. If the library name is unknown, check with the Sync Server administrator. Otherwise, have the Sync Server administrator reset the user and try again.
DSYC301E | Failed to load adapter: <adapter name> |
Explanation: The Sync Client could not load the adapter library after use.
User Response: Check that the library for 'adapter name' is present on the device. If the library name is unknown, check with the Sync Server administrator. Otherwise, have the Sync Server administrator reset the user and try again.
DSYC302E | Failed to close adapter: <adapter name> |
Explanation: The Sync Client could not close the adapter library after use.
User Response: Check that the library for 'adapter name' is present on the device. If the library name is unknown, check with the Sync Server administrator. Otherwise, have the Sync Server administrator reset the user and try again.
DSYC303E | Configuration synchronization failed, synchronization aborted |
Explanation: The Sync Client did not properly sync the configuration information.
User Response: Have the user reset by the Sync Server Administrator and try again. If problems persist, contact IBM software support.
DSYC304E | Authentication failed - synchronization aborted. |
Explanation: The provided username/password doesn't pass the authentication on the Sync Server
User Response: Make sure that the password is entered correctly, and try again. If problems persist, contact the Sync Server administrator.
DSYC305E | Failed to update the sync mode for application |
Explanation: The Sync Client could not update the synchronization mode for applications
User Response: Have the user reset by the Sync Server Administrator and try again. If problems persist, contact IBM software support.
DSYC306E | Authentication failed (invalid encryption key) - synchronization aborted. |
Explanation: The Sync Server could not successfully encrypt/decrypt the message from the client.
User Response: Make sure that the password is entered correctly, and try again. If problems persist, contact the Sync Server administrator.
DSYC307E | Client encryption/decryption failed - synchronization aborted |
Explanation: The Sync Client could not successfully encrypt/decrypt the received message.
User Response: Make sure that the password is entered correctly, and try again. If problems persist, contact the Sync Server administrator.
DSYC308E | Encryption not available |
Explanation: Encryption is not supported for Palm OS V3.2 or earlier versions. The encryption library is not installed, or the path is not set correctly.
User Response: Make sure that the operating system supports the encryption, and the encryption library is properly installed and the path is set correctly. If problem persists, contact the Sync Server administrator.
DSYC309E | Failed to open encryption library |
Explanation: Encryption is not supported for Palm OS V3.2 or previous versions. The encryption library is not installed, or the path is not set correctly.
User Response: Make sure that the operating system supports the encryption, and the encryption library is installed properly and the path is set correctly. If problem persists, contact the Sync Server administrator.
DSYC310E | Incompatible Sync Client version |
Explanation: The Sync Client version is incompatible with the Sync Server version.
User Response: Upgrade the Sync Client to the latest version, and try again. If problem persists, contact the Sync Server administrator.
DSYC400E | Failed to allocate a SQL environment |
Explanation: The Sync Client could not allocate the environment for the DB2 Everyplace database engine.
User Response: The device could be low on available memory. Quit some unused applications, and try again. If problems persist, consult the DB2 Everyplace database engine documentation or contact IBM software support.
DSYC401E | Failed to allocate a SQL connection |
Explanation: The Sync Client could not allocate a connection to the DB2 Everyplace database engine.
User Response: The device could be low on available memory. Quit some unused applications, and try again. If problems persist, consult the DB2 Everyplace database engine documentation or contact IBM software support.
DSYC402E | Failed to connect to the database engine |
Explanation: The Sync Client could not make a connection to the DB2 Everyplace database engine.
User Response: Make sure the DB2 Everyplace database engine is operational with other applications (e.g., sample applications that come with the database). If problems persist, consult the DB2 Everyplace database engine documentation or contact IBM software support.
DSYC403E | No tables specified |
Explanation: No database tables were specified for synchronization.
User Response: There may be missing information in the DB2 Everyplace database subscription. Contact the Sync Server administrator.
DSYC404E | Config Adapter not already loaded |
Explanation: The Sync Client could not find the configuration adapter.
User Response: Make sure the configuration adapter's library is installed on the device. Check with the Sync Server administrator for details on this library or contact IBM software support.
DSYC405E | Failed to allocate a SQL statement |
Explanation: The Sync Client could not allocate memory for a statement handle to the DB2 Everyplace database engine.
User Response: The device could be low on available memory. Quit some unused applications, and try again. If problems persist, consult the DB2 Everyplace database engine documentation or contact IBM software support.
DSYC406E | Unexpected sync mode |
Explanation: The Sync Client has encountered unexpected internal information while synchronizing the DB2 Everyplace database.
User Response: The user must be reset by the Sync Server Administrator. If problems persist, contact IBM software support.
DSYC408E | Unexpected suSTATE value |
Explanation: The Sync Client has encountered an unexpected internal error.
User Response: Contact IBM software support.
DSYC411E | Unexpected SQL data type |
Explanation: The Sync Client has encountered an unexpected or invalid data type.
User Response: The data from the Sync Server may be invalid or a DB2 Everyplace database table may have been altered by another application. Check with the Sync Server administrator, have the user reset, and try again. If problems persist, contact IBM software support.
DSYC412E | Unexpected message format |
Explanation: The Sync Client has encountered unexpected internal information during synchronization of DB2 Everyplace data.
User Response: Have the user reset by the Sync Server Administrator and try again. If problems persist, contact IBM software support.
DSYC413E | No matching local table |
Explanation: The Sync Client cannot find a DB2 Everyplace database table which is involved in the synchronization process.
User Response: The table may have been deleted by another application. Have the user reset by the Sync Server Administrator and try again. If problems persist, contact IBM software support.
DSYC414E | Unexpected end of block data |
Explanation: The Sync Client has encountered unexpected end-of-data during synchronization of DB2 Everyplace data.
User Response: Have the user reset by the Sync Server Administrator and try again. If problems persist, contact IBM software support.
DSYC415W | Truncating - data too long for database field |
Explanation: The Sync Client was forced to truncate data that was too large
User Response: There may be problems with the Sync Server data. Check with the Sync Server administrator.
DSYC416E | Server reported invalid user or password |
Explanation: The username or password sent to the Sync Server was invalid.
User Response: Check the username and password in the "Settings" menu and try again. If problems persist, check with the Sync Server administrator that the user has permission to sync.
DSYC417E | Server reported user or device not enabled |
Explanation: The username and the device ID are not associated on the Sync Server.
User Response: Check the username in the "Settings" menu and try again. If problems persist, check with the Sync Server administrator that the user has permission to sync.
DSYC418E | Records rejected by server |
Explanation: The changes the Sync Client made to the database had conflicts with changes made by the server or other clients.
User Response: Check the Sync Client log, and consult the DB2 Everyplace database engine documentation with the provided SQL state in the error message or contact IBM software support.
DSYC419E | Error in executing a SQL statement: |
Explanation: The Sync Client encountered an error in executing a SQL statement.
User Response: Check the Sync Client log, and consult the DB2 Everyplace database engine documentation with the provided SQL state in the error message or contact IBM software support.
DSYC420E | Attempt to modify read only table |
Explanation: The table the Sync engine just synchronized is read-only, thus no changes are allowed on the server. Although the changes to the table are still effective on the client, they are not synchronized to the server.
User Response: Request that the Sync Server administrator allow write permission to the subscribed table.
DSYC421E | Invalid operations on tables in a PUT subscription |
Explanation: The client attempts to update/delete records of a table belonging to a PUT subscription, which allows insert operations only. Although the updates and deletes to the table are still effective on the client, they are not synchronized to the server.
User Response: Request that the Sync Server administrator allow update/delete permission on the subscription.
DSYC600E | Failed to open connection |
Explanation: The Sync Client has problem opening connection with the Sync Server. This could be due to: 1) Wrong server IP address (or hostname) or port number 2)Server is not up.
User Response: Check to ensure: 1)Server's IP address (or hostname) and port number are correctly entered 2)The Sync Server is currently operational 3)Click on "Retry". If problems persists, contact IBM software support.
DSYC601E | Failed to establish connection |
Explanation: The Sync Client has problem opening connection with the Sync Server. This could be due to: 1)Wrong server IP address (or hostname) or port number 2)Server is not up 3)Network is busy 4)PPP program is not operational.
User Response: Check to ensure: 1)Server's IP address (or hostname) and port number are correctly entered. 2)The Sync Client has access to the Sync Server through either a serial cable (for example, Windows RAS), a modem, or a network connection. 3)The Sync Server is currently operational. 4)If using Mocha (freeware version), stop and restart the program 5)Click "Retry". If you are using a Palm device, select Drop connection after sync in the advanced settings, and retry several times. If the problem persists, contact IBM software support.
DSYC602E | Failed to send request |
Explanation: The Sync Client has successfully connected to the Sync Server, but has problem sending a request to the server. This could be due to: 1)Server is not up 2)Connection is lost.
User Response: Check to ensure: 1)The Sync Client has access to the Sync Server through either a serial cable (e.g., through Windows RAS), a modem, or a network connection. 2)The Sync Server is currently operational. 3)Click on "Retry". If problems persists, contact IBM software support.
DSYC603E | Failed to receive reply |
Explanation: The Sync Client has successfully connected to, and sent a request to the Sync Server, but has problem receiving the reply from the server, or the received message is corrupted or in an unexpected format. This could be due to: 1)Unregistered user 2)Server is not up 3)Connection is lost.
User Response: Check to ensure: 1)The user name and password are correctly entered, and the user is registered with the Sync Server administrator. 2)The Sync Client has access to the Sync Server through either a serial cable (e.g., through Windows RAS), a modem, or a network connection. 3)The Sync Server is currently operational. 4)Click on "Retry". If problems persists, contact IBM software support.
DSYC604E | Timeout while receiving reply |
Explanation: The Sync Client has successfully connected to, and sent a request to the Sync Server, but has not received the reply from the server before timeout. This could be due to: 1)Server needs more time preparing the inquired information 2)Network is busy 3)Server is not up 4)Connection is lost
User Response: Check to ensure: 1)The Sync Client has access to the Sync Server through either a serial cable (e.g., through Windows RAS), a modem, or a network connection. 2)The Sync Server is currently operational. 3)Click on "Retry". If problems persists, contact IBM software support.
DSYC605E | Failed to receive acknowledge |
Explanation: The Sync Client has successfully connected to, sent a request to the server, and received the reply from the Sync Server, but does not receive the acknowledge from the server. This could be due to: 1)Server needs more time preparing the inquired information 2)Network is busy 3)Server is not up 4)Connection is lost
User Response: Check to ensure: 1)The Sync Client has access to the Sync Server through either a serial cable (e.g., through Windows RAS), a modem, or a network connection. 2)The Sync Server is currently operational. 3)Click on "Retry". If problems persists, contact IBM software support.
DSYC606E | Failed to open the Net library |
Explanation: The Sync Client has problem opening the Network library. This could be due to the "Redirect Net.Lib calls to host TCP/IP" box is not checked.
User Response: Make sure the check box under Settings->Properties is set (checked).
DSYC607E | Failed to load the Net library |
Explanation: The Sync Client has problem loading the Network library. This could be due to the "Redirect Net.Lib calls to host TCP/IP" box is not checked.
User Response: Make sure the check box under Settings->Properties is set (checked).
DSYC608E | Failed to close the Net library |
Explanation: The Sync Client has problem closing the Network library. This could be due to the "Redirect Net.Lib calls to host TCP/IP" box is not checked.
User Response: Make sure the check box under Settings->Properties is set (checked).
DSYC609E | Failed to resolve hostname |
Explanation: The Sync Client cannot resolve the IP for the provided hostname.
User Response: Make sure the server hostname is correctly specified.
DSYC610E | Failed to allocate working buffer for transport |
Explanation: The Sync Client could not allocate sufficient memory as transport buffer.
User Response: Close the applications that you are not using and try again. If the problem persists, install more memory on the machine.
DSYC699E | (ISYNCINFO_ErrNetUnknown) Unknown network error |
Explanation: The Sync Client has encounter an unknown error while communicating with the Sync Server.
User Response: Contact IBM technical support
DSYD000E | A DB2 database adapter set wait was interrupted for database <database name>, synchronization window <sync window name>, flag <flag name>. |
Explanation: The adapter for the named database was waiting for the specified flag, but was interrupted. Because synchronization is a multi-threaded process, several messages may be issued for an interruption.
User Response: To find the source of the problem, access the log in the Mobile Devices Administration Center and review the error with the timestamp preceding the timestamp of this message. Follow the recommended actions for that message. If no previous message exists in this message sequence, contact IBM Software Support.
DSYD002E | The DataPropagator manager wait for database <database name> was interrupted. |
Explanation: This error is a secondary effect of another error. Because synchronization is a multi-threaded process, several messages may be issued for an interruption.
User Response: To find the source of the problem, access the log in the Mobile Devices Administration Center and review the error with the timestamp preceding the timestamp of this message. Follow the recommended actions for that message. If no previous message exists in this message sequence, contact IBM Software Support.
DSYD006E | The MDSS session monitor encountered an exception from the SQL statement: <SQL statement>. |
Explanation: The DB2 Everyplace Sync Server records information about the state of each synchronization session in session monitoring tables in the administration control database, DSYCTLDB. The Sync Server issues an SQL statement to add an entry for each new session so that session state information is persistent. The SQL statement failed because the session monitor tables could not be accessed.
User Response: Ensure that the DSYCTLDB database is functional and that storage is not exhausted. If no problems are found, contact IBM Software Support.
DSYD007E | The MDSS connection pool encountered the exception: <exception details>. |
Explanation: The DB2 Everyplace Sync Server creates a pool of database connections for each database accessed. In this case, the Sync Server attempt to use a connection from this pool for the named database failed, probably because the named database is not functional.
User Response: Ensure that the named database is functional. If no problems are found, contact IBM Software Support.
DSYD010E | The DB2 adapter failed to generate a DataPropagator password file for Apply qualifier <apply qualifier>. |
Explanation: A password file is generated for each Apply qualifier each time you start the DB2 Everyplace Sync Server. DB2 Data Propagator uses the user ID and password in this file to access the source database. Synchronization fails for all subscriptions whose Apply qualifier does not have a corresponding password file. File creation might have failed because of inadequate storage in the directory where the Sync Server is running.
User Response: Ensure that adequate storage is available in the directory where the DB2 Everyplace Sync Server is running. Then stop and restart the Sync Server to attempt to generate the password file. If problems persist, contact IBM Software Support.
DSYD011E | The DB2 adapter was unable to create the tables required for synchronizing table <schema name>.<table name> in database <database name>. |
Explanation: The DB2 Everyplace Sync Server creates staging tables for each mirror table involved in synchronization. These tables are created when you create a subscription against the database that corresponds to the mirror referenced in the message. Creation of these tables could fail because of inadequate storage or a non-functional database.
User Response: Ensure that the database referenced in the message is functional and that adequate storage is available. Open the Mobile Devices Administration Center and remove and recreate the subscriptions for the referenced database to attempt to create the staging tables again. If you continue to receive this message, contact IBM Software Support.
DSYD012E | The DB2 adapter was unable to drop the tables required for synchronizing table <schema name>.<table name> in database <database name>. |
Explanation: To manage synchronization, the DB2 Everyplace Sync Server creates multiple tables in association with a given mirror database. When you delete subscription sets associated with the mirror in the named database, the Sync Server drops the tables associated with the deleted subscription set. This drop operation might fail if the database is not functional.
User Response: Ensure that the database named in the message is functional.
DSYD014E | The DB2 adapter was unable to access the synchronization mirror table <schema name>.<table name> in database <database name>. |
Explanation: An error occurred while attempting to access the mirror table.
User Response: Ensure that you are connected to the mirror database named in the message and that the database has adequate storage capacity. If problems persist, contact IBM Software Support.
DSYD015E | The DB2 adapter was unable to access the synchronization tables peripheral to mirror table <schema name>.<table name> in database <database name>. |
Explanation: To manage synchronization, the DB2 Everyplace Sync Server creates multiple tables in association with a given mirror table. An error occurred when the Sync Server attempted to access these tables for the mirror table referenced in the message.
User Response: Ensure that the database named in the message is functional. If problems persist, contact IBM Software Support.
DSYD016E | The DB2 adapter was unable to initialize the session-monitoring tables in database <database name>. |
Explanation: The session-monitoring tables are part of the control database (DSYCTLDB) and are initialized at the start of a synchronization session. Initialization might fail because the control database is not functional or storage is exhausted.
User Response: Ensure that the control database is functional and that storage is adequate. If problems persist, contact IBM Software Support.
DSYD017E | The DB2 adapter was unable to add database <database name> to the session monitoring tables. |
Explanation: An error occurred while attempting to add a database for synchronization to the session-monitoring tables.
User Response: Ensure that the control database (DSYCTLDB) is functional. If problems persist, contact IBM Software Support.
DSYD018E | The DB2 adapter was unable to access the ASN.IBMSNAP_APPLYTRAIL table in database <database name>. |
Explanation: An error occurred while attempting to access the DataPropagator apply trail table.
User Response: Ensure that the database named in the message is functional, and that the DB2 Data Propagator subscription was properly set up. Additionally, see the DB2 UDB Replication Guide and Reference for reasons the Apply Trail table could not be accessed. If problems persist, contact IBM Software Support.
DSYD019E | The DB2 adapter was unable to access the ASN.IBMSNAP_UOW table in database <database name>. |
Explanation: An error occurred while attempting to access the DataPropagator unit-of-work table.
User Response: Ensure that the database named in the message is functional, and that the Data Propagator subscription was properly set up. Additionally, see the DB2 UDB Replication Guide and Reference for reasons the unit-of-work table could not be accessed. If problems persist, contact IBM Software Support.
DSYD020E | The DB2 adapter was unable to access the <database name> database. |
Explanation: An error occurred while attempting to access the administration control database (DSYCTLDB). The DB2 Everyplace Sync Server accesses this database to authenticate each user at the start of a session, obtain information on the data and files to which the user is subscribed, and to monitor the synchronization session.
User Response: Ensure that DSYCTLDB is functional. If problems persist, contact IBM Software Support.
DSYD021E | The DB2 adapter was unable to perform successful recovery on database <database name>. |
Explanation: An error occurred while attempting to recover this database from a previous disruption. The DB2 Everyplace Sync Server continues, at intervals, to try to recover synchronization for the database.
User Response: Ensure that the database named in the message is functional. If problems persist, contact IBM Software Support.
DSYD022E | The DB2 adapter was unable to access the change data table <schema.table name> in database <database name>. |
Explanation: An error occurred while attempting to access the Data Propagator change data table.
User Response: Ensure that the database named in the message is functional, and that the subscription was properly set up in the Mobile Devices Administration Center. If problems persist, contact IBM Software Support.
DSYD023E | The DB2 adapter is creating a cumulative error <error>. |
Explanation: After the DB2 Everyplace Sync Server authenticates the client, it attempts to read the synchronization request. If several rows of data in the request are unreadable, the Sync Server returns a single cumulative error indicating that the message appears to be unreadable, rather than returning an individual message for each row of the request that cannot be read. A cumulative error can result if the metadata for the source table differs from that of the target table (for example, if the client added a column that was not in the source table and tried to synchronize).
User Response: Stop the DB2 Everyplace Sync Server and use the UDB Control Center to compare the metadata for the synchronizing tables. Then restart the Sync Server and instruct the client to refresh the target table on the device (which replaces the local copy of the data with the data in the source table).
DSYD024E | The DB2 adapter is aborting a session running on database <database name>. |
Explanation: An error occurred which caused the DB2 adapter to abort all sessions currently running against the database named in the message. The DB2 Everyplace Sync Server might be having trouble communicating with the database because the database is not functional.
User Response: Check whether the specified database is functional. If problems persist, contact IBM Software Support.
DSYD025E | The DB2 adapter is encountering excessive numbers of errors across clients on database <database name>. |
Explanation: Cumulative errors are being reported to several clients issuing synchronization requests for this database. If several rows of data in a client's synchronization request are unreadable, the DB2 Everyplace Sync Server returns a single cumulative error indicating that the message appears to be unreadable, rather than returning an individual message for each row of the request that cannot be read. A cumulative error can result if the metadata for the source table differs from that of the target table (for example, if the client added a column that was not in the source table and tried to synchronize).
User Response: Stop the DB2 Everyplace Sync Server and use the Control Center to compare the metadata for the synchronizing tables. Then restart the Sync Server and instruct the client to refresh the target table on the device (which replaces the local copy of the data with the data in the source table).
DSYD026E | The DataPropagator Capture process failed for database <database name>. |
Explanation: Synchronization of this database is not possible until the Data Propagator Capture error is addressed.
User Response: See the DB2 UDB Replication Guide and Reference for information about why the Capture program failed. If problems persist, contact IBM Software Support.
DSYD027E | The DataPropagator Apply process failed for database <database name>, Apply qualifier <apply qualifier>. |
Explanation: Synchronization of this database is not possible until the DataPropagator Apply error is addressed.
User Response: See the DB2 UDB Replication Guide and Reference for information about why the Apply program failed. If problems persist, contact IBM Software Support.
DSYD028I | A synchronization element for database <database name>, table <schema name>.<table name>, primary key <primary key value>, from device <device id> was rejected due to <reject code>. |
Explanation: The synchronization element for the relational database row specified was not accepted for synchronization for the reason given.
User Response: No action required.
DSYD029W | The DB2 Everyplace Sync Server detected a syntax error in the user WHERE clause of the mirror table <full table name> in database <database name>. <Message from parser> <WHERE clause> |
Explanation: The DB2 Everyplace Sync Server parses the WHERE clause to obtain the information to handle WHERE clauses that involve multiple tables. If the WHERE clause refers to only one table, this warning can be safely ignored.
User Response: Correct the WHERE clause in Mobile Devices Administration Center. If problems persist, contact IBM Software Support.
DSYD032E | Look-up table <table_name> is not found in mirror database, but is mentioned in the user filter of <mirror_table_name> in <subscription_name>. |
Explanation: The filter makes reference to a table that does not exist in the mirror database.
User Response: Correct the filter in Mobile Device Administration Center to make it refer to only those tables that are replicated to the mirror database.
DSYF000E | MDSS encountered an exception <exception details>. |
Explanation: MDSSServlet encountered an exception.
User Response: Gather trace and log files, and contact IBM Software Support for the specific adapter.
DSYF001E | MDSS servlet failed to initialize. |
Explanation: The Mobile Devices Synchronization Server servlet failed to intitialize.
User Response: Contact IBM Software Support
DSYF002E | MDSS adapter servlet initialization failed |
Explanation: The MDSS adapter servlet initialiation failed.
User Response: Gather trace and log files, and contact IBM Software Support for the specific adapter.
DSYG000E | Invalid password specified for user <user name>. |
Explanation: The named user failed authentication due to an invalid password.
User Response: Specify the valid password for the user and try again.
DSYG001E | An unexpected exception occurred: <exception>. |
Explanation: DB2 Everyplace Sync Server encountered the specified unexpected exception.
User Response: Report the error to your administrator.
DSYG002E | Unable to locate file <filename>. |
Explanation: The specified file could not be located and therefore could not be read.
User Response: Verify the file path and file name and try again.
DSYG003E | Unable to connect to database <database name>. |
Explanation: A connection to the specified database could not be established.
User Response: Verify that the database name, driver, userid and password is valid and that it is operational. Verify that the placeholder brackets "{" and "}" are not used when specifying the file name.
DSYG004I | Connection to database <database name> successful. |
Explanation: A connection to the specified database was successfully established.
User Response: No action required.
DSYG005E | The Evaluation License for this product installation has expired. |
Explanation: This product installation has been licensed for evaluation purposes only, and the evaluation period has expired.
User Response: Please contact IBM for information on purchasing this product.
DSYG006I | The Evaluation License for this product installation expires in <remaining days> days. |
Explanation: This product installation has been licensed for evaluation purposes only, and will cease to operate in the number of days reported.
User Response: Please contact IBM for information on purchasing this product to avoid interruption in service.
DSYJ000E | The database adaptor detected a non-insertion operation in a Put subscription: <operation>. |
Explanation: In a upload subscription, only insertion is allowed. Deletion and update are rejected.
User Response: No action is required.
DSYJ001E | A database error occurred. <the error message from database> |
Explanation: A database error occurred. The error message is obtained from the database.
User Response: Refer to the documentation of your database to diagnose the problem. If the problem persists, contact your database administrator.
DSYJ002E | Invalid JDBC driver name <driver name>. |
Explanation: The MDSS is unable to determine which database the specified JDBC driver name is used.
User Response: Verify that the JDBC driver name is correct. If it is correct, add the JDBC driver to the file com\ibm\mobileservices\DSYJdbcDriverList.properties.
DSYM000E | Unable to start the DB2 Everyplace Mobile Devices Administration Center because the required control database 'DSYCTLDB' does not exist or is invalid. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not be started because the required control database 'DSYCTLDB' does not exist or is invalid.
User Response: Verify the existence of the control database 'DSYCTLDB' and possibly rerun the script to create the control database (such as dsyctldb.bat).
DSYM001E | Unable to locate ID for subscription set <subscription set name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not locate the specified subscription set.
User Response: Correct the error and try again.
DSYM002E | Unable to associate group with subscription set <subscription set name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not associate a group with the specified subscription set. Possible reason: the group is invalid or does not exist.
User Response: Verify that the group is valid and try again.
DSYM003E | Unable to disassociate group from subscription set <subscription set name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not disassociate a group from the specified subscription set. Possible reason: the group is invalid or does not exist.
User Response: Verify that the group is valid and try again.
DSYM004E | Unable to associate subscription with subscription set <subscription set name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not associate a subscription with the specified subscription set. Possible reason: the subscription is invalid or does not exist.
User Response: Verify that the subscription is valid and try again.
DSYM005E | Unable to disassociate subscription from subscription set <subscription set name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not disassociate a subscription from the specified subscription set. Possible reason: the subscription is invalid or does not exist.
User Response: Verify that the subscription is valid and try again.
DSYM006E | Invalid or duplicate subscription set name <subscription set name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified subscription set because the name is invalid or another subscription set with the same name exists.
User Response: Specify a unique, valid subscription set name and try again.
DSYM007E | Update subscription set <subscription set name> name failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified subscription set because the name is invalid or it already exists.
User Response: Specify a unique, valid subscription set name and try again.
DSYM008E | Update subscription set <subscription set name> description failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified subscription set description because the description is invalid.
User Response: Specify a valid subscription set description and try again.
DSYM009E | Update subscription set <subscription set name> signature failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified subscription set signature because the signature is invalid.
User Response: Specify a valid subscription set signature and try again.
DSYM010E | Update subscription set <subscription set name> subscriptions failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified subscription set subscriptions. Possible reason: the subscription is invalid or does not exist.
User Response: Verify that the subscription is valid and try again.
DSYM011E | Update subscription set <subscription set name> groups failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified subscription set groups. Possible reason: the group is invalid or does not exist.
User Response: Verify that the group is valid and try again.
DSYM012E | Unable to locate ID for user <user name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not locate the specified user.
User Response: Correct the error and try again.
DSYM013E | Invalid or duplicate user name <user name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified user because the name is invalid or another user with the same name exists.
User Response: Specify a unique, valid user name and try again.
DSYM014E | Update user <user name> name failed. Action canceled. |
Explanation: The DB2 Everywhere Mobile Devices Administration Center could not update the specified user because the name is invalid or it already exists.
User Response: Specify a unique, valid user name and try again.
DSYM015E | Update user <user name> description failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified user description because the description is invalid.
User Response: Specify a valid user description and try again.
DSYM016E | Unable to associate group with user <user name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not associate a group with the specified user. Possible reason: the group is invalid or does not exist.
User Response: Verify that the group is valid and try again.
DSYM017E | Update user <user name> password failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified user password because the password is invalid.
User Response: Specify a valid user password and try again.
DSYM018E | Update user <user name> enable state failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified user enable state because the enable state is invalid.
User Response: Specify a valid user enable state and try again.
DSYM019E | Update user <user name> data filters failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified user data filters. Possible reasons: 1) the group level data filter is invalid or does not exist; 2) the user data filter value is invalid.
User Response: Correct the error and try again.
DSYM020E | Unable to remove data filter <data filter name> from the user. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not remove the specified data filter from the user. Possible reasons: the data filter is invalid or is no longer defined at the group level.
User Response: Correct the error and try again.
DSYM021E | Unable to remove data filter <data filter name> from the group. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not remove the specified data filter from the group. Possible reason: the data filter is invalid or no longer exists.
User Response: Correct the error and try again.
DSYM022E | Unable to disassociate subscription set from group <group name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not disassociate a subscription set from the specified group. Possible reason: the subscription set is invalid or does not exist.
User Response: Verify that the subscription set is valid and try again.
DSYM023E | Unable to locate id for group <group name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not locate the specified group.
User Response: Correct the error and try again.
DSYM024E | Invalid or duplicate group name <group name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified group because the name is invalid or another group with the same name exists.
User Response: Specify a unique, valid group name and try again.
DSYM025E | Update group <group name> name failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified group because the name is invalid or it already exists.
User Response: Specify a unique, valid group name and try again.
DSYM026E | Update group <group name> description failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified group description because the description is invalid.
User Response: Specify a valid group description and try again.
DSYM027E | Update group <group name> password failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified group password because the password is invalid.
User Response: Specify a valid group password and try again.
DSYM028E | Update group <group name> enable state failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified group enable state because the enable state is invalid.
User Response: Specify a valid group enable state and try again.
DSYM029E | Unable to associate user with group <group name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not associate a user with the specified group. Possible reason: the user is invalid or does not exist.
User Response: Verify that the user is valid and try again.
DSYM030E | Unable to associate subscription set with group <group name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not associate a subscription set with the specified group. Possible reason: the subscription set is invalid or does not exist.
User Response: Verify that the subscription set is valid and try again.
DSYM031E | Update group <group name> data filters failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified group data filters. Possible reason: the group data filter value is invalid.
User Response: Correct the error and try again.
DSYM032E | Unable to locate ID for subscription <subscription name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not locate the specified subscription.
User Response: Correct the error and try again.
DSYM033E | Unable to associate subscription set with subscription <subscription name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not associate a subscription set with the specified subscription. Possible reason: the subscription set is invalid or does not exist.
User Response: Verify that the subscription set is valid and try again.
DSYM034E | Unable to disassociate subscription set from subscription <subscription name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not disassociate a subscription set from the specified subscription. Possible reason: the subscription set is invalid or does not exist.
User Response: Verify that the subscription set is valid and try again.
DSYM035E | Unable to locate ID for file subscription <subscription name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not locate the specified file subscription.
User Response: Correct the error and try again.
DSYM036E | Invalid or duplicate file subscription name <file subscription name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified file subscription because the name is invalid or another file subscription with the same name exists.
User Response: Specify a unique, valid file subscription name and try again.
DSYM037E | Unable to create file subscription <file subscription name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not create the specified file subscription.
User Response: Correct the error and try again.
DSYM038E | Update file subscription <file subscription name> name failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified file subscription because the name is invalid or it already exists.
User Response: Specify a unique, valid file subscription name and try again.
DSYM039E | Update file subscription <file subscription name> dirty bit failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified file subscription dirty bit because the dirty bit is invalid.
User Response: Correct the error and try again.
DSYM040E | Update file subscription <file subscription name> timestamp failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified file subscription timestamp because the timestamp is invalid.
User Response: Correct the error and try again.
DSYM041E | Update file subscription <file subscription name> description failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified file subscription description because the description is invalid.
User Response: Specify a valid file subscription description and try again.
DSYM042E | Update file subscription <file subscription name> source failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified file subscription source because the source is invalid.
User Response: Specify a valid file subscription source and try again.
DSYM043E | Update file subscription <file subscription name> target failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified file subscription target because the target is invalid.
User Response: Specify a valid file subscription target and try again.
DSYM044E | Unable to associate subscription set with file subscription <file subscription name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not associate a subscription set with the specified file subscription. Possible reason: the subscription set is invalid or does not exist.
User Response: Verify that the subscription set is valid and try again.
DSYM045E | Invalid source database for table subscription <table subscription name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center detected an invalid source database for the specified table subscription.
User Response: Verify that the source database is correct and in the {SYSTEM}.{INSTANCE}.{DATABASE} format.
DSYM046E | Invalid or duplicate table subscription name <table subscription name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified table subscription because the name is invalid or another table subscription with the same name exists.
User Response: Specify a unique, valid table subscription name and try again.
DSYM047E | Invalid or missing DataPropagator subscription. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not locate the associated DataPropagator subscription.
User Response: Correct the error and try again.
DSYM048E | Unable to create source replication properties for table subscription <table subscription name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not create the source replication properties for the specified table subscription.
User Response: Correct the error and try again.
DSYM049E | Unable to create mirror replication properties for table subscription <table subscription name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not create the specified table subscription mirror replication properties.
User Response: Correct the error and try again.
DSYM050E | Unable to create table subscription <table subscription name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not create the specified table subscription.
User Response: Correct the error and try again.
DSYM051E | Unable to locate ID for table subscription <table subscription name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not locate the specified table subscription.
User Response: Correct the error and try again.
DSYM052E | Unable to locate source replication properties id for table subscription <table subscription name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not locate the specified table subscription source replication properties.
User Response: Correct the error and try again.
DSYM053E | Unable to locate mirror replication properties id for table subscription <table subscription name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not locate the specified table subscription mirror replication properties.
User Response: Correct the error and try again.
DSYM054E | Update table subscription <table subscription name> name failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified table subscription because the name is invalid or it already exists.
User Response: Specify a unique, valid table subscription name and try again.
DSYM055E | Update table subscription <table subscription name> description failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified table subscription description because the description is invalid.
User Response: Specify a valid table subscription description and try again.
DSYM056E | Update table subscription <table subscription name> source system failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified table subscription source system because the source system is invalid.
User Response: Specify a valid table subscription source system and try again.
DSYM057E | Update table subscription <table subscription name> source instance failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified table subscription source instance because the source instance is invalid.
User Response: Specify a valid table subscription source instance and try again.
DSYM058E | Update table subscription <table subscription name> source database failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified table subscription source database because the source database is invalid.
User Response: Specify a valid table subscription source database and try again.
DSYM059E | Update table subscription <table subscription name> source user ID failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified table subscription source user ID because the source user ID is invalid.
User Response: Specify a valid table subscription source user ID and try again.
DSYM060E | Update table subscription <table subscription name> source password failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified table subscription source password because the source password is invalid.
User Response: Specify a valid table subscription source password and try again.
DSYM061E | Update table subscription <table subscription name> mirror database failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified table subscription mirror database because the mirror database is invalid.
User Response: Specify a valid table subscription mirror database and try again.
DSYM062E | Update table subscription <table subscription name> mirror user ID failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified table subscription mirror user ID because the mirror user ID is invalid.
User Response: Specify a valid table subscription mirror user ID and try again.
DSYM063E | Update table subscription <table subscription name> mirror password failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified table subscription mirror password because the mirror password is invalid.
User Response: Specify a valid table subscription mirror password and try again.
DSYM064E | Update table subscription <table subscription name> mirror sync window failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified table subscription mirror sync window because the mirror sync window is invalid.
User Response: Specify a valid table subscription mirror sync window and try again.
DSYM065E | Update table subscription <table subscription name> mirror sync maximum users failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified table subscription mirror sync maximum users because the mirror sync maximum users is invalid.
User Response: Specify a valid table subscription mirror sync maximum users and try again.
DSYM066E | Update table subscription <table subscription name> target database failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified table subscription target database because the target database is invalid.
User Response: Specify a valid table subscription target database and try again.
DSYM067E | Update table subscription <table subscription name> Apply qualifier failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified table subscription Apply qualifier because the Apply qualifier is invalid.
User Response: Specify a valid table subscription Apply qualifier and try again.
DSYM068E | Update table subscription <table subscription name> mirror only failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified table subscription mirror only because the mirror only is invalid.
User Response: Specify a valid table subscription mirror only and try again.
DSYM069E | Update table subscription <table subscription name> user WHERE clause failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified table subscription user WHERE clause because the user WHERE clause is invalid.
User Response: Specify a valid table subscription user WHERE clause and try again.
DSYM070E | Update table subscription <table subscription name> subtables failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified table subscription subtables because a subtable is invalid.
User Response: Specify a valid table subscription subtable and try again.
DSYM071E | Unable to associate subscription set with table subscription <table subscription name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not associate a subscription set with the specified table subscription. Possible reason: the subscription set is invalid or does not exist.
User Response: Verify that the subscription set is valid and try again.
DSYM072E | Unable to create DataPropagator table manager control tables for table subscription <table subscription name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not complete the changes to the specified subscription as an exception was encountered during processing.
User Response: Correct the error and try again.
DSYM073I | Unable to update DataPropagator table manager control tables for table subscription <table subscription name>. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not complete the changes to the specified subscription as an exception was encountered during processing.
User Response: No action required.
DSYM074E | The replication subscription using source table <source table name> and target table <target table name> does not contain a target column with a primary key. Action canceled. |
Explanation: The specified replication subscription table is invalid because it does not contain a target column defined as a primary key.
User Response: Use the advanced subscription definition, dialog, target columns tab to select one or more target columns to be a primary key.
DSYM075E | The DB2 Everyplace Mobile Devices Administration Center encountered an unexpected exception: <exception>. Close the DB2 Everyplace Mobile Devices Administration Center and try again. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center encountered the specified exception.
User Response: Close the DB2 Everyplace Mobile Devices Administration Center and try again. If the error persists, verify that two subscriptions in the same subscription set do not have the same name and are trying to subscribe to the same table. If two subscriptions have the same name, assign them to two different subscription sets.
DSYM076E | Unable to create DataPropagator table manager control tables for table subscription <table subscription name> as no tables were found at the mirror. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not complete the changes to the specified subscription because no tables were found at the mirror.
User Response: Verify that the specific subscription mirror authentication is correct and has the proper authorizations to access the mirror
DSYM077E | User <user name> password and verify password are not the same. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified user password because the password and verify password are not the same.
User Response: Specify a valid, matching password and verify password and try again.
DSYM078E | Group <group name> password and verify password are not the same. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified group password because the password and verify password are not the same.
User Response: Specify a valid, matching password and verify password and try again.
DSYM079E | Table subscription <table subscription name> source database password and verify password are not the same. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified table subscription source database password because the source database password and source database verify password are not the same.
User Response: Specify a valid, matching source database password and verify password and try again.
DSYM080E | Table subscription <table subscription name> mirror database password and verify password are not the same. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified table subscription mirror database password because the mirror database password and mirror database verify password are not the same.
User Response: Specify a valid, matching mirror database password and verify password and try again.
DSYM082E | Duplicate target table names for table subscription <table subscription name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center detected duplicate target table names for the specified table subscription. The target table names within a single table subscription must be unique.
User Response: Specify unique target table names and try again.
DSYM083E | Duplicate target table names for table subscriptions assigned to subscription set <subscription set name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center detected duplicate target table names for two or more table subscriptions assigned to the specified subscription set. The target table names of table subscriptions assigned to a subscription set must be unique.
User Response: Ensure that the table subscriptions assigned to the specified subscription set use unique target table names and try again.
DSYM084E | Duplicate target table names for table subscriptions assigned to subscription sets of the group <group name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center detected duplicate target table names for two or more table subscriptions in subscription sets assigned to the specified group. The target table names of table subscriptions assigned to subscription sets of a group must be unique.
User Response: Ensure that the table subscriptions assigned to the specified group use unique target table names and try again.
DSYM085E | Assignment of subscription set <subscription set name> to one or more selected groups would result in duplicate table subscription target table names. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center detected that the assignment of the specified subscription set to the group(s) would result in duplicate target table names. The target table names of table subscriptions used by a group must be unique.
User Response: Ensure that the groups using the table subscriptions assigned in the specified subscription set use unique target table names and try again.
DSYM086E | Assignment of the the table subscription <table subscription name> to one or more selected subscription sets would result in duplicate table subscription target table names. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center detected that the assignment of the specified subscription to the subscription set(s) would result in duplicate target table name names. The target table names of table subscriptions used by a subscription set must be unique.
User Response: Ensure that the subscription sets using the specified table subscription use unique target table names and try again.
DSYM087E | Assignment of one or more subscription sets to group <group name> would result in duplicate table subscription target table names. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center detected that the assignment of subscription set(s) to the specified group would result in duplicate target table names. The target table names of table subscriptions assigned to subscription sets of a group must be unique.
User Response: Ensure table subscriptions assigned to subscription sets for the specified group contain unique target table names and try again.
DSYM088E | Unable to delete the instance of a DSY default adapter <adapter name>. Action ignored. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center detected an attempt to delete the specified DSY default adapter. The specified adapter can not be deleted as it is required by the DB2 Everyplace Mobile Devices Administration Center.
User Response: Do not remove any DSY default adapter.
DSYM089E | Invalid or duplicate adapter name <adapter name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified adapter because the name is invalid or another adapter with the same name exists.
User Response: Specify a unique, valid adapter name and try again.
DSYM090E | Unable to locate ID for adapter <adapter name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not locate the specified adapter.
User Response: Correct the error and try again.
DSYM091E | Update adapter <adapter name> name failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified adapter because the name is invalid or it already exists.
User Response: Specify a unique, valid adapter name and try again.
DSYM092E | Update adapter <adapter name> description failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified adapter description because the description is invalid.
User Response: Specify a valid adapter description and try again.
DSYM093E | Update adapter <adapter name> signature failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified adapter signature because the signature is invalid.
User Response: Specify a valid adapter signature and try again.
DSYM094E | Update adapter <adapter name> subscriptions failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified adapter subscriptions. Possible reason: the subscription is invalid or does not exist.
User Response: Verify that the subscription is valid and try again.
DSYM095E | Update adapter <adapter name> communication attributes failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified adapter communication attributes because one or more communication attributes are invalid.
User Response: Specify valid communication attributes and try again.
DSYM096E | Update adapter <adapter name> file attributes failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified adapter file attributes because one or more file attributes are invalid.
User Response: Specify valid file attributes and try again.
DSYM097E | Update adapter <adapter name> subscriptions failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified adapter subscriptions. Possible reason: the subscription is invalid or does not exist.
User Response: Verify that the subscription is valid and try again.
DSYM098E | Unable to associate adapter with subscription <subscription name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not associate an adapter with the specified subscription. Possible reason: the adapter is invalid or does not exist.
User Response: Verify that the adapter is valid and try again.
DSYM099E | Unable to disassociate adapter from subscription <subscription name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not disassociate an adapter from the specified subscription. Possible reason: the adapter is invalid or does not exist.
User Response: Verify that the adapter is valid and try again.
DSYM100I | DataPropagator table subscription <table subscription name> created successfully. Additional steps may be required before the table subscription can be used for synchronization. Refer to the DB2 Everyplace Sync Server Administration Guide for more information. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center successfully created the specified table subscription. However, additional steps may be required before the specified subscription can be used for synchronization.
User Response: Refer to the DB2 Everyplace Sync Server Administration Guide for further information.
DSYM101E | Update table subscription <table subscription adapter> adapter failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified table subscription because the adapter is invalid.
User Response: Specify a valid table subscription adapter and try again.
DSYM102E | Unable to delete adapter <adapter name> as one or more subscriptions are currently using it. Action ignored. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center detected an attempt to delete the specified adapter. The specified adapter can not be deleted as it is still used by one or more subscriptions.
User Response: Reassign all subscriptions using the specified adapter to use different adapters and try again or refresh the adapter object and try again.
DSYM103E | Update file subscription <file subscription adapter> adapter failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified file subscription because the adapter is invalid.
User Response: Specify a valid file subscription adapter and try again.
DSYM104E | Unable to connect to database <database name> using driver <driver name>, userid <userid> and password <password>. |
Explanation: A connection to the specified database could not be established.
User Response: Verify that the database name, driver, userid and or password is valid and that it is operational.
DSYM105E | Update table subscription <table subscription name> source database failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified table subscription source database because the source database is invalid.
User Response: Specify a valid table subscription source database and try again.
DSYM106E | Update table subscription <table subscription name> mirror database failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified table subscription mirror database because the mirror database is invalid.
User Response: Specify a valid table subscription mirror database and try again.
DSYM107E | Update table subscription <table subscription name> source driver failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified table subscription source driver because the source driver is invalid.
User Response: Specify a valid table subscription source driver and try again.
DSYM108E | Update table subscription <table subscription name> mirror driver failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified table subscription mirror driver because the mirror driver is invalid.
User Response: Specify a valid table subscription mirror driver and try again.
DSYM109E | Update table subscription <table subscription name> source userid failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified table subscription source userid because the source userid is invalid.
User Response: Specify a valid table subscription source userid and try again.
DSYM110E | Update table subscription <table subscription name> mirror userid failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified table subscription mirror userid because the mirror userid is invalid.
User Response: Specify a valid table subscription mirror userid and try again.
DSYM111E | Update table subscription <table subscription name> source password failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified table subscription source password because the source password is invalid.
User Response: Specify a valid table subscription source password and try again.
DSYM112E | Update table subscription <table subscription name> mirror password failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified table subscription mirror password because the mirror password is invalid.
User Response: Specify a valid table subscription mirror password and try again.
DSYM113E | Update table subscription <table subscription name> subtable columns failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified table subscription subtable columns because a column is invalid.
User Response: Specify a valid table subscription subtable column and try again.
DSYM114W | Table subscription <table subscription name> subtable column <subtable column name> no longer defined in the source database. If you continue, your subscription may be modified. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center detected that the specified column was no longer defined on the specified database.
User Response: Verify that the source table and columns are correct and try again.
DSYM115W | More than <maximum tables> available tables were found in the master database <master database name>. Only the first <maximum tables> tables will be displayed. Use the Filter button to limit the available tables result set. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center detected that more than specified maximum available tables at the specified master.
User Response: If the desired table is not listed, use the Filter button to limit the result set.
DSYM116E | Invalid or duplicate custom subscription name <custom subscription name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified custom subscription because the name is invalid or another custom subscription with the same name exists.
User Response: Specify a unique, valid custom subscription name and try again.
DSYM117E | Unable to create custom subscription <custom subscription name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not create the specified custom subscription.
User Response: Correct the error and try again.
DSYM118E | Unable to locate ID for custom subscription <subscription name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not locate the specified custom subscription.
User Response: Correct the error and try again.
DSYM119E | Update custom subscription <custom subscription name> name failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified custom subscription because the name is invalid or it already exists.
User Response: Specify a unique, valid custom subscription name and try again.
DSYM120E | Update custom subscription <custom subscription name> description failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified custom subscription description because the description is invalid.
User Response: Specify a valid custom subscription description and try again.
DSYM121E | Update custom subscription <custom subscription adapter> adapter failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified custom subscription because the adapter is invalid.
User Response: Specify a valid custom subscription adapter and try again.
DSYM122E | Update custom subscription <custom subscription name> other failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified custom subscription other because the other is invalid.
User Response: Specify a valid custom subscription other and try again.
DSYM123E | Unable to associate subscription set with custom subscription <custom subscription name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not associate a subscription set with the specified custom subscription. Possible reason: the subscription set is invalid or does not exist.
User Response: Verify that the subscription set is valid and try again.
DSYM124E | Unable to load adapter <adapter name> customizer <customizer class name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not load the specified adapter customizer. Possible reason: the adapter Communication attributes Command is invalid, the class is not found or is not specified in the CLASSPATH environment variable.
User Response: Verify that the the adapter Communication attributes Command is valid, the command class is found and that it is specified in the CLASSPATH environment variable.
DSYM125E | Unable to load adapter <adapter name> customizer <customizer class name>, exception <exception>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not load the specified adapter customizer. Possible reason: the adapter Communication attributes Command is invalid, the class is not found or is not specified in the CLASSPATH environment variable.
User Response: Verify that the the adapter Communication attributes Command is valid, the command class is found and that it is specified in the CLASSPATH environment variable.
DSYM126E | Update user <user name> device dirty state failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified user device dirty state.
User Response: Correct the error and try again.
DSYM127E | No valid custom adapters found. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not allow the custom subscription action because no custom (non-DSY) adapters were found.
User Response: Define at least one custom adapter and try again.
DSYM128E | Unable to locate a local database which could be used as a mirror database. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not locate any local database(s) which could be used as a mirror database. At least one local database must be defined for use as a mirror database.
User Response: Ensure at least one local database is defined and try again.
DSYM129E | Unable to create table manager control tables for table subscription <table subscription name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not complete the changes to the specified subscription as an exception was encountered during processing.
User Response: Correct the error and try again.
DSYM130I | Unable to update table manager control tables for table subscription <table subscription name>. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not complete the changes to the specified subscription as an exception was encountered during processing.
User Response: No action required.
DSYM131E | Unable to create table manager control tables for table subscription <table subscription name> as no tables were found at the mirror. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not complete the changes to the specified subscription because no tables were found at the mirror.
User Response: Verify that the specific subscription mirror authentication is correct and has the proper authorizations to access the mirror
DSYM132E | The AS/400 source database <database name> is not supported for JDBC table subscriptions. |
Explanation: The specified database name is not supported by the DB2 Everyplace Sync Server for synchronization using a JDBC table subscription. DB2/400 V5R1 or later is required for Sync Server support for a AS/400 source database.
User Response: Use DB2/400 V5R1 or later for JDBC table subscription support. If using an earlier version of DB2/400, refer to the subscription type DataPropragator table subscription.
DSYM133E | Unable to complete custom subscription <subscription name> as the custom adapter reported a failure while processing the save request. Action canceled. |
Explanation: The custom adapter failed reported that the request to save failed.
User Response: Refer to the documentation for the custom adapter.
DSYM134E | Update adapter <adapter name> class name failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified adapter class name because the class name is invalid.
User Response: Specify a valid adapter class name and try again.
DSYM135E | Duplicate source and mirror database <database name> found. |
Explanation: The table subscription is attempting to use the specified database as both the source and the mirror. The source and mirror database must be different.
User Response: Specify a different source and mirror database name and try again.
DSYM136E | Update subscription <subscription name> encryption level failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified subscription because the encryption level is invalid.
User Response: Specify a valid encryption level and try again.
DSYM137E | Table <table name> does not contain at least one primary key. Action canceled. |
Explanation: No primary key was found the specified table. A table must have at least one primary key defined in order to be used as a table subscription.
User Response: Select a table with at least one primary key and try again.
DSYM138E | Update table subscription <table subscription name> subcolumns failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified table subscription subcolumns because a subcolumn is invalid.
User Response: Specify a valid table subscription subcolumn and try again.
DSYM139E | Duplicate target table index names for table subscriptions assigned to subscription set <subscription set name>. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center detected duplicate target table index names for two or more table subscriptions assigned to the specified subscription set. The target table index names of table subscriptions assigned to a subscription set must be unique.
User Response: Ensure that the table subscriptions assigned to the specified subscription set use unique target table index names and try again.
DSYM140E | Update subscription <subscription name> table index name <table index name> failed. Action canceled. |
Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified subscription table index name as the specified table index name is invalid. Table index names must be unique across a Sync Server instance.
User Response: Specify unique table index name and try again.
DSYP003E | Could not access the Lotus Notes database <database>. |
Explanation: The Notes database <database> may be locked by another application.
User Response: Try again later and make sure that your Notes client is closed. If the problem persists, consult the DB2 PIM replication documentation or contact IBM software support.
DSYS000I | Complete synchronization request received; synchronization started for user <user name>, session <session number>. |
Explanation: A complete synchronization request has been received from the specified user as the last message has been received. The DB2 Everyplace Sync Server will now begin the synchronization process.
User Response: No action required.
DSYS001I | Synchronization ended for user <user name>, session <session number>. |
Explanation: The synchronization process for the specified user has ended.
User Response: No action required.
DSYS002E | Synchronization failed for user <user name>, session <session number>: <reason>. |
Explanation: The synchronization process for the specified user has failed.
User Response: Contact your administrator.
DSYS003I | Replication started for database <source database name>. |
Explanation: The replication process as begun for the specified database.
User Response: No action required.
DSYS004I | Replication ended for database <source database name>. |
Explanation: The replication process as ended for the specified database.
User Response: No action required.
DSYS005E | Replication failed for database <source database name>: <reason>. |
Explanation: The replication process for the specified database failed.
User Response: Contact your administrator.
DSYS006I | Receiving synchronization request from user <user name>, session <session number>. |
Explanation: The specified user initiated the synchronization process as the first message has been received by the DB2 Everyplace Sync Server.
User Response: No action required.
DSYT000E | Invalid group name <group name>. |
Explanation: The specified group name is invalid or does not exist.
User Response: Specify a valid group name and try again.
DSYT001W | Line: <line number> - invalid user name. |
Explanation: The ImportUsers tool did not process the specified line as the user name was invalid.
User Response: Correct the error and try again.
DSYT002I | Line: <line number> - insert user <user name> successful. |
Explanation: The ImportUsers tool successfully inserted the specified user.
User Response: No action required.
DSYT003W | Line: <line number> - insert user <user name> failed. |
Explanation: The ImportUsers tool failed to insert the specified user.
User Response: Correct the error and try again.
DSYT004W | Line: <line number> - insert user <user name> failed, exception <exception text>. |
Explanation: The ImportUsers tool failed to insert the specified user due to the specified exception.
User Response: Correct the error and try again.
DSYT005E | Errors occurred - performing rollback. |
Explanation: The ImportUsers tool encountered one or more errors and is performing a rollback.
User Response: Correct the error and try again.
DSYT006I | com.ibm.mobileservices.admin.tools.ImportUsers <filename> |
Explanation: The ImportUsers tool has been invoked against the specified filename.
User Response: No action required.
DSYT007I | com.ibm.mobileservices.admin.tools.ImportUsers {-commit}{-exception}{-fail}{-group [name]} filename\n where\n {-commit}: commit each successful insert and do not rollback if an error occurs\n {-exception}: display exceptions\n {-fail}: display failed only\n {-group [name]}: group {name} to assign users to\n filename: the comma-deliminated file containing the user(s) to import. File format is: user name,{user password},{user description} |
Explanation: Displays parameters for invoking the ImportUsers tool.
User Response: No action required.
DSYT008I | Users inserted: <insert count>; failed: <failed count>. |
Explanation: The ImportUsers tool is complete and reported the specified successful user insert count and failed count.
User Response: No action required.
DSYT009I | DSYCTLDBMigration process started. |
Explanation: The DSYCTLDBMigration tool process to migrate older versions of the DB2 Everyplace Sync Server control database DSYCTLDB to the latest version has started.
User Response: No action required.
DSYT010I | DSYCTLDBMigration is migrating to version <version.release.modification>. |
Explanation: The DSYCTLDBMigration tool is migrating the DB2 Everyplace Sync Server control database DSYCTLDB to the specified version.
User Response: No action required.
DSYT011I | DSYCTLDBMigration process complete. |
Explanation: The DSYCTLDBMigration tool process to migrating older versions of the DB2 Everyplace Sync Server control database DSYCTLDB to the latest version is complete.
User Response: No action required.