Skip to main content

LevelBlue Completes Acquisition of Cybereason. Learn more

LevelBlue Completes Acquisition of Cybereason. Learn more

Services
Cyber Advisory
Managed Cloud Security
Data Security
Managed Detection & Response
Email Security
Managed Network Infrastructure Security
Exposure Management
Security Operations Platforms
Incident Readiness & Response
SpiderLabs Threat Intelligence
Solutions
BY TOPIC
Offensive Security
Solutions to maximize your security ROI
Operational Technology
End-to-end OT security
Microsoft
Unlock the full power of Microsoft Security
Securing the IoT Landscape
Test, monitor and secure network objects
Why LevelBlue
About Us
Awards and Accolades
LevelBlue SpiderLabs
LevelBlue Security Operations Platforms
Security Colony
Partners
Microsoft
Unlock the full power of Microsoft Security
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Loading...
Loading...

PRB: Security Reporting Center stops creating reports for a scheduled job

Expand / Collapse


This article applies to:

  • Security Reporting Center 2.1

Symptoms:

  • Security Reporting Center stops creating reports for a scheduled job.
  • A report has been generated fine for a while, and then stops being generated by the same job.
  • The job is set to generate reports for this time frame, but it is not generating reports.

Causes:

This problem could occur if the MySQL database loses track of its indexes and unique identifiers. In this situation, when a new record is inserted, the databases uses a bad identifier and this problem can result. 

Information:

The following procedure should resolve the issue:

  1. Stop the NetIQ Scheduler Agent service.
  2. Open a command prompt
  3. cd to the Security Reporting Center installation directory. For instance the directory may be:
    C:\Program Files\NetIQ\Security Reporting Center\
  4. From the installation directory, cd into the common\mysql\bin directory
  5. Log into mysql. You need to use this command to log in:

    mysql -u username -p

    Note: The username is case sensitive.
  6. When you log in, you will see the following:

    Enter password: ******
    Welcome to the MySQL monitor.  Commands end with ; or \g.
    Your MySQL connection id is 27804 to server version: 3.23.54-nt
    mysql>
  7. Change to the wt_config database with the following command:
    mysql> USE wt_config

    You will see this after the command is successful:
    Database changed
  8. To see what is listed in the chronicles database, use the following command:

    mysql> select * from netdb_chronicles;
  9. To delete all of the data in this database, use the following command:

    mysql> delete from netdb_chronicles;
  10. Use the command from step 8 (select * from netdb_chronicles;) and make sure the table is empty
  11. Exit mysql by using the following command:

    mysql> \q
  12. Start the NetIQ Scheduler Agent service

Notes:

CAUTION: Editing the MySQL database directly is potentially dangerous. The changes recommended above are irreversible. A front end interface allows greater control and should be used if available.

A number of free GUI tools for MySQL administration are available.

The tool maintained by MySQL AB is available at the following URL: http://dev.mysql.com/downloads/gui-tools/

Note: SRC uses an older version of MySQL, so you may see a warning about version mismatch.

MySQL-Front, a well-known GUI tool, is no longer available.

This article was previously published as:
NETIQKB48997

To contact LevelBlue about this article or to request support:


Rate this Article:
     
Tags:

Add Your Comments


Comment submission is disabled for anonymous users.
Please send feedback to Trustwave Technical Support or the Webmaster
.