Built job doesn't run when deployed on Windows Server 2012

[Anonymous]

Hi all, 

I built a job in Talend for ESB v. 6.4.1. and it ran succesfully when running from the studio. Also when I deployed it in the task scheduler of my own PC (Windows 10, java build 1.8.0_45-b15) , but... It won't run when deployed in the same way at the server from where it should run. It's a Windows Server 2012, with the latest Java update build 1.8.0_162-b12.  

I don't understand why it won't run properly, it doesn't throw errors or anything, it just doesn't start up. Even though it does say it has run afterwards. 

And in the Task scheduler I just start the .bat file from the built job, the same way I do with other jobs, that are running just fine.. 

I hope someone has an idea what could be the problem! 

[Anonymous]

Well, it's our test server, so no danger there. 

But i will discuss with others here whether i can delete the old version

Thanks anyway. 

[Anonymous · Accepted solution]

We solved the issue by putting the compliance level of Java on 1.7, via View >> Preferences >> Java >> Compiler  (see picture attached). 

JavaComplienceLevel.png

[Anonymous]

Is this 'Windows Server 2012' an aws -EC2 instance?