Trapped Errors are InterAction internally-generated errors that can usually only be viewed by InterAction administrators.

The error will show the InterAction user that generated the error.

If the error was not generated by the Vuture system account then it is unlikely that the error is related to the Vuture platform.

VutureAdmins Only:  If the error was generated by the Vuture system account then it can be investigated by looking at the CRM Queue Error report and the Vuture Errors Inbox to see if there are any Vuture errors that match the time of the InterAction error.

Clients should send Vuture Support copies of any recurring trapped errors for further investigation.

Invalid Contact ID Trapped Errors

These typically occur when a contact is merged or deleted in InterAction. We have the original IA contact ID and when we try to retrieve or update this contact an error is generated since the contact no longer exists in InterAction.

There are two ways to work out the contact ID:

• If the Vuture call to InterAction was asynchronous (e.g. updating contact fields) then there should be a corresponding error in the VutureAdmin only CRM Queue Error report which should contain the IA contact ID.
• If the Vuture call to InterAction was synchronous (e.g. pre-filling a form) then there will be an error in the Vuture errors inbox - only Vuture's technical team have access to this. It will include the GUID for the contact in the parameter named "sid". This can be looked up to get the IA Contact ID@
  • SELECT tblEmail.ExternalId1 FROM tblEmail WHERE EmailId = (Select EmailId FROM tblEmailHistory WHERE HistoryGUID = '{sid}')

Trapped Error - java.sql.BatchUpdateException: Error 52601, severity 14, state 3

Vuture Only - see https://jira.vutu.re/browse/PS-8857

ERROR

Unable to add field 8589943523 "Status" from contact(s) 2 / 8590006032. Value=Approved: qualification=: response=<?xml version="1.0" standalone="yes"?>

java.sql.BatchUpdateException: Error 52601, severity 14, state 3 was raised, but no message with that error number was found in sys.messages. If error is larger than 50000, make sure the user-defined message is added using sp_addmessage.

REASON

This error occurs when the InterAction database has been moved to a server that has never had InterAction before and Step 5 in the Moving InterAction Database document has not been completed.

SOLUTION

It will be necessary for the firm’s Database Admin to run the below script against their  SQL Master Database:

/* MSG: Adding a user defined message */

if (select count(*) from master.dbo.sysmessages where error = 52601) = 0

execute sp_addmessage 52601,14, 'Attempt to insert duplicate key row. Command has been aborted.'

Go

For more information on this see:

http://support.interaction.com/eglink/documents/Documentation/movingdb.pdf