HP Structured Records Management Solution Tutorial, August 2011

HP Structured Records Management Solution Tutorial 57
Runtime issues
...
</dbarch>
If you are uncertain of the connection name or details, consult your DBA or
HP TRIM administrator.
Warning when adding Groovy script
Symptom When you choose SRMS > Add SRMS activity to Business Flow, you get a
warning indicating that you have two instances of the Groovy script and you only
need one:
Business Flow already contains an SRMS Loader activity.
Only one call per business flow is needed. Continuing
adding another call?
Cause You must have previously added a Groovy script that calls the SRMS Loader.
Solution Click
Cancel to avoid creating a duplicate Groovy script. Alternatively, you could
click
OK, create the new Groovy script, and delete the previous one.
Runtime issues
This section describes issues that might arise when you are running an SRMS
cartridge.
Job fails with Groovy error
Symptom When you run an SRMS business flow, the job fails with the following error:
org.codehaus.groovy.control.MultipleCompilationErrorsExcepti
on: startup failed, General error during parsing: Did not
find four digit hex character code. line: 10 col:43
Cause The path specification in the Groovy script was incorrect. It used a single
backslash (\). It must use a double backslash (\\) or a single forward slash (/)
instead.
Solution Ensure that your path specification in the Groovy script uses either a double
backslash (\\) or a single forward slash (/), both of which will resolve to a single
backslash (\). For example:
… "SYNCHRONOUS","c:\\temp\\mydir\\")
or
… "SYNCHRONOUS","c:/temp/mydir/")
Job fails with Groovy exception
When you run an SRMS business flow, the job fails with the following Groovy
exception: