Please note all of the above is IdentityMinder specific, but am noticing that this problem affects other CA products, which interface with the report server as well.
In case you're still having issues you may want to implement tracing on the job server to try to isolate what might be causing the issue.
The job server processes the report requests, but it then spawns off a JobServerChild process to do the actual request - and it is this where I am guessing the connection is failing.
There are two ways to get logging on BO, either via _trace.ini files or via the CMC (Central Management Console).
a) If via CMC then
Add the following to properties of Servers/"Crystal Report Job Server"
-type OUTPROC -trace xs -reqtrace on -sdktrace on -crpetrace 7
b) If via
trace.ini files taking template from \SC\CommonReporting3\BusinessObjects Enterprise 12.0\logging\logConfig\BOtrace.ini
create JobServerClient_trace.ini
Give setting something similar to :
active = true;
importance = xs;
alert = true;
severity = ' ';
keep = false;
size = 100 * 1000;
Then place JobServerChild_trace.ini in directory :
\SC\CommonReporting3\BusinessObjects Enterprise 12.0\win32_x86
Restart the JobServer service.
For a comprehensive guide on BusinessObjects 3.1 debug and tracing, please see
this document.