[omniORB] OmniORB on a Win 64 machine.

[Obermaier, Stephen J (IS)]

Howdy!

I'm wondering if anyone has encountered this particular problem:

When I run omniNames on a Windows Server 2003 box (x64 version), the
names server seems to run just fine, but I cannot resolve the Names IOR
when running a local application on the same machine. The strange thing
is, if I run an application on another machine on the network (i.e. a
workstation running XP-SP3, x32), it can resolve the Names IOR (from the
Server box) just fine. I've confirmed that the IOR registry setting is
correct on the server box, so that doesn't seem to be an issue.

I am simply using the omniORB 4.1.4 binaries from the website (although
I'm tempted to just rebuild the ORB under x64, just to see what
happens).

It would be awfully strange if there is some Server 2003 Policy that
would prevent a locally run application from getting to the assigned
omniNames port number but hey, it is Windows!

Any insight would be much appreciated.

Thanx,

Steve O.

Stephen J. Obermaier

Northrop Grumman Mission Systems
***@ngc.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20100924/f4793df9/attachment.htm

[Martin B.]

Post by Obermaier, Stephen J (IS)
[...]
When I run omniNames on a Windows Server 2003 box (x64 version), the
names server seems to run just fine, but I cannot resolve the Names IOR
when running a local application on the same machine. The strange thing
is, if I run an application on another machine on the network (i.e. a
workstation running XP-SP3, x32), it can resolve the Names IOR (from the
Server box) just fine. I?ve confirmed that the IOR registry setting is
correct on the server box, so that doesn?t seem to be an issue.
[...]
It would be awfully strange if there is some Server 2003 Policy that
would prevent a locally run application from getting to the assigned
omniNames port number but hey, it is Windows!
Any insight would be much appreciated.

No insight, but ORBtraceLevel should be very helpful here.
Try tracing on the server process and on the failing client process and
I guess it should be easy enough to get closer to the problem.

Also: Do you have any endPoint[Publish] setting enabled?

br,
Martin

[Duncan Grisby]

Post by Obermaier, Stephen J (IS)
When I run omniNames on a Windows Server 2003 box (x64 version), the
names server seems to run just fine, but I cannot resolve the Names
IOR when running a local application on the same machine.

Run your client with -ORBtraceLevel 25 -ORBtraceInvocations 1. That will
show what it's doing and where it fails.

Cheers,

Duncan.

[Obermaier, Stephen J (IS)]

Thanks, I'll give this a shot. FYI one of the things I did discover is that Win64 machines have parallel registry keys, one set for x64 applications, and one set for x32 applications. So when you install the 32-bit omniORB on a x64 machine, the sample registry file must be modified so that HKEY_LOCAL_MACHINE\SOFTWARE\omniORB registry keys are also migrated to HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\omniORB or the 32-bit ORB won't see them. So with this fix, I can at least get the correct NS Initref, but there are still some issues passing objects around that I need to track down.

Steve O.

Northrop Grumman
Mission Systems

-----Original Message-----
From: Duncan Grisby [mailto:***@grisby.org]
Sent: Wednesday, September 29, 2010 5:56 AM
To: Obermaier, Stephen J (IS)
Cc: omniorb-***@omniorb-support.com
Subject: EXTERNAL:Re: [omniORB] OmniORB on a Win 64 machine.

Post by Obermaier, Stephen J (IS)
When I run omniNames on a Windows Server 2003 box (x64 version), the
names server seems to run just fine, but I cannot resolve the Names
IOR when running a local application on the same machine.

Run your client with -ORBtraceLevel 25 -ORBtraceInvocations 1. That will
show what it's doing and where it fails.

Cheers,

Duncan.