by community-syndication | Apr 5, 2007 | BizTalk Community Blogs via Syndication
Environment:
– BizTalk 2004 works on the CORPBTS1 server (Windows Server 2003)
– SQL Send ports send the messages to the SQL 2000 DB on the CORPNT5 server .
After installing the SP2 for Windows Server 2003 I’ve got the events:
“
Event Type: Error
Event Source: BizTalk Server 2004
Event Category: BizTalk Server 2004
Event ID: 5754
Date: …
Time: …
User: N/A
Computer: CORPBTS1
Description:
The “SQL” adapter is suspending an outbound message going to destination
URL:”SQL://CORPNT5/Prod/“. Details:”New transaction cannot enlist in the specified transaction coordinator. “.
…
“
When I try to Refresh the SQL Adapter Receive/Send handlers I’ve got the errors that something wrong with Distributed transaction coordinator (DTC).
More interesting was that I work with database on the CORPNT5 server through the .NET code from the map (with the Enterprise Library), and this works fine!
The problem was resolved when I changed on the CORPBTS1:
Administrative Tools \ Component Services \ My Computer \ Properties \ MSDTC \ Security Configuration \ Transaction Manager Communication \ “Mutual Authentication Required” –> “Incoming Caller Authentication Required”
by community-syndication | Apr 5, 2007 | BizTalk Community Blogs via Syndication
Recharge the batteries and look out for that Rabbit 🙂
I’m back from Perth survived the ‘Red-Eye’
Take care,
Mick.
by community-syndication | Apr 5, 2007 | BizTalk Community Blogs via Syndication
Environment:
– BizTalk 2004 works on the CORPBTS1 server (Windows Server 2003)
– SQL Send ports send the messages to the SQL 2000 DB on the CORPNT5 server .
After installing the SP2 for Windows Server 2003 I’ve got the events:
“
Event Type: Error
Event Source: BizTalk Server 2004
Event Category: BizTalk Server 2004
Event ID: 5754
Date: …
Time: …
User: N/A
Computer: CORPBTS1
Description:
The “SQL” adapter is suspending an outbound message going to destination
URL:”SQL://CORPNT5/Prod/“. Details:”New transaction cannot enlist in the specified transaction coordinator. “.
…
“
When I try to Refresh the SQL Adapter Receive/Send handlers I’ve got the errors that something wrong with Distributed transaction coordinator (DTC).
More interesting was that I work with database on the CORPNT5 server through the .NET code from the map (with the Enterprise Library), and this works fine!
The problem was resolved when I changed on the CORPBTS1:
Administrative Tools \ Component Services \ My Computer \ Properties \ MSDTC \ Security Configuration \ Transaction Manager Communication \ “Mutual Authentication Required” –> “Incoming Caller Authentication Required”
by Richard | Apr 5, 2007 | BizTalk Community Blogs via Syndication
Convoying is one of BizTalk’s real strengths but it has a lot of pitfalls (I’m talking performance, zombies etc). This article is really good at explaining the different patterns used for creating convoys. It also makes some deep dives into how the subscriptions are solved, why zombies are created and how to deal with them.
Even if you feel you understand the convoy patters from before the part about how BizTalk solves the subscriptions for correlations (the part called Basic Convoy Theory) is great.
Using sequential convoy to handle ordered delivery
A big selling point in BizTalk 2006 is it’s ability to handle Ordered Delivery. It’s important however to understand that this setting (on the Receive and Send port) only works in a pure messaging scenario (a scenario without orchestration, just passing messages between ports). To get order delivery in a scenario using orchestrations one has to use the sequential convoy pattern (basically forcing the orchestration to only one instance on one thread). This Webcast explains this in depth and also deals with some of the different problems that are related to the issue. Problems like performance of course, but also the requirement for receive adapter (on the send side all adapters support ordered delivery) for enabling ordered delivery (you’ll have to use MSMQ, MQSeries or specific scenarios of File, SOAP or HTTP).
Both convoying and ordered delivery are important concepts to understand in depth to be able to make the right decisions in a BizTalk 2006 solution.
by community-syndication | Apr 5, 2007 | BizTalk Community Blogs via Syndication
Convoying is one of BizTalk’s real strengths but it has a lot of pitfalls (I’m talking performance, zombies etc). This article is really good at explaining the different patterns used for creating convoys. It also makes some deep dives into how the subscriptions are solved, why zombies are created and how to deal with them.
Even if you feel you […]
by community-syndication | Apr 4, 2007 | BizTalk Community Blogs via Syndication
I was trying to signup for a service, and I was prompted the following form to fill out.
I’m afraid I’m not human anymore.
Any other human out there who can help me?
by community-syndication | Apr 4, 2007 | BizTalk Community Blogs via Syndication
To access R2 Public Beta, please follow these instructions:
Sign in using your passport
Click on Available Connections (on the Connect Home menu)
Scroll down to the Programs table (shown below)
Apply for BizTalk 2006 R2 Beta program
Program |
Nomination Start Date |
Nomination End Date |
Options |
BizTalk 2006 R2 Beta |
4/2/2007 |
8/1/2007 |
Details Apply |
You’ll immediately get access to the R2 public beta site and download.
Marjan
by community-syndication | Apr 4, 2007 | BizTalk Community Blogs via Syndication
Last January 31th my good friends Javier and Carmen Mariscal were blessed with the birth of their second son, Daniel Mariscal. After two months, the baby got his first exposure to the Microsoft world. DO NOT make any assumptions about the finger; he is…(read more)
by community-syndication | Apr 4, 2007 | BizTalk Community Blogs via Syndication
I recently had reason to revisit the exact mechanisms Microsoft use when you assert facts to the Microsoft Rules Engine. I was discussing stuff on-line with a fellow rules enthusiast when a terrible thought occurred to me. Can the MS BRE always uniquely identify each different fact, or is there a chance that sometimes it might confuse two facts with each other?
For a couple of days, I was convinced that I had stumbled on a significant bug. Indeed, at one point, I thought there was such a serious problem that I would have to recommend to my company that we desist from any further use of Microsoft’s rules engine. Melodramatic, huh! Fortunately, after a bit more research, I discovered that I was quite wrong. The MS BRE does not suffer from a terminal flaw and can be trusted to always distinguish correctly between all your facts. It’s worth recording my suspicions, mistakes and eventual enlightenment. There is something useful to learn, here, about the inner workings of the engine, and also about Microsoft’s implementation of the Hashtable class in .NET.
Read more at http://geekswithblogs.net/cyoung/articles/110852.aspx
by community-syndication | Apr 4, 2007 | BizTalk Community Blogs via Syndication
84% it wasn’t that bad, but it should have been easy after 3+ years working with BizTalk, lots on BAM and the BRE. I think I lost marks on the drag and drop questions and there was a tricky question on coding a BRE fact retriever. I used Saravana’s exam preparation diary.
