BizTalk tasks ignore Server parameter

Nov 19, 2007 at 4:31 PM
A few of the BizTalk 2006 tasks appear to be ignoring the Server parameter - the ones I've run into so far are:


There may be more - I'm slowly working my way through all the problems.
Anyone else have this problem?
Dec 2, 2007 at 3:08 PM
we've running into the same problem (read my previous post)

As a workaround to this bug, we specify a “dummy” Password without a user name. This way, the Server attribute is NOT ignored, and Windows authentication is used (because the User name is blank).

Hope this will help !

Dec 3, 2007 at 1:53 PM
I ran across your post about the dummy password. And that works for most of the tasks.
Seems as though that trick doesn't work for the Application.Exists task, though. As a "workaround", we just ignore (but log) any errors generate by the tasks during undeployment. Then hope the deployment fails if there really was a problem. Not exactly the best "workaround"...

Jan 3, 2008 at 7:17 PM
TerminateInstances also appears to have this problem.