Hi,

I have an ActiveX Exe running under IIS (singelton), hooks to the running instance of the EXE are created every time somebody logs in. If the EXE is not running, the first request creates the EXE in memory. This all works fine, however, sometimes we get 2 instances of the EXE running in memory and this causes allsorts of issues. More than likely this is caused because of an error or something telling IIS that the EXE is not running/inaccessible ?

Can anyone help with an article or something that could help me trace this ?
Would placing the ActiveX in legacy components in Out of PRocess components in IIS help in any way ?

Need only one exe to be running at any one time....

Many thanks for reading.

Chubby.