Job stopped working

[welshsteve]

I have a job that uses a tREST Client component. I run the job a couple of hours ago and it worked fine. I have made no changes to the job at all, yet now it has decided it has issues and is erroring with the usual completely unhelpful error messages. These error messages are designed for interpretation by java experts, not end users who are not java experts. I am a SQL developer and have no clue how to troubleshoot.

The error being returned is this:

If I look at the code for line 3028, it's to do with Proxy settings.

This job is not using the Proxy Settings in the tRESTCLient component, so why is it complaining?

I have another job with a tRESTClient component in it, an this is set up exactly the same, and this job is working, so I really do not understand why this particular job is not working.

Thanks

Steve

[welshsteve · Accepted solution]

I've fixed the job. I replaced the tRESTClient component with a new tRESTClient component. I entered EXACTLY the same settings in the new tRESTClient component as are set in the old tRESTClient compoent, yet it now works.

This I think is a prime example of what I believe the issue is. Each setting in a component will obviously write code to the job behind the scenes. When you change settings, untick boxes etc, it seems to retain old settings and doesn't delete the code no longer required. This results in compile errors when you run the job, resulting in the issues I've been getting.

[Anonymous]

Hello,

Thanks for letting us know that you have resolved this issue by yourself.

Best regards

Sabrina