One of our guys came up across this error recently on a system we have been developing for one of our clients.  It's not en error that I have seen before so I thought it worth mentioning.  The full error was:

The InboundTransportLocation is disallowed. This could be because the receive location is disabled or its service window is currently inactive.

It took us a bit to figure out (i think about 10 minutes combined), and it turns out that the document that we were receiving was invalid and we were using an XMLReceive pipeline with the AllowUnrecognisedMessage property of the pipeline set to False.

So, yeah, this was the correct message.  Ideally, this is a scenario you don't run in to much, as in the perfect world you always receive valid documents.  I guess we all know that is a bit of a pipe-dream.

Bookmark with :
Digg It! DZone StumbleUpon Technorati Reddit Del.icio.us Newsvine Furl Blinklist
posted @ Friday, April 27, 2007 12:04 PM | in BizTalk Server

Comments

Gravatar
# re: The InboundTransportLocation is disallowed
Posted by vijay
on 7/5/2007 9:10 PM
first time i resume the all suspended messages from Admin console on that time receive port was disabled, after enable receive port itried to reseume the suspended messages again i'm getting this error The InboundTransportLocation is disallowed. This could be because the receive location is disabled or its service window is currently inactive
Gravatar
# re: The InboundTransportLocation is disallowed
Posted by Matt Nield
on 7/9/2007 9:00 AM
Vijay, did you check that the documents being received are valid and recognised in the receive pipeline?

Perhaps if you supply a little more information about the documents that you are sending and you set-up, I could have a look?

Post Comment

Title *
Name *
Email
Url
Comment *  


Please add 5 and 5 and type the answer here: