Review the following solutions to help troubleshoot Oracle connection issues in Toad.
Issue | Cause/Solution |
---|---|
Attempting to connect when Oracle Instant Client is installed results in a System.NullReferenceException error |
Solution: In order to connect using the Oracle Instant Client, the directory for the Instant Client must be included in the environmental path, or you must copy the client files for the instance to the root install directory of Toad Data Point. You can also connect to the database without using an Oracle client or TNSNames file by selecting the Direct tab in the Create New Connection window. |
An error occurs when attempting to connect to Oracle Rdb using an ODBC driver | Toad does not support Oracle Rdb at this time. |
Attempting to connect to Oracle 18c results in the error ORA-28040: No matching authentication protocol | SQLNET.ALLOWED_LOGON_VERSION has been deprecated. Upgrade your Oracle client or set the parameter value to 12c. |
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 |
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: Note: Clicking may result in a "Path not found error". If you receive this error, manually enter the location in the field. |
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. |
Toad integrates with your existing version control system so you can maintain multiple revisions of objects. See Configure Version Control for Objects for more information on configuring version control in Toad.
For Version Control of your files handled by Toad see Version Control for Toad Files.
Important: See Troubleshoot Version Control for more information about issues when upgrading version control from a previous version.
Notes:
You must install a supported version control client on the computer where Toad is installed. The following table lists the supported version control providers and the versions tested with Toad.
Supported Provider | Server Version Tested | Client Version Tested |
---|---|---|
Apache Subversion™
|
Subversion 1.7.5 on Windows |
CollabNet Subversion Command-Line Client 1.7.5 Note: Any Subversion client must have svn.exe in its installation directory to use version control in Toad. |
Git | Toad works only with the local repository. For commands such as clone, pull and push use an external tool. | |
Team Foundation Server (TFS) |
TFS 2008, 2010, 2012, 2013 |
Visual Studio® (2008, 2010, 2012, 2013) Team Explorer Client
|
File system based | Toad allows to utilize practically any version control system using the external client tool. In this case Toad Version Control tool works with the directories at local HDD while you commit changes to the repository with version control client tool. | |
Note: Toad connects to your version control system based on login information included in the configuration. Your version control client does not need to run for Toad to connect. |
Details of Team Foundation Server support:
Visual Studio/Team Explorer version | TFS 2013 support notes | TFS 2012 support notes | TFS 2010 support notes |
---|---|---|---|
Visual Studio 2015 | Supported (RTM or latest update) | Supported (RTM or latest update) | Supported (RTM or latest update) |
Visual Studio/Team Explorer 2013 | Supported (RTM or latest update) | Supported (RTM or latest update) | Supported (RTM or latest update) |
Visual Studio/Team Explorer 2012 | Requires latest Visual Studio 2012 update. Supports Git with Visual Studio Tools for Git extension | Supported (RTM or latest update). Supports Git with Visual Studio Tools for Git extension | Supported (RTM or latest update). Supports Git with Visual Studio Tools for Git extension |
Note: Additional functionality and compatibility with older clients is possible but out of scope of what we are able to test.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback 使用条款 隐私 Cookie Preference Center