Carlos Medina's Blog

If you have(had) any problem when you are(were) publishing orchestrations as Web Services... then you must read this article "You cannot call an orchestration that is exposed as a Web service on a server that is running BizTalk Server 2004"....

The article explains three symptoms, its causes and how we can resolve it.  As part of article, these are the symptoms explained:

Symptom 1

The following error messages are logged in the Application event log on the server that is running BizTalk Server 2004:

The Messaging Engine failed to register the adapter for "SOAP" for the receive location "/VirtualDirectory/Name.asmx". Please verify that the receive location is valid, and that the isolated adapter runs under an account that has access to the BizTalk databases.

An attempt to connect to "BizTalkMgmtDb" SQL Server database on server "Server" failed with error: "Cannot open database requested in login 'BizTalkMgmtDb'. Login fails.".

Symptom 2

On a remote server that is running BizTalk Server 2004, the following error message is logged in the Application event log when you call the orchestration that is exposed as a Web service:

The "SOAP" adapter is suspending an outbound message going to destination URL:"<http://VirtualDirectory/Name.asmx>". Details: "Server was unable to process request. --> File or assembly name FileName.dll, or one of its dependencies, was not found.".

When you call the orchestration that is exposed as a Web service from a client computer that is not running BizTalk Server 2004, you may receive an error message that is similar to the following:

SoapException: Internal SOAP Processing Failure

Symptom 3

The following error message is logged in the Application event log on the server on which the Web service is exposed:

There was a failure executing the receive pipeline:
"Microsoft.BizTalk.DefaultPipelines.XMLReceive" Source: "Microsoft.BizTalk.Messaging" Receive Location: "/VirtualDirectory/Name.asmx" Reason: Specified cast is not valid.

Now, we can send e-mails with local file(s) as attachment(s) in BizTalk 2006 without add these files as Multipart-MessageParts of the message that we'll send.  This new feature can be used for both static and dynamic ports.

If you use static ports, you can use the new Admin Console to select the file(s) that you can send without problems.  But, if you need that these files change depending of message type, then you must use a dynamic port and set the path of file(s) to new SMTP.Attachments context property of http://schemas.microsoft.com/BizTalk/2003/smtp-properties namespace.  There is only one restriction, you have to use a pipe character (|) to separate all path file(s) and one more pipe in the end of path(s), for example:

This is a fantastic new feature of SMTP Adatper in BizTalk 2006.

To people that have not begin to test Windows Workflow Foundation yet... and people that are testing Windows Workflow Foundation now, here is 10 reason to love WF and believe in it....

Thanks to Michael Zammuto for it.....

In MSDN Magazine Aaron Skonnard has published An XML Guru's Guide To BizTalk, Part II, this is the last article in the serie.  You can read the first article in An XML Guru's Guide To BizTalk, Part I.

Microsoft has released Windows Workflow Foundation 1.2... this version must be installed on a machine with Visual Studio 2005 RTM.  There are two downloads available:

• The first download consists of the platform components for Office "12" Beta User needed to run WF applications
• The second download consists of solutions templates, activities, SDK and other tools that developers need to construct WF application using Visual Studio 2005 RTM

Article: An XML Guru's Guide to BizTalk Server 2004, Part I