All of our Symantec EndPoint Protection (SEP) installs have been flawless up until today.
Unable to communicate with the reporting component.
Trying to find the solution in the midst of all of the fluff that comes up while searching for it has been tough!
The following Symantec knowledge base article helped us out:
- Error: "Unable to communicate with the reporting component" when opening Symantec Endpoint Protection Manager (MR2) on Microsoft Small Business Server 2003
First, we needed to correct the ODBC settings. Since we are on SBS 2008, we need to access the 32bit version of the ODBC manager.
- Start –> Run –> odbcad32.exe [Enter]
- UAC: Continue
- System DSN tab:
- ODBC: Leave
- User ID: DBA
- Password: Same as your SEP Admin
- Server Name: MY-SBS
- TCP/IP: SBS IP Address
- Leave alone.
You should see:
From there, elevate a command prompt and:
- iisreset [Enter]
The second part of the mentioned article indicated that we should change the service associated with the DefaultAppPool. We did not do this since so many services depend on that pool.
After resetting IIS, restart the two Symantec services and you should see:
At least we are not looking at a reinstall!
Note that the Symantec communication ports need to be added to the SBS 2008 Windows Firewall with Advanced Security:
- Admin site: 8014
- Admin communication: 8443
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book