![]() |
Learn more about Toad for SQL Server Find solutions and downloads at the |
Toad for SQL Server 6.6 |
The following table describes issues related to installing Toad.
Issue | Cause/Solution |
---|---|
When installing Toad on Windows 7 64-bit, Program Compatibility Assistant may appear with “This program might not have installed correctly” message. |
Solution: Select This program installed correctly to continue installation. For more information, see http://windows.microsoft.com/en-PH/windows7/Program-Compatibility-Assistant-frequently-asked-questions |
Issue | Cause/Solution |
---|---|
Toad Plug-in cannot be invoked from Microsoft SQL Server Management Studio after you uninstalled one of several editions of Toad that resided on your machine side-by-side. |
If you have several editions of Toad for SQL Server installed side-by-side (for example, Beta, Trial and Commercial) and you uninstall one of them, Toad Plug-in files are removed as a part of un-installation process. Solution: Select one of the following:
|
Review the following solutions to help troubleshoot SQL Server connection issues in Toad.
Issue | Cause/Solution |
---|---|
Cannot specify a port number when connecting |
Currently, Toad does not have a separate field for specifying a port number. Solution: You can connect if you know the port number for the instance by entering the following in the Server name field on the New Connection window: ServerName,Port or IPAddress,Port For example: 10.1.29.129,1234 (where 1234 is the port number of the instance) |
Cannot connect to a remote instance in SQL Server 2005 |
Remote connections may not be enabled in SQL Server 2005. Also, named instances are configured to use dynamic ports and select an available port once the SQL Server Service starts. If you are connecting to a named instance through a firewall, configure the Database Engine to listen on a specific port, so that the appropriate port is opened in the firewall. Note: Remote connections are disabled by default in the Express and Developer editions of SQL Server 2005. Solution: To enable remote connections, see "How to configure SQL Server 2005 to allow remote connections" at: http://support.microsoft.com/kb/914277 |
"Path is not of a legal form" error message when connecting or "Could not find a part of the path |
You attempted to migrate settings from a previous install of Toad to the current install, but the settings file (InitialSqlServer.Sql) for the previous install was either removed, moved, or corrupt. You may also receive this error if you installed Toad and migrated settings from a previous version, and later uninstalled the previous version. Solution: You must specify a valid location for the InitialSqlServer.Sql file in Toad. To specify a valid location
By default, this file is located in the following directory: C:\Program Files\Dell\Toad for SQL Server version \Templates\Scripts Note: Clicking
|
Cannot establish Named Pipes connection |
If you are trying to connect to the server using Named Pipes, "Poll service status in connection list" option should be cleared. Solution:
|
Cannot establish Azure connection |
Failing to establish Azure connection may indicate that your IP address is restricted from having access to the Azure server. Solutions:
|
Cannot access some functionality when working with Azure connection. |
To utilize majority of Toad functionality VIEW DEFINITION grant is required for those databases you want to work with. |