OECGI with mapped drive (OpenInsight 32-Bit) [Revelation On-Line Wiki]

OpenInsight 32-Bit, Rudhy B, //www.sprezzatura.com]The Sprezzatura Group[/url], Wayne Shepard

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

At 25 JUN 2003 05:17:11AM Rudhy B wrote:

I am using IIS v5.1 accessing mapped drive (win2000 server).

I manage to create a virtual directory using the UNC \\Optikseis\Drive-G\Revsoft\Oinsight.

What should I put under the WorkingDirectory in the registry ?

If i put WorkingDirectory=g:\revsoft\oinsight, it gives me the following error message (in IE):

OECGI SetCurrentDirectory failure

If I put WorkingDirectory=\\Optikseis\Drive-G\Revsoft\oinsight the computer just beeps and does nothing (in IE)

Rudhy

At 25 JUN 2003 05:46AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:

Does Pat's response help here?

The Sprezzatura Group

World Leaders in all things RevSoft

At 25 JUN 2003 09:43AM Rudhy B wrote:

I read that Microsoft Article. It helps me in setting the virtual directory using mapped drive under IIS.

But I think the problem is now on how to set the registry value for WorkingDirectory.

Rudhy

At 25 JUN 2003 01:57PM Wayne Shepard wrote:

The usual problem is that OECGI is starting an OENGINE which is using the Data Manager to attach your data files. Unfortunately, the data manager uses mapped drives to attach the files and the execution space it is operating in has no drives mapped. A way to test for this is to unmap all drives containing OI data and try running OpenInsight from the Command Line. You should see the error message.

If this is your situation, the solution is to eliminate the Data Manager. Remove all files that are defined in your application that don't reside in REVBOOT from your attach-image via the Data Manager. Then write a startup program that uses Attach_Table to attach the files you want. Attach_Table will accept UNC addressing. Make this program run at startup by entering the name and account in the format progname*account in field 32 of the applications ENV_ record in SYSENV.

Another possible problem is that you don't have a SYSPROG user defined in your app. Apparently, the OECGI logs in as SYSPROG regardless of what user name you might enter in the registry settings. So you have to make sure you have SYSPROG enabled as a user.

Wayne Shepard