Export (0) Print
Expand All

Troubleshooting SQL Server Connection Problems

Microsoft Dynamics Nav 2009

After installing and configuring Microsoft Dynamics NAV 2009 software, you may not be able to connect the RoleTailored client to Microsoft Dynamics NAV Server. The following error message appears when you attempt to start the RoleTailored client.

The program could not create a connection to the server. Do you want to try again?

This topic describes configuration changes that you can try to resolve SQL Server connection problems.

Enable Protocols in SQL Server Configuration Manager

SQL Server Configuration Manager is a tool for managing SQL Server services and network connectivity. You can use SQL Server Configuration Manager to enable and disable network protocols. For Microsoft Dynamics NAV to work correctly, the Named Pipes and TCP/IP protocols must be enabled for SQL Server.

Follow these steps to verify that these protocols are enabled or to enable them if they are currently disabled.

To enable Named Pipes and TCP/IP in SQL Server

  1. Start SQL Server Configuration Manager

  2. Expand the SQL Server Network Configuration node in the tree view, and then click Protocols for MSSQLSERVER.

  3. Under Protocol Name in the right pane, verify that Named Pipes and TCP/IP have the status Enabled.

  4. If either protocol is not enabled, right-click the protocol, and then click Enable.

After exiting SQL Server Configuration Manager, start the RoleTailored client again to see if the connection problem has been resolved.

Allowing SQL Server with Windows Firewall

If Windows Firewall is running on the computer running SQL Server, then you must explicitly specify the SQL Server executable file as an allowed exception before you can connect to the Microsoft Dynamics NAV database with the Classic client.

To allow SQL Server with Windows Firewall

  1. In Windows Server 2003, in Control Panel, open Windows Firewall, and then click the Exceptions tab.

    -or-

    In Windows Server 2008, in Control Panel, open Windows Firewall, click Change settings, and then click the Exceptions tab.

  2. Click Add program.

  3. Click Browse, and then browse to the location of the SQL Server executable file (sqlservr.exe). The default location on a computer running Windows Server 2003 is:

    Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlservr.exe
    
  4. Double-click the executable file to select it and to exit the Browse window, and then click OK to close the Add a Program window.

  5. Click OK to close Windows Firewall.

After exiting SQL Server Configuration Manager, start the RoleTailored client again to see if the connection problem has been resolved.

See Also

Community Additions

ADD
Show:
© 2014 Microsoft