BizTalk Server 2006 BTSTask An invalid value for property "DestinationFolder".

I was fighting with a BizTalk Server 2006 error with bindings imports. 

 These binding files were being generated by an XML preprocessing system and then loaded into BizTalk 2006 Server using BTSTask.exe

This error is mentioned in a Microsoft BizTalk KB / Hot Fix, http://support.microsoft.com/kb/923733, but that only applies (and only installs) if you have installed a LOB Adapter pack, but we did not have the LOB Adapter pack on this server. 

The error is the exact same, however.  The exception we got during binding import (both in the UI and in the CLI) is:

===================================

 

Failed to update binding information. (mscorlib)

 

===================================

 

Could not validate configuration of Primary Transport of Send Port 'portname' with SSO server.
An invalid value for property "DestinationFolder". (Microsoft.BizTalk.ExplorerOM)

 

------------------------------
For help, click: http://go.microsoft.com/fwlink/?LinkId=47400&ProdName=Microsoft+BizTalk+Server+2006&ProdVer=3.5.1602.0&EvtSrc=Microsoft.BizTalk.ExplorerOM.Resources&EvtID=IDS_ERR_TRANSPORTINFO_INVALID_TRANSPORT_DATA

 

===================================

 

An invalid value for property "DestinationFolder".

 

------------------------------
Program Location:

 

   at Microsoft.BizTalk.ExplorerOM.IPersistPropertyBag.Load(IPropertyBag propertyBag, Int32 errorLog)
   at Microsoft.BizTalk.ExplorerOM.Helper.ValidateTransportProps(String transportTypeData, String transportAddress, String publicAddress, IProtocolType transportType, Boolean IsTransmit)
   at Microsoft.BizTalk.ExplorerOM.TransportInfo.Microsoft.BizTalk.ExplorerOM.IBaseObject.ValidateObjectData()

The solution for us was to make changes to the content of our bindings file by removing all whilespace and line breaks from the contents of the <Address /> and <PhysicalAddress /> elements.  These line breaks were being added to some bindings files by our XML preprocessor and could not, for some reason, be imported to BizTalk.

The "with SSO Server" junk is actually some type of mask for the real error, which I found out by disassembly BizTalk assemblies and checking out some of the error handling around a bit of unmanaged code that was getting invoked.

--
Cory Trese
e-m:    cory.trese@gmail.com
www:  http://www.corytrese.com/
---
California Wedding Photography
http://www.corytrese.com/wedding.html