BizTalk – Strange Exception Messages and Corresponding Fixes.

  During our BizTalk development we come across some really strange error message, which normally doesn’t reflect the real cause. I always wanted to consolidate everything in one place. After seeing couple of errors that’s being raised in the news groups, I thought this is the right time to materialise it. If you have come across any strange errors and willing to share please let me know via my contact page. ========================================================================== Exception: ‘System.Xml.XmlDocument’ does not contain a definition for ‘Status’ ========================================================================== Cause: System.Diagnostics.Debug.WriteLine(PO_SOURCE.Status.ToString()); Resolution: status = PO_SOURCE.Status; System.Diagnostics.Debug.WriteLine(status.ToString()); where “status” is a variable of type System.String. Credit: Tim Remark: When you try to do the conversion directly on the context property, the above exception is raised. You can easily fix it by first assigning the context property to a local variable and then doing the conversion. DateLogged: 17th May 2007 (BizTalk 2006) ========================================================================== ERROR: The BAM deployment failed. A connection cannot be made. Ensure that the server is running. No connection could be made because the target machine actively refused it ========================================================================== Credit: Saravana Kumar Remark: If you receive the following error when you try to deploy BAM activities using bm.exe tool The error information doesn’t reflect on the actual cause. Make sure, “SQL Server Analysis Services” is started. DateLogged: 26th April 2007 (BizTalk 2006) Nandri! Saravana