Hi Every body,

I have develped an ASP.NET Application that works fine locally on my windows XP; however once deployed to production environment which is Windows Server 2003.. the thread function does not work and even kills the sessions.

I hope some one can help in this issue; It could be some settings to the IIS or asp.net acount privilges or windows server 2003 itself.

All the features and function of the application works fine in both environments except for the thread thing.

Thank you in advance.  

aalamer:

Hi Every body,

I have develped an ASP.NET Application that works fine locally on my windows XP; however once deployed to production environment which is Windows Server 2003.. the thread function does not work and even kills the sessions.

I hope some one can help in this issue; It could be some settings to the IIS or asp.net acount privilges or windows server 2003 itself.

All the features and function of the application works fine in both environments except for the thread thing.

Thank you in advance.  

Hi,

According to your description, it is hard to detect where the problem is. Actually, I would strongly like to suggest you posting this issue to Microsoft IIS forum, since the problem is much related to IIS setting.

Here are the links of the sections [General Discussion of IIS 5.x & 6.0] and [Troubleshooting of IIS 5.x & 6.0]: http://forums.iis.net/1029.aspx & http://forums.iis.net/1039.aspx. Hope this helps.

Best Regards,
Shengqing Yang

>All the features and function of the application works fine in both environments except for the thread thing.

Does the function part exist as a separate class project?

If so try the following:

• Write a harness application to check the function will run on the Windows Server 2003 run by an admin account
• Write a windows service to call the function (non-threaded) on the Windows Server 2003 run by an service account

Do you use Custom Event Logging?

If so, instrument up your application to write trace messages to the custom event log around the threading code. Put try...catch around suspect code and in the catch, log the exception and rethrow.