Job would not run, all DB reads were set to Priority 1. Now all DB reads throw a 500 error (1 reply)
Crisis averted, I backed up the Job Conf file and re-wrote all the priority numbers for each of the database reads that started a new "leg".
Any idea how this happens or why priority could be set to = "-1" ?
Hello all.
I am trying not to panic.
I just ran my job through the scheduler and noticed that it only went through the first 3 transforms, starting with the first DB read.
The second, third & fourth DB reads did not even get processed. When I checked this, I noticed that all the DB reads were set to "Priority = 1."
I started changing these DB reads to be Priority 1,2,3,4.
But during that process, when I opened a DB read, suddenly I got a 500 error. Ugghhhh. Here is the error, below. Now I cannot open any DB read at all and am at a complete standstill. I'm assuming we need to edit the JobConf file but it's hard for me to understand- some of the transforms show a priority of "-1" and I don't want to recklessly edit since things are already broken.
Advice please?
HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.
Detailed Error Information:
Config Source:
More Information:
This error occurs when there is a problem reading the configuration file for the Web server or Web application. In some cases, the event logs may contain more information about what caused this error.
View more information »