Jump to content

Production failing in staging troubleshooting tips


Recommended Posts

  • Escalation Engineer

If you ever run into an issue where you try to run a production or export only to have Eclipse tell you "there was an error starting the job" there are a few things to check.

 

1. Ensure that the Ipro Integration Service is running on the eCapture machine that is hosting it (usually the main controller machine and Queue Manager machine, but double check environmental documentation to be sure). This service is what bridges Eclipse and eCapture, and is essential for running productions and exports our of Eclipse.

2. Check the Controller and Queue Manager logs. One of them will most likely report another error message that should help identify why staging has failed.

3. If the service is running and eCapture is not reporting any errors, then try recycling the Application pools for both ADD and Eclipse in IIS. To confirm that this works you will need to re-create the job or make a copy of it, but this can sometimes prevent the issue as well.

 

As always the best place for getting error messages for production is going to be the eCapture logs, but sometimes the error can be picked up in the ReviewAdmin.ExceptionLog in the Eclipse Config database in SQL as well. Make sure to check them both to help pinpoint the exact error that is causing staging to fail. Note that these jobs will need to be removed manually from SQL afterwards, or can be ignored.

Link to post
Share on other sites
  • Escalation Engineer

If you ever run into an issue where you try to run a production or export only to have Eclipse tell you "there was an error starting the job" there are a few things to check.

 

1. Ensure that the Ipro Integration Service is running on the eCapture machine that is hosting it (usually the main controller machine and Queue Manager machine, but double check environmental documentation to be sure). This service is what bridges Eclipse and eCapture, and is essential for running productions and exports our of Eclipse.

2. Check the Controller and Queue Manager logs. One of them will most likely report another error message that should help identify why staging has failed.

3. If the service is running and eCapture is not reporting any errors, then try recycling the Application pools for both ADD and Eclipse in IIS. To confirm that this works you will need to re-create the job or make a copy of it, but this can sometimes prevent the issue as well.

 

As always the best place for getting error messages for production is going to be the eCapture logs, but sometimes the error can be picked up in the ReviewAdmin.ExceptionLog in the Eclipse Config database in SQL as well. Make sure to check them both to help pinpoint the exact error that is causing staging to fail. Note that these jobs will need to be removed manually from SQL afterwards, or can be ignored.

Link to post
Share on other sites
  • IPRO Employee

Adding to this, I think it is also important to narrow down what the error is related to:

  • Does this error consistently happen for the same documents?
  • Is this a communication issue between Eclipse (Review) and eCapture (Processing)?
  • Are file directories accessible by the workers, and proper permissions granted?

Link to post
Share on other sites
  • IPRO Employee

Adding to this, I think it is also important to narrow down what the error is related to:

  • Does this error consistently happen for the same documents?
  • Is this a communication issue between Eclipse (Review) and eCapture (Processing)?
  • Are file directories accessible by the workers, and proper permissions granted?

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...