It is telling you that you have a bad key in the CI_Item file is my guess. I would rebuild the Key Files in Library Master utilities, and select the CI_Item file and see what report says

I'd rebuild key files for all module data. 

Also make sure there are no active connections to Sage data when running the utility.  You need absolute exclusive access to that company code's data tables. (Ex. disable any automated imports...).  instlock.txt can help with that.

The specific program makes me think a server reboot might help (corrupted locks).  If that fails, I think there is a utility to fix key errors in system files, but you'd probably want to get Sage involved (open a support case) if the normal utility and server reboot don't fix the issue.

I'd rebuild key files for all module data. 

Also make sure there are no active connections to Sage data when running the utility.  You need absolute exclusive access to that company code's data tables. (Ex. disable any automated imports...).  instlock.txt can help with that.

The specific program makes me think a server reboot might help (corrupted locks).  If that fails, I think there is a utility to fix key errors in system files, but you'd probably want to get Sage involved (open a support case) if the normal utility and server reboot don't fix the issue.