Data Services 4.1 Job Server Issue

dataservices administration
1

I have the BODI-1241021 Job server is not responding issue. Again this is on 4.1.

I have worked with Data Services for a long time and know that most of the time this is a port issue.

I can confirm that its not port related.
I can run designer from the server and can connect to the job server. I just can not from the client. I also can not connect to the Central Repo from the client. However I can connect to the profiling server from the client on port 8080.
I can confirm there is no firewall between the client and the server.
I can telnet on the job server port from the client to the server and from the server to the client. So I can see that its open.

I have also checked that the server name is defined correctly in the CMS or is it called SI since there is no BOE server installed.
I am pretty sure my host file is set up correctly just double chekcing that now.

Does any one else have any other ideas to check before I open an SAP support ticket.

The work around now is to either use the server or build the jobs from the client and run them from the web tool. This is very annoying.

Thanks for the help.

msavagedk (BOB member since 2013-03-21)

2

In repo table AL_MACHINE_INFO the host name to the job server is listed as an ip-address or a host name? And is it the full host name?

If not, could you please change it to the full host name or even better: use the ip-address?

Johannes Vink :netherlands: (BOB member since 2012-03-20)

3

That was it thanks!!! Where are you at I will send you a pizza :slight_smile:

msavagedk (BOB member since 2013-03-21)

4

Hi, We have a similar error and thought to continue this thread.
We are trying to execute a job from the Console but get the following exception once the job is executed- “Exception thrown when trying to communicate with Job Server:XXXXXXv007:3500. Socket is closed”. However, I am able to telnet to the Job Server Port using CMD from the Client.

Please let me know if there is anything we can try to resolve this error.

Ankit J (BOB member since 2013-03-14)

5

Definitely not a similar issue. Please keep it on your on topic :wink:

Johannes Vink :netherlands: (BOB member since 2012-03-20)