On Wed, Mar 16, 2011 at 5:55 AM, Matt C <[email protected]> wrote: > I've actually just run into this exact same error, and this thread is > the only result Google returned. We've set up OpenBD v1.4 on a Unix > server for a client and set up a datasource to their SQL Server 2008 > server. The datasource verifies fine, but queries result in the error > "failed to verify remote server/socket @ _________:1433". We've > checked to make sure SQL Server has port 1433 open (as apparently they > no longer have it open by default), and I don't think it's the OS > firewall settings of the SQL Server's OS because I can telnet to the > machine on that port from our unix box.
Unfortunately I've tried and cannot reproduce this error. And you've tried both drivers? Make sure to delete the datasource entirely (or create a new one) to be absolutely sure the driver change happens. Next step would be some wireshark-type analysis or (and bear in mind my SQL Server knowledge is pretty weak for this kind of stuff) is there some sort of logging in SQL Server you can enable to see more of what's happening when the query attempt happens? Sorry I can't be of more specific help but I've tried this in various ways on SQL 2005 and 2008 and can't reproduce this behavior. With more information, log info, etc. we can dig a little deeper. -- Matthew Woodward [email protected] http://blog.mattwoodward.com identi.ca / Twitter: @mpwoodward Please do not send me proprietary file formats such as Word, PowerPoint, etc. as attachments. http://www.gnu.org/philosophy/no-word-attachments.html -- official tag/function reference: http://openbd.org/manual/ mailing list - http://groups.google.com/group/openbd?hl=en
