CIS Error messages
In a CIS environment, you might encounter errors from the following sources:
- Oracle errors at the database level, including:
- Database calls from within the CIS software.
- Pass-through of errors that occur within Clintrial packages.
- CIS errors, which can indicate a problem within the CIS code.
- .NET errors, which are generated by the Windows .NET Framework and then handled in the CIS processing code.
This appendix lists the error messages initiated by CIS processing. For more information, see Suggested troubleshooting procedure.
Error |
Description |
---|---|
Cannot receive comment on non-existent Patient Data. |
No record exists with which to associate the given comment. |
Visit or Page Information not found. |
Visit or page properties not found in the INF_OBJECTS table. |
Invalid parameters passed to the Data Deletion GetAllItems method. |
Low level code problem. The method requires either FORM or DATA to be passed. Anything else results in this error. |
Invalid parameters passed to the Data Deletion GetCTrecids method. |
Similar to above. |
Subject not enrolled. |
Subject was not found in the INF_SUBJECT table. |
No Updates allowed to the Patient Enrollment Data. |
Once a patient is enrolled, changes to enrollment data cannot be made (feature of the Clintrial software). |
Patient screening data has not been loaded. |
No screening data has been found. |
Clintrial Core module not registered. |
No Clintrial installation at target instance. |
Protocol not in correct state to load data. |
Clintrial protocol must be in "NORMAL" state. |
InForm User information not found. |
InForm user is not found in the INF_USER_UPDATE table. |
Cannot insert item SDV status - protocol is not in correct state to load data. |
An incorrect SDV record has been received. |
Query Information not found in Clintrial ErrorStatus Table. |
Outgoing transaction record has CT_RECID for a query that was not found in the INF_ERRORSTATUS table. |
Inform Patient Guid not found for CT Subject Id. |
Clintrial SUBJECT_ID given did not have matching record in INF_SUBJECT table. |
Source Record not found for Query in outgoing transactions. |
Outgoing transaction record has CT_RECID for a query that was not found in the INF_ERRORSTATUS table. |
Invalid Query-State transition. |
The conflict resolver found an inconsistent query state transition. |
Database Execute Exception. |
General exception (not database exception) occurred during execution of a database command. |
Database GetValue Exception Table: {0}, Column: {1}, RowNum: {2} - There are {3} rows in the DataSet.\n\n{4}. |
General exception (not database exception) occurred during retrieval of a database value ({} values indicate where extra information is given). |
Unsupported conversion to string from type {0}. |
Could not convert from the given type to a string. |
Unsupported conversion to BOOL from type {0}. |
Could not convert from the given type to a Boolean value. |
Database SetValue Exception Table: {0}, Column: {1}, RowNum: {2} - There are {3} rows in the DataSet.\n\n{4}. |
General exception (not database exception) occurred during the setting of a database value. |
Database Delete Row Exception Table: {0}, Column: {1}, RowNum: {2} - There are {3} rows in the DataSet.\n\n{4}. |
General exception (not database exception) occurred during deletion of a database row. |
Database Add Row Exception AddRow Exception - Table: {0}. |
General exception (not database exception) occurred during creation of a database row. |
Cannot process System Message of unknown type. |
Create CIS Trial processor has been passed XML that is not a CREATECISTRIAL element. |
CISMapsetProcessor can process XML tag EXTERNALMAPSET; was passed wrong tag. |
Mappings processor has been passed XML that is not a EXTERNALMAPSET element. |
NULL Transaction Parameter. |
Transaction re-player (for new mappings feature) was passed a null transaction. |
ProcessMessages() err: Access denied or SendNewData() err: Access denied. |
Method was called by a user not assigned the CISManager role within the CISManager COM+ package. |
startProcessMessageThread() err: concurrent processing. |
Another thread (possibly on another machine) is already processing the messages. This might occur when you try to start the processing manually when directly invoking the web service. |
Cannot process message. No mapping information provided. |
The first message does not contain the definition of the MAPSET (or the MAPSET name has been removed from the CIS database). |
No Vector node message found - messages available {0}. |
There was no synchronization connection information in the message that was requested to be processed. |
Error finding Bookmark Bookmark {0} - only {1} nodes in message. |
Requested bookmark is out of bounds of the number of transactions in message. |
Stopped processing due to New Mapping Exception. |
Occurs if one has chosen to stop processing upon encountering a new mapping. This is the correct behavior of this new mapping option. |
Invalid OnNewMapping Selection. |
Incorrect new mapping selection given. |
GC.Collect() has failed: |
Call to Garbage Collector failed. |
Cannot connect to database User: [{0}] Password: [{1}] Connection: [{2}]. |
Unable to connect to database. |
Unsupported Clintrial Context Type |
Clintrial Context items must have type between 0 and 4. |
Unsupported Clintrial Item Type. |
Clintrial item types must be FIXED, FLOAT, TEXT, DATE, or DATETIME. |
Not a valid DB format specifier. |
Oracle database format is not recognized. |
The value is not a valid dimension for this DB format. |
Oracle database format is recognized but appears to have invalid dimensions. |
The database format dimension of an installed item cannot be made smaller. |
Column already exists in database with larger dimension (width) than new specification. |
The value is not a valid number of decimal places. |
Invalid number of decimal places for database column. |
The number of decimal places cannot exceed the database format width. |
Exceeded number of decimal places for the specified column width. |
Number is too large for column Number {0} is too large for column of width {1} and precision {2}. |
The given number (data) is too big to fit into the column. This occurs when a numeric data point is too large for the target Clintrial item. |
Floating-Point Rounding - Panel {0}, Item {1} Floating point numbers submitted to this column have exceeded the number of places specified. For example, the value {1} was rounded to the correct number of decimal places as {2} This message will not appear again for this Item. |
The number has been truncated to fit into the target column. This occurs when a floating point number needs to be truncated to fit into the target Clintrial item. The CIS software issues this error as a warning. It is commonly seen with values that have been normalized in the InForm software. |
Unsupported Clintrial Panel Type. |
Clintrial panels must have type between 0 and 5. |
Error_Clintrial_Tablespaces_Nearly_Full At least one of the Clintrial tablespaces (CT_META_D, CT_META_I, CT_DATA_D, or CT_DATA_I) is running low on space. CIS will not create protocols or process transactions until more space is added. The minimum required free bytes per tablespace is {0}. These tablespaces have fewer free bytes: {1}. |
The value for {0} indicates the number of free bytes required for each Clintrial tablespace, and the value for {1} identifies each tablespace that has fewer bytes than the number of required bytes and the amount of free space for that table. For the CIS software to continue processing transactions, you must increase the number of bytes for a table to meet the required number of free bytes. |
Unsupported Clintrial Lock Status. |
Clintrial panel Lock Status must be between 0 and 2. |