[omniORB] Problems with omniORB4 and WinNT4/2K

[Krzysiek Czarnowski]

Ulf Stoermer wrote:
> Hi,
>
> did you have an older version of omniORB running before?

Yes!

> I had omniORB3 running before on my Win2K machine
> and upgraded to omniORB4. When starting the new
> omniNames I had the same Access violation error
> (I've used the binary distribution)
>
> I don't know exactly anymore how I solved the problem,
> but in my case it had to do with, that there were still old references
> to omniNames3 around. That means you have to make sure
> that the environment variable points to the correct location
> of the omniNamesLog directory and also make sure that
> any old log-files are deleted.
> Also, when running omniNames the first time, you have to
> start it with the '-start' option. Then all subsequent invocations
> can be done without that option.
>
> In the end I got it all up and running again. So my suggestion
> is, check your environment and get rid off any old omniORB
> stuff. Hope that helps.

Hm... I thought I'd already done that.
Anyway, I'll check everything again.

Thanks,
Krzysztof



> > -----Original Message-----
> > From: omniorb-list-admin@omniorb-support.com
> > [mailto:omniorb-list-admin@omniorb-support.com]On Behalf Of
> > Krzysiek Czarnowski
> > Sent: Saturday, 5 January 2002 12:22 AM
> > To: omniorb-list@omniorb-support.com
> > Subject: [omniORB] Problems with omniORB4 and WinNT4/2K
> >
> >
> > Hi,
> > I experience problems when compiling and running omniORB-4.0.0 under
> > Windows.
> >
> > * CASE 1
> > WinNT4, VC++6, SP's installed
> >
> > Running 'omninames -start' results in (in VC++ debug):
> > =======================================
> > Loaded 'D:\omniORB4\bin\x86_win32\omniNames.exe', no matching symbolic
> > information found.
> > Loaded 'C:\WINNT\system32\NTDLL.DLL', no matching symbolic information
> > found.
> > Loaded 'D:\omniORB4\bin\x86_win32\omniORB400_rt.dll', no matching
symbolic
> > information found.
> > Loaded 'D:\omniORB4\bin\x86_win32\omnithread30_rt.dll', no
> > matching symbolic
> > information found.
> > Loaded 'C:\WINNT\system32\MSVCRT.dll', no matching symbolic information
> > found.
> > Loaded 'C:\WINNT\system32\KERNEL32.DLL', no matching symbolic
information
> > found.
> > Loaded 'C:\WINNT\system32\WS2_32.DLL', no matching symbolic information
> > found.
> > Loaded 'C:\WINNT\system32\USER32.DLL', no matching symbolic information
> > found.
> > Loaded 'C:\WINNT\system32\GDI32.DLL', no matching symbolic information
> > found.
> > Loaded 'C:\WINNT\system32\ADVAPI32.DLL', no matching symbolic
information
> > found.
> > Loaded 'C:\WINNT\system32\RPCRT4.DLL', no matching symbolic information
> > found.
> > Loaded 'C:\WINNT\system32\WS2HELP.DLL', no matching symbolic information
> > found.
> > Loaded symbols for 'C:\WINNT\system32\Msvcirt.dll'
> > The thread 0xC7 has exited with code 0 (0x0).
> > First-chance exception in omniNames.exe (NTDLL.DLL): 0xC0000005: Access
> > Violation.
> > The thread 0x59 has exited with code 128 (0x80).
> > The program 'D:\omniORB4\bin\x86_win32\omniNames.exe' has exited with
code
> > 128 (0x80).
> > ========================================
> >
> > Any ideas?
> > (Before I will be forced to further dig into it... Perhaps a debug
library
> > got mixed with non-debug ones? Or perhaps I get it wrong...)
> >
> > The result is the same regardless I use the binary distribution
> > (omniORB-4.0.0) or compile omniORB-4.0.0-latest (Sep 26). (I performed
the
> > standard non-debug build. The compilation on this machine is
> > successful. On
> > another Win2K system I get same problems with binaries and I can't
succeed
> > with building omniORB-4.0.0, but let's leave it out for the moment...)
> >
> > Regards,
> > Krzysztof
> >
> >
> >
> >
> > _______________________________________________
> > omniORB-list mailing list
> > omniORB-list@omniorb-support.com
> > http://www.omniorb-support.com/mailman/listinfo/omniorb-list
> >