|
Home > Archive > BizTalk Server General > June 2004 > Submit adapter troubleshooting
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 |
Submit adapter troubleshooting
|
|
|
|
I'm running BTS04 on Windows 2003 Server and I'm trying to use the submit adapter that comes with the SDK.
I'm using the debugger, and the instant I step into the IBTTransportBatch.SubmitMessage call, I get the following runtime error:
************** Exception Text **************
System.Runtime.InteropServices.COMException (0xC0C0164B): Exception from HRESULT: 0xC0C0164B.
at Microsoft.BizTalk.TransportProxy.Interop.IBTTransportBatch.SubmitMessage(IBaseMessage msg)
[...]
********
Can anyone tell me if there is a way to figure out what that exception code represents?
Thanks in advance.
| |
| Allen Zhang 2004-06-09, 5:01 pm |
| 0xC0C01648 is "The InboundTransportLocation is dissallowed. This could be
because the receive location is dissabled or a service window is currently
active. " The same error message should have been logged in the Eventlog.
You will need to enable the receive location in the BizTalk Explorer.
- Allen Zhang (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------[vbcol=seagreen]
I'm running BTS04 on Windows 2003 Server and I'm trying to use the submit
adapter that comes with the SDK.
I'm using the debugger, and the instant I step into the
IBTTransportBatch.SubmitMessage call, I get the following runtime error:
************** Exception Text **************
System.Runtime.InteropServices.COMException (0xC0C0164B): Exception from
HRESULT: 0xC0C0164B.
at
Microsoft.BizTalk.TransportProxy.Interop.IBTTransportBatch.SubmitMessage(IBa
seMessage msg)
[...]
********
Can anyone tell me if there is a way to figure out what that exception code
represents?
Thanks in advance.[vbcol=seagreen]
| |
|
|
Thanks Allen.
The message in my event viewer was actually this one:
'The Messaging Engine did not recognize the InboundTransportLocation:"submit://submitmessage". Check the receive location configuration.'
However, it appears that all I needed to do was enable the receive location, as you said.
Thanks again
|
|
|
|
|