Check the AD Bridge database on the database server to check whether the table containing events is complete. If necessary, write a manual query to view recent events or to look for an event. For example, with SQL you can use the SQL command-line utility to open the LikewiseEnterprise database and run the following command to display all the events in the table named Events:
select * from Events;
If you cannot open or read the database, you might not have sufficient privileges to access it, which can result in problems when you run reports in the management console or use the Operations Dashboard.
If you use SQL Server and the Events table is empty, use the SQL Server Configuration Manager to make sure that the name-pipe client protocol is enabled. If it is not and you have to enable it, you must restart the SQL Server service for the changes to take effect.
If you find events in the Events table, check whether the events are also present in the EventsViewWithOUName view. If an event appears in the Events table but not in the EventsWithOUName view, it is because the database cannot associate your event with a computer in Active Directory. Run the ldbupdate.exe script and then check whether the event now appears in both views.
Collector is not Displayed in the Management Console
Right-click the Enterprise Database Management node to check the Reporting database connection.
Run a test connection to ensure that it can connect.
Close the BeyondTrust management console.
On the services server, open the Reporting Database Connection.
Configure the reporting connection for the Reaper service.
Restart the Collector and Reaper services.
Open the management console and the collector is displayed under the Database Management node.
