Tuxedo Jolt Service Lookup Problem

[CARRINGTON, Mike(EDS)]

Name: Mike Carrington
Company: EDS (Westpac)
Email Addr: mike.ca...@eds.com

We are currently having a problem with Jolt.
Some background: We have Tuxedo 6.5, with a Jolt1.2 JSL,JSH.
We have one NetDynamics 5.0 Client running
with JavaSoft JDK1.2 for WindowsNT and Jolt1.2 and
one NetDynamics 4 client running Javasoft JDK1.1.6 and Jolt1.1 for Windows
NT.

For some reason, with one specific service
(the name happens to be muUFASTReport00)
the call does not work from the ND5 box
but does work from the ND4 box.

I attempted to reproduce this by writing a
simple Jolt client to call the service.
I have tried this client with Jolt 1.1,
Jolt1.2 and using JDK1.1.8, 1.2 and 1.3.
The following exception is always raised:
Service muUFASTReport00 didn't work because of bea.jolt.ServiceException:
Service muUFASTReport
00 is not available.
bea.jolt.ServiceException: Service muUFASTReport00 is not available.
at bea.jolt.JoltRemoteService.init(JoltRemoteService.java:108)
at bea.jolt.JoltRemoteService.<init>(JoltRemoteService.java:64)
at CallFAST.main(Compiled Code)
at the point where the:
request = new JoltRemoteService (services[ii], session);
is made.

I have tried this same call with all other
services, they all work except for the muUFASTReport00 service.

We also placed ulog dye on, so traced the calls made by the JSH to resolve
the name:

122513.mudevl11!JSH.15891: TRACE:at: { tpalloc("FML32", "", 20)
122513.mudevl11!JSH.15891: TRACE:at: } tpalloc = 0x8000000000073510
122513.mudevl11!JSH.15891: TRACE:at: { tpcall(".GETSVC",
0x8000000000073510, 0, 0x800003ffff7f1c48, 0x800003ffff7f1c40, 0xa)
122513.mudevl11!JSH.15891: TRACE:at: } tpcall = -1 [tperrno TPESVCFAIL]
122513.mudevl11!JSH.15891: TRACE:at: { tpfree(0x800000000008d8f8)
122513.mudevl11!JSH.15891: TRACE:at: } tpfree

Any thoughts ?

thanks
Mike Carrington.