If you happen to be close to Oslo, Norway June 6th you should definitely attend this event The event is hosted by Microsoft Norway and is purely dedicated to BizTalk and especially BizTalk 2013. Here’s the agenda: 12.00 -12.30 welcome and a little inspiration around integrations. 12.30 – 13.15 Integration – from strategy to successful […]
Blog Post by: Tord Glad Nordahl
BizTalk Terminator is a very useful tool for troubleshooting common BizTalk issues. It also provides various tasks to view information like Spool Count and Orphaned Instances from the MsgBoxDB.
Sometimes while executing a Terminator task you might come across this exception
************************************************************
DataAccess::RunExecutionAsync: Invalid column name ’Relationship’. Invalid column name ’Relationship’
************************************************************
The Terminator tool works by executing WMI and SQL scripts against your BizTalk SQL Server.
In this particular case the ’View Spool Message Count of Instances’ executes a SQL script. You can view the script in the ’Description’ tab.
The script internally uses a table called TempMessageReferences to aggregate all the information needed to calculate the Spool count.
The table TempMessageReferences is created in the MsgBoxDB temporarily it is supposed to be created at the beginning of the Terminator script and dropped at the end.
In this particular case the script was failing because the TempMessageReferences table did not have a column called Relationship.
The table structure expected by the ’View Spool Message Count of Instances’ script is
but the one present in the MsgBoxDB was
The table name TempMessageReferences is used across various SQL scripts that the BTS Terminator uses. So in this case for some reason the TempMessageReferences table was created from a different SQL script (Terminator Task) and when the ’View Spool Message Count of Instances’ was being run it was failing.
To resolve this issue we just dropped the TempMessageReferences table from the MsgBoxDB and reran the Terminator task. Most likely two administrators had run a Terminator Task against the same BizTalk Cluster which overwrote the table.
The Terminator tool though very useful and easy to use has to be used with great precaution. I have personally seen a lot of administrators simply ignore the initial warnings of stopping the host instances, SQL Agent and backing up the DB.
Few tasks in Terminator under the View section, even though just query information create and drop tables in the MsgBoxDB. The tasks under the Delete and Manage section directly make changes to the tables that BizTalk uses.
Blog Post by: Shinva
UDDI Services provides Universal Description, Discovery, and Integration (UDDI) capabilities for sharing information about Web services within an organization’s intranet, between business partners on an extranet, or on the Internet. UDDI Services can help improve the productivity of developers and information technology (IT) professionals with more reliable and manageable applications. With UDDI Services you can […]
Blog Post by: Sandro Pereira
For BizTalk people probably you don’t need any introduction to Message Box Viewer. It became as the de-facto tool to analyse and fix any issue you find in your environment. The tool was initially built as hobby project by one of the Microsoft PSS (support) person called Jean-Pierre Auconie (JP) and over the years it’s […]
The post Message Box Viewer 13 included in BizTalk Server 2013 appeared first on BizTalk360 Blog.
Blog Post by: Saravana Kumar
BizTalk Adapter Pack 2010 along with BizTalk AppFabric Connect, RFID features, UDDI services and ESB Toolkit are not automatically installed with the default installation process, instead you have to additional install this features The Microsoft BizTalk Adapter Pack contains adapters that enable enterprise applications and databases to interface with each other by implementing a common […]
Blog Post by: Sandro Pereira
At a certain point in time when installing BizTalk, you will need to install some extra components. In the BizTalk installation wizard this is referred to as a prerequisite file.
This file can be downloaded automatically from within the wizard, but you might want to download them first. Here’s the list from BizTalk 2006 R2 up to BizTalk 2013!
I have run into an instance where I need to terminate and raise an exception from within an XSLT template, based on values (or lack thereof) within the source document. The XSLT transform is running within a BizTalk map. The secret is the following little-known XSLT construct, which can be conditionally called at any point […]
Blog Post by: Brett
After you configure with success BizTalk Server 2013 BAM Alerts, the configurator will create a new Database Mail Account called “BAM_Alerts_Account” that will be used by BizTalk to send BAM Alerts. To Validate Mail account used by BizTalk to send BAM Alerts: Press the “Windows key” to switch to Metro UI and type “SQL Management” […]
Blog Post by: Sandro Pereira
Normal
0
false
false
false
EN-US
X-NONE
X-NONE
Hello to the BizTalk community !
The last time I updated that blog to provide a new version of MBV is far but it took me a while to update MBV for BizTalk 2013 and collect ideas of new queries and rules to add.
For your information, a first version of MBV 13 is already provided in the support Tools folder of BizTalk 2013 !
I worked indeed with my US peers (a big thank to Mike Shea who is BizTalk Escalation Engineer in US) to produce that new version and we collaborated with the BizTalk Product group to integrate MBV in BizTalk 2013.
A first release of MBV 13 was so sent to the Product group well before the BizTalk 2013 release and since that time we continued to update the tool with additional queries and rules, and we had to fix some queries to make MBV fullly compatible with the final version of BizTalk 2013.
It is this last version of MBV 13 which is now available on my blog, and new update of MBV should be also available in each next BizTalk CUs.
MBV 13 provides the new features below :
MBV is now fully compatible with BizTalk 2013
MBV detects the new adapters provided and the additional BizTalk version, checks the build number features specific to BizTalk 2013.
New simplified UI
The graphic version of MBV was refreshed and its main window was reorganized to be smaller and easier to use.
The interface is more “flat” than before and provides so better clarity.
The format of output files changed
MBV is generating now by default a subfolder for each collect containing HTML files (and the XML and TXT ones depending of the selected options).
The output file named “MBVOutputMAINPAGE.html” is the main file to open to start the analyse of an MBV report and is composed of four frames : two of them present the list of the main report sections and the query categories, and the two remaining present the content of the selected section or query category.
This new format makes much more easy the analyze of an MBV report.
Additional queries and rules
Additional queries were added in MBV 13 about CUs, SQL, BAM, ESB, EDI, etc…
These queries and rules come from all the BizTalk community at Microsoft and my experience working with my own customers, but also from customers themselves who suggested me some ideas.
You are of course welcome to contact me to suggest queries and rules if I think they are pertinent for all the BizTalk community.
You can find this new version attached in that post.
I will continue updating MBV and its query repository,following the CUs update cycle and adding some critical rules when needed. The pertinence of MBV analyze is the key of success of that tool and comes from its queries and rules.
As usual, feel free to report me your feedbacks or submit any issues,questions or suggestions you could have about MBV.
Thanks !
JP
Jean-Pierre Auconie
Premier Mission Critical Engineer and BizTalk Escalation Engineer
MCROSOFT FRANCE
jpierauc@microsoft.com l
Blog Post by: JPAUC