HP Structured Records Management Solution Tutorial, August 2011

58 Appendix A: Troubleshooting
Runtime issues
Exception while executing a Groovy script
Cause The archive data files were not found at the location specified in the Groovy script
that calls the SRMS Loader. Hence, the SRMS Loader failed.
Solution Ensure that your path specification in the Groovy script matches the location of
the archive data files. You can ensure that the archive files reside in the specified
location in one of two ways:
• In the Web Console, when you run the business flow, choose a destination
location that matches your path specification. If necessary, you can create a
new location in the Web Console for this purpose.
• Manually move the archive files from wherever HP Database Archiving
generated them to the path you specified in your SRMS Loader call.
Failure when launching an SRMS cartridge
Symptom When you attempt to launch an SRMS business flow from the Web Console, you
find the following message in the log file:
16.07.2009 13:51:38 Connected to TRIM.. Exit Code: 7
16.07.2009 13:51:38 Got folder record type 'STRUCTURED
RECORDS FOLDER. Exit Code: 0
16.07.2009 13:51:40 Got document record type 'STRUCTURED
RECORD. Exit Code: 0
16.07.2009 13:51:42 Failed to save document. An error
occurred accessing external record addIn
(srmsTRIMAddIn.srmsRecordAddInDeferredDelete) for PostSave.
Invalid Additional Field object passed in to TRIM SDK.. Exit
Code: 14
16.07.2009 13:51:42 SF09/34. Exit Code: 0
Cause The most likely reason for this error message is that srmsLoader_config.xml
and
srmsTRIMAddIn.xml were not configured for the HP Database Archiving
instance.
Solution Ensure that
srmsLoader_config.xml and srmsTRIMAddIn.xml, which are
located in
<install_dir>\obt\config, point to a valid instance of HP TRIM
that has the HP TRIM Enabler Pack properly installed and configured. If you are
uncertain of the configuration details, consult your DBA or HP TRIM
administrator.
Reload fails against source database for non-intrusive environments
Symptom When you attempt to reload data to the source database of a non-intrusive
environment, you receive the following error:
Status: Initialization Failed
· 1 Validation Failed: Reload not allowed for D2F
non-intrusive environment
No actions executed
Cause In a non-intrusive environment, you cannot reload data back to the source
database.