Skip to end of metadata
Go to start of metadata

Here are some advanced methods to troubleshoot SQL server connection when Clarity connection works from the server but not the workstation(s).

These methods require server access and the use of SQL Server Configuration Manager.

Verify that the Server Browser service is running.

Once SQL Server Configuration Manager is open, select 'SQL Server Services' and make sure that SQL Server Browser is 'Running' and 'Automatic'.

Clarity requires the Named Pipes and TCP/IP protocols.

Click the small arrow next to 'SQL Server Network Configuration'. Select 'Protocols for AKM' or 'Protocols for AKMUS'.

Verify that 'Named Pipes' and 'TCP/IP' are enabled in the right hand pane of the window.

Verify the port being used by SQL for the AKM or AKMUS Instance

Select 'Protocols for AKM or AKMUS' and then right-click TCP/IP in the right pane, and choose 'Properties'

In the TCP/IP Properties window, select the 'IP Addresses' tab and scroll to the bottom. The port being used by the instance is listed under 'TCP Dynamic Ports'.

Start Clarity on the server and on the login screen, select 'Database options' and add the port to the end of the instance name (Example: testserver\akm,11111). If this works, do the same on the workstation.

If still unable to connect from the workstation, then an exception needs to be added to the server firewall for TCP and UDP in and out (usually 4 exceptions) for this port number.

If this fails, exceptions may need to be added to the workstation firewall or the instance might have been set up without using mixed mode authentication which would require creating a new instance.