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 Security
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 Security
Unlock the full power of Microsoft Security
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Loading...
Loading...

BUG: Report Blocked Requests by Rule fails for longer time periods or periods with large data amounts

Expand / Collapse


This article applies to:

  • WebMarshal Reports 6.X
  • Marshal Reporting Console 2.1
  • Report "Blocked Requests by Rule"

Symptoms:

  • Running the report for a short time period (or a small group) succeeds
  • Running the report for a longer time period fails
  • Error message: No rowset was returned for this table, query or procedure
  • Error message: Error detected by database DLL

Causes:

  • A variable in the SQL Stored Procedure that summarizes data for this report is incorrectly defined. Large data values are not permitted.

Resolution:

To resolve this issue, upgrade to the latest version of MRC. This issue was first fixed in release 2.5.0.1189.

 

Workaround

 

If you cannot upgrade immediately and you are comfortable editing SQL stored procedures, you can correct the issue.

  1. Open the WebMarshal database using SQL Server Enterprise Manager or SQL Server Management Studio.
  2. For WebMarshal Reports, edit/Modify the Stored Procedure RPT_ExceptionByRule
  3. Locate the line [FileSize] int,
  4. Alter this line to read [FileSize] bigint,
  5. Update the Stored Procedure by saving or clicking Execute, depending on the version of SQL management software you are using.
  6. For Marshal Reporting Console, edit/Modify the Stored Procedure MRC_BlockedRequestsByRule
  7. Locate the line [FileSize] int,
  8. Alter this line to read [FileSize] bigint,
  9. Update the Stored Procedure by saving or clicking Execute, depending on the version of SQL management software you are using.


To contact Trustwave about this article or to request support:


Rate this Article:
     

Add Your Comments


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