Error messages

This topic lists the error messages and their meanings, and it provides suggested actions to correct the problem identified in the message. Use this appendix with Handling synchronization problems to identify and correct problems.

Explanation: The DB2 Everyplace control database could not assign the device to the specified user as the device is currently assigned to the specified registered user.

User Response: If the device should be registered to the specified user, use the DB2 Everyplace Mobile Devices Administration Center to reset registered user of the device and try again.

Explanation: Some of the data changes that the Sync Client requested have been rejected due to data conflicts or no permission.

User Response: Check with the Sync Server administrator to ensure that the user has permission to perform the desired operation. Since the requested changes have been rejected, the user has to reapply the changes, or have the Sync Server administrator reset the user and try again. If problems persist, contact IBM software support.

Explanation: The Sync Client could not open the adapter library after use.

User Response: Check that the library '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.

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.

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.

Explanation: The Sync Client did not properly synchronize the configuration information.

User Response: Have the Sync Server Administrator reset the user, and try again. If problems persist, contact IBM software support.

Explanation: The provided username/password does not 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.

Explanation: The Sync Server could not successfully recognize and encrypt/decrypt the message from the client.

User Response: Make sure that encryption is supported on the Sync Client platform, do a soft reset on the device and try again. If problems persist, contact the Sync Server administrator.

Explanation: The Sync Client could not successfully encrypt/decrypt the received message.

User Response: Make sure that encryption is supported on the client's operating system, do a soft reset on the device and try again. If problems persist, contact IBM software support.

Explanation: Encryption is not supported for Palm OS 3.2 and earlier. The encryption library is not installed or the path is not set correctly.

User Response: Make sure that the client's operating system supports the encryption, the encryption library is properly installed, and the path is set correctly. If problems persist, contact the Sync Server administrator.

Explanation: Encryption is not supported for Palm OS 3.2 and earlier. The path for encryption is not set correctly.

User Response: Make sure that the operating system supports the encryption, the path for encryption is set correctly. If problems persist, contact the Sync Server administrator.

Explanation: The version for the Sync Client is not compatible with the Sync Server.

User Response: Upgrade the Sync Client to the latest version, and try again. If problems persist, contact the Sync Server administrator.

Explanation: The Sync Server cannot find the subscription that the client is requesting. It may be because the configuration has changed since the client starts synchronization.

User Response: Try to sync again, or have the Sync Server administrator reset the user and sync again. If problems persist, contact the Sync Server administrator.

Explanation: The subscription has been blocked by the Sync Server because the Sync Server administrator is performing maintenance on the control database or modifying the configuration.

User Response: Please wait and try to sync again. If problems persist, contact the Sync Server administrator.

Explanation: The synchronization session of the client and the one persisting on the Sync Server do not match. The client configuration may be corrupted or overwritten.

User Response: Have the Sync Server administrator reset the user. Try to sync again. If problems persist, contact the Sync Server administrator.

Explanation: The user has not been added to any group with synchronization privilege.

User Response: Check that the username is entered correctly and have the Sync Server administrator verify that the user has been added to a synchronization-enabled group. Try to sync again. If problems persist, contact the Sync Server administrator.

Explanation: The Sync Server cannot register the device. The Sync Client has changed its user information, and therefore, no longer matches the registered user information on the Sync Server.

User Response: Check that the username is entered correctly and have the Sync Server administrator reset the user. Try to sync again. If problems persist, contact the Sync Server administrator.

Explanation: The definition of a subscription has changed since the last time the client was configured. The Sync Server administrator is modifying the configuration.

User Response: Wait for a while and try to sync again. If problems persist, contact the Sync Server administrator.

Explanation: The Sync Client could not allocate adapter-specific resources (for example, database connections, or statement handles) for synchronizing the subscribed data.

User Response: Check that the required adapter-specific resources are not occupied and try again. If problems persist, consult the DB2 Everyplace Application Development Guide or contact IBM software support.

Explanation: The Sync Client detected problems when connecting to or accessing the target data.

User Response: Check the access rights and existence of the resource or make sure the resource is not being used by another application. If synchronizing encrypted tables, make sure the provided DB2 Everyplace username and password have been granted the encryption privilege. Have the Sync Server administrator reset the user and try again. If problems persist, contact IBM software support.

Explanation: The Sync Client detected problems disconnecting or releasing the target data.

User Response: Check the access rights and existence of the resource or make sure the resource 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.

Explanation: The Sync Client received unexpected empty or missing subscription information (for example, no subscribed table information) from the server.

User Response: There may be missing information in the subscription. Contact the Sync Server administrator.

Explanation: The Sync Client does not recognize some message information from the server during synchronization of a subscription.

User Response: Have the Sync Server administrator reset the user and try again. If problems persist, contact IBM software support.

Explanation: The Sync Client cannot find the target data (for example, table not found) for synchronization.

User Response: The target data may have been deleted by another application. Have the Sync Server administrator reset the user and try again. If problems persist, contact IBM software support.

Explanation: The Sync Client has encountered unexpected missing or end-of-data during synchronization of a subscription.

User Response: Have the Sync Server administrator reset the user and try again. If problems persist, contact IBM software support.

Explanation: The Sync Client received data that was too large (for example, over-sized file). Data may have been truncated.

User Response: The data from the Sync Server may be invalid. Check with the Sync Server administrator.

Explanation: The Sync Server administrator has not enabled the user to synchronize.

User Response: Make sure that the username is entered correctly, and have the Sync Server administrator enable the user, and try again. If problems persist, contact the Sync Server administrator.

Explanation: The Sync Server could not synchronize this user due to an unexpected error.

User Response: Contact the Sync Server administrator.

Explanation: The subscription adapter attempts to modify the target data which is read-only.

User Response: Check that the user has write capability on the target data, and try to sync again. If problems persist, contact the Sync Server administrator.

Explanation: The subscription adapter detected problems performing operations on the target data.

User Response: Check with the administrator and make sure the user has permission to perform the operations. Have the Sync Server administrator reset the user and try again. If problems persist, contact IBM software support.

Explanation: The user is not authorized to access the requested data.

User Response: Check that the username and password are entered correctly, and that the user is authorized to access the requested data. Have the Sync Server administrator reset the user and try again. If problems persist, contact the Sync Server administrator.

Explanation: The requested data is not available. The target data is being used by another application.

User Response: Check that the Sync Client has permission to modify the target data, and that 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.

Explanation: The subscription adapter does not support the requested data type. For example, you can only synchronize .prc and .pdb files to a Palm device and there are some columns types which are not supported by DB2 Everyplace.

User Response: Have the Sync Server administrator verify that all the subscribed data are supported (for example, file type and column types), and try to sync again. If problems persist, contact IBM software support.

Explanation: The user-provided subscription target path is either not a valid path name, or the path is not relative to the device target path.

User Response: Make sure the specified subscription target path is a valid path name and relative to the device target directory.

Explanation: The Sync Client has a problem opening a connection with the Sync Server because either you have a wrong server URL (Uniform Resource Locator), or the server is not up.

User Response: Check to ensure: 1) Server URL is correctly entered 2) The Sync Server is currently operational. Click on "Retry". If problems persist, contact IBM software support.

Explanation: The Sync Client has a problem opening connection with the Sync Server. This could be due to: 1) Wrong server URL (Uniform Resource Locator) 2) Server is not up 3) Network is busy 4) Network connection is not operational.

User Response: Check to ensure: 1) Server URL is correctly entered 2) The Sync Client has access to the Sync Server through either a serial or USB cable, a modem, or a network connection. 3) The Sync Server is currently operational. 4) If using Windows RAS, or some PPP connection software (for example, Mocha PPP for the serial port, Softick PPP for the USB port), make sure the PPP connection between the mobile device and the desktop computer is established. 5) Try to synchronize again. If problems persist, contact IBM software support.

Explanation: The Sync Client has successfully connected to the Sync Server, but has a problem sending a request to the server. This could be due to the following: 1) Server is not up 2) Network connection is lost.

User Response: Check to ensure: 1) The Sync Client has access to the Sync Server through either a serial or USB cable, a modem, or a network connection. 2) The Sync Server is currently operational. 3) If using Windows RAS, or some PPP connection software (for example, Mocha PPP for the serial port, Softick PPP for the USB port), make sure the PPP connection between the mobile device and the desktop computer is established. 4) Try to synchronize again. If problems persist, contact IBM software support.

Explanation: The Sync Client has successfully sent a request to the Sync Server, but has a problem receiving a reply from the server, or the received message is corrupted or in an unexpected format. This could be due to the following: 1) Server is not up 2) Network connection is lost.

User Response: Check to ensure: 1) The Sync Server is currently operational. 2) If using Windows RAS, or some PPP connection software (for example, Mocha PPP for the serial port, Softick PPP for the USB port), make sure the PPP connection between the mobile device and the desktop computer is established. 3) Try to synchronize again. If problems persist, contact IBM software support.

Explanation: The Sync Client has successfully connected sent a request to the Sync Server, but has not received a reply from the server before timeout. Either the server needs more time preparing the acquired information, the network is busy, the server is not up, or the network connection is lost.

User Response: Check to ensure: 1) The Sync Server is currently operational. 2) If using Windows RAS, or some PPP connection software (for example, Mocha PPP for the serial port, Softick PPP for the USB port), make sure the PPP connection between the mobile device and the desktop computer is established. 3) Try to synchronize again. If problems persist, contact IBM software support.

Explanation: The Sync Client has successfully sent a request and received a reply from the Sync Server, but does has not received an acknowledgement from the server. Either the server needs more time preparing the inquired information, the network is busy, the server is not up, or the network connection is lost.

User Response: Check to ensure: 1) The Sync Server is currently operational. 2) If using Windows RAS, or some PPP connection software (for example, Mocha PPP for the serial port, Softick PPP for the USB port), make sure the PPP connection between the mobile device and the desktop computer is established. 3) Try to synchronize again. If problems persist, contact IBM software support.

Explanation: The Sync Client has a problem opening the Network library.

User Response: Check to ensure: 1) The Network library is present. 2) If using the PalmOS emulator, make sure the check box under Settings->Properties is set (checked). 3) Try a soft reset on the device, and synchronize again. If problems persist, contact IBM software support.

Explanation: The Sync Client has a problem closing the Network library.

User Response: Try a soft reset on the device, and synchronize again. If problems persist, contact IBM software support.

Explanation: The Sync Client cannot resolve the IP for the provided hostname in the server URL (Uniform Resource Locator).

User Response: Make sure the server hostname is correctly specified.

Explanation: The Sync Client could not allocate sufficient memory for completing synchronization.

User Response: The device could be low on available memory or the dynamic heap memory. Close out or delete some unused applications, and try again. If problems persist, consult the DB2 Everyplace documentation for system requirements or contact IBM software support.

Explanation: The user is not allowed to synchronize to the server.

User Response: Check that the user is authorized to synchronize to the Sync Server. Try to synchronize again. If problems persist, contact the Sync Server administrator.

Explanation: The server cannot be found because either a wrong server URL (Uniform Resource Locator) is being used, the server is not up, or the Sync Server is not installed properly.

User Response: Check to ensure: 1) Server URL (Uniform Resource Locator) is correctly entered; 2) The Sync Server is currently operational; 3) The Sync Server is installed properly. Try to sync again. If problems persist, contact the Sync Server administrator.

Explanation: An internal error has occurred on the Sync Server.

User Response: Restart the Sync Server and try to synchronize again. If problems persist, contact IBM software support.

Explanation: Servers are not responding to the client requests. All servers are not available (either busy or blocked).

User Response: Check with the Sync Server administrator that the Sync Server is available. Try to synchronize again. If problems persist, contact IBM software support.

Explanation: The transport protocol specified in the server URL (Uniform Resource Locator) is not supported.

User Response: Make sure the protocol specified in the server URL is supported. Currently, the only supported protocol is HTTP (HyperText Transfer Protocol). Use HTTPS if both Sync Server and Sync Client have been configured for SSL (Secure Socket Layer).

Explanation: The subscription adapter encountered errors or inconsistent state from the DB2 Everyplace database engine when synchronizing the subscribed data.

User Response: Check the Sync Client configuration log, and identify the subscription type (config, table, or file). If applicable, consult the DB2 Everyplace Application Development Guide with the provided SQL state in the error message. Have the Sync Server administrator reset the user and try again. If problems persist, contact IBM software support.

Explanation: The Sync Client has encountered an unknown error while communicating with the Sync Server.

User Response: Contact IBM technical support.

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 the storage is not exhausted. If no problems are found, contact IBM Software Support.

Explanation: The DB2 Everyplace Sync Server creates a pool of database connections for each database accessed. In this case, the Sync Server attempted to use a connection from this pool for the named database failed. A possible explanation for this error is 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.

Explanation: Each time you start the DB2 Everyplace Sync Server, a password file is generated for each Apply qualifier. The 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 fails because of inadequate storage in the directory where the Sync Server is running.

User Response: First, 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.

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. Inadequate storage or a non-functional database causes the creation of these tables to fail.

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.

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.

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.

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.

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. In addition, see the DB2 UDB Replication Guide and Reference for more information on why the Apply Trail table could not be accessed. If problems persist, contact IBM Software Support.

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 more information on why the unit-of-work table could not be accessed. If problems persist, contact IBM Software Support.

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 is properly set up in the Mobile Devices Administration Center. If problems persist, contact IBM Software Support.

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.

Explanation: The synchronization element for the relational database row specified was not accepted for synchronization for the reason given.

User Response: No action required.

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 the Mobile Devices Administration Center. If problems persist, contact IBM Software Support.

Explanation: com.ibm.mobileservices.adapter.rdb.Replicate was not executed with one command-line argument.

User Response: Run com.ibm.mobileservices.adapter.rdb.Replicate with a mirror database name as the command-line argument.

Explanation: A request to initiate replication on the mirror database was successfully communicated.

User Response: No action is required.

Explanation: The filter makes reference to a table that does not exist in the mirror database.

User Response: Correct the filter in the Mobile Device Administration Center to make it refer to only those tables that are replicated to the mirror database by deleting the subscription and creating a new one with the correct filter.

Explanation: The DB2 adapter received a request for an invalid subscription from the specified user and device. The specified subscription ID no longer exists.

User Response: Reset the users device and try again.

Explanation: The Sync Server cannot ensure that it is safe to perform the replication because it cannot communicate with some synchronization-enabled servers.

User Response: Check the log folder of the Mobile Device Administration Center. Look for DSYD038E to find out which server is unreachable. If the unreachable server is down, mark it as offline. If the server is up, stop it and restart it.

Explanation: No table subscription is defined for the specified mirror database.

User Response: Create a table subscription using the specified mirror database name before requesting replication.

Explanation: The server is either down, unreachable, or there are unknown communication problems.

User Response: Check that the server is up and reachable on the network.

Explanation: A required default value is undefined for an unsubscribed column.

User Response: Ensure that the parameters of vertical filtering are defined and spelled correctly. Make corrections in the Subscription, Group, and/or User folders in the Mobile Device Administration Center.

Explanation: The infrastructure that supports the replication of JDBC subscriptions is not at the level required by this installation of Sync Server.

User Response: Run the migration utility that came with this installation of Sync Server. The utility migrates JDBC subscriptions from previous versions of Sync Server to the version of Sync Server installed.

Explanation: The MDSS Servlet encountered an exception.

User Response: Gather trace and log files, and contact IBM Software Support for the specific adapter.

Explanation: DB2 Everyplace Sync Server encountered the specified unexpected exception.

User Response: Report the error to your administrator.

Explanation: A connection to the specified database could not be established.

User Response: Verify that the database name, driver, user ID and password is valid and that it is operational.

Explanation: A connection to the specified database was successfully established.

User Response: No action required.

Explanation: A valid license must be installed for this product.

User Response: Please contact IBM for information on purchasing this product.

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.

Explanation: The DB2 Everyplace Sync Server was unable to open the log file because the specified exception was encountered.

User Response: Verify that the DSYGdflt.properties file, Trace.Path variable specifies a valid path and that the current user has the necessary create/read/write permissions.

Explanation: The DB2 Everyplace Sync Server was unable to write to the specified log file because the specified exception was encountered.

User Response: Verify that the DSYGdflt.properties file, Trace.Path variable specifies a valid path and that the current user has the necessary create/read/write permissions.

Explanation: This sync server requires that the installation be at the same level as the DSYCTLDB control database.

User Response: If you are upgrading or installing a new sync server, the DSYCTLDB control database needs to be installed or upgraded to the same level using the install package. If the DSYCTLDB database has been upgraded, then this sync server installation needs to be upgraded to the same level. If neither of these actions applies, or is unsuccessful in resolving the problem, please contact IBM Software Support.

Explanation: The specified file could not be read because the file does not exist or the permissions prohibit this action.

User Response: Verify that the specified file exists and that it is accessible.

Explanation: A class designated by the DB2 Everyplace Administrator to be an implementation of a CustomLogicPolicy could not be loaded.

User Response: Ensure that the specified CustomLogicPolicy subclass is accessible by all Sync Server instances, by any standalone dsyreplicate process, and by the Mobile Devices Administration Center and XML Scripting Tool. If this is unsuccessful in resolving the problem, please contact IBM Software Support.

Explanation: Requesting the servers to stop servicing synchronization and replication requests for this mirror database.

User Response: No action required.

Explanation: Applying the requested changes in the control database.

User Response: No action required.

Explanation: Requesting the servers to continue servicing synchronization and replication requests for this mirror database.

User Response: No action required.

Explanation: Subscription was not fully initialized earlier and editing at this time is not possible since subscription details are not known.

User Response: Make sure that source and if required mirror databases are accessible and their contents are valid. If there is connection problem, check to make sure URL is correct and drivers are on CLASSPATH. The subscription relies on information in the source and the mirror to fully define itself. When source and/or mirror database is down, actions that can be applied to the subscription are limited.

Explanation: Replicating the mirror database to bring it in sync with the source.

User Response: No action required.

Explanation: No changes will be made in the control database for this operation.

User Response: No action required.

Explanation: This is a progress message.

User Response: No action required.

Explanation: This is a progress message.

User Response: No action required.

Explanation: This is a progress message.

User Response: No action required.

Explanation: This is a progress message.

User Response: No action required.

Explanation: This is a progress message.

User Response: No action required.

Explanation: This is a progress message.

User Response: No action required.

Explanation: This is a progress message.

User Response: No action required.

Explanation: To be able to retrieve subscription details, access to the specified database is required but the database is either down or there is another connection problem.

User Response: Make sure the specified database is up and running and configured properly. Make sure JDBC URL is correct and JDBC drivers are on Java CLASSPATH.

Explanation: Subscription uses a table that does not exist in the database or the database was not accessible at the time of this error and list of tables could not be retrieved.

User Response: Make sure the specified table exists in the database and verify that the specified database is up and running and configured properly for JDBC access.

Explanation: Details of the subscription's tables were not retrieved due to an error. Actual cause is likely to be a source or a mirror database being down, or a bad database URL or a missing JDBC driver on CLASSPATH.

User Response: Verify that the source and mirror databases are up and running and configured properly for JDBC access. Make sure that the tables which the subscription references still exist.

Explanation: In a Put subscription, only insertion is allowed. Deletion and update are rejected.

User Response: No action is required.

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.

Explanation: The MDSS is unable to determine which database the specified JDBC driver name is using.

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.

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.' Rerun the script to create the control database (such as dsyctldb.bat).

Explanation: The DB2 Everyplace Mobile Devices Administration Center could not locate the specified subscription set.

User Response: Correct the error and try again.

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.

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.

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.

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.

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.

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.

Explanation: The DB2 Everyplace Mobile Devices Administration Center could not locate the specified user.

User Response: Correct the error and try again.

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.

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.

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.

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.

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.

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.

Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified user data filters. Possible reasons: the group level data filter is invalid or does not exist or the user data filter value is invalid.

User Response: Correct the error and try again.

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.

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.

Explanation: The DB2 Everyplace Mobile Devices Administration Center could not locate the specified group.

User Response: Correct the error and try again.

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.

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.

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.

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.

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.

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.

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.

Explanation: The DB2 Everyplace Mobile Devices Administration Center could not locate the specified subscription.

User Response: Correct the error and try again.

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.

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.

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.

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.

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.

Explanation: The DB2 Everyplace Mobile Devices Administration Center could not locate the associated DataPropagator subscription.

User Response: Correct the error and try again.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Explanation: The DB2 Everyplace Mobile Devices Administration Center could not complete the changes to the specified subscription due to an exception.

User Response: Correct the error and try again.

Explanation: The DB2 Everyplace Mobile Devices Administration Center could not complete the changes to the specified subscription due to an exception.

User Response: No action required.

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.

Explanation: The DB2 Everyplace Mobile Devices Administration Center encountered the specified exception. The exception may include additional information that may be used to identify the cause of the error and corrective steps.

User Response: Attempt to correct the error specified in the exception. If unable to do so, close the DB2 Everyplace Mobile Devices Administration Center and try again. If the error persists, contact the database administrator.

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.

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.

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.

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.

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.

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.

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.

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

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.

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 attempt to remove any DSY default adapter.

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.

Explanation: The DB2 Everyplace Mobile Devices Administration Center could not locate the specified adapter.

User Response: Correct the error and try again.

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.

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.

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.

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.

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.

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 exists and is valid and try again.

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 exists and is valid and try again.

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.

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

Explanation: A connection to the specified database could not be established.

User Response: Verify that the database name, driver, user ID and/or password is valid and that it is operational.

Explanation: The DB2 Everyplace Mobile Devices Administration Center detected that more than the 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.

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.

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 adapter communication attributes command is valid and verify that the command class exists and that it is specified in the CLASSPATH environment variable.

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 adapter communication attributes command is valid and verify that the command class exists and that it is specified in the CLASSPATH environment variable.

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.

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.

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.

Explanation: The custom adapter reported that the request to save failed.

User Response: Refer to the documentation for the custom adapter.

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.

Explanation: The table subscription is attempting to use the specified database as both the source and the mirror. The source and mirror databases must be different.

User Response: Specify a different source and mirror database name and try again.

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.

Explanation: No primary key was found in 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 a primary key and try again.

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.

Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified subscription because the name is invalid or another subscription with the same name exists.

User Response: Specify a unique, valid subscription name and try again.

Explanation: The DB2 Everyplace Mobile Devices Administration Center could not create the specified subscription.

User Response: Correct the error and try again.

Explanation: The DB2 Everyplace Mobile Devices Administration Center could not locate the specified subscription.

User Response: Correct the error and try again.

Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified subscription because the name is invalid or it already exists.

User Response: Specify a unique, valid subscription name and try again.

Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified subscription description because the description is invalid.

User Response: Specify a valid subscription description and try again.

Explanation: The DB2 Everyplace Mobile Devices Administration Center could not update the specified subscription because the adapter is invalid.

User Response: Specify a valid subscription adapter and try again.

Explanation: The DB2 Everyplace Mobile Devices Administration Center automatically removed one or more user defined indexes as they were duplicates of primary key indexes.

User Response: No action required.

Explanation: The DB2 Everyplace Mobile Devices Administration Center automatically removed one or more imported indexes as they were duplicates of primary key indexes.

User Response: No action required.

Explanation: The define subscription button has been disabled because a connection to the specified database could not be established. Typically, this is the result of the password being changed.

User Response: Verify that the database name, driver, user ID and or password is valid and that it is operational by using the test connection button and apply any changes by clicking the OK button. Once the changes are applied, try again.

Explanation: The DB2 Everyplace Mobile Devices Administration Center detected that the specified mirror was already in use by another subscription. Source databases may not share the same mirror database.

User Response: Change the mirror database name and try again.

Explanation: The DB2 Everyplace Mobile Devices Administration Center could not determine which DB2 Everyplace devices were installed. One or more DB2 Everyplace device types must be installed in order to create or modify a subscription of this type.

User Response: Check your DSYIdflt.properties file and ensure that you have a DB2e.InstalledDeviceTypes entry or rerun the DB2 Everyplace installation program.

Explanation: One or more Sync Server servers were unable to block the specified subscription. A subscription must be blocked on all alive servers in order to process the edit request.

User Response: The administrator should perform the following steps to ensure that the attempted action will succeed. 1. Ensure that all servers (or the server in a single server environment) are not currently running. 2. Ensure that in the MDAC Server view, all entries on the right pane show that each server is marked as offline. If they are not, right-click on each server and select "Mark as offline". 3. If the servlet engine listens for http requests on a port other than 8080, be sure that the property Server.Port is set to the corresponding value in the DSYGdflt.properties file. After adding this value, delete the server in the MDAC Server view if there is an entry with an incorrect value. Be aware that this port must be accessible from any machine that is running MDAC or MDAC scripting. 4. If more than one server is running on this machine be sure that Server.Name is defined to something unique in the DSYGdflt.properties file. After defining this value, delete the server in the MDAC Server view if there is an entry with an incorrect value. 5. If there is more than one IP address that the server is on, ensure that the one the servlet engine is listening on is defined in DSYGdflt.properties by the Server.IP variable. Again, delete any entries in the MDAC Server view if they contain an incorrect value. 6. To prevent the error in the future, be sure that all servers are shut down by a supported shutdown method, as opposed to killing the process or JVM. In the case of a failure that prevents proper shutdown, open MDAC and mark the servers that are no longer running as offline as describe above. After verifying all of the above, the server may be restarted and/or the action may be attempted again.

Explanation: Unable to connect to the specified LDAP server using the specified user name and password.

User Response: Specify a valid user name and/or password and try again or modify the DSYLDAP.properties to change the LDAP default connection information.

Explanation: Unable to determine the LDAP server to connect to as no WEBSERVICE_SOAP_ROUTER was specified in the file com/ibm/mobileservices/DSYLDAP.properties.

User Response: Specify a valid WEBSERIVCE_SOAP_ROUTER in the com/ibm/mobileservices/DSYLDAP.properties file and try again.

Explanation: No groups matching DB2e* were found at the specified LDAP server.

User Response: Define at least one DB2* group.

Explanation: No users were found in the specified sync group.

User Response: Specify a sync group containing one or more users and try again.

Explanation: The DB2 Everyplace Mobile Devices Administration Center has detected that you have requested that the table be encrypted, but one or more DB2 Everyplace installed device types do not support encryption. Thus, table data on these unsupported encryption devices will not be encrypted.

User Response: No action required.

Explanation: DB2 Everyplace requires primary key column length may not exceed 255 characters. DB2 Everyplace requires that the total length of all primary key columns may not exceed 1024 characters.

User Response: Select a valid table and try again.

Explanation: One or more Sync Server servers were not offline. All sync servers must be marked as offline to create a DataPropagator subscription.

User Response: Mark all servers as offline and try again.

Explanation: One or more Sync Server servers were not offline. All sync servers must be marked as offline to edit a DataPropagator subscription.

User Response: Mark all servers as offline and try again.

Explanation: The DB2 Everyplace Mobile Devices Administration Center detected a syntax error in the source to mirror (all rows needed) where clause in the specified table.

User Response: Validate the source to mirror (all rows needed) where clause for the specified table and try again.

Explanation: The specified users' device was reset.

User Response: No action required.

Explanation: The DB2 Everyplace Mobile Devices Administration Center can not update the specified subscription custom logic policy as the specified policy is invalid.

User Response: Specify a valid policy type and try again.

Explanation: The DB2 Everyplace Mobile Devices Administration Center could not add the specified table as one or more column name lengths exceeded the specified maximum column name length.

User Response: Specify a table with valid column name lengths and try again.

Explanation: DB2 Everyplace Mobile Devices Administration Center could not communicate with one or more servers and did not perform replication on the specified mirror database for the specified exception. To prevent loss of data, the edit request was canceled.

User Response: The administrator should perform the following steps to ensure that the attempted action will succeed. 1. Ensure that all servers (or the server in a single server environment) are not currently running. 2. Ensure that in the MDAC Server view, all entries on the right pane show that each server is marked as offline. If they are not, right-click on each server and select "Mark as offline". 3. If the servlet engine listens for http requests on a port other than 8080, be sure that the property Server.Port is set to the corresponding value in the DSYGdflt.properties file. After adding this value, delete the server in the MDAC Server view if there is an entry with an incorrect value. Be aware that this port must be accessible from any machine that is running MDAC or MDAC scripting. 4. If more than one server is running on this machine be sure that Server.Name is defined to something unique in the DSYGdflt.properties file. After defining this value, delete the server in the MDAC Server view if there is an entry with an incorrect value. 5. If there is more than one IP address that the server is on, ensure that the one the servlet engine is listening on is defined in DSYGdflt.properties by the Server.IP variable. Again, delete any entries in the MDAC Server view if they contain an incorrect value. 6. To prevent the error in the future, be sure that all servers are shut down by a supported shutdown method, as opposed to killing the process or JVM. In the case of a failure that prevents proper shutdown, open MDAC and mark the servers that are no longer running as offline as describe above. After verifying all of the above, the server may be restarted and/or the action may be attempted again.

Explanation: DB2 Everyplace Mobile Devices Administration Center could not delete the specified subscription due to internal validations failing. To prevent loss of data, the delete request was canceled.

User Response: The administrator should perform the following steps to ensure that the attempted action will succeed. 1. Ensure that all servers (or the server in a single server environment) are not currently running. 2. Ensure that in the MDAC Server view, all entries on the right pane show that each server is marked as offline. If they are not, right-click on each server and select "Mark as offline". 3. To prevent the error in the future, be sure that all servers are shut down by a supported shutdown method, as opposed to killing the process or JVM. In the case of a failure that prevents proper shutdown, open MDAC and mark the servers that are no longer running as offline as describe above. After verifying all of the above, the server may be restarted and/or the action may be attempted again.

Explanation: DB2 Everyplace Mobile Devices Administration Center could not delete the specified subscription due to internal cleanup failing. To prevent loss of data, the delete request was halted.

User Response: The administrator should perform the following steps to ensure that the attempted action will succeed. 1. Ensure that all servers (or the server in a single server environment) are not currently running. 2. Ensure that in the MDAC Server view, all entries on the right pane show that each server is marked as offline. If they are not, right-click on each server and select "Mark as offline". 3. To prevent the error in the future, be sure that all servers are shut down by a supported shutdown method, as opposed to killing the process or JVM. In the case of a failure that prevents proper shutdown, open MDAC and mark the servers that are no longer running as offline as describe above. After verifying all of the above, the server may be restarted and/or the action may be attempted again.

Explanation: The DB2 Everyplace Mobile Devices Administration Center detected that the specified target table name was already used by another table subscription for the specified mirror. The target table names within a mirror must be unique.

User Response: Specify a unique target table name and try again.

Explanation: The DB2 Everyplace Mobile Devices Administration Center detected that the specified target table contained a Join Filter that is unsupported for the specified reason.

User Response: Correct the filter for the table and try again.

Explanation: The DB2 Everyplace Mobile Devices Administration Center could not locate any local database(s) which could be used as a source database. At least one local database must be defined for use as a source database.

User Response: Ensure at least one local database is defined and try again.

Explanation: The DB2 Everyplace Mobile Devices Administration Center detected that DB2 UDB v8.1 is installed. Since DB2 Everyplace Sync Server does not fully support UDB v8.1 yet, Control Center specific objects will be hidden or disabled and DPROPR functionality will be disabled in the DB2 Everyplace Mobile Device Administration Center. To administrate DPROPR, use the Replication Center and the DB2 Everyplace XML Scripting tool.

User Response: To administrate your DB2 UDB installation, use the Control Center. To administrate DPROPR, use the Replication Center and the DB2 Everyplace XML Scripting tool.

Explanation: The DB2 Everyplace Mobile Device Administration Center was unable to retrieve a list of tables from the specified source database due to the unexpected specified exception.

User Response: Correct the exception and try again.

Explanation: The DB2 Everyplace Mobile Devices Administration Center detected that the specified source table contained one or more columns that are not supported and are nullable with no default value specified. The table cannot be used in a table subscription.

User Response: Specify a table that does not contain unsupported data types and are not nullable with no default value specified.

Explanation: The DB2 Everyplace Mobile Devices Administration Center detected that the specified subscription could not be unblocked until a replication of the specified mirror database has been completed.

User Response: Perform a replication and try again.

Explanation: The DB2 Everyplace Mobile Devices Administration Center detected that the specified target table contained a Join Filter that is unsupported for the specified reason. Changes to the subscription were committed.

User Response: Correct the filter for the table and try again.

Explanation: The specified target table name is invalid. Target table names may be a maximum of 18 characters in length.

User Response: Specify a valid target table name and try again.

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.

Explanation: The synchronization process for the specified user has ended.

User Response: No action required.

Explanation: The synchronization process for the specified user has failed.

User Response: Contact your Sync Server administrator.

Explanation: The replication process has begun for the specified database.

User Response: No action required.

Explanation: The replication process has ended for the specified database.

User Response: No action required.

Explanation: The replication process for the specified database failed.

User Response: Contact your Sync Server administrator.

Explanation: The specified user initiated the synchronization process and the first message has been received by the DB2 Everyplace Sync Server.

User Response: No action required.

Explanation: Synchronization was restarted for the specified user by the DB2 Everyplace Sync Server.

User Response: No action required.

Explanation: Synchronization has started for the specified user.

User Response: No action required.

Explanation: Synchronization has completed for the specified user.

User Response: No action required.

Explanation: Synchronization is starting for the specified user. No specific subscription has yet been specified.

User Response: No action required.

Explanation: A synchronization request is being received for the specified subscription from the specified user. Server processing on behalf of this request has not yet begun.

User Response: No action required.

Explanation: A complete synchronization request has been received for the specified subscription from the specified user, and server processing on behalf of this request has begun.

User Response: No action required.

Explanation: Server processing of the specified subscription synchronization has completed successfully.

User Response: No action required.

Explanation: Server processing of the specified subscription synchronization did not complete successfully.

User Response: Contact your administrator.

Explanation: The messages from a previous subscription synchronization were never retrieved by the client. Session cancellation recovery was needed.

User Response: No action required.

Explanation: The Sync Server has determined that the specified User has not performed a synchronization of the specified table for a period of days defined by the property MaxSyncPeriod.Days. On its next synchronization, the User will receive notification that it must refresh the table. Forcing this refresh allows the Sync Server to improve performance for more frequently-synchronizing Users.

User Response: No action required.

Explanation: The auto deployment servlet has determined that the user has successfully upgraded.

User Response: No action required.

Explanation: The auto deployment servlet has determined that the user failed to upgrade.

User Response: No action required.

Explanation: The auto deployment servlet has determined that the user started the upgrade.

User Response: No action required.

Explanation: The directory specified in DSYDeploy.properties does not exist.

User Response: Administration must take action.

Explanation: The specified user is not a member of the required LDAP group. A user must be a member of the SYNCGROUP specified in com/ibm/mobileservices/DSYLDAP.properties in order to synchronize.

User Response: Contact your administrator.

Explanation: The specified user is a member of more than one group named DB2e* which has subscriptions assigned to it. An LDAP may not belong to multiple DB2e* groups due to possible subscription conflicts.

User Response: Contact your administrator.

Explanation: The server has begun to queue new synchronization request because the thread pool is full. This will cause increased response times from the server for new requests.

User Response: If the machine's resources are not fully maximized, then increasing the thread pool size is recommended. The thread pool size is determined based on the property ThreadPoolCount in DSYGdflt.properties.

Explanation: The server has begun to wait for connections because all connections in the connection pool are currently in use. This will cause increased response times from the server for new requests.

User Response: If the machine's database resources are not fully maximized, then increasing the connection pool size is recommended. The connection pool size is determined based on the property Jdbc.MaxConnections in the control database properties table.

Explanation: The device has failed to authenticate because it is not enabled.

User Response: Check to make sure that this device/user/group are enabled.

Explanation: Users can only use data filters that are defined in their groups to customize the data filter value based on current user. In this case, the XML script tried to refer to a data filter to specify customized filter value but no such data filter exists in the users group.

User Response: Fix XML script to reference data filter names that are valid for the related group.

Explanation: The XML script contains duplicate references for a data filter making the required action unclear.

User Response: Fix XML script to reference data filter names uniquely.

Explanation: The XML script tries to change a subscription as if it were a JDBC subscription, where as the subscription type is different.

User Response: Fix XML script to match subscription type you are trying to make changes to.

Explanation: The XML scripting tool failed to create the specified index in the mirror database. This may be caused by invalid column references, table name or index may already exist.

User Response: Fix XML script to specify correct index description.

Explanation: The XML script tries to change a subscription as if it were an Upload subscription, where as the subscription type is different.

User Response: Fix XML script to match subscription type you are trying to make changes to.

Explanation: The XML script tried to associate a subscription with an adapter where the adapter and subscription types do not match.

User Response: Fix XML script to match the subscription type and adapter type that you are trying to associate the subscription with.

Explanation: The XML script tries to change a subscription as if it were a File subscription, where as the subscription type is different.

User Response: Fix XML script to match subscription type you are trying to make changes to.

Explanation: The admin tool could not unblock a subscription that was blocked earlier to prevent synchronization while it was being changed.

User Response: A server that is down may be marked as running, thus admin tool is not able to communicate with it, or a running server may not be responding. There may also be a network problem. Using admin GUI, check to make sure that subscription is not blocked if you wish synchronization to proceed.

Explanation: The XML script tries to change a subscription as if it were a Custom subscription, where as the subscription type is different.

User Response: Fix XML script to match subscription type you are trying to make changes to.

Explanation: The XML script had ambiguous tags where it was not clear whether to include or exclude a referenced item.

User Response: Fix XML script to remove ambiguous include or exclude tags.

Explanation: The XML script specified incorrect ordering of items such as Subscription Sets in Groups, or Subscriptions in Subscription Sets. When order of items are specified, they must appear in ascending order or the 'order' tag must be omitted in which case the order that the items appear will be used.

User Response: Fix XML script to remove or change ambiguous 'Order' tags.

Explanation: The XML script specified a column with an unsupported data type.

User Response: Fix XML script to remove or change columns that have unsupported data types. Depending on the types of databases involved, some data types may not be supported. Read documentation about unsupported data types and data type mappings for further information to better design your data synchronization system.

Explanation: The XML script did not specify any tables for the table subscription.

User Response: Fix XML script to add tables to the subscription.

Explanation: The XML scripting tool is including the table into the subscription to be replicated and synchronized.

User Response: No action required.

Explanation: Table is already included in the subscription. A table cannot be added to a subscription more than once with the same target schema and table name.

User Response: Fix the XML Script to remove offending table description or change it's target name.

Explanation: XML Scripting tool could not change the details of a table of a subscription because subscription does not have a table with that name.

User Response: Fix the XML Script to remove offending table description or change it's target name to refer to an existing table.

Explanation: XML Scripting tool is about to change the details of a table of a subscription.

User Response: No action required.

Explanation: XML Script contains unknown character for join filter setting. It must be one of Y (enabled), N (disabled), or G (Use whatever the Global setting is).

User Response: Fix XML Script to use one of the valid join filter setting identifiers.

Explanation: XML Script contains instruction for join filter setting for a table of an upload subscription where as this setting is used only for replicated subscriptions.

User Response: To avoid this message, fix XML Script to remove join filter settings for tables of upload subscriptions.

Explanation: XML Script contains instruction to add an index that should be created in the mirror database but subscription does not have a mirror or adding such index is not possible at this time.

User Response: To avoid this message, fix XML Script to remove invalid AddIndex tags.

Explanation: XML Scripting tool is excluding a column of a table. This is typically required if the source database has changed and column no longer exists. Normally you should not exclude any column of a replicated table.

User Response: No action required.

Explanation: XML Scripting tool is processing the setup of a column of a table.

User Response: No action required.

Explanation: The source database table contains a column whose replication and synchronization properties are not specified for the Data Sync Server. Replication process may not be able to figure out how to replicate this column. Setup process will continue, however, Sync Server may fail trying to use this column.

User Response: Make sure all columns of the source table are listed in the XML Script with correct replication and synchronization settings.

Explanation: XML Scripting tool is requesting the servers to stop servicing synchronization requests for this subscription.

User Response: No action required.

Explanation: XML Scripting tool is requesting the servers to continue servicing synchronization requests for this subscription.

User Response: No action required.

Explanation: XML Scripting tool is expecting an integer, where as it is unable to interpret the specified value as a valid integer.

User Response: Fix the XML content to specify a valid integer where required.

Explanation: It is possible to put a table in a Tablespace in DB2. This tag is used to specify the tablespace of a table in a DB2 database. It is not meaningful if source database is not DB2.

User Response: Fix the XML content to remove this tag.

Explanation: The admin tool could not block a mirror database to prevent synchronization while it was being changed.

User Response: A server that is down may be marked as running, thus admin tool is not able to communicate with it, or a running server may not be responding, or the mirror database may be down. There may also be a network problem.

Explanation: In LDAP environment, XML Tool cannot edit the name of a user.

User Response: You can try to remove the LDAP user in the LDAP server and add a user with a different name.

Explanation: XML Tool failed to create a user.

User Response: This maybe be because the user already exists, or one of it's properties were invalid. There may be more information displayed as the root cause.

Explanation: XML Tool failed to create a group.

User Response: This maybe be because the group already exists, or one of it's properties were invalid. There may be more information displayed as the root cause.

Explanation: In LDAP environment, XML Tool cannot edit the name of a group.

User Response: You can try to remove the LDAP group in the LDAP server and add a group with a different security name.

Explanation: An invalid name was specified for a user.

User Response: Provide a valid username. In LDAP environment this name must satisfy LDAP requirements also.

Explanation: Changes are being written to Sync Server control database.

User Response: No action required.

Explanation: An invalid name was specified for a group.

User Response: Provide a valid group name. In LDAP environment this name must satisfy LDAP requirements also.

Explanation: An invalid name was specified for a SyncGroup group. Valid SyncGroups are listed in DSYLDAP.properties file in LDAP enabled Sync Server installations.

User Response: Provide a valid group name that is listed in DSYLDAP.properties as a SyncGroup.

Explanation: In LDAP enabled Sync Server installations, to be able to synchronize, a user needs to belong to 1 'DB2e' group whose name starts with 'DB2e'. This 'DB2e' group is used by Sync Server for synchronization purposes.

User Response: Provide a valid group name that starts with 'DB2e' in addition to other groups this LDAP user may already belong to.

Related concepts

• Handling synchronization problems