cancel
Showing results for 
Search instead for 
Did you mean: 

JobServerChildCrash - Error - Component not installed or corrupt

Former Member
0 Kudos

The description for Event ID 0 from source JobServerChildCrash cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

OS: Windows 2008R2

Version: BO XI 3.1

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

Please try to implement the below switch at the end of the Command line of your Job Server in the CMC and then restart it and then check if the issue occur after the report is scheduled.

-procreportoptions __noverifydatabase__forceApplyParamsAfterDBL

( There are two underscores between the options and starts with a dash )

Regards,

Philippe

Former Member
0 Kudos

Which Job server? I have Adaptive Job Server, Crystal..., Destination..., ListOfValues..., Program... and Publication.

Is there another place other than the event viewer to see logs? Should I turn on auditing on each job server?

Thanks,

Phil

Former Member
0 Kudos

This error is usually due to schedules

so test the command according to the type of the documents that you schedule.

If you schedule Crystal reports, then it's Crystal report job server

if it's deski reports, then deski job server

Webi -> adaptive job server

Publications -> publication job server

Regards,

Philippe

Answers (1)

Answers (1)

Former Member
0 Kudos

How did you resolve your issue? I'm experiencing the same error and tried implementing this solution for the Crystal Reports Job Server but it didn't fix it.

Regards,

Anthony

Former Member
0 Kudos

I think it came down to the reports failing because someone forgot to remove the default printer. If you see your server using a huge amount of dsik space, several gigs or more, then I would take a look at removing the default printer. I also changed the job server to create only 15 jobs on a 4 core server instead of the recommended 5 per core.