The reports utilize SQL queries to complete. Were you using SQL 2008 Express R2 or a "full size" SQL 2008 edition such as Standard or Enterprise? If using normal SQL Server, is it installed with WebInspect or (better) collocated on a nearby machine?
Is your account a Local Administrator, or are you needing to use the Run As Admin feature to operate WebInspect?
I believe I ran into this sort of issue with the Developer Reference or Crawled URLs when testing out the new release. At first I thought the report was broken, but then later it ran fine, albeit a bit long. Just in case, I have submitted a defect investigation request to have those two reports reviewed for their SQL logic. Perhaps there is something inefficient inside their logic or views?
To troubleshoot this, sometimes the Report generator tool displays an error at the bottom, but sometimes not. I would check within the WebInspect application log and perhaps send it to Fortify Support. The logs for the app are located at the default folder below, although your own Application Settings (Directories panel) could have something else defined. You can also browse these logs using the Logs Viewer tool, but you have to click the "WebInspect" button to switch its focus away form the scan log folders.
The windows Application Log may also hold something, but the app log folder below is best for WebInspect details.
- C:\Users\%CURRENTUSER%\AppData\Local\HP\HP WebInspect\Logs\00000000-0000-0000-0000-000000000000\
-- Habeas Data
Micro Focus Fortify Customers-Only Forums – https://community.softwaregrp.com/t5/Fortify/ct-p/fortify
