Home/ Questions/Q 87607
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T22:25:45+00:00

I’ve inherited a BizTalk 2006 application that uses several SOAP ports to request data

  • 0

I’ve inherited a BizTalk 2006 application that uses several SOAP ports to request data from a 3rd party web service. The web service is secured by ‘basic’ authentication – username / password. After making a few enhancements to the application I deployed to an integration test server which has access to the 3rd party web service. The BizTalk app was unable to retrieve the data and I soon realised that I had forgotten to set the username / password on the SOAP send ports. I wanted the make deployment of the BizTalk app as automated as possible because I may not be present when it is deployed to the live server. I opened up the binding file, located the 1st of the problem SOAP send ports and looked for the * that BizTalk uses to replace the password – except that it doesn’t! It seems that the password for SOAP ports is set to NULL rather than *, see here for more details: http://msdn.microsoft.com/en-us/library/aa547319.aspx

I proceeded to update the binding but when I came to test, after importing my amended binding file, I found that I had the same problem as before. I’ve double checked and can confirm that the correct password is now present in the binding file but, although BizTalk doesn’t complain during the import, when I run the app I get the following exception:

Details:’ArgumentNullException: String reference not set to an instance of a String. Parameter name: s ‘.

If I then manually amend the password through the BizTalk admin console everything work fine.

Has anyone else had a similar problem with the bindings for a SOAP port – does anyone have a solution?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. I’ve been bit by something like this in the past. The password is either put in as ‘****’. This is ok. I wouldn’t want all of my secrets exported with the binding file. What does get you is when you export the bindings and you leave the password NULL. The Variable Type (vt) attribute on the XML element for the password is set to vt=’1′ which is the same as NULL. It won’t matter what you put in for the password. It may even cause the error you described. I would suggest you include a copy of the binding XML for review.

    • 0