notification server error (BODI-1241023)

Data Services XI 3.2 12.2.2.3
Client components : Windows XP - Server components : Linux 64bit

Behaviour
•We are not able to execute jobs from Designer : "The job server you selected is not working. "
•In the status bar, when you hover the cursor over the job server icon : notification server error (BODI-1241023)
•We are able to execute and schedule jobs in the Management Console

Test of the 2 way communication (according to SAP KB 1416303)

1. Designer --> Job Server
on the pc : telnet deks01068 3500
--> succesful
deks01068 = hostname running the job server
3500 = port of the job server

2. Job Server --> Designer
on the Linux-box : telnet pc9040447 3510
--> succesful
pc9040447 = name of my pc (ip address : 10.122.40.216)
3510 = listening port, specified in Designer (Tools --> Options --> Environment --> Designer Communication Ports : from : 3510 - to : 3510

–> Conclusion : the 2 way communication is ok

However, in the log file of the job server, I notice this :

…
(12.2) 10-28-10 10:30:15 (32469:1149274432) JobServer: Marking notification object for client inet:10.123.5.35:4000 for deletion. (BODI-850265)
(12.2) 10-28-10 10:30:43 (32469:1095772480) JobServer: Creating notification object for client inet:10.123.5.35:4000. (BODI-850264)
(12.2) 10-28-10 10:31:57 (32469:1094719808) JobServer: Marking notification object for client inet:10.123.5.35:3510 for deletion. (BODI-850265)
(12.2) 10-28-10 10:32:19 (32469:1129347392) JobServer: Marking notification object for client inet:10.123.5.35:4000 for deletion. (BODI-850265)
(12.2) 10-28-10 10:32:25 (32469:1095772480) JobServer: Creating notification object for client inet:10.123.5.35:3510. (BODI-850264)
…

These entries (“marking for deletion”) indicate that the job server stops communicating with the client
Even more, 10.123.5.35, is not the ip-address of one of the workstations, but from the gateway between the job server and the clients.

The 10.123.5.35:3510 --> should be 10.122.40.216:3510 (ip address of my pc, followed by the listening port)

Question : where does this 10.123.5.35:3510 come from ?
It seems that the gateway does not transfer correctly the ip address of my pc to the job server.

Any ideas are welcome.

Hans


hsegers :belgium: (BOB member since 2009-06-05)

Please open at least a port range of three ports in Designer, not just one. Don’t ask why, I only noticed it a few years back. And I might be off completely.


Werner Daehn :de: (BOB member since 2004-12-17)

Hi Werner, thanks for your reply.
Unfortunately, it doesn’t help.
I’m pretty sure that it is a network/security/firewall issue. I hope the network team can sort it out.


hsegers :belgium: (BOB member since 2009-06-05)

Hi Hans!

Did you find a way to resolve this?

Thank you.


R.A. :philippines: (BOB member since 2008-10-28)

Hello Gurus,

We are facing exactly the same problem.

There is definitely a two way communication between server and client, but somehow the server is not responding back.

When I ping from server to client and client to server, it works fine.

We raised a ticket with SAP and they said it is a network/firewall issue.

But the firewall is off on server as well as on the client.

Any help would be greatly appreciated.

Thanks,
Rahul Tada


Rahul Tada :india: (BOB member since 2012-04-17)

Hi!

We got to fix this problem by talking to the network guys… Just like what you’ve said, even if the firewalls are turned off the problem still exists. One thing you can check is the network policy. In our case, there is some network policy that denies certain ip and port ranges to communicate.

Hope this would give you a start.


R.A. :philippines: (BOB member since 2008-10-28)

Thanks Estadilla for your reply.

I have updated the network guys reagarding this issue. I am hoping they would come up with some solution.


Rahul Tada :india: (BOB member since 2012-04-17)

I’m running into the same problem but it seems to be isolated to a specific client/Designer machine. My local repository uses the same logical job server and I’m able to run jobs just fine from Designer.


eganjp :us: (BOB member since 2007-09-12)

I’m having the same problem, in my case it happens on at least 2 local machines that I checked. The difference is that when I execute the job, I’m getting the error that the job server is not working, but the jobs still executes, I can’t see the Monitor log from the designer, but can see it from the Data Services Management Console.
In the Job Log i’m getting the following error: Notification Server ‘inet:[PC_Name]:53340’ is not working. Can’t access trace log. (BODI-1100015)

This started to happen after the Data Services Job Server VM has been migrated to a new VM with a new IP address.

Thanks,
Shal


shal (BOB member since 2012-01-05)

Is the machine name of the new VM the same? Check the repository table AL_MACHINE_INFO to make sure the names and ports agree.


eganjp :us: (BOB member since 2007-09-12)

Yes, the new VM kept the same name as the old one. I checked the AL_MACHINE_INFO table and it references the same name and port number 3500.

Thanks,
Shal


shal (BOB member since 2012-01-05)

I suspect you need to get with your network staff and find out if the ports are open.


eganjp :us: (BOB member since 2007-09-12)

Yes, I already started a thread with the Network team before raising the question here… The problem was that they were not convinced it is a port/firewall issue.

I worked with the Network team last night and eventually we got it to work, they had to open the port ranges from 3510-3512 from the DS job server to all desktops, and I have set these ports in the Designer (by un-checking the option to allow the Designer to set its on ports).

Thanks,
Shal


shal (BOB member since 2012-01-05)

Good deal. Thanks for updating the thread with confirmation that it worked.


eganjp :us: (BOB member since 2007-09-12)