The Site Server fails to show up in SS Console with a message "Could not connect to Root Site Server".
- On the affected Site Server machine, open Site Server Configuration (typically "C:\Program Files\AccessData\SiteServer\SS_Config.exe")
- Take note of what certificates are being used for Secure Communications
Note: All Site Servers (root & children) must have a local copy of the same certificates.
- Make sure your certificates meet these requirements.
- View the certificates properties and make sure they have not expired. If they have, the client will need to generate or obtain new valid certificates to replace them.
- On the Work Manager responsible for Site Server jobs, open Infrastructure.WorkExecutionServices.Host.exe.config in a text editor (typically "C:\Program Files\AccessData\eDiscovery\Work Manager\Infrastructure.WorkExecutionServices.Host.exe.config")
- Find the entries for SSAgentCertFile, SSCommunicationCertPath, and AgentCertificatePath
Note: The Work Manager responsible for Site Server jobs must have a local copy of the certificates.
- Verify the value/path for the SSAgentCertFile and AgentCertificatePath are using the same certificate as the "Public Certificate" from the Site Server Configuration
- Verify the value/path for the SSCommunicationCertPath is using the same certificate as the "Private Certificate" from the Site Server Configuration
- Find the entry for SSRootInstanceHostName
- Verify the hostname/value is correct
- Find the entry for SSConnectionPort
- Verify that matches the "Client Port" from the Site Server Configuration
- Save the changes to Infrastructure.WorkExecutionServices.Host.exe.config
- Verify firewalls are not blocking any of the ports listed in the Site Server Configuration
- Click "Apply" in the Site Server Configuration
- Recycle services and confirm all services start correctly
This typically occurs when the Work Manager Certificate and Site Server Certificate do not match or have expired.