Could not find the context .... in Studio 7.0.1

[Anonymous]

Hi,

Some jobs in the Studio have a problem with context groups. In the output window a message is written like: "Could not find the context TST". In the same output window all kinds of errors are showing that indicate that indeed the context variables are not there. (like: java.sql.SQLException: The syntax of the connection URL 'jdbc:jtds:sqlserver://null:null//null;....)

In the job itself in the Contexts-tab the context groups are all there and in the Run Window I can select the context 'TST'. 

As mentioned not all the jobs suffer from this problem, and I know for a fact that this job did run properly some time ago, in the same version of Talend Studio.

I've tried deleting the context groups and adding them again, with no luck. If all the context groups are deleted and I run the job under 'Default', the message is also shown ("Could not find the context Default").

Edit: 2019-05-24

I added a screenshot about the output.

I've been testing some more. If I delete all contexts and run the job with a tDBConnection component, that still links to the deleted context variables, I get a 'Update Detection' window. If I click 'OK', then this context is added. And running the job works, so these context variables are now present. 

 

But if I add other context these do not work...

Hope someone has a solution for this....

[Anonymous]

@Steven_Knolle 

Could you please share some screen shots of the job flow, how you have configured context groups, how you are running from the Studio and the area where the job is throwing error with full error message?

It will help us to get more idea about the flow so that we can give better recommendations.

Warm Regards,
Nikhil Thampi

Please appreciate our Talend community members by giving Kudos for sharing their time for your query. If your query is answered, please mark the topic as resolved 🙂

[Anonymous]

I added a screenshot to the original post. 

[Anonymous]

Hi,

   I could not reproduce this issue as it is working fine for me every time. 

   Let us check with @rhall  or @xdshi 

Warm Regards,
Nikhil Thampi

Please appreciate our Talend community members by giving Kudos for sharing their time for your query. If your query is answered, please mark the topic as resolved 🙂

[Anonymous]

Hi @Steven_Knolle,

This is certainly behaviour that you should not be experiencing. I assume that you are using the Open Studio and not the Enterprise Edition. Since 7.0.1 was a first edition of a new major release, it is likely that this had a few bugs in it. I do not have a copy of this edition, but have used subsequent versions of TOS and have not experienced this issue. Is it possible for you to take a new version? This would be the easiest way to get beyond this problem.

If you get this problem in a newer version, would it be possible for you to export your job (removing any private information) and post it here for us to look at?

Regards

Richard