Unable to communicate with the reporting component and in the Reporting webpage appears Internal server error
|Article:TECH148753|||||Created: 2011-01-21|||||Updated: 2012-07-21|||||Article URL http://www.symantec.com/docs/TECH148753|
The message "Unable to communicate with the reporting component" is received after logging into the SEPM console and data for the Home, Monitors and Reports pages is not loaded.
If logging into the Reporting webpage http://<IP_address>:<port>/Reporting the message "Internal server error" appears.
--- snip ---
Fatal error: Uncaught exception 'com_exception' with message 'Failed to create COM object `ADODB.Connection': Class not registered ' in C:\Program Files\Symantec\Symantec Endpoint Protection Manager\Inetpub\Reporting\Common\ado.php:20 Stack trace: #0 C:\Program Files\Symantec\Symantec Endpoint Protection Manager\Inetpub\Reporting\Common\ado.php(20): com->com('ADODB.Connectio...', NULL, 65001) #1 C:\Program Files\Symantec\Symantec Endpoint Protection
--- snip ---
For this error to be displayed in the browser, the PHP errors need to be enabled in the php.ini.
C:\Program Files\Symantec\Symantec Endpoint Protection Manager\php\
display_errors = On
display_startup_errors = On
Unregistered ADO DLLs.
If available for the Operating System, consider to reinstall the Microsoft Data Access Components (MDAC) package.
External reference: http://msdn.microsoft.com/en-us/library/ms810805.aspx
Otherwise execute the following procedure:
1. Go to Start > Run
2. Run the commands:
Regsvr32 "C:\Program Files\Common Files\system\ado\Msado15.dll"
Regsvr32 "C:\Program Files\Common Files\Microsoft Shared\DAO\Dao360.dll"
3. It should be possible to log into the Reporting web page, which means that the issue was solved.
Article URL http://www.symantec.com/docs/TECH148753