FieldPoint Error and Warning Codes

The following table lists error and warning codes that FieldPoint can return from procedure calls. Error codes have a negative value and warning codes have a positive value. Errors and warnings between 33486 and 33792 (absolute value) are specific to the FieldPoint module type. Refer to the FieldPoint I/O Module Quick Reference for descriptions of module-specific error codes if they are not listed in this help file.

To convert from FieldPoint server error code to FieldPoint module error code, use the following formulas:

If the FieldPoint server error code is between 33486 and 33586, inclusive:

Module Error Code = FieldPoint Error Code – 33486

If the FieldPoint server error code is greater than 33586, the return code indicates that some, but not all, of the channels associated with a FieldPoint item have a module error code:

Module Error Code = FieldPoint Error Code – 33586

Error or Warning Code	Meaning of Error or Warning
–34244	Unable to delete a nonexistent or empty object.
–34238	Incomplete object state. Some of the information in a configuration file is not in the proper format. The necessary data to create a comm resource, device, or item either was not present or could not be interpreted. The configuration file may be corrupt.
–34220	The current configuration file is read-only. You can view and use the file but cannot save any changes to it.
–34219	Failed to open/read the configuration file. Verify that the specified path name is correct and that you have access privileges to the file.
–34218	Error closing a file. Possible cause: The file was not opened successfully or it has already been closed.
–34217	Error creating the configuration file. Possible cause: Another file with the same name already exists or the system is out of disk space or you do not have privileges to create a file.
–34216	Error opening a configuration file. Possible cause: The file does not exist or you do not have access to it.
–34215	The internal state of the object is invalid. The object is either not properly initialized or has been corrupted.
–34214	Failed to create module information file for an FP-TB-10 module. The required dual-channel module information is either nonexistent or corrupt.
–34211	Error creating Windows registry key. Possible cause: The key already exists or the user does not have access to modify the registry.
–34210	Error opening Windows registry. Possible cause: The key does not exist or the user does not have access to the registry with the ACCESS parameters specified by the open call.
–34209	Could not write to Windows registry key. Possible cause: The key is opened in read-only mode or the user does not have access to modify the registry.
–34208	Failed to read Windows registry. Possible causes: The required key does not exist or the user does not have read access to the registry.
–34201	Memory allocation has failed. Possible cause: The system is out of memory. Close some other applications to free memory.
–34117	Attempt to publish data of incorrect type for specified item. The value wired into the input value terminal of the FP Publish Data VI does not match the data type of the existing item.
–34116	Desired value is outside the configured range for some channels.
–34115	The tag handle passed to a FieldPoint VI is invalid or unknown.
–34114	Invalid IO Control string. The string value of the FieldPoint IO Control Node could not be parsed into constituent configuration file path name, comm resource, device, and item.
–34112	The specified .iak file path is not valid for the configuration alias provided. The server name must match the alias assigned to the provided configuration file path.
–34110	The requested new configuration file short name is already associated with a different configuration path.
–34109	The database that associates short names with configuration paths is unavailable. Most likely the file could not be opened. Make sure you have read privileges for the directory where FieldPoint is installed.
–34108	The specified name is not associated with a configuration file path. The requested action cannot be taken using the name provided.
–34107	Unable to load the FieldPoint server .dll. Possible cause: The .dll does not support the required interface.
–34106	The registered path for the FieldPoint server is invalid. Make sure the FieldPoint software is properly installed and registered.
–34104	A required .dll failed to load properly. The .dll path may be invalid or the dll may not exist on this machine.
–34103	Invalid parameter. At least one of the parameters passed to this function/VI has an invalid or unsupported value.
–34102	Invalid Custom Create Tag VI. Custom Create Tag VIs must be in the vi.lib\FieldPoint\Custom Create Tag directory.
–34101	Desired value is outside the configured range.
–33818	The desired IP address is already in use by a different FieldPoint network module.
–33817	Unable to use the COM port. Another comm resource in this configuration is already using this COM port.
–33816	Unexpected character received from Optomux response.
–33812	Unable to use the COM port. The COM port is already in use by a different FieldPoint communication resource with different baud rate settings.
–33811	Unable to bind to the COM port. Another application is already using the COM port.
–33810	The message from the serial port has a checksum different from the one calculated by the host application.
–33809	The specified COM port does not exist on your machine. Check your system devices to make sure your COM port(s) is present and has required system resources
–33808	The desired baudrate is not supported by the underlying network bus.
–33807	The IP address is invalid. The given IP address does not follow the IP address syntax required by the Ethernet protocol.
–33806	The required network connection was not found. Possible cause: A network resource specified in a Create Tag call was not available when the tag was created.
–33805	The server received an invalid termination character from Serial communication.
–33804	Ethernet communication has failed. Possible cause: missing or disconnected network card or network card drivers.
–33803	The channel has not yet been subscribed to.
–33802	The host has read-only access to this device.
–33801	The host does not have access to this device.
–33192	Deadbanding is not supported for the selected channel. Deadbanding is supported only for analog input and count input channels on FieldPoint Ethernet banks. Older versions of the FP-1600 firmware (older than 3.0) also do not support deadbanding.
–33191	The desired range is not supported by this I/O module. Refer to the I/O module documentation for a list of supported ranges and corresponding range IDs.
–33190	The IP pattern used to configure FieldPoint Access Control is not valid. Valid combinations are: *, [num].*, [num].[num].*, [num].[num].[num].* (where [num] can be any integer from 0-255).
–33189	A module of different type already exists at the specified address in the currently loaded configuration.
–33186	Invalid attribute value. The specified attribute(s) does not support the desired attribute setting. Check the operating instructions to make sure this setting is valid for the I/O module you are using.
–33185	Invalid channel attribute. The specified attribute is not supported by the addressed channel(s).
–33184	Invalid deadband value.
–33183	Unable to create an I/O item for this device. The device does not support I/O items..
–33181	Invalid password. The password provided to change network security settings is invalid or incorrect.
–33180	The amount of data provided does not match the number of data items required or the number of channels to be addressed.
–33165	The item addressed does not exist. Possible cause: The device is not connected or the item address is invalid.
–33160	The requested feature is not supported by this type of network or I/O module.
–33159	The firmware on the network module does not support the requested feature. Upgrade the firmware to the latest released version (download from ni.com\support\fieldpoint) and try again.
–33157	The I/O module at this address has been hotswapped by a module of an incompatible type. Replace with a module of the original type for proper operation.
–33156	The device is offline. Make sure the device is connected and its power is on.
–33155	Module information not available for any FieldPoint module. You may have accidentally deleted the module information files or corrupted your registry. Rerun the FieldPoint installer to repair your FieldPoint installation.
–33154	The module addressed is not of the selected type.
–33153	Error identifying module. Possible causes: (1) The module information is not available on your system, or (2) the module is returning an invalid module ID. For (1), the module may be newly released and it must be online for the software to configure it the first time, OR you may have accidentally deleted the module information file(s) and/or corrupted your registry. Rerun the FieldPoint installer to repair your FieldPoint installation. For (2), module may not be correctly plugged in or the EEPROM on the module may be corrupted.
–33036	Unknown error. An unidentifiable error condition has occurred.
–33035	Hardware error on instrument. An irrecoverable fault has occurred.
–33034	The response to the last command is unavailable.
–33033	The module addressed by the "Resend Last Response" is not the same module that was addressed by the previous command.
–33032	The module has been hotswapped since it was last sent a command. This response is sent only if the network module is enabled to report hotswaps, and if the hotswap occurred after hotswap reporting mode was enabled. The command was ignored. This error number can be sent in response to a standard command if you have enabled hotswap reporting for the bank.
–33030	One or more attributes specified either do not exist or do not support the setting specified. The command was ignored.
–33029	One or more ranges specified in the command either do not exist or do not support the setting specified. The command was ignored.
–33028	One or more channels specified in the command either do not exist or do not support the operation specified. The command was ignored.
–33027	The module addressed does not exist.
–33026	The FieldPoint network module detected a serial framing error in the command. The command was ignored.
–33025	The command is valid but is not supported by the addressed module.
–33024	One or more characters sent in the command could not be correctly converted to a digit (hex or decimal).
–32903	The specified limits are invalid for the command. This includes notification that an invalid digit (hex or decimal) was received.
–32902	Communications link network watchdog timed out. The command was ignored.
–32901	Not enough characters received. The module received an insufficient or incorrect number of characters for the specified command.
–32900	An unprintable ASCII character was received by the module. Only characters from ASCII value 33 to 127 are permitted within commands. The command was ignored.
–32899	Input buffer overrun. The received command was too long. The command was ignored.
–32898	The checksum does not match the sum of command characters. The checksum in the command does not match the calculated checksum of the characters in the command. The command was ignored.
–32897	Undefined or invalid command. The command character was not a legal command character, or the addressed module does not support this command. The command was ignored.
–32896	Power-up clear expected. The FieldPoint bank has power cycled since the last communication was sent. The command was ignored.
–32834	An advise operation on the selected item has already been started. You must stop the current operation before starting a new one.
–32831	The selected comm resource has no network or I/O modules associated with it. Make sure the FieldPoint bank is online and you have access to the network module. An empty Ethernet comm resource, if saved, can create an invalid .iak file.
–32824	The specified item name is already defined.
–32823	The specified device name is already defined.
–32822	The specified comm resource name is already defined.
–32819	The specified item is not present in the currently loaded configuration file.
–32817	The specified device is not present in the currently loaded configuration file.
–32816	The specified comm resource is not present in the currently loaded configuration file.
–32811	The FieldPoint server failed either to destroy some of its active objects or to terminate some service(s).
–32810	The FieldPoint server initialization failed. Possible causes: 1. Missing or corrupt configuration file; 2. Failed to create callbacks.
–32809	The FieldPoint server has already been initialized.
–32808	The FieldPoint server has not been initialized.
–32806	Tag name too long. Possible cause: Tag name exceeds the character limit (31 characters) set by the configuration file.
–32805	The tag name contains illegal characters. Possible cause: The name of a channel, block, device, or comm resource includes a line feed or a carriage return.
–32802	An invalid completion was specified.
0	Success
32768	The task is terminated. Most likely the FP Close was called before this task was finished.
32769	The task is pending.
32803	An invalid task ID was specified. The task ID used when calling FP_ReadCache or FP_Stop is invalid. Verify that the task ID used matches the task ID returned by FP_Advise.
32804	An invalid IAHandle was specified. Verify that the configuration file is valid and the IAHandle used matches the IAHandle returned by FP_Open.
32812	The specified tag name was not found.
32816	The specified comm resource is not present in the currently loaded configuration file.
32817	The specified device is not present in the currently loaded configuration file.
32819	The specified item is not present in the currently loaded configuration file.
32820	The item is read only.
32821	The item is write only.
32822	The specified comm resource name is already defined.
32823	The specified device name is already defined.
32824	The specified item name is already defined.
32826	Failed to create or initialize at least one of the objects in the configuration file. Your next save will save only the objects that were successfully created.
32828	The connection to a remote device timed out.
32832	Initialization of default channel name database failed. Any new item created by "Find Devices" will be named "Channel." Make sure your FieldPoint software is installed and registered properly.
32896	Power-up clear expected. The FieldPoint bank has power cycled since the last communication was sent. The command was ignored.
32897	Undefined or invalid command. The command character was not a legal command character, or the addressed module does not support this command. The command was ignored.
32898	The checksum does not match the sum of command characters. The checksum in the command does not match the calculated checksum of the characters in the command. The command was ignored.
32899	Input buffer overrun. The received command was too long. The command was ignored.
32900	An unprintable ASCII character was received by the module. Only characters from ASCII value 33 to 127 are permitted within commands. The command was ignored.
32901	Not enough characters received. The module received an insufficient or incorrect number of characters for the specified command.
32902	Communications link network watchdog timed out. The command was ignored.
32903	The specified limits are invalid for the command. This includes notification that an invalid digit (hex or decimal) was received.
33024	One or more characters sent in the command could not be correctly converted to a digit (hex or decimal).
33025	The command is valid but is not supported by the addressed module.
33026	The FieldPoint network module detected a serial framing error in the command. The command was ignored.
33027	The module addressed does not exist.
33028	One or more channels specified in the command either do not exist or do not support the operation specified. The command was ignored.
33029	One or more ranges specified in the command either do not exist or do not support the setting specified. The command was ignored.
33030	One or more attributes specified either do not exist or do not support the setting specified. The command was ignored.
33032	The module has been hotswapped since it was last sent a command. This response is sent only if the network module is enabled to report hotswaps, and if the hotswap occurred after hotswap reporting mode was enabled. The command was ignored. This error number can be sent in response to a standard command if you have enabled hotswap reporting for the bank.
33033	The module addressed by the "Resend Last Response" is not the same module that was addressed by the previous command.
33034	The response to the last command is unavailable.
33035	Hardware error on instrument. An irrecoverable fault has occurred.
33036	Unknown error. An unidentifiable error condition has occurred.
33153	Error identifying module. Possible causes: (1) The module information is not available on your system, or (2) the module is returning an invalid module ID. For (1), the module may be newly released and it must be online for the software to configure it the first time, OR you may have accidentally deleted the module information file(s) and/or corrupted your registry. Rerun the FieldPoint installer to repair your FieldPoint installation. For (2), module may not be correctly plugged in or the EEPROM on the module may be corrupted.
33154	The module addressed is not of the selected type.
33156	The device is offline. Make sure the device is connected and its power is on.
33157	The I/O module at this address has been hotswapped by a module of an incompatible type. Replace with a module of the original type for proper operation.
33158	The I/O module at this address has been hotswapped by a different module of compatible type. No action necessary.
33161	The write operation failed to change the value on the FieldPoint bank. The connection may be broken.
33162	Unable to connect to the data item on the module. Possible causes: (1) A connection is broken, or (2) the network module is not powered on.
33163	The connection to the module has been broken. Check cabling, power, etc.
33183	The desired configuration value was out of range. It has been coerced to the nearest valid number.
33185	Invalid channel attribute. The specified attribute is not supported by the addressed channel(s).
33186	Invalid attribute value. The specified attribute(s) does not support the desired attribute setting. Check the operating instructions to make sure this setting is valid for the I/O module you are using.
33191	The desired range is not supported by this I/O module. Refer to the I/O module documentation for a list of supported ranges and corresponding range IDs.
33436	Bad channel status reported by module. The module is in one of the following states: Unconfigured, Bad Status "A", Bad Status "B".
33437	The specified serial network module was sent a Power-Up Clear command.
33438	Bad channel status "A" reported for all contained channels. A channel-specific error has occurred. Check module documentation for more details.
33439	Bad channel status "B" reported for all contained channels. A channel-specific error has occurred. Check module documentation for more details.
33440	Bad channel status "Unconfigured" reported for all contained channels. All channels are in the "unconfigured" state. This error can occur if the network module is unable to configure the module because of a hardware failure.
33441	None of the contained channels exists.
33442	An unknown warning was returned by the optomux-based serial hardware. Possible cause: recoverable fault.
33443	Bad channel status reported by several channels. At least one channel is in one of the following states: Unconfigured, Bad Status "A", Bad Status "B"
33445	Bad channel status "B" reported for several contained channels. A channel-specific error has occurred. Check module documentation for more details.
33446	Bad channel status "Unconfigured" reported for several contained channels. Some channels are in "unconfigured" state. This error can occur if the network module is unable to configure a module because of a hardware failure.
33447	Several contained channels do not exist.
33448	Bad channel status reported for all contained channels. All channels are in one of the following states: Unconfigured, Bad Status "A", Bad Status "B".
33487	Out of range. The input signal you are measuring has gone out of the specified measurement range. Check the signal and, if necessary, change the range the channel is using.
33488	Open current loop. Check wire connections for possible breakage or disconnection.
33489	Open thermocouple. The thermocouple module did not detect a thermocouple connection on the channel. Check connections for possible breakage or disconnection.
33490	Open RTD detected. The RTD module did not detected an RTD on the channel. Check connections for possible breakage or disconnection.
33491	Count overflowed since last read. The counter module has reached its maximum count value. No action required.
33492	The channel is sourcing the maximum current allowed. The device attached to the channel is drawing the maximum current from the channel. Check for possible shorts or external device failure.
33493	The channel is in overcurrent protection mode. The device attached to the channel is passing more current than is allowed through the channel. Check for possible shorts or external device failure.
33494	Empty base or slot. The specified module cannot be detected by the network module or the FP-TB-10 base. Make sure the module is firmly fitted into the base and that the POWER and READY LEDs are lit.
33495	Bad data from channel. The data is corrupted and cannot be displayed correctly.
33496	The channel exceeded the specified terminal count.
33587	Some channels out of range. More than one of the input signals that you are measuring has gone out of the specified measurement range. Check the signals and, if necessary, change the range the module is using.
33588	Open current loop on some channels. One or more channels of the module has detected an open current loop. Check wire connections for possible breakage or disconnection.
33589	Open thermocouple on some channels. More than one channel on the thermocouple module has failed to detect a thermocouple connection. Check connections for possible breakage or disconnection.
33590	Open RTD on some channels. More than one channel on the RTD module has failed to detect an RTD. Check connections for possible breakage or disconnection.
33591	Count overflowed since last read for some channels. Some channels on the counter module have reached their maximum count value. No action required.
33592	More than one channel is sourcing the maximum current allowed. The device attached to the channel is drawing the maximum current from the channel. Check for possible shorts or external device failure.
33593	Some channels are in overcurrent protection mode. The device attached to the channel is passing more current than is allowed through the channel. Check for possible shorts or external device failure.
33594	Empty base or slot. The specified module cannot be detected by the network module or the FP-TB-10 base. Make sure the module is firmly fitted into the base and that the POWER and READY LEDs are lit.
33595	Bad data from channel(s). The data is corrupted and cannot be displayed correctly.
33818	The desired IP address is already in use by a different FieldPoint comm resource.
34206	An invalid status code was specified. The status code received does not match the predefined list of error codes returned by the FieldPoint software.
34208	Failed to read Windows registry. Possible causes: The required key does not exist or the user does not have read access to the registry.
34212	Error closing Windows registry. Possible cause: The key does not exist or has not been opened.
34213	Error accessing module information. The corresponding file either cannot be found or cannot be opened.
34218	Error closing a file. Possible cause: The file was not opened successfully or it has already been closed.
34220	The current configuration file is read-only. You can view and use the file but cannot save any changes to it.
34238	Incomplete object state. Some of the information in a configuration file is not in the proper format. The necessary data to create a comm resource, device, or item either was not present or could not be interpreted. The file configuration may be corrupt.