Configuring the Firewall

Compare the paths for the .exe files for the SQL server services with the Firewall configured settings and add them, if necessary. Follow the steps that apply to your situation:

  1. Open Services.
  2. At the same time, start the Windows Firewall with Advanced Security and go to the Inbound Rules.

A. Default instance or default installation of a named instance, which is the only running instance on the computer, and which is run with a static TCP port:

  1. If you carried out the installation using the Citavi Setup, you can find a rule in Windows Firewall with Advanced Security with the name Microsoft SQL Server Express for Citavi.
    1. Switch to the Services window and search for SQL Server (Instance name) > right-click > Properties > General. Make a note of the path to the .exe file.
    2. In Windows Firewall with Advanced Security, double-click the inbound rule, and then click the Programs and Services tab. The path displayed there must be the same as the path for the .exe file that you noted in step A1.1. If it is not, correct the path in the Firewall rule.
  2. If the rule is not present, add it manually by following steps A2.1-2.6 above.
    1. Right-click Inbound rules and then select New Rule.
    2. Select the Program rule type.
    3. Under This program path enter the path to the SQL Server .exe file.
    4. Select the Allow the connection option.
    5. Select the profiles to which the rule applies (in most cases Domain and potentially also Private).
    6. Enter a name for the rule, add a description if you want, and then click Finish.

B. Named Instances when using dynamic TCP ports.

  1. Check if an inbound rule for the SQL Server Browser is present.
    1. Switch to the Services window, and search for the SQL Server Browser > right-click > Properties > General. Make a note of the path to the .exe file.
    2. In Windows Firewall with Advanced Security, double-click the inbound rule, and then click the Programs and Services tab. The path displayed there must be the same as the path for the .exe file that you noted in step B1.1. If it is not, correct the path in the Firewall rule.
  2. If the rule is not present, add it manually by following steps A2.1-2.6 above.

If you are using an alternate or additional Firewall, you will need to check the inbound rule and add it if it is not present.