When you try to redeploy Pipeline Components BizTalk locks the dlls under C:\Program Files\Microsoft BizTalk 2006\Pipeline Components. They are locked by the BizTalk Host Instance that used them. To update a Pipeline Component one has to stop the Host Instance, redeploy and then start the Host Instance. UPDATE: Thanks to Th Almeida who pointed me to this: Pipeline Components are locked by the host that is using the pipeline not by the standard host. I did my pipeline deployment test with a dynamic...
Short Update to my previous post about this: Setting the AuthenticationScheme to NTLM means that the user of the host instance is sending the message to the destination. In case of a dynamic port there is no host specified - BizTalk then automatically executes the dynamic Send Port under the standard host user. (for example BizTalk Server Application)
Today I faced a really interesting problem when redeploying a BizTalk application: In an orchestration I map the Response of a WebService call together with another message to an outbound message. Everything went fine until I changed the WebService. I put the WebMethod into another WebService (called method and return parameter remained the same as before), deleted the whole webreference, added the webreference to the new WebService and changed the types of my Webservice request and response messages...
When calling a WebService from BizTalk, beside specifying Username and Passwort, one has to set the form of authentication (Anonymous, Basic, NTLM, etc.) too. This can be done either on the Sendport Configuration or - when using a dynamic port - by the following code (example for using NTLM = Windows Integrated Authentication) in an expression shape: MessageName(SOAP.Authentica... = "NTLM";