QuoteWerks Knowledgebase Topic (Article ID 6546)

SQL - SQL Server does not exist or access denied, general or when syncing

This information applies to :

Article ID

April 19, 2019


Are you using the most current release of QuoteWerks?
Version 5.5 Build 5
When attempting to launch QuoteWerks, or attempting to synchronize with the master installation of QuoteWerks, the end user receives the following error message:

"Error: (-2147467259). Error opening connection in ConnOpen()
SQL Server does not exist or access denied"

While you're able to access the shared Master QuoteWerks folder, and you can also likely ping or "see" the SQL Server you're attempting to sync with, QuoteWerks is unable to access it.

Solution 1:

1) On the server where SQL is installed, go into Control Panel -> Administrative Tools -> Services and make sure the SQL Browser service is started.

2) On the server, go into Start -> Programs (or All Programs) -> Microsoft SQL Server -> Configuration Tools -> SQL Server Configuration Manager. Once that's up, expand the option for Network Configuration, select the option for Protocols and ensure that TCP/IP is enabled, as well as Named Pipes.

Solution 2:
1) On the server where SQL is installed, review the firewall settings and ensure that the proper ports are open for both incoming and outgoing connections.
2) On the workstation or remote, review the Windows firewall settings as well and ensure that the appropriate ports are open for both incoming and outgoing connections.

For further information on SQL ports, see the references later in this documentation.

If the above solutions did not assist with resolving the issue, then there is some other underlying element causing the connectivity issue. To aid in testing (and keep you from having to load QuoteWerks every time) Technical Support has a database testing tool that you can download:

You enter a connection string, for example:


If this testing tool is able to make the connection to the SQL server, then QuoteWerks should be able to as well.

Alternately, you can test the connection using notepad:

Further, more detailed, information concerning troubleshooting connectivity to the SQL server can be found on Microsoft's website: http://social.technet.microsoft.com/wiki/contents/articles/2102.how-to-troubleshoot-connecting-to-the-sql-server-database-engine.aspx

In addition, there may also be an issue related to the Named Pipes Provider. End users will receive a, "error: 40 - Could not open a connection to SQL Server". This can be resolved using the following Microsoft article: http://blogs.msdn.com/b/sql_protocols/archive/2007/03/31/named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server.aspx

Dynamic Ports and SQL Express:
By default, named instances of SQL Express use dynamic ports. That means that every time that the Database Engine starts, it identifies an available port and uses that port number. If the named instance is the only instance of the Database Engine installed, it will probably use TCP port 1433. If other instances of the Database Engine are installed, it will probably use a different TCP port. Because the port selected might change every time that the Database Engine is started, it is difficult to configure the firewall to enable access to the correct port number. Therefore, if a firewall is used, we recommend configuring the Database Engine to use the same port number every time. This is called a fixed port or a static port. For more information, see Configure a Server to Listen on a Specific TCP Port (SQL Server Configuration Manager).
Ports used by database engine: https://msdn.microsoft.com/en-us/library/cc646023(v=sql.110).aspx#BKMK_ssde
Configuring the Listening Port: https://msdn.microsoft.com/en-us/library/ms177440(v=sql.110).aspx

New Search