I have created a very simple compound PDF document. It consists of a Master Page Layout and Page Layout 1. The master page is very simple and consists of nothing but an image and some text.

The Page Layout 1 has only a report added and it references a procedure. When I run the compound PDF procedure it gives the following message "Unknown error occurred. Agent on reporting server EDASERVE may have crashed. Please investigate reporting server log." I can run the Master Page by itself and it works no problem. I can also run the referenced procedure for the report on Page Layout 1 and it works no problem. They just do not work together.

I have checked my server log and this is what I see.

12/13/2011 12:26:11 agent started (tscomid=30, pid=2452, svc=DEFAULT)
12/13/2011 12:26:11 request by t3rp2452 to notify agent is ready (tscomid=30)
12/13/2011 12:26:11 accepting cmrpip000006 tcp=192.168.6.16:49213
12/13/2011 12:26:11 request by cmrpip000006 from NGXXJ769 for explicit connect t
o agent (DEFAULT)
12/13/2011 12:26:11 connecting cmrpip000006 tscomid=30,sesid=6
12/13/2011 12:26:11 processing cmrpip000006 u=administrator,l=SRV
12/13/2011 12:26:11 request by t3rp2452 to notify disconnect of sesid=6
12/13/2011 12:26:11 disconnect cmrpip000006 tscomid=30,sesid=6
12/13/2011 12:26:11 agent needs refresh after 1 sessions (tscomid=30)
12/13/2011 12:26:11 Agent (tscomid=30) statistics:
12/13/2011 12:26:11 tscomid connect state active query time last cmd
last class
12/13/2011 12:26:11 > pid foc/ext
12/13/2011 12:26:11 user sesid

12/13/2011 12:26:11 > io
12/13/2011 12:26:11 30 -- idle -- Dec 13 12:26:11
--
12/13/2011 12:26:11 > 2452 0/34
12/13/2011 12:26:11 number of sessions: 0
12/13/2011 12:26:11 last command:

12/13/2011 12:26:11 last response time: 0:00:00.081
12/13/2011 12:26:11 last errnum: 0
12/13/2011 12:26:11 last executed class: --
12/13/2011 12:26:11 last procedure name: --

12/13/2011 12:26:11 last masterfile name: tbl_guidelines

12/13/2011 12:26:11 focus i/o: 0
12/13/2011 12:26:11 external database input: 34
12/13/2011 12:26:11 number of transactions or hli commands: 0
12/13/2011 12:26:11 pagefaultcount: 3963
12/13/2011 12:26:11 peakworkingsetsize (kb): 14804
12/13/2011 12:26:11 workingsetsize (kb): 13176
12/13/2011 12:26:11 quotapeakpagedpoolusage: 85348
12/13/2011 12:26:11 quotapagedpoolusage: 78516
12/13/2011 12:26:11 quotapeaknonpagedpoolusage: 9304
12/13/2011 12:26:11 quotanonpagedpoolusage: 7800
12/13/2011 12:26:11 pagefileusage: 6971392
12/13/2011 12:26:11 peakpagefileusage: 7942144
12/13/2011 12:26:11 total execution time: 0:00:00.125
12/13/2011 12:26:11 agent deactivated (tscomid=30, pid=2452)
12/13/2011 12:26:11 accepting cmrpip000007 tcp=192.168.6.16:49215
12/13/2011 12:26:11 request by cmrpip000007 from NGXXJ769 for explicit connect t
o agent (DEFAULT)
12/13/2011 12:26:11 connecting cmrpip000007 tscomid=29,sesid=7
12/13/2011 12:26:11 request by edapmon to notify agent is stopped (tscomid=30)
12/13/2011 12:26:11 agent started (tscomid=31, pid=2532, svc=DEFAULT)
12/13/2011 12:26:11 processing cmrpip000007 u=administrator,l=SRV
12/13/2011 12:26:11 request by t3rp2328 to notify disconnect of sesid=7
12/13/2011 12:26:11 disconnect cmrpip000007 tscomid=29,sesid=7
12/13/2011 12:26:11 agent needs refresh after 1 sessions (tscomid=29)
12/13/2011 12:26:11 Agent (tscomid=29) statistics:
12/13/2011 12:26:11 tscomid connect state active query time last cmd
last class
12/13/2011 12:26:11 > pid foc/ext
12/13/2011 12:26:11 user sesid

12/13/2011 12:26:11 > io
12/13/2011 12:26:11 29 -- idle -- Dec 13 12:26:11
--
12/13/2011 12:26:11 > 2328 0/32
12/13/2011 12:26:11 number of sessions: 0
12/13/2011 12:26:11 last command:

12/13/2011 12:26:11 last response time: 0:00:00.095
12/13/2011 12:26:11 last errnum: 0
12/13/2011 12:26:11 last executed class: --
12/13/2011 12:26:11 last procedure name: --

12/13/2011 12:26:11 last masterfile name: tbl_compliancest
andards
12/13/2011 12:26:11 focus i/o: 0
12/13/2011 12:26:11 external database input: 32
12/13/2011 12:26:11 number of transactions or hli commands: 0
12/13/2011 12:26:11 pagefaultcount: 3960
12/13/2011 12:26:11 peakworkingsetsize (kb): 14792
12/13/2011 12:26:11 workingsetsize (kb): 13164
12/13/2011 12:26:11 quotapeakpagedpoolusage: 85348
12/13/2011 12:26:11 quotapagedpoolusage: 78516
12/13/2011 12:26:11 quotapeaknonpagedpoolusage: 9304
12/13/2011 12:26:11 quotanonpagedpoolusage: 7800
12/13/2011 12:26:11 pagefileusage: 6963200
12/13/2011 12:26:11 peakpagefileusage: 7929856
12/13/2011 12:26:11 total execution time: 0:00:00.078
12/13/2011 12:26:11 agent deactivated (tscomid=29, pid=2328)
12/13/2011 12:26:11 request by edapmon to notify agent is stopped (tscomid=29)
12/13/2011 12:26:11 agent started (tscomid=32, pid=2504, svc=DEFAULT)
12/13/2011 12:26:11 request by t3rp2532 to notify agent is ready (tscomid=31)
12/13/2011 12:26:11 request by t3rp2504 to notify agent is ready (tscomid=32)
12/13/2011 12:27:12 accepting cmrpip000008 tcp=192.168.6.16:49217
12/13/2011 12:27:12 request by cmrpip000008 from NGXXJ769 for explicit connect t
o agent (DEFAULT)
12/13/2011 12:27:12 connecting cmrpip000008 tscomid=31,sesid=8
12/13/2011 12:27:12 processing cmrpip000008 u=administrator,l=SRV
12/13/2011 12:27:16 request by edapmon to notify agent has crashed (tscomid=31)
12/13/2011 12:27:16 agent started (tscomid=33, pid=3064, svc=DEFAULT)
12/13/2011 12:27:17 request by t3rp3064 to notify agent is ready (tscomid=33)

The only other thing I can think of is that the referenced procedure has a loop in it. It may only go through once but it could go through 'n' number of times.

Does anyone have any ideas what is wrong?

Thanks,

Dave

Crashing agents are difficult to pin down.

My suggestion is to start putting break points in the code to determine the code that is causing this. (-EXIT)

Then start commenting out bits until it works, so you can find the offending code.

quote:

Originally posted by Waz:
Crashing agents are difficult to pin down.

My suggestion is to start putting break points in the code to determine the code that is causing this. (-EXIT)

Then start commenting out bits until it works, so you can find the offending code.

Currently going through those steps. I was hoping for an easier method.

Waz,
Do you know if running DOS commands in a procedure could be causing this issue?

Thanks,
Dave

This message has been edited. Last edited by: dburton,