Use the search and browse feature to view Kepware's repository of more than 500 Knowledge Base articles. Narrow your results or type your query into the search field below.

Search Solutions Results By: View All Solutions

Kepware Knowledge Base: Solution


Server/OPC Specific Error Codes


Last Update: 11/12/2018

The error codes listed below are specific to the Server/OPC application, and will be returned to a client application from the server.

Returned Error Code 0xC0040001 (3221487617)

Problem:
The handle's value is invalid.

Possible Cause:
The item does not exist in the server.

Solution:
Add the item or remove the request.

Returned Error Code 0xC0040004 (3221487620)

Problem:
The server cannot convert the data between the requested data type and the canonical data type.

Possible Cause:
The data type cannot be marshaled to the requested data type.

Solution:
Request the proper data type.

Returned Error Code 0xC0040005 (3221487621)

Problem:
The requested operation cannot be done on a public group.

Solution:
Check the server's supported features to determine if this operation is supported. Kepware's server products do not support public groups.

Returned Error Code 0xC0040006 (3221487622)

Problem:
The item's Access privileges do not allow the attempted operation.

Possible Cause:
An attempt was made to write to an item whose Access is Read Only.

Solution:
1. Change the item's Access privileges.

2. Do not attempt to write to the item.

Returned Error Code 0xC0040007 (3221487623)

Problem:
The item is no longer available in the server's address space.

Possible Cause:
1. The item failed to be added but was not removed from the OPC group by the client application.

2. The server timed out and removed all the items from its poll table.

Returned Error Code 0xC0040009 (3221487625)

Problem:
The filter string is invalid.

Possible Cause:
The Browse filter is set incorrectly.

Solution:
Correct or remove the filter string.

Returned Error Code 0xC004000A (3221487626)

Problem:
The item's Access Path is not known to the server.

Possible Cause:
When adding an OPC Item from a client application, one of the options available is to set an Access Path (which is part of the OPC Item). For example, if the OPC Item was "Channel1.Device1.Tag1," the Access Path could be set to "Channel1.Device1" and the OPC Item would then be "Tag1". This error indicates that the access path is blank or has been entered incorrectly for the OPC Item.

Solution:
Correct or remove the Access Path.

Returned Error Code 0xC004000B (3221487627)

Problem:
The item's value is out of range.

Possible Cause:
This is typically seen when data is requested from a tag (for example) that is set to a DWord but requested as a Word. This error will be received once the actual value is greater than 65537.

Returned Error Code 0xC004000C (3221487628)

Problem:
Duplicate names are not allowed.

Possible Cause:
An attempt was made to add the same OPC group name twice.

Solution:
Create a unique OPC group name.

Returned Error Code 0x0004000D (262157)

Problem:
The server does not support the requested update rate.

Solution:
The server will use the closest available update rate. This message is simply a report back to the client application of the update rate that will be used. For example, the fastest update rate that is allowed by OPC is 10 milliseconds. If the update rate is set in the group to 5 milliseconds, it will change to 10 milliseconds and this will be reported back by the server.

Returned Error Code 0x0004000E (262158)

This error code is returned when a value passed to a write operation was accepted, but the output was clamped. For example, if writing 40000 to an item that is a Short (SINT) data type, the server will clamp the value written to 32767.

Returned Error Code 0x0004000F (262159)

Problem:
The operation cannot be completed because the object has existing references.

Possible Cause:
This error can occur when trying to remove an item that is waiting for the completion of a synchronous process.

Returned Error Code 0xC0040203 (3221488131)

Problem:
The server does not recognize the Property ID.

Possible Cause:
The GetOPCItem() method is being used, and the ItemID being passed is either invalid or not currently in use. For example, a scaling parameter is being requested but no scaling is set.

Solution:
Use a valid or in-use ItemID.

Returned Error Code 0xC0040406

This error code is returned when an OPC Client performs the IOPCSyncIO2::WriteVQT Method. This method allows client applications to write the Value, Quality, and TimeStamp to an OPC Item, but it is not mandatory that all servers support the writing of the Quality and Timestamp. As such, if the server does not support the combination (which could be a single quantity like Timestamp) attempted by the client application, it will not perform the write and will return this error code instead.

Note: KEPServerEX only supports the writing of the Value to an OPC Item, and will return 0xC0040406. The server's error string or description is "The server does not support writing of Quality and/or Timestamp".

Related Products
KEPServerEX