The "Collector" database fails to install when I install the IntelligenceCenter.
How can I resolve a failed installation of IC where the install seems to complete, but if you examine the databases present on the box, you find that “collector” database (the database used by the DataCollector) is not present but the PolicyVision database (the database used by the IntelligenceCenter server) is present?
ANSWER: This problem occurs because a library file named SSLEAY32.dll and LIBEAY32.dllhas become corrupted or replaced with a different version than the one which supports Postgres 8.4. The offending version(s) of SSLEAY32.DLL and LIBEAY32.dll must be manually replaced. The issue can be determined by examining that the coll_db_config.log file in following directory will be empty:
C:\Program Files (x86)\PostgreSQL\8.4\data (for 64 bit)
In case of migration, C:\BlueCoat\DataCollector\logs\collector_migration_<Day>.log file will not be created. The error is not directly logged in any file but if you run configure_database separately, you’ll see the message as given:
C:\BlueCoat\DataCollector\lib\dbscript>set PG_HOME=C:\Program Files\PostgreSQL\8.4
C:\BlueCoat\DataCollector\lib\dbscript>C:\BlueCoat\IntelligenceCenter\Python\\python C:\BlueCoat\DataCollector\lib\dbscript\coll_db_config.py 1>"C:\BlueCoat\data\coll_db_config.log"
It also, because it is so widespread, has been a target for disguise of Key logger and Trojan software. It is often impossible to determine which software component replaced this file, but a post mortem should note any time stamps or audit trails or other locations on the server where this file is found.
1) In order to do so, the customer should obtain a copy of the PostgreSQL 8.4 validated file from BlueCoat support:
A. Open a command prompt and change to one of the locations noted above.
Rate this Page
Please take a moment to complete this form to help us better serve you.