Hi All,
      We have a developed a site using Dotnet. We have asp.net pages
interacting with Vb.Net assemblies which are COM+ enabled. The whole
site works fine. We have several Nigthly batch processes which refer
the same assemblies. Even these batch process run perfectly fine. Now
the problem arises when both of these are run simultaneously the Site
becomes unavailable.
     
     I feel that the batch process which runs in a loop performing
several operation on the Database records is locking the COM+
transaction context, which causes the site to go down.
   
     We have set the transaction context to "Required" in COM+, also
all the standard setting required for executing a COM+ transaction are
done. But still something is missing which causes such a behaviour.
 
     Can someone help me out and put some light on this matter.
Thanks in advance

Thanks and Regards,
Hemant