OECGI2 going nuts - what's the secret? (OpenInsight 32-Bit)
At 29 AUG 2007 06:37:25AM Matthew Jones wrote:
Having got over the login failure problem, I am going absolutely nuts with this oecgi2!
If I set everything up as the defaults, I can get a connect.
If I change the port to 8089 as per examples, I get "Unable to connect to Engine Server localhost:8088 - The attempt to connect was forcefully rejected"
Yes, I have changed the registry settings for port 8089.
Yes, I have changed the eserver.cfg file PortNumber setting to 8089.
Yes, I have stopped the OEngineServer service and restarted it.
If I do a netstat -an ?find /i "listening" I see that my server is actually listening on the port I want.
But it doesn't get through - arrrgh!
Any help / advice / suggestions gratefully received.
Matthew Jones.
More info - if it helps - if I keep the default setup and try to setup a separate IIS virtual directory (as per the instructions) that points to a different server, when I go to the browser and try the new address with the virtual directory I get sent back to the default setup!
At 30 AUG 2007 07:58AM Matthew Jones wrote:
I'm using Windows Server 2003 x64.
It seems oecgi2.exe is not reading the registry on the server at all.
If I put an application, username and password into eserver.cfg, and listen on port 8088, it works!
I can change the OECGI2 key name in the registry to something completely invalid, and it makes no difference.
As long as the info is ok in eserver.cfg, it works.
I can change any setting in the registry and it doesn't see it, such as url etc.
Obviously this is a problem, because I'm restricted to port 8088, and to working locally on the server, one application only.
Has anyone else out there in RevLand got oecgi2 working on Windows Server 2003 x64 version, and using a different port other than 8088, or a different url other than localhost?
If so, was there something specific required in setup?
RevGuy? SRP? Sprezz?
Cheers,
Matthew Jones.
At 31 AUG 2007 05:36PM Richard Bright wrote:
Just a couple of reflections
1. Sometimes get problems because of resolution of the path to virtual directory etc may be different for different clients issue with DNS.
2. Firewall passing port?
From my Registry I have
HKEY_LOCAL_MACHINE\SOFTWARE\RevSoft\OECGI2\EXAMPLES
"UserName"=EXAMPLES"
"UserPassword"="
"ApplicationName"=EXAMPLES"
"ServerURL"=localhost"
"ServerPort"=8088"
"ProcedureName"=RUN_OECGI_REQUEST"
"EngineName"="
"FileName"="
"FilePath"=\"
and similar entries for other applications.
Note" "localhost" could also be IP address or HostName or full.host.DomainName - depends on context
At 31 AUG 2007 06:14PM Bob Carten wrote:
As I recall there are 2 issues:
1 - Install 32bit java, not 64, else socketserver fails.
2 - Put the registry settings in the 32bit virtual (WOW64) registry
I don't remember the exact regedit commands.
See this MSDN article about
[url=http://msdn.microsoft.com/library/default.asp?url=/library/en-us/win64/win64/running_32_bit_applications.asp]running_32_bit_applications[/url]HTH
Bob