ansaurus

Question

Login Using MS SQL Express: Success! Migration Toolkit login: fail?

Answer 1

A:

Check if your SQL server "listen" ip, tcp protocol and port 1433.

Try to execute

telnet server_ip_addres 1433

If telnet window will be closed - the SQL server doesn't listen the ip, the port or tcp. If you have an access to "SQL Server Configuration Management" or to registry of the server, you can visually find the information(Configuration Management - Protocols, TCP/IP, IP Addresses, port) and correct connection string as necessary. Just in case link to doc of jdbc driver, that you are using.

FoxyBOA 2009-06-17 20:08:15

hey Foxy, thanks for the reply. 1433 is open and listening. (confirmed using the telnet string above, and checked with the admin).

jmccartie 2009-06-18 02:52:23

1. Are your SQL works in "Mixed Mode" (username/password based authentication)? That mode implies in your connection string (http://msdn.microsoft.com/en-us/library/ms143705.aspx).2. Are you connection to default instance (imply in connection string as well) or to named instance (http://msdn.microsoft.com/en-us/library/ms143744(SQL.90).aspx)?

FoxyBOA 2009-06-18 05:20:28

1) username/password auth is allowed -- this is how I've connected using both SQL Management and dbVisualizer. 2) print @@servername returns "DEDICATED"

jmccartie 2009-06-18 17:11:18

Last idea - check that you have the latest version of jtds driver or at least that you are able to connect to the SQL using the same jdbc driver (jtds) and using the same settings.

FoxyBOA 2009-06-19 08:40:28

Answer 2

A:

I think there a missing rights to specific database or table of the SQL Server. I had the same problem a time ago with dts migration.

User needed read rights to the MSDB or the sysdtspackag tables.

I think your problem is similar "The list of schema names could not be retrieved" maybe your user has insufficient rights on some system tables.

Richard 2009-06-22 12:58:02

Thanks, Richard. The sysadmin confirms that I have those permissions.

jmccartie 2009-06-23 14:24:42

Answer 3

A:

Does your connection string contain special (non alphanumeric) characters in parameter values ? If so, try urlencoding them (like / => %2f) and/or enclose them in braces {}.

streetpc 2009-06-23 09:35:08

No, there are no special characters in the connection string.

jmccartie 2009-06-23 14:26:27

Answer 4

+3 A:

I see, there is a blog with almost the same error description

http://house9.blogspot.com/2007/12/mysql-migration-toolkit.html

Also, in order to run the tool you need access rights

master INFORMATION_SCHEMA

I would suggest executing a query (this should be done by your admin)

use [master]
GO
GRANT SELECT ON SCHEMA::[INFORMATION_SCHEMA] TO [MYUSERNAME]
GO
use [master]
GO
GRANT VIEW DEFINITION ON SCHEMA::[INFORMATION_SCHEMA] TO [MYUSERNAME]
GO

Finally, if you granted these rights, but you have the same error, then ask your system administrator to run SQL Profiler, then run your tool and see what queries it tries to execute and what SQL or security exceptions happen there (if any)

Bogdan_Ch 2009-06-23 09:39:01

It's SQL Express so Profiler isn't an option

Joel Mansford 2009-06-24 11:24:09

I was using the SQL express client, but the server was SQL 2000

jmccartie 2009-06-24 18:03:33

ansaurus

tags:

views:

answers:

Login Using MS SQL Express: Success! Migration Toolkit login: fail?

related questions