http://winterdom.com/2005/04/sqladaptertroubleexplained by dæmons be driven Tue, 16 Mar 2010 06:33:03 +0000 http://wordpress.org/?v=2.9.2 hourly 1 http://winterdom.com/2005/04/sqladaptertroubleexplained/comment-page-1#comment-471 Stefan Mon, 12 Feb 2007 07:33:47 +0000 http://winterdom.com/2005/04/sqladaptertroubleexplained#comment-471 Thank you Will, I red many posts, and you are the only one who provided the right solution Regards, Stefan Thank you Will,
I red many posts, and you are the only one who provided the right solution
Regards,
Stefan

]]> http://winterdom.com/2005/04/sqladaptertroubleexplained/comment-page-1#comment-470 Will Wed, 31 May 2006 10:39:02 +0000 http://winterdom.com/2005/04/sqladaptertroubleexplained#comment-470 This problem for me was caused by too restrictive DTC settings. Reducing security allowed all the ports to bind successfully. Start | Control Panel | Admin Tools | Component Services Component Services | Computers | Right click My Computer and select Properties. Select Security Configuration on the MSDTC tab. I allowed inbound and outbound communication with no authentication. This problem for me was caused by too restrictive DTC settings. Reducing security allowed all the ports to bind successfully.
Start | Control Panel | Admin Tools | Component Services
Component Services | Computers | Right click My Computer and select Properties.
Select Security Configuration on the MSDTC tab.
I allowed inbound and outbound communication with no authentication.

]]> http://winterdom.com/2005/04/sqladaptertroubleexplained/comment-page-1#comment-469 Anonymous Wed, 05 Apr 2006 07:03:59 +0000 http://winterdom.com/2005/04/sqladaptertroubleexplained#comment-469 I had a similar error that caused me fits. I was using BTSDeploy with a binding file to deploy a project and getting the 0x80131500 error message. The credentials in the binding file were correct, I could connect to the SQL database, and I could create the port manually. The binding file continued to fail. It ended up being that the SQL cluster to which the port was pointing had failed over, but the DTC had not failed with it. I had a similar error that caused me fits. I was using BTSDeploy with a binding file to deploy a project and getting the 0×80131500 error message. The credentials in the binding file were correct, I could connect to the SQL database, and I could create the port manually. The binding file continued to fail. It ended up being that the SQL cluster to which the port was pointing had failed over, but the DTC had not failed with it.

]]>