Bug #26205 | Not Conecting so MS SQL Server 2000 | ||
---|---|---|---|
Submitted: | 9 Feb 2007 0:38 | Modified: | 9 Feb 2007 16:35 |
Reporter: | Alejandro Tobon | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Migration Toolkit | Severity: | S1 (Critical) |
Version: | 1.1.9 | OS: | Windows (Windows) |
Assigned to: | CPU Architecture: | Any |
[9 Feb 2007 0:38]
Alejandro Tobon
[9 Feb 2007 3:12]
MySQL Verification Team
Thank you for the bug report. I was not able to repeat when connecting against SQL Server 2005. Notice you need to be sure that MS SQL Server has enabled the TCP/IP protocol with 2005 version can be verified using the Xp_readerrorlog (read the documentation of your version) and which port is listening (in your error message you pasted the default one which MySQL Migration Toolkit offers and on my side most of time isn't the listening port). Also you need to setup the server to accept mixed authentication. Thanks in advance.
[9 Feb 2007 16:35]
Alejandro Tobon
Hello Miguel, thanks for the help. I have look for the advices you tell me and I see that the protocol TCP/IP is enabled at port 1433 and the mixed authentication is enabled to, I search for a posible solution, one of them was to change the port to 0, I have change to 0 on SQl Server 2000 and in the Migration ToolKit but it still doesn't work, when I did more research about the problem it looks like it's a problem with SQL Server 2000, the problem is produced when other aplication tries to connect to a port in SQL Server 2000, so I Install the latest service pack, the number 4, but it still doesn't work. Please forgive me for all the problem, but I realy need to solve it, Thanks for your time I realy apreciate it
[14 May 2008 20:02]
Francisco Igor
I get it work using "named pipes" : Add the option ";namedPipes=true" in your connection string Ex: "jdbc:jtds:sqlserver://server1/db;namedPipes=true" Read the faq at http://jtds.sourceforge.net/faq.html#connectionRefused