The DSC Module VIs can return the following error codes. Refer to the KnowledgeBase for more information about correcting errors in LabVIEW.

Code Description
−2147220995 The OPC Client I/O server is not connected to any OPC server. Verify the configurations for the OPC Client I/O server. Also check the network settings if you are trying to connect to a remote OPC server. Ensure the DCOM security settings on both the server side and the client side are correct.
−1967362022 An attempt was made to read from an empty memory buffer.
−1967353913 The Modbus Slave I/O server failed to create the socket object. Ensure TCP/IP configuration of the computer is correct.
−1967353912 The Modbus Slave I/O server failed to bind to port 502. Ensure no other Modbus Slave or application occupies TCP port 502.
−1967353911 The Modbus I/O server failed to send a frame. Ensure that the configuration of the specified serial port for modbus master is correct.
−1967353910 The input value of the Modbus I/O server data item is invalid. Ensure that the data type of the input value matches that of the Modbus I/O server data item. If the input value is an array, also ensure that the length of the array matches that of the Modbus I/O server data item.
−1967353909 The response from the Modbus slave device does not include the specified data items. Check the communication settings between the Modbus master and slave devices.
−1967353908 The specified data item address is not an allowable address for the Modbus slave device. If the Modbus I/O server requests a range of addresses in one command, but one or more addresses in the requested range does not exist in the Modbus slave device, this error returns for all data item addresses in the range. Refer to "Advanced Attribute Settings Dialog Box" in the LabVIEW Help to reduce the Maximum Data Points Per Command. If this error persists after you have set Maximum Data Points Per Command to 1 for any address in question, refer to the Modbus slave device documentation for information about supported addresses.
−1967353907 The Modbus I/O server failed to communicate with the Modbus slave device. Ensure that the Modbus slave device works properly.
−1967353906 The response from the Modbus slave device is not readable. Check the communication settings between the Modbus master and slave devices.
−1967353905 The Modbus slave device does not support the specified operation. Refer to the documentation of the Modbus slave device for information about supported operations.
−1967353904 The response from the Modbus slave device is not readable. Check the serial connection and the communication settings between the Modbus master and slave devices.
−1967353903 The communication between the Modbus master and slave devices was interrupted. Check the connection status between the two devices.
−1967353902 The Modbus I/O server failed to receive any response from the Modbus slave device. Ensure that the Modbus slave device works properly and that the connection between the Modbus master and slave devices is configured correctly.
−1967353901 The Modbus I/O server failed to connect to the Modbus Ethernet slave device. Ensure that the Modbus Ethernet slave device works properly and that the connection between the Modbus master and slave devices is configured correctly.
−1967353900 The Modbus I/O server failed to allocate a serial port. Ensure that the specified serial port is available.
−1967353854 The specified traces do not exist in the Citadel database.
−1967353853 The DSC Module does not support the version of the specified Citadel database file. You must convert the Citadel database file to Citadel version 5. Refer to the Measurement and Automation Explorer Help for Historical Data Viewer, available by selecting Help»Help Topics»Historical Data Viewer in MAX, for more information about converting Citadel database files.
−1967353851 You must set the Enabled property of a SharedVariableIO class to TRUE before using the other properties in that same class. For example, you must set the Scaling:Enabled property to TRUE before you can use any of the other Scaling properties, such as the Scaling:Invert property.
−1967353850 The DSC Module failed to modify this shared variable because the shared variable was deployed from a version of LabVIEW different from the version you use. Redeploy this shared variable with the current version of LabVIEW.
−1073479676 The OPC Server cannot convert the data between the specified format or the requested data type and the canonical data type. This error description is defined by the OPC Foundation.
−1073479674 The OPC items AccessRights do not allow the operation. This error description is defined by the OPC Foundation.
−1073479673 The item ID is not defined in the OPC server address space (on add or validate) or no longer exists in the OPC server address space for reading or writing. This error description is defined by the OPC Foundation.
−1073479669 The value that the OPC Client I/O server tried to write to the OPC server is out of range. This error description is defined by the OPC Foundation.
−1073414400 The OPC Server returned a value with a bad status for an unknown reason. Consult the vendor documentation for your OPC Server to resolve this error. This error description is defined by the OPC Foundation.
−1073414399 The value has been overridden. This typically means the input has been disconnected from the OPC server and a manually-entered value has been 'forced'. This error description is defined by the OPC Foundation.
−1073414398 An OPC server-specific problem with the configuration occurred. For example, an OPC item has been deleted from the configuration. This error description is defined by the OPC Foundation.
−1073414397 The OPC items are not connected to a data source. This error may indicate that no value is available at this time. For example, the data source has not provided the value. This error description is defined by the OPC Foundation.
−1073414396 The OPC server detects a device failure. This error description is defined by the OPC Foundation.
−1073414395 The OPC server detects a sensor failure. This error description is defined by the OPC Foundation.
−1073414394 The device and OPC server fail to communicate with each other. The last known value is available. Note that the 'age' of the value may be determined from the TIMESTAMP in the OPCITEMSTATE. This error description is defined by the OPC Foundation.
−1073414393 The device and OPC server fail to communicate with each other. The last known value is not available. This error description is defined by the OPC Foundation.
−1073414392 The block is off scan or otherwise locked. This error also can occur when the active state of the OPC item is InActive or when the active state of the group that contains the OPC item is InActive. This error description is defined by the OPC Foundation.
−1073414391 Whatever was writing this value has stopped doing so. The returned value should be regarded as 'stale'. This error is associated with the failure of some external source to 'put' something into the value within an acceptable period of time. Note that the 'age' of the value can be determined from the TIMESTAMP in OPCITEMSTATE. This error description is defined by the OPC Foundation.
−1073414390 Either the OPC value has 'pegged' at one of the sensor limits (in which case the limit field should be set to 1 or 2) or the sensor is otherwise known to be out of calibration via some form of internal diagnostics (in which case the limit field should be 0). This error description is defined by the OPC Foundation.
−1073414389 The returned OPC value is outside the range of values defined for this parameter. Note that in this case (per the Fieldbus Specification) the 'Limits' field indicates which limit has been exceeded but does not necessarily imply that the value cannot move farther out of range. This error description is defined by the OPC Foundation.
−1073414388 The OPC value is derived from multiple sources and has less than the required number of good sources. This error description is defined by the OPC Foundation.
−1073414387 The initial values are not available in the OPC server. After you add OPC items to a group, the OPC server might take some time to obtain the initial values for those OPC items. This error description is defined by the OPC Foundation.
180129793 An alarm or event subscription has been requested.
180129794 Not all specified traces exist in the Citadel database. Ensure that the specified trace names are correct.