BizTalk Server Orchestration - Isolated adapter dehydrated instances

This is Interesting: Free IT Magazines  
Home > Archive > BizTalk Server Orchestration > May 2005 > Isolated adapter dehydrated instances





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Isolated adapter dehydrated instances
biztalker

2005-05-26, 5:54 pm

Hello,

For the dehydrated instances of Isolated adapter that have been appearing in
HAT for quite some time, what is the proper way of terminating them? Does IIS
need to be restarted? In some events, it has been noticed that terminating
such instances has caused problems whereby the senders to an HTTP or SOAP
receive location start receiving 'Internal Server 500' error code. Can anyone
provide or point to more information as to why this happens?

Thanks
Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com