Common Errors and Possible Solutions

The common errors and the possible solutions to fix the errors are provided in the following table.

Table 18. Common Errors and Possible Solutions

Error ID	Description	Possible Cause	Possible Solution	Error Source
001	Data Exchange has experienced an unknown error.	An Agent or a Runtime Service error has occurred.	Inspect the Runtime Service log to identify the issue, and then contact Unisys Support if you have not found a resolution.	Common
100	The Agent has experienced an unknown error.		Inspect the Runtime Service log to identify the issue, and then contact Unisys Support if you have not found a resolution.	Common
101	Failed to connect to the Agent.	The Agent is not running.	Restart the Agent DSS.	Common
		The Agent port number as specified on the System subtab is invalid.	Ensure that the port number provided in the Edit System Settings dialog box is correct.
		A firewall is blocking access to the Agent port.	Configure the Windows firewall to allow access to the port.
102	The Agent has stopped.	The Agent Worker has crashed or Agent DSS has restarted.	Restart the Agent. Contact Unisys Support if you are unable to restart the Agent.	Common
104	Failed to handshake with the Agent.	The Agent port number as specified on the System subtab is in use by another program.	Provide the correct Agent port number on the Edit System Settings dialog box.	Common
106	Data Exchange is disabled on this partition.	The DASDL Audit definition does not specify the “DATAEXCHANGE” attribute.	Modify the DASDL Audit definition to specify the “DATAEXCHANGE” attribute.	MCP host as the source
107	The Agent has failed to read the audit file.	The source database audit file is invalid. No audit found for the specified Audit Timestamp. The Agent has insufficient priivileges to read the audit file. Timestamp mismatch detected for the expected audit.	Check that the Audit file to restart from is correct.	Common
108	The Agent has experienced an error.	The Agent has an internal error.	Restart the Agent DSS.	Common
109	The product version of the Agent does not match the product version of the Administrative Service.	The product version of the Agent does not match the product version of the Administrative Service.	Upgrade the Agent to the version of the Administrative Service or upgrade the Administrative Service to the version of the Agent.	Common
110	The Agent detected that the source database is in an inconsistent state.	The source database is in a status that needs to be recovered. The source database is undergoing a reorganization.	Restart the changed data transformation after the source database is available.	Common
111	The OS 2200 Agent could not find any profile elements in the host configuration file.	The configuration file used by this Agent is incorrect.	Check with your System Administrator.	OS 2200 host as the source
112	The OS 2200 Agent has reported a security error.	The user credentials you specified are not correct.	Use valid user credentials for the OS 2200 host and try again.	OS 2200 host as the source
113	The OS 2200 Agent failed to find the Application Group.	The Application Group has been removed from the OS 2200 host.	Add the Application Group.	OS 2200 host as the source
114	The user running on the OS 2200 Agent does not have privileges to read the audit.	The OS 2200 Agent is not running under an appropriate User Id.	Ensure the OS 2200 Agent is running under an appropriate User Id.	OS 2200 host as the source
118	The Agent is reserved exclusively by the Administrative Service at <host name>.	Another Administrative Service is already using the MCP Agent port.	Perform the following steps to release the Agent port: Change the port number in the Agent TCP Port settings in the Administration Site where the Agent is reserved. Restart the MCP Agent. Open a new Administration Site and provide the required port number.	MCP host as the source
119	File deployment on MCP failed for transformation target <target_name>.	The inbound library could not be copied from the MCP Service folder to the target database folder.	Check the user code, database name, and pack name for the MCP Service.	SQL Server as the source
120	Internal file error. The Data Exchange license for a target DMSII database was not found.	You do not have a Data Exchange inbound license for a target Enterprise Database Server.	Purchase a Data Exchange license for a target Enterprise Database Server.	MCP host as the target
121	Deployment of internal files failed, because of connection error to the DMSII Adapter.	The DMSII Adapter TCP port you use is not accessible.	Configure the DMSII Adapter correctly and try again.	MCP host as the target
		The product version of the DMSII Adapter does not match the product version of the Administrative Service.
		The other Administrative Service has reserved this DMSII Adapter because it is configured to use the same DMSII Adaptor TCP port.
122	Change data capture is not configured correctly in the transformation source.	CDC is not enabled for the database or the table(s) used in the transformation(s).	Enable CDC for the tables and the respective columns, update the schema and the transformation(s), and then redeploy the transformation.	SQL Server as the source host.
		CDC is not enabled for some columns used in the transformation(s).
		The property of Active Capture Instance is not set in DDW for some table(s) in the transformation(s).
		Some schema changes have been detected (some tables or columns have been deleted, or the capture instance is disabled) since the transformation was deployed.
123	The transformations cannot be run at the same time.	Two or more active transformations have the same source table and the source table has different active capture instances in different transformations.	Modify the source table property in the Properties window in DDW, so that it has the same active capture instance in all the transformations to be run concurrently. Redeploy the modified transformations.	SQL Server as the source host.
124	SQL Server change data capture job of the transformation source is not running.	SQL Server Agent service is stopped.	Set the startup type of the SQL Server Agent service to Automatic, and restart the service.	SQL Server as the source host.
124		SQL Server change data capture job may be deleted or stopped.		SQL Server as the source host.
125	Invalid License: The Data Exchange license for a source DMSII database was not found.	You do not have a Data Exchange outbound license for a source Enterprise Database Server.	Purchase a Data Exchange license for a source Enterprise Database Server.	MCP host as the source
126	The Date Time entered for the changed data transformation is in the future.	A changed data transformation cannot start from a future date/time.	Provide the current date/time for the changed data transformation.	OS 2200 and SQL Server as source hosts
127	The Data Exchange Agent for SQL Server failed to connect to, or execute SQL commands against, the source SQL Server database.	The source SQL Server database is not online.	Restart the transformation after the source database becomes available to the DE Agent for SQL Server.	SQL Server as the source host.
		The account of the DE Agent for SQL Server does not have sufficient privilege to access the transformation source.	Provide the “db_datareader” privilege to the account.
		Connection information, including transformation source credentials, are incorrect or have expired.	Verify the connection information.
		SSL encryption is not enabled for the SQL Server instance.	Enable SSL encryption for the SQL Server instance.
		The certificate chain was issued by an authority that is not trusted.	On the system where DE Agent for SQL Server is running, install the root certificate that the certificate authority (CA) issued to the SQL Server.
128	Source data changed on resuming Bulk Data Transformation.	Source data or the database has been modified.	Clear the target DB or change the Data Manipulation Language setting as "Insert -> Merge" ("Create -> Merge" for Enterprise Database Server). Restart Bulk Data Transformation from the beginning.	SQL Server only
129	The Agent has failed to check the schema change.	The database you specified may not exist.	Contact your Unisys Support Representative.	MCP or SQL Server
130	The login user or password is invalid for the source database.	The login user does not exist. The password is invalid for the login user. The login user does not have sufficient privilege to access the audit file. The password has expired in the MCP host.	In the System Settings tab, enter the valid login user and password, and try again.	MCP only
131	Insufficient privileges to access the description file.	You do not have sufficient privileges to access the description file of the source database.	In the System Settings tab, enter the valid login user and password, and try again.	MCP only
132	The Agent is waiting for the audit file and change data transformation is paused till the audit file is made available.	The audit file has been moved to renamed.	Make the required audit file available to the Agent. The Agent will begin reading the audit file and changed data transformation will resume.	MCP only
133	Insufficient privileges to deploy files on MCP for transformation target <target_name>	The user does not have enough privileges to copy the inbound library from the MCP Service folder to the target database folder.	Ensure that the Login User used to load schema of the target has the privileges to copy files from the MCP Service folder to the target database folder.	SQL Server only
134	File deployment on MCP failed.	The outbound library could not be copied from the MCP Service folder to the source database folder on the MCP host.	Check the user code, database name, and pack name for the MCP Service.	MCP only
135	Insufficient privileges to deploy files on MCP.	The user does not have enough privileges to copy the outbound library from the MCP Service folder to the source database folder.	Ensure that the Login User you entered in the System Settings has the privileges to copy files from the MCP Service folder to the source database folder.	MCP only
140	The audit file number is invalid.	The audit file number entered for the Changed Data Transformation is invalid.	Ensure that the audit file number exists and is valid.	MCP only
200	The Runtime Service has experienced an unknown error.	The Runtime Service encountered an internal error.	Inspect the Runtime Service log to identify the issue, and then contact Unisys Support if you have not found a resolution.	Common
201	Failed to connect to the Data Exchange Service.	The Data Exchange Service is not installed or is not running.	Ensure that the Data Exchange Service is installed and running appropriately.	Common
		The Data Exchange Service port is blocked by a firewall.	Configure the Windows firewall to allow access to the port.
		The Service Host and/or Service Port as specified on the System subtab are incorrect.	Reconfigure the host name and/or the port number.
		The Service port is blocked by a firewall.	Configure the Windows firewall to allow access to the port.
202	The Runtime Service has stopped.		Restart the Runtime Service.	Common
203	The Runtime Service has failed to read messages.	For DMSII as the source, Runtime Service cannot establish AIS connection to the host.	Contact your Unisys Support Representative.	Common
		For OS 2200 as the source, Runtime Service cannot establish socket connection to the host.
		For SQL Server as the source, the Runtime Service failed to read message from the DE Agent for SQL Server.
204	The Data Exchange Service failed to update target database(s).	The destination database is not online.	Inspect the Runtime Service log to identify the issue, and then contact Unisys Support if you have not found a resolution.	Common
		Connection information, including destination credentials, is incorrect or has expired.	Update the database connection details in DDW, redeploy the transformation, and then restart the changed data transformation.
		SSL encryption is not enabled for the SQL Server instance.	Enable the SSL encryption.
		The transformation produced SQL statements that caused an error in the destination database.	Inspect the Runtime Service log to identify the issue, and then contact Unisys Support if you have not found a resolution.
205	The Runtime Service has failed to initialize.	Some error occurred while the Runtime Service attempted to start a changed data transformation or a bulk data transformation.	Inspect the Runtime Service log to identify the issue, and then contact Unisys Support if you have not found a resolution.	Common
206	The Data Exchange Service has failed to process a transformation.	Truncation errors whereby the destination field was too small to hold the data value without loss of integrity.	Update the transformation target schema to increase the field sizes, reload the schema, and redeploy the transformation.	Common
		Conversion errors whereby the type of the destination could not store the data value without loss of integrity.	Update the transformation target schema to increase the field sizes, reload the schema, and redeploy the transformation.
		DDW reported warnings for the transformation indicating potential data loss at Runtime.
207	The Data Exchange Service has failed to load a transformation.	The transformation file is corrupted, or it is not in the same revision level of the Runtime Service.	Inspect the Runtime Service log to identify the issue, and then contact Unisys Support if you have not found a resolution.	Common
208	The Data Exchange Service has failed to update the internal tracking database.	The UnisysDExchTrackingDB database is not online.	Bring up the tracking DB if it is offline. Inspect the tracking DB and recommit the last transaction, or continue with the next transaction based on your analysis.	Common
208		Connection information, including destination credentials, is incorrect or has expired.	Reinstall the Runtime Service and provide the new credentials during installation.
209	The Data Exchange Service has detected a schema mismatch error.	The version of the schema loaded in DDW is out of date.	Update the schema in DDW and redeploy your transformations.	Common
210	The Data Exchange Service detected an error related to OLE DB.	The transformation source information provided in the Bulk Data Transformation Settings dialog box is incorrect.	Reconfigure the Bulk Data Transformation Settings dialog box with the correct values.	MCP host as the source
		The version of OLE DB installed on the service host is incompatible with the MCP OLE DB server.	Ensure that the same version of the OLE DB is installed on both the MCP host and the Windows machine.
		An Enterprise Database Server construct used in the transformation source is not supported by OLE DB.	Remove the unsupported data type from the transformation file used for the bulk data transformation.
		OLE DB is not installed on the machine where the Runtime Service is running.	Install OLE DB of the same version as MCP OLE DB server.
211	The product version of the Runtime Service does not match the product version of the Administrative Service.	The product version of the Runtime Service does not match the product version of the Administrative Service.	Upgrade the Runtime Service to the version of the Administrative Service.	Common
212	The Runtime Service has experienced an unknown error.		Restart the changed data transformation and input a desired audit file number to start from. If the issue is not resolved, check the Runtime Service log for more information. While performing a changed data transformation with RDMS as the source, when there is no audit record processed yet, there is no starting point for recovery. So recovery try fails with a NeedStartingPoint error.	Common
213	The Runtime Service encountered an error reading OS 2200 data files.	The user credentials you specified are not correct.	Provide the correct user credentials.	OS 2200 host as the source
		The AIS connection name to the OS 2200 host is invalid.	Verify the AIS connection name.
		The OS 2200 files containing the extracted data may have been deleted.
214	The Runtime Service detected an error when connecting to the SQL Server.	The transformation source information provided in the bulk data transformation setting is incorrect.	Provide the correct transformation source information.	SQL Server as the source host
		The source SQL Server database is not online.
		If the source SQL Server instance is on a different partition from the Runtime Service, then Windows Authentication does not work.	Use SQL Server Authentication.
		The Runtime Service account does not have sufficient privilege to access the transformation source.	Provide the “db_datareader” privilege to the Runtime Service user account.
215	The Runtime Service detected an error when connecting to the Enterprise Database Server target.	The target database is not available at this location.	Restart the transformation after the target database becomes available.	SQL Server as the source host
		The target database is in a status that needs to be recovered.
		The target database is undergoing a reorganization.
		The AIS Connection Name as specified in the System Settings tab is incorrect.
216	The Runtime Service detected an error when connecting to the transformation target.	The target database is not available at this location.	Restart the transformation after the target database becomes available.	Common
		Runtime Service account does not have privilege to access the transformation target.	Provide correct privileges to the Runtime Service.
		The secured connection configuration is incorrect for the transformation target(s).	Check the secured connection configuration for the transformation target(s).
217	The Runtime Service detected a version mismatch for user-defined functions.	The assembly file version of the user-defined function in the Runtime Service does not match with the version in DDW.	Verify the versions of the user-defined function assembly files in DDW and in Runtime Service. *Note:* The assembly files can be found in the following paths, if you had installed Data Exchange with the default settings: C:\Program Files\Unisys\Data Exchange<version_ number>\Development Workbench\Functions\External C:\Program Files\Unisys\Data Exchange<version_ number>\Runtime Service\Functions\External Close and re-launch DDW and restart the Runtime Service if you make any changes to the files. Redeploy the transformation from DDW.	Common
218	The user-defined function assembly files are missing.	The user-defined function assembly files in the Runtime Service are missing.	Copy the user-defined function assembly files in the Development Workbench to the Runtime Service, in this location: C:\Program Files\Unisys\Data Exchange<version_ number>\Runtime Service\Functions\External.	Common
300	No address set to send email to.	The target database is in a status that needs to be recovered.	Configure the Edit Recovery Settings dialog box to include an email ID for the system to send an alert upon any failure.	Common
301	Failed to initialize SMTP.	The target database is undergoing a reorganization.	Verify the values in the Edit SMTP Server Settings window and reconfigure them to the correct values.	Common
302	Failed to send email.	The values provided in the Edit SMTP Server Settings window are incorrect.	Verify the Edit SMTP Server Settings window and reconfigure them to the correct values.	Common
302	Failed to send email.	Company firewall or network policy blocks the SMTP server requests.	Reconfigure the Windows firewall to allow the SMTP Server requests.
303	Data Exchange changed data transformation and bulk data transformation cannot be started at the same time.	A bulk data transformation should be performed before a changed data transformation.	Attempt another operation only upon completion of one operation.	Common
305	Failed to send and receive messages to the Agent.	Some error occurred with the TCP socket between the Agent and the Administrative Service.	Contact Unisys Support. Restarting both can fix the issue.	Common
306	Data Exchange is running.	A Data Exchange system setting change was attempted. A transformation activation was attempted.	Ensure that you do not change the values on the System subtab or activate a transformation while the changed data transformation is running.	Common
307	Failed to update internal database of the Administrative Service.	The UnisysDExchAdminDB might be offline.	Bring up the UnisysDExchAdminDB if it is offline.	Common
308	The Host Id is missing.	The web page is out of date. The Administrative Service requires restarting.	Restart the Administrative Service and refresh the web page.	Common
309	Source database Id is missing.	The web page is out of date. The Administrative Service requires restarting.	Restart the Administrative Service and refresh the web page.	Common
310	Transformation Id is missing.	A new version of a transformation has been deployed while the Runtime Service is still running with the old transformation.	Stop and then restart the changed data transformation, so the new version of the transformation becomes active.	Common
311	No transformation is activated.	No transformations have been activated.	Go to the Transformations tab and activate a transformation.	Common
312	The Agent is running.	An attempt was made to change the port of the Agent while there are active transformations for databases on the host.	Ensure that you do not change the port number of the Agent while the changed data transformation associated with the Agent is running.	Common
313	Data Exchange has detected a mismatch of the database schema.	The version of the schema that was loaded into DDW is out of date.	Update the schema in DDW and redeploy the transformations.	Common
314	Data Exchange has detected unsupported data type.	The transformation includes an unsupported data type for the bulk data transformation, and this mismatch is ignored during the transformation.	Remove the mapping that includes the unsupported data type from the transformation, and redeploy the transformation. Use alternative methods for loading this data, if required.	Common
315	Data Exchange has detected unknown state transactions.	The Runtime Service issued SQL statements to a target database but received no confirmation of their success or failure.	Upon restarting, verify if the SQL statements listed in the dialog box have been committed or not, and respond to the dialog box appropriately. You can also set a default value. In the Runtime Service configuration file you can set the value of CDTTargetTransactionState to AssumeCommitted or AssumeNotCommitted, as required. The default value is Verify.	Common
316	Failed to load transformation.		Contact Unisys Support.	Common
317	Data Exchange detected a newer version of the transformation while the Runtime Service is running.	A new version of a transformation has been deployed while the Runtime Service is still running with the old transformation.	Stop and then restart the changed data transformation, so the new version of the transformation becomes active.	Common
318	Unsupported Data Structure is detected.	A data set contains an embedded data set, but it has no sets. This structure is not supported by bulk data transformations.	Contact the Database Administrator.	Common
319	The transformations cannot be run at the same time.	Some of the transformations share the same source and target schema combination; they cannot be run at the same time due to potential data conflict in the transformation targets.	Combine the transformation contents with the same source and target schema into one transformation in DDW.	Common
320	Transformation needs migration.	Transformations that were deployed from the earlier version of the product must be migrated.	Either the transformation structure or transformation rules have been changed in the new version of the product. You need to migrate the transformations before they can be run. Download the transformations from the Administration Site and import them into the same version of DDW. DDW automatically migrates the transformations to support the new structure. If there are transformation rule changes, make appropriate modifications based on the new warning/error messages. Redeploy the transformations to the Administration Site.	SQL Server as source host
321	Data conflict when committing to target.	Data conflict in target database. The target database is not online.	Update the Target Commit Error Handling Policy to another option. Update the transformation in DDW. Restart the transformation after the target database becomes available.	Common
322	Invalid bootstrap server(s) detected.	Bootstrap server(s) cannot be reached. Bootstrap server(s) is down from the dedicated Kafka cluster. The security setting on Producer does not match with that on the Bootstrap server(s).	Ensure that the bootstrap server(s) can be connected to. Add more servers from the same cluster. Ensure that the security connection on Bootstrap server(s) and Producer are both ON or OFF.	MCP and OS 2200 hosts
323	Invalid Kafka topic(s) detected.	The designated topic is not found.	Use a topic that is available.	MCP and OS 2200 hosts
324	The Kafka server on the leader broker and the replication broker(s) of the topic are unreachable.	The Kafka server on the leader broker is unreachable, and there is no replica for the topic. The Kafka servers on the leader broker and the replication broker(s) of the topic are all unreachable.	Restart the Kafka server on the leader broker of the topic. If the replication factor of the topic is 1, then extend it and start the Kafka server(s) on the replication broker(s) of the topic.	MCP and OS 2200 hosts
325	Producer Configurations are invalid or mismatched with Broker.	The security setting on Producer does not match with that on the Bootstrap server(s). Configuration Key is not valid.	Ensure that the client certificate configured on Producer matches with the configuration on Bootstrap server(s). Ensure that the Producer configuration is valid.	MCP and OS 2200 hosts
326	Insufficient privilege to deploy transformation	Deploy failed, because the user has no such privilege.	Check the privileges you have, and find out whether you have the deploy privilege.	Common
	Unknown State Transactions Detected	This error appears when Data Exchange encounters an unknown state error. It displays the Last Command and waits for the user’s response.	The Last Command is the last SQL command that Data Exchange was trying to commit to the target database. Perform the following steps to resolve the issue: Go to the target table specified in the last command. Check the record that was to be updated. If it is an INSERT command, check if the record is there. If it is a DELETE command, check if the record is not there. If it is an UPDATE command, check if the record is updated with the new values. If the action specified in the command is committed, then select Committed. Else, select Not Committed. Click Start. You can also set a default value. In the Runtime Service configuration file you can set the value of CDTTargetTransactionState to AssumeCommitted or AssumeNotCommitted, as required. The default value is Verify.	Common