
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
WebInspect API not working after SQL upgrade
Hi,
The webInspect API was working fine on the SQL server 2008. By fine, I mean, I was able to create/start new scans etc. But recently, we upgraded the SQL server to 2014 version and suddenly I cannot create/start scans. I keep getting this message: An error has occured.
Few more points:
1. I can create/start scans from the UI and they all work fine. Its just the API seems to have stopped working.
2. I turned on the debug level and have attached the log file.
4. I am using this curl command:
curl -d "settingsName=<Settings file name>&overrides={\"ScanName\":\"Test\",\"StartUrl\":\"http://zero.webappsecurity.com\",\"CrawlAuditMode\":\"CrawlAndAudit\",\"StartOption\":\"Url\"}" "http://<Host>/webinspect/scanner/"
If you have nay idea, what might be causing this issue or how I can debug it, please let me know.
Thanks,
Tarveen

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Unfortunately MS SQL 2014 is not yet supported by WebInspect, only SQL 2012 and SQL 2008. From the (attached) HP_Fortify_System_Requirements_4.30.pdf, here are the permitted databases for WebInspect 10.40 released April 2015.
SQL Server
(Theoretically no scan database limit)
Microsoft SQL Server 2012 with SP1 - Recommended
Microsoft SQL Server 2012 with SP2
Microsoft SQL Server 2008 R2 with SP2
SQL Server Express
(10 GB scan database limit)
Microsoft SQL Server 2012 Express with SP1 - Recommended
Microsoft SQL Server 2012 Express with SP2
Microsoft SQL Server 2008 R2 Express with SP3
Verified customers can access all documentation and internal forums at Protect724:
https://protect724.hp.com/community/fortify/fortify-product-documentation
-- Habeas Data
Micro Focus Fortify Customers-Only Forums – https://community.softwaregrp.com/t5/Fortify/ct-p/fortify