Terminal Server blue screen after update (OpenInsight 32-bit Specific)
At 14 JAN 2003 12:14:42PM Dean Lowe wrote:
We just recently upgraded our OI32 to version 4.1.2. We have been running terminal server as a gateway from our Dallas office to our Houston office for our Novell server for OI about a year now without a problem. After the upgrade, whenever someone was in Terminal Server in the Dallas office and logged into the OI, it will crash our Windows 2000 server leaving a blue screen that says
STOP 0x000000D1
Driver_IRQL_LESS_OR_EQUAL. And if references a novell file NWSIPX32.sys. This was the only thing we have done as far as upgrades and no new hardware has been added to the server. Anyone have any ideas on this?
Thanks
Dean Lowe
At 15 JAN 2003 01:02AM Dean Lowe wrote:
Well we found our problem. After reverting back to version 4.02 the crashing stopped. What caused it was anytime someone was in OI in Terminal server on any version 4.1 and above, if the OI app was minimized and then tried to maximize it would cause the crash. Seems to have something to do with the conversion of the oengine.exe to a dll. My next question would be, is it possible to run verison 4.1.2 with the oengine.exe or does it need the dll?
At 15 JAN 2003 02:59AM Donald Bakke wrote:
Dean,
There are techniques for launching OpenInsight 4.1x to an out-of-process engine (i.e. not using a DLL). However, this may not solve your problem and most likely your performance will suffer suffer. I would recommend trying to resolve the problem another way if possible.
We have other clients using 4.1.2 on Terminal Server. I would have to assume that if this was a universal problem then they would have said something already.
Let me know if I can help in any way.
dbakke@srpcs.com
At 15 JAN 2003 10:25AM Jeff Miller wrote:
Don, are those people using the sever as a gateway or is OI running strictly off the 2000 server? I think that is a problem in itself because of the Novell. I am working toward moving entirely over to NT but I was hoping I could just do it with OI and not take AREV over and reconfigure the printing and deal with getting AREV to run properly since we still have people that are using it.
At 15 JAN 2003 11:46AM Donald Bakke wrote:
Jeff,
I believe Terminal Server is a client to another server in most of these situation, although that server is Microsoft and not Novell. I forgot that you are still running in that environment. Unfortunately, because you are on Novell this eliminates any way of running OpenInsight against an out-of-process engine because you need to be able to launch OENGINE.EXE on the server itself. Obviously Novell won't allow that.
Do you think the problem is Novell specific or whenever Terminal Server is used as a client/gateway into another server?
dbakke@srpcs.com
At 15 JAN 2003 01:58PM Jeff Miller wrote:
Novell is allowing the oengine.exe to execute off the Novell server and run through Terminal Server. It has been running that way for about 1 year. The problem comes in when the first update to OI which I think was 4.1 where the oengine was changed from an exe to a DLL. We went through each update starting at 4.03 and installed and tested each update. When we got to 4.1, it cratered. For some reason Terminal Server running as a client/gateway to a Novell server does not like that. When OI is running, if someone minimizes OI or opens another program and then tries to bring OI back to the front, it crashes. I don't think it is Novell specific because the Houston location can run the program fine, but they are accessing the Novell server directly and not using Terminal Server like the Dallas office is. It is really puzzling.
At 15 JAN 2003 02:05PM Donald Bakke wrote:
Jeff,
Novell is allowing the oengine.exe to execute off the Novell server and run through Terminal Server.
What I meant was to run OENGINE.EXE from a command line on the server. Since OENGINE.EXE is a Win32 app this can't be done directly on a Novell server (i.e. it's not a Novell executable, like an NLM.) This is what is required in order for OI to connect to an out-of-process engine and not use the DLL.
For some reason Terminal Server running as a client/gateway to a Novell server does not like that. When OI is running, if someone minimizes OI or opens another program and then tries to bring OI back to the front, it crashes. I don't think it is Novell specific because the Houston location can run the program fine, but they are accessing the Novell server directly and not using Terminal Server like the Dallas office is. It is really puzzling.
To be more specific, I don't think this is a Terminal Server issue but rather something specific in how Novell's gateway client works with Terminal Server. I'm trying to find out if anybody with a near similar configuration can duplicate your problem.
dbakke@srpcs.com