, , , , ,

Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community

Citrix, DEP & 4.6 (OpenInsight 32-Bit)

At 04 NOV 2010 07:49:50AM Martin Drenovac wrote:

I have a curious situation.

Deploying our first 9.x app onto Citrix. App starts, presents our MDI, we wait a few seconds and the app dies. After a couple of runs, we logoff. Disconnect from Citrix. Come back in. The system gives the OINSIGHT failed do you want to send this to MSOFT memory dump.

So, I track to the dump file and out of one of the listings there is this line:

Stage1URL=/StageOne/OINSIGHT_exe/0_0_0_0/lh46clnt_dll/0_0_0_0/0000832f.htm

ErrorSubPath=OINSIGHT.exe\0.0.0.0\lh46clnt.dll\0.0.0.0\0000832f

How can I set OI to log where it is in its exec cycle - mind has gone blank?

My lh46clnt.dll is dated 26/06/2009 size 155,648.

Any & all tips on how to debug where my world is crashing greatly appreciated.

Cheers


At 04 NOV 2010 08:32AM Jared Bratu wrote:

Did you remember to install the LinearHash service and place a REVPARAM file in base of all common directory paths where .LK/.OV files are stored?

Are the database files on the Citrix server or another machine?

Is oinsight.exe on the Citrix server or another machine?


At 04 NOV 2010 09:39AM Martin Drenovac wrote:

Jared - all of the files are on the one machine, the one we link into.

I've not installed an LHSERVICE as this is only a pilot and the customer has not purchased the application.

There is no revparam file of any form in the directory, should I have one with serveronly=0 installed?


At 04 NOV 2010 10:05AM Jared Bratu wrote:

The LinearHash service and Universal Driver are required for any multi-user access from OInsight or OEngineServer.

The Network Product Matrix was recently updated with currently supported configurations. http://www.revelation.com/knowledge.nsf/d397fbbab8ac707185256dd600218f18/3f8813a5cfd57e5085256f34006ad4ae?OpenDocument

In the past, the type of setup you're attempting was possible with the All Networks Driver. The All Networks Driver would go into cooperative byte range locking mode when the LinearHash service wasn't available. Since the All Networks Driver is no longer supported in OpenInsight 9.x this configuration is not possible.

Install the LinearHash service and configure the REVPARAM file OR stick to one instance of OInsight.exe/OEngineServer at a time.


At 04 NOV 2010 05:02PM Ray Chan wrote:

What Window Server version are you running. I see that you have DEP in your subject line. Have you disable DEP?

Ray Chan


At 08 NOV 2010 06:09PM David Goddard wrote:

G'day Martin,

Either change the network driver to the All Networks V2.1 or turn off DEP on the server or add oinsight.exe, oengine.exe and oengine.dll to the list of programs that DEP will ignore.

If you choose changing the DEP settings then you will need to remove your app and then copy it back again as I have found that once DEP flags a process as banned, it will stay that way regardless of how much you change the DEP settings. Windows must do something to the files so that it knows not to run the program again. Deleting your app and copying it back again fixes this.

regards

Dave G


At 09 NOV 2010 09:21PM Richard Hunt wrote:

You might want to check the security permissions of the folder that OI is installed in.

Basically I have all the boxes checked except for "special permissions".

And check the advanced security settings so that the "apply to" column has "this folder, subfolders and files".

Also uncheck both the "Allow inheritable permissions…" and "Replace permission entries…".


At 10 NOV 2010 08:20AM Jared Bratu wrote:

If you're concerned about the NTFS permissions on the OpenInsight directory there are two knowledge base articles that will be helpful. The first gives complete examples of how to prevent users from deleting and changing files inside the OpenInsight directory.

http://www.revelation.com/knowledge.nsf/07dbcbabb6b3e379852566f50064cf25/0c73cbc52264a1058525765600459b64?OpenDocument

The second goes even further and sets the file permissions to prevent users from being able to access the .LK/.OV files at the operating system level.

http://www.revelation.com/knowledge.nsf/07dbcbabb6b3e379852566f50064cf25/534eb50960c214ce8525778c00488083?OpenDocument

Removing "Allow inheritable permissions" could have undesirable results and should be done with caution.

View this thread on the Works forum...