Troubleshooting the "Invalid object name 'IDC'" Robot log in systems with Retain v7
Who is this article for?
Users encountering problems syncing data to Retain v7
Database Administrator permissions are required to resolve the issue.
After upgrading Retain to v7 you might find that:
- Adding new staff, audits or assignments doesn't cause a new corresponding record to be created in Retain.
- Robot job UpdateRetain logs the error Invalid object name 'IDC'.
- UpdateRetain messages get stuck in the Microsoft message queue.
This article explains what causes the issue and how to resolve it.
1. Issue
When adding a new record to Retain, the Robot uses a table called IDC to get the next available ID. In the Retain v7 upgrade, this table is dropped and replaced with a similar table called IDN.
The Robot is not able to find the expected table, so:
- Logs the "Invalid object name" error.
- MSMQ messages are processed unsuccessfully, and so are added back to the message queue.
- No new records are created in the Retain database.
2. Solution
Historically this has been fixed by creating a view in the Retain database called IDC, which selects IDN_TABLE and IDN_IDCOUNT from the new table IDN.
Ideagen cannot provide guidance on use or configuration of the Retain applications. Contact support at Retain International for further support for the Retain database.