Primeworks - Data Port Command Error Codes

open all | close all

Data Port Command reports error or status values using the standard process return value. There are two kinds of values that can be returned from Data Port Command: preprocessing errors and OLE DB errors (or statuses).

Error value	Meaning
0	No error
1	No command line parameters or missing option.
2	Incorrectly formatted parameter.
9	Trial period has expired (does not apply to RF version).
-1	Invalid license.
-2	Pipe is already connected.
-3	CeRapiInit failed.
-4	Timeout connecting to device.
-5	CeRapiInvoke failed.
-6	Out of memory allocating data.
-7	Failed to start RAPI client.
-8	Failed to copy RemSqlCe.dll to the device.
-10	Timeout waiting for the device.

Other than these, OLE DB error or status messages can be reported. OLE DB errors are large negative numbers, where statuses will be large positive ones. Note that Data Port Command may terminate with a status number such as DB_S_ERRORSOCCURRED (0x00040EDA in Hex or 265946 in decimal) and still be successful. This situation is typical when importing into Access tables that have AutoNumber columns. The correct data is written, but Access complains that a value was written to an auto-generated column that should be read-only.

The following table shows the most likely OLE DB error codes. To see a full list of error codes, please refer to the oledberr.h file distributed with the Windows SDK.

OLE DB Error	Meaning
0x80040E14	The command contained one or more errors
0x80040E21	Errors occurred
0x80040E2F	A specified value violated the integrity constraints for a column or a table

Support / Knowledge Base / Data Port Command / Data Port Command Error Codes