Maybe someone would provide advise on the best way to handle a situations that I encountered tonight. In rebuilding indexes in OI, the system broke to debugger (message something about divide with zero). After this, nothing in OI worked. Regardless of what I click, I would get a message that "Another process has exclusive access to the engine or the debugger has suspended engine execution…." At this point I was forced to "kill" the OpenEngine via the Task Manager undre NT. However, OI warned me that "Shutting down OpenEngine while tasks are running can cause unpredictable behavior…"

I shut down OE. After this, when I tried to get back in to OI, I got a message that "OpenInsight Bootup Failed." I could not get back in. I took my backup and did a restore. Even with this I still could not get back in. I rebooted my computer and voila. I could again access OI and my "new" application.

As you can image, I was a bit concern. What the best way to handle such a situation as described above.

Also, what does "Database template missing in SYSENV table" mean?

Thanks for any input. Someone posted a message regarding posting bugs reports. I think that would be a good idea.

Ray-

When your running OpenInsight on NT, you can look in the Task Manager under processes, and locate oengine.exe. It should be found under an NTVDM image. You should also see under the same image oinsight.exe and wowexec.exe. When you shut down Oengine and Oinsight, the wowexec is still running, and you can't launch another OI. If you also shut down Wowexec you can launch OI again.

Hope it helps-

Mike Ruane

Since you are running on NT, you can run multiple sessions of OI by running each one in a seperate memory space. Every now and again, the sessions get confused as to which OI/OE combo it should be talking to, but this gets better as MS fixes bugs in NT and RTI moves more things into PS.

As for the database template missing in SYSENV, all the information needed to load the application is stored in records in SYSENV and SYSAPPS. Depending on how you crash, OI is able to load, but cannot make the connection to OE. Since it needs OE to retrieve this information, you will get this error.

Usually this will require a session closing, a reboot, or a look at network settings. If none of these work to solve, you'll have to load OE first and try and work through where the connection problem is.

The Sprezzatura Group

[/i]World leaders in all things RevSoft[/i]

Thanks again for your expert commentary.

I shall file this tibit away and look for the mysterious file. Hopefully, I won't have to.

As I become more involve in OI, I can see some of its darker side. I hope that RTI will attend to some of these stability issues (or quirks ???) in 3.8.

Forward march and hope the road isn't too bumpy. Otherwise,…

Dear MSG,

I was re-reading an earlier response that you provided to one of my earlier question. In your response, you indicated you ran multiple OI sessions under NT.

How do you do this? When I try to do this, I get a message:

"Cannot start a new application without command line switch?"

Thanks much.

Check the run in seperate memory box.

The Sprezzatura Group

[/i]World leaders in all things RevSoft[/i]

Dear Mr.SG

The solution was too easy. But that's the kind of guy I am. I like easy problems with easy solutions.

Is this the way of OI ? I hope so.

Thanks.

View this thread on the Works forum...