We have encountered an issue and can't get past it.  We have a few
orchestrations deployed as  web services on our development BizTalk server
and none of them are able to send the send response back to the application
that is consuming the web service.

The request does make it through properly to BizTalk and the orchestration
works as it should including sending out the proper response according to HA
T
Orchestration Debugger.  The orchestration gets a "Complete" status in HAT.
An error is logged to event viewer as follows:


Event Type: Error
Event Source: SQLSERVERAGENT
Event Category: Alert Engine
Event ID: 318
Date:  12/14/2005
Time:  8:54:20 AM
User:  N/A
Computer: WGBT01
Description:
Unable to read local eventlog (reason: The data area passed to a system call
is too small).

For more information, see Help and <st1:place w:st="on"><st1:PlaceName
w:st="on">Support</st1:PlaceName> <st1:PlaceType
w:st="on">Center</st1:PlaceType></st1:place> at
http://go.microsoft.com/fwlink/events.asp.


We haven't found any helpful information about this error.  All hits seem to
indicate that this is a somewhat bogus error and that something else is
causing the error to be written to event viewer.


On the client that consumed the web service, it eventually times out since a
response is never returned.  It fails here, waiting for the response

object[] results = this.Invoke("AcceptCompositonRequest", new object[
;]
{TXML});

In the IIS log file we got the folliwng logged

2005-12-14 16:52:43 172.25.75.116
POST
/WGEB.PrepressComposer.Orchestrations_Proxy/WGEB_PrepressComposer_Orchestrat
ions_OEPreview_ComposerRequestPort.asmx
- 80 - 172.25.2.123
Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+1.1.4322.
2032) 500 0 64

We did deploy a simple C# web service to this server and do get a response
back as expected.  So, we are thinking it is a problem where BizTalk hands
off the request back to IIS.  We just can't determine what the problem is.

Any thoughts or suggestions from anyone?

Thanks,

Laura

[ Post a follow-up to this message ]