Microsoft Servers

BizTalk Orchestration State Serialization

Saqib Ullah — Sun, 30 Sep 2007 22:58:10 GMT

In the production servers BizTalk Orchestration some time takes long phase to finish the complete business process.

Scenario:
Like An employee might wait several days or weeks to approve for vacations.

This means that the orchestration will also be in a waiting state for a very long time and its mean taking up resources on the server. BizTalk Server automatically stops the active orchestration instance and save the orchestration instance state into a SQL Server database in the serialized form and this process is called ‘Dehydration’. The orchestration engine might determine that a dormant orchestration instance has been idle for relatively long period of time. Orchestration thresholds value is used to determine how long it will wait for response and if threshold exceeded orchestration will be dehydrate.

BizTalk Server Error in deploying policy

Saqib Ullah — Fri, 28 Sep 2007 00:21:00 GMT

Error :
The database "172.31.0.18:BizTalkRuleEngineDb" associated with the deployment driver does not match the database ":" specified during product configuration.

I am facing the same problem when I deploy my policy for testing on one of my development machine. After checking the error on web I try all prospects to resolve this error but I didn’t get any achievements.I change my IP address into database server name and try again but problem is still there. After a lot of hidden try I receive the another following error message.

Solution:
This time error message is surprisingly meaning full. I check my BizTalk Server configuration setting where I found BizTalkMgmtDb database cannot lucratively configure. Resolve the problem by supplying right credential and apply configuration setting and after successfully applying run the Business Rule Composer and deploy your policy.

BizTalk Server SQL Adapter Raise an error

Saqib Ullah — Sat, 22 Sep 2007 23:51:28 GMT

Yesterday I start writing Simple BizTalk Server 2006 application on Windows 2003 with SQL Server 2005. In have two databases in SQL Server source database name is CustomerSource and destination database name is CustomerDestination and both have same tables in term of their schemas, but their names are different like Customers and 2006Customers in my destination database. My BTS application does a very simple job its fetch all records from Customers table by using the simple query. "Select * from Customers for xml auto" and put that records in the destination database table. I build, deploy and configure the application. When I start the application I found the following error in my Event Viewer. Here one thing that I also want to share with you is that my destination table works fine when I connect it from native application.

Fig 1. SQL Adapter Failed.

How Can I Resolve This Problem?
I rename my destination table from 2006Customers to tbCustomers and try again and this time no error has been come and application perform its job. If anyone face the same problem that I had faced so please share it’s with me should leave comments.

BizTalk Default Pipelines Mapping issue "The root element is missing"

Saqib Ullah — Wed, 19 Sep 2007 00:36:42 GMT

Error Message:
There was a failure executing the send pipeline: "Microsoft.BizTalk.DefaultPipelines.XMLTransmit" Source: "XML assembler" Send Port: "Target\Path" Reason: The root element is missing.
Solution:
When ever this error comes its mean your input xml document is not schema validated.
Get Valid Input XML Document
Open your mapping file and right click on its and the click on Test Map. Get XML document from the Output Window and pass this XML document as a input source.

What is BizTalk Server 2006 R2

Saqib Ullah — Sun, 16 Sep 2007 18:38:29 GMT

Another release of Microsoft BizTalk Server. I must say its good step toward target of SOA. BizTalk Server 2006 R2 builds upon the Business Process Management and SOA/ESB capabilities and address core challenges found in key vertical industries such as manufacturing and retail.Native capabilities of BTS R2 include support for Electronic Data Interchange (EDI) and AS2 ,Windows Workflow Foundation, WCF as well as RFID.

Oracle Adapter for BizTalk Server 2006

Saqib Ullah — Tue, 11 Sep 2007 04:57:54 GMT

In BizTalk Sever 2006 Microsoft provides lot of new adapters and in these adapters Oracle adapter for BizTalk Server 2006 is one of them. Most of the adapters need some tricky things to do and Oracle adapter is again one of them. Recently I was establishing connectivity between BizTalk Server 2006 and Oracle for data transformation so I need do Oracle adapter configuration. During my configuration I found really interesting and knowledgeable blog regarding to Oracle adapter for BizTalk Server so I want to share it with you. oracleadapterinstallation.blogspot.com

.Net Web Services in BizTalk Server 2006

Saqib Ullah — Tue, 14 Aug 2007 13:25:02 GMT

I posted this article for those geeks who are not easily understand the working and calling of .Net Web Service in BizTalk Server 2006. Read its and should give comments about its. My article.

(407) Proxy Authentication Required.

Saqib Ullah — Sat, 11 Aug 2007 07:30:37 GMT

The remote server returned an error: (407) Proxy Authentication Required.

This is a very common error message when you try to get a resource on internet through your application. Why you getting this error from your application not from explorer. The reason is very simple either you use LAN that requires proxy setting or you use proxy server.

Example :

DataSet myds = new DataSet();
//Set the system proxy with valid server address or IP and port.
System.Net.WebProxy pry = new System.Net.WebProxy("172.16.0.1",8080);
//The DefaultCredentials automically get username and password.
pry.Credentials = CredentialCache.DefaultCredentials;
GlobalProxySelection.Select = pry;
myds.ReadXml("http://msdn.microsoft.com/netframework/rss.xml", XmlReadMode.Auto);
myds.WriteXmlSchema(@"c:\\f.xml");
this.GridView1.DataSource = myds.Tables[2];
this.GridView1.DataBind();

2 Technologies

Saqib Ullah — Tue, 31 Jul 2007 12:52:41 GMT

It’s a very common question in I.T. industry, when I use BizTalk Server or Windows Workflow Foundation. I found a short and simple definition of both technologies.

BizTalk Server is a licensed product designed to implement workflow [orchestrations] across disparate applications and platforms.

Windows Workflow Foundation is a developer framework designed to expose workflow capabilities within your application. There are no fees or licensing restrictions associated with using or deploying Workflow Foundation.

Debug BizTalk Server Orchestration

Saqib Ullah — Tue, 24 Jul 2007 05:14:21 GMT

The main purpose of writing this is to show how debugging is easy. Orchestration debugging is possible through Health and Activity Tracking (HAT) tool. By the help HAT you can easily debug any active or dehydrated orchestration. Once an instance of an orchestration executes and encounters one of these breakpoints, it will go into a wait state in the BizTalk MessageBox, allowing a developer or administrator to manually step through the orchestration.

Run BizTalk application at least one time and then follow the steps.

· Open the Health and Activity Tracking tool.

· Select "Most recent 100 service instance" from queries and select "Yes".

· Right-Click on your orchestration that you want to debug.

· Set the breakpoint on the receive class.

· Copy input files in “In” folder and run again Run Query from Query Builder View.

· Right-Click on your orchestration that you want to debug again.

· From debug menu Attach debugger to the orchestration.

Note:
You can attach only to orchestrations that have not completed. If this is the first time that the orchestration has executed, it will likely have already completed. You may need to start a new instance before the orchestration will pause on a breakpoint that has been set.

User should be a member of BizTalk Server Administrators Group.