Entry

Import binding file gives this error: Failed updating binding information. BindingException: Could not validate TransportTypeData or Address properties for Primary Transport of Send Port 'prtSpAffiliateSourceCodeGet'. Exception from HRESULT: 0x80131500.

Apr 6th, 2005 22:55
Balaji Ramachandran, http://biztalk-training.com/Default.aspx?tabid=57

I've already discovered my problem, but thought I would document it 
here. 
My thought on the binding wizard is that if I have fewer than 3 or 4 
ports, it probably wasn't worth the trouble. But now, I am looking at 
automating a little. 
I ran the deployment wizard (export option) for a particular 
orchestration (that has 2 or 3 SQL request/response ports), then 
unenlisted that orchestration, then imported the binding file (created 
by the export). 
I'm getting this ERROR: 
Failed updating binding information. BindingException: Could not 
validate TransportTypeData or Address properties for Primary Transport 
of Send Port 'prtSpAffiliateSourceCodeGet'. Exception from HRESULT: 
0x80131500.
The binding file for the SQL port looks like this: 
endPortCollection>
SQL://sqldev/ThirdPartyFeeds/
<CustomProps><AdapterConfig vt="8"><Send 
xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-
instance"><connectionString>Provider=SQLOLEDB.1;Password=******
*********;Persist Security Info=True;User ID=xxxxxx;Initial 
Catalog=ThirdPartyFeeds;Data 
Source=sqldev</connectionString><outputRootElementName>Affil
iateSourceCodeGetResp</outputRootElementName><documentTargetNam
espace>http://Odimo.com/Amazon/spAffiliateSourceCodeGet</documentT
argetNamespace><uri>SQL://sqldev/ThirdPartyFeeds/</uri>&l
t;/Send></AdapterConfig></CustomProps>
3
5
false
2004-10-21T01:00:00.0000000-04:00
2004-10-22T00:59:59.0000000-04:00
true
false
3
5
false
2004-10-21T01:00:00.0000000-04:00
2004-10-22T00:59:59.0000000-04:00
false
false
0
I changed the Password=*************** to Password=mypass and it worked.
So obviously this is great when you are using integrated security but 
bad when using passwords. 
We really wish the concept of the UDL had not disappeared with .NET 
(and therefor Biztalk)!!!