The Site Server Console reports the Site Server Status is "Invalid" and it says "Could not connect to Root Site Server" or "Could not connect to root instance".
- 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: The certificates on all Site Servers (root & children) must match.
- View the certificates properties and make sure they have not expired. If they have, you 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 and SSCommunicationsCertPath
- Verify the value/path for the SSAgentCertFile matches the "Public Certificate" from the Site Server Configuration
- Verify the value/path for the SSCommunicationsCertPath matches 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 settings for the Work Manager don't match the Site Server Configuration our the necessary certificates have expired.