PDA

Click to See Complete Forum and Search --> : DLL not running in separate memory space on IIS server


ramdasv
Dec 27th, 1999, 05:29 AM
I have created a webclass DLL and deployed in an IIS server. It is working fine when I access the site from any other machine using IE.
When I set the directory property to run in separate memory space and try to access from the remote mechine it hangs the server. When I go the task manager in server It is found that MTX.exe is running occupying the available memory and CPU.
I had to restart the server to regain control of the server.

D0 I have to change some settings in my application or is it some code in my application that is creating the problem.

Advance thanks

Ramdas

Clunietp
Dec 27th, 1999, 10:22 AM
Something in your code must be the problem... When you tell IIS to run your app in a separate memory space, it creates a package in MTS which contains your app.

If your code was in some sort of loop, it would show that MTX (MTS Executable) was the problem, but it is really your app because your app runs within a MTS process.

HTH

Tom

ramdasv
Dec 28th, 1999, 05:47 AM
I dont have any code that loops.
My application has a class module that access data from sql server, a logging module that logs error and events to a xls file and necessary htm templates.
Since the event log is there I would be able to find if any of the function are executing repetitively, which is not happening
Mtx.exe is keeps on running and the screen which makes the request hangs.
I tried to put my application as a mts package and then deployed. This time I was able to access the first page but soon it hanged and I had to restart the server.

Any help regarding this would be appreciated.
thanks

Clunietp
Dec 28th, 1999, 12:23 PM
Some info here: http://support.microsoft.com/support/kb/articles/Q189/5/39.ASP

Also, from MS site:

No Support for Transacted Web Classes
-------------------------------------

Transacted Visual Basic Web Classes are not supported in Visual
Basic 6.0.

ramdasv
Dec 30th, 1999, 01:47 AM
Thanks for that