Hi all
I'm actually a DBA but our entire team is researching our problem.
We use SQL 2000, ASP, W2K Server, IIS 5.0 and COM+.
We have an issue with our application where the objects are being "stolen" between sessions/processes. Eg. In one session your logon info is domain\john and then another session opens the object and the user is domain\paul but the new session takes domain\john as the logon user.
We have enabled Retain In Memory and Unattended Execution and recompiled all the dlls. We have rebooted the server and still have the same errors. We have gotten hold of Microsoft and they suggested the above compilation options and put us in touch with their back office specialist who is 1000kms away from us so the communication is slow.
Has anyone run into this or have any ideas? Are we overlooking IIS settings or options? As I mentioned I'm a DBA so my IIS/COM+ knowledge is limited and I do apoligise if my explanation isn't all that clear.
Any help would be appreciated.
Thanks
John
I'm actually a DBA but our entire team is researching our problem.
We use SQL 2000, ASP, W2K Server, IIS 5.0 and COM+.
We have an issue with our application where the objects are being "stolen" between sessions/processes. Eg. In one session your logon info is domain\john and then another session opens the object and the user is domain\paul but the new session takes domain\john as the logon user.
We have enabled Retain In Memory and Unattended Execution and recompiled all the dlls. We have rebooted the server and still have the same errors. We have gotten hold of Microsoft and they suggested the above compilation options and put us in touch with their back office specialist who is 1000kms away from us so the communication is slow.
Has anyone run into this or have any ideas? Are we overlooking IIS settings or options? As I mentioned I'm a DBA so my IIS/COM+ knowledge is limited and I do apoligise if my explanation isn't all that clear.
Any help would be appreciated.
Thanks
John
