I just installed Universal Driver 4.5. There is one OI 9.0 app and one AREV32 app in our environment. My users have no problem getting to thier OI app using a desktop shortcut. Trying to open the AREV32 app from a shortcut gives only a blank window with black background and one menu choice "edit" in the upper left corner. Seems as though the AREV32_STANDALONE_WINDOW is failing. What do I need to do?

Thanks,

Jim

Check that the required controls are registered on the workstation. In particular the rvcmdctl.ocx file.

The article OpenInsight 9.0 Workstation Installation Notes has more information about the required controls.

OpenInsight 9.1 includes a client installer to automatically register all the required controls and components on a new workstation.

Thanks Jared,

rvcmdctl.ocx is registered on the cient. What should I look for next?

Jim

Hi, James. Originally you were writing about seeing the username and password prompt, and not being able to log in. Has your problem changed into what you describe here (a blank window), or do you now have both problems?

The first problem you saw (the username and password prompt coming up and not being able to log in) sounds to me like the standalone form attempted to start a new engine (as it should), but that the engine creation failed. After a number of these attempts, you might have some 'orphan' OEngine's running on the server (they were started, but never connected); further attempts at connection might 'block' while trying to access these OEngines, resulting in the blank screen. If you go to 'task manager' on the server, do you see an entry (or entries) for oengine?

For diagnostic purposes, I would suggest you run the Engine Server in 'debug' mode. This can be done by opening up a DOS command prompt window on your server, moving into your OI directory, and running:

java -jar oesocketserver.jar -d 3

(Note that you'll have to stop the Engine Server service if it's running, first).

You should then be able to see when the AREV32 standalone form attempts to connect. If you do _not_ see any connection attempts displayed in the DOS box when you start the standalone form, then your SYSENV CTO record might not be pointing to the proper location for your engine server, or you might have some port blocking between the client and the server.

If you see the connection attempt, but it fails to connect, there may be useful information in the debug display; please copy and paste it so I can see what it says?

Thanks,

- Bryan Shumsky

Revelation Software

Thanks Bryan,

Yes I am having both problems.

I stopped the OI engine in services and I'm running the engine in debug mode but not seeing any activity except the Cleanup task running ever minute or so. This is true even when I successfully run another OI app - different from the AREV32 app but running from the same Open Insight.exe. What am I doing wrong?

Jim

Hi, Jim. Running OpenInsight does not use the EngineServer, so successfully running OI doesn't impact what's going on here.

The fact that you don't see any "chatter" in the DOS command box tells us that your client is not talking to the Engine Server (assuming you did start up the 'java' command line with the '-d 3' part at the end). The things to look at include:

1. The CTO configuration record

The record named CTO in SYSENV specifies the IP and port of the engine server. It can be overridden by a record named CTO in the MD table of the application, and _that_ can be overridden by a record named CTO* in the MD table. So, if you're running as user TESTUSER in application TESTAPP, the records that control CTO configuration would be:

  CTO*TESTUSER in the MD table in TESTAPP

  CTO in the MD table in TESTAPP

  CTO in SYSENV

Unless you specifically created the 'override' records, you'll most likely need to only concern yourself with the SYSENV CTO record. What is in field 1 and 2 of this record? It should contain the IP address and port # of the Engine Server.

2. Firewall Issues

Assuming your appropriate CTO configuration record is indeed pointing at the EngineServer address and port number, perhaps something is 'blocking' that port on the server.

Those are the first two things I'd look at to address this.

Hope that helps,

- Bryan Shumsky

Revelation Software

View this thread on the forum...