Applies to: @RISK for Excel 5.x and Up

Troubleshooting @RISK Library Server Visibility

Issue:

When using the Connect or Create buttons in @RISK Library, only your own machine appears; network servers are not listed.

Cause/Solutions:
This usually stems from firewall restrictions, permissions, or SQL Server configuration issues. Use native SQL tools to isolate the problem.

Steps to Check SQL Server Connectivity:

1. Open SQL Server Management Studio (SSMS):

   • Click Start → Programs → Microsoft SQL Server → SQL Server Management Studio (or SSMS Express).

   • If not installed, download it from Microsoft’s Download Center by searching for “Microsoft SQL Server Management Studio Express”, then install and run it.

2. Test Local Server:

   • The Server Name field should be pre-populated with your local server.

   • Click Connect, then in Object Explorer, expand Databases and navigate through any path.

   • If errors occur, your SQL Server installation may be faulty.

3. Test Network Servers:

   • Click Connect → Database Engine.

   • The Server Name should default to your local machine.

   • Click the drop-down arrow and select Browse for more.

   • In the Browse for Servers dialog, select the Network Servers tab.

   • Wait while it retrieves servers; you should see Database Engine and a list of networked machines.

Interpret Results:

• Networked machines are visible: SQL Server is functioning correctly, and permissions are likely sufficient. If @RISK still cannot see them, contact support.

• Networked machines are not visible: This indicates a network, firewall, or SQL configuration issue. Consult your IT department to troubleshoot connectivity.

Notes:

• Ensure firewalls allow SQL Server discovery.

• Verify proper SQL Server authentication and permissions.

• This process isolates SQL connectivity issues from @RISK-specific issues.