Jul 12, 2012 Hi, We are trying to integrate sale force with sap and in the process send IDocs to Powercenter. We have created RFC destination, connection test. EMC NetWorker Release 7.5 Error Message Guide 3. Program not registered. ' for server '.' Nsr daemons die on the server after upgrade from networker 7.4.2 to 7.5.1 Hi. 'unable to connect to server: program not registered' but I guess. Nsr Server Program Not Registered. All not appear to be a NetWorker server running on XXXXXXXXXXX.com. In /etc/hosts or the NIS hosts map.
I keep geeting this message when I try to use a RedHat 7. Alfred Rappaport 7 Value Drivers more. 1 server connecting to a RedHat 7.1 client. * fey:/shares/SHARE1/Data/ 1 retry attempted * fey:/shares/SHARE1/Data/ nsrexec: authtype nsrexec * fey:/shares/SHARE1/Data/ savefs: RPC error: Program not registered * fey:/shares/SHARE1/Data/ savefs: Cannot access nsr server `Fey.XornDomain.com` savefs fey:failed. I have aliases in /etc/hosts/,DNS, and NIS all for the servers I am attempting to reach. I tried taking both DNS and NIS out of the picture and still no luck. I am able to ping and do rpcinfo -p fey successsfully. Besides normal info there is 351396 1 udp 997 351396 1 tcp 999 390113 1 tcp 7937 showmount -e fey shows Export List for Fey: /SHARE3 * /SHARE2 * /SHARE1 * so I know rpc is working between the server and the client. Any clues to what I am missing.
I have tried deleting the /nsr/nsr.res b/c it might be corrupted. But that did not help either. I made sure the I update the ncurses and glibc according to the Legato compatability for RedHat 7.1 Server. From a Win2K server I can access the client just fine.
I have also tried accessing a different RedHat 7.1 client and I get the same result. Both RedHat 7.1 clients are SNAP Guardians products. One is a Guardian 1U 4400 and the other is a Guardian 14000 Server. RE: RPC error: Program not registered (MIS) 30 Jan 03 09:59. Some checks and tricks that might help you: - Check your licenses. For Linux clients you need an linux enabler.
Since version 6.? It Linux isn't considered a unix client anymore. - Check your firewall (if you have one) rules. See the docs for the right port ranges. If it is only partially closed you might get all kinds of weird problems including RPC errors. - Sometimes (as a last resort) restarting the client daemons and/or the server software (I hate that) might help to get rid of weird problems.
I suspect obscure network/firewall problems in those cases. Probably resulting in some kind of zombie tcp sessions blocking further correct communication.