XI 3.0 Scheduled Reports Stay As Pending

[Former Member]

I have a brand new install of BOXI 3.0 with FP1 and SAP Integration KIT.

When I schedule a report in WebI (using eFashion as universe) as Run Now or Run Once the report goes in as pending and stay as pending.

I have tried restarting the SIA, recreating the WebI processing server and recreating the Adaptive job server to no avail.

I've seen blogs suggesting issues with DB Connectivity associated with this symptom however I'm discounting that on the grounds that the SQL Server instance for the Repository DB Server is on the same box as the Business Objects install

Another item that may be relevant is that this machine is quite slow.

Does anyone have any ideas?

JB

[Former Member · Accepted solution]

Hi John,

See the second last post on this thread

Cheers

Alan

[Former Member · Accepted solution]

I paused Instance manager, cleaned off the old jobs and added the following switches to the Job Servers:

-maxChildReqs 1 -childProcTimeOut 30 -checkChildForNonExistence 1

I then stopped the SIA and started it and confirmed from the logs that the job server log was clear.

I then scheduled one report to run 'Now'. It is persisting in a state of pending.

The logs show:

trace message: Parent_impl::wait() 13000

trace message: Parent_impl::findChild: 1884

trace message: Parent_impl::findChild: could not find 1884

trace message: SI_IInfoProcessing_implMixedProc::childRequest() waiting for child: [1884]

trace message: Parent_impl::wait() 13000

This then repeats for a total of 5 times then does:

trace message: Destinations::loadProperty(): [ISPROP_IPROC_CURJOBS].

trace message: [jobserver]::countAndCleanupJobsHelper(): checkChildForNonExistence[1], forceGetLoad[true], timeElapsed[60020], currentLoadTotal[0]

trace message: [jobserver]::countAndCleanupJobsHelper(): returning currentLoadTotal[0]

trace message: Destinations::loadProperty(): [ISPROP_IPROC_MAXJOBS].

trace message: CServiceAdmin_impl_base::getNVMetrics

trace message: Parent_impl::findChild: 1884

trace message: Parent_impl::findChild: could not find 1884

trace message: [jobserver]::newIJob(): [Couldn't get IJob interface or writing IAudit: Pipe exception. Reason: jobserverchild (WebIJavaSchedulingService, 0, Timeout waiting for Child [1884] to register ([120]seconds).

Cycles through the parent_impl again and then starts again for the same job with a new child number.

It looks like it's processing through but is instead stuck in and endless loop.

[Former Member · Accepted solution]

Hi John,

Did you ever resolve this?...we are seeing the exact same behavior and "Timeout waiting for Child" messages.

Thanks.

Kevin

[Former Member · Accepted solution]

This workaround solved it for one of my customers:

1) Under CMC, stop the Publication Job Server and Adaptive Job Server.

2) Under > Properties > Host Identifiers, select Auto assign. Save and Close.

3) Restart the servers.

HTH