Forum Replies Created
-
AuthorPosts
-
Sounds like you are doing it right using the Correlation to promote the Message Type on the send port.
Usually when I see this problem it is because of a namespace issue with the message or the schema. The map will use Message Type to match on the map. Also, might want to ensure you update the schema inside the map. Just in case it has changed.
Hope this helps.
Stephen W. Thomas
It has been a long time since I’ve worked with Array inside BizTalk. Support has been getting better for them… but I don’t think you can have more than one Complex Types as input for a web service call.
One work around would be to make the Web Service call in the .Net Helper class that you call from the Orchestration. Basically just wrap the call. This would remove the retry logic of using the Adapter though.
Hope this helps.
Stephen W. Thomas
Here are some sample that might help:
http://www.biztalkgurus.com/media/p/15506.aspx
http://www.biztalkgurus.com/media/p/15502.aspx
Hope this helps.
Stephen W. Thomas
You would need to set up a Convoy to receive all the messages one at a time. If you need them in order, you can enable Ordered Delivery on the Receive Port inside the Orchestration.
Inside the Orchestration, right after your Send Shape add a Delay Shape for 2 seconds.
That is probably the easiest way I could think of to accomplish this.
Hope this helps.
Stephen W. Thomas
August 6, 2009 at 2:46 AM in reply to: MSMQ "GetTempFileName Failed" error while receiving a message from a queue #22972Hi,
I’m getting same problem. bigger messages dont pass through MSMQ adapter.
MSMQ and Biztalk aplication ar installed on separate servers.
Could you point which servers “Temp” folder message is being copied to ?
August 5, 2009 at 10:22 AM in reply to: The published message could not be routed because no subscribers were found. This error occurs if the subscribing orchestration or send port has not been enlisted, or if some of the message properties necessary for subscription evaluation have not been pro #22970I was having this issue recently in one of my applications after i refreshed an application dll. It turned out to be that the receive pipeline was changed from XMLReceive to PassThru because the wrong pipeline was pre-configured in the orchestration…
So check your receive pipeline!!!
-Will B.
Env: BizTalk Server 2006 R2
I fixed it myself – by changing the web service namespace to match that of message coming in. re-referencing the Web Service to update the WSDL and it worked. I didn’t really want to do this as now all of my consumers need to deploy an updated agent with their apps because the namespace passed in the soap header no longer matches the new namespace of the web service … oh well!
increase time limit
Not by design but you can create a .Net helper class to execute Business Rules and then use it’s methods from your map via scripting functoid (external .Net assembly).
There may be some gotchas if you want to send the whole source document or it’s node-like parts into the rules. Same for returning multiple result objects. But still possible with some .Net scripting involved. You will not be able to assign values into resulting document directly within a rule though.
August 5, 2009 at 1:23 AM in reply to: Error with BizTalk Http Adapter and Custom Pipeline Component #22966I had also tried HTTP Adapter but thier is no access realted issues … why iam nt able to configure
August 4, 2009 at 4:31 PM in reply to: BizTalk Edi Application deleted (!) How to restore it? #22965some how, i didn’t show up in our server.., so I just reconfigured EDI/AS2, and it showed up
Thank you! That was very helpful.
One thing I have been doing with some spare time was go through the services and stuff that is running on the machine and shut down some of the crap that is running in the background.
Once I did this I managed to get the thing open again.
The one thing I have installed since I last worked on it is Office 2007
Anyway main thing is it opens and I can deal with it – thanks for all your help
Hi Rick,
I am wondering what changed on that machine in that timeframe to cause the IDE to crash when trying to open that particular orchestration. Is it happening for other orchestration files too?
I know this is time-consuming, but maybe, try to uninstall BizTalk and Visual Studio, and then re-install Visual Studio and BizTalk on the problematic machine, and see if this fixes the issue.
Good luck.
Hi Daniel
Thanks for the pointer – tried it and nada it failed again.
This is very frustrating as about 10 days ago I had two projects open and was comparing the orchestrations when checking something and now it is playing silly devils
It is really weird that there is just no error messages at all
-
AuthorPosts