
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
There is no python code in my project though.
Had this on e JEE project (Java, JSP, JS) & on a NodeJS project.
Is SCA stumbling on something else and incorrectly reporting a Python related error? If so, on what?
Accepted Solutions

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
reply from support:
"Just found out that this is related to a bug in 4.30 which was fixed in 4.40 The dev comment as follows:
If "-django-template-dirs" skipped in command line (or refers to dir without html files) then there is no LicenseException for python when translating any html file (including django template html file)
So please update to 4.40 to fix this."

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hmm, Python's licensed separately which is why this warning occasionally crops up. It's odd we'd throw that when there's no Python present however. Is it possible to submit a case to fortifytechsupport@hp.com with the debug log for this scan? That should show what we're triggering this on.
It's also worth noting we don't actually support NodeJS just yet, although it's something we're actively working on. I've added you to the open enhancement request for this. It's possible support will be available in our next release, v4.40, along with the next rulepack release, 2015-R3. However this is subject to change.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
I switched to debug mode, got this output and sent it to fortifytechsupport. Hope they can help
[2015-07-13 14:30:28.348 Thread-13 Master SEVERE 236]
Your license does not allow access to Fortify SCA for Python
com.fortify.licensing.UnlicensedCapabilityException: Your license does not allow access to Fortify SCA for Python
at com.fortify.licensing.Licensing.getCapabilityConfig(Licensing.java:117)
at com.fortify.licensing.Licensing.requireCapability(Licensing.java:60)
at com.fortify.sca.frontend.PythonFrontEnd.runTranslator(PythonFrontEnd.java:133)
at com.fortify.sca.frontend.FrontEndSession.runSingleFrontEnd(FrontEndSession.java:242)
at com.fortify.sca.frontend.FrontEndSession.runFrontEnd(FrontEndSession.java:150)
at com.fortify.sca.Main$Sourceanalyzer.runSourceanalyzer(Main.java:613)
at com.fortify.sca.Main$Sourceanalyzer.run(Main.java:489)

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Thanks Geert, would it be possible to also attach the full log to the Support case? The stack from above shows us exactly what's being triggered, but outside of the context of the log we can't see what in your code is doing the triggering.
The good news is that without any Python in the code, this shouldn't actually be having an effect on the final results.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
reply from support:
"Just found out that this is related to a bug in 4.30 which was fixed in 4.40 The dev comment as follows:
If "-django-template-dirs" skipped in command line (or refers to dir without html files) then there is no LicenseException for python when translating any html file (including django template html file)
So please update to 4.40 to fix this."

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Not fixed in the recent 4.31 Patch?
Hopefully Support can provide you 4.40, since it does not release until this Fall. 😉
-- Habeas Data
Micro Focus Fortify Customers-Only Forums – https://community.softwaregrp.com/t5/Fortify/ct-p/fortify

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Oops. I was surprised that he mentioned 4.40 since I don't recall seeing it announced. So, that is why...

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
The fix came after 4.31 had ventured out into the world so missed out unfortunately.
If all goes to plan 4.40 is currently set for a September release. This bug shouldn't affect the result set though so in the meantime it is safe to just ignore the warning.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Is there a fix for SCA 18.20? I did not intend sourceanalyzer to scan any Python code (and there is none in the tree).

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
In fact you do not even need to run sourceanalyzer to get the error in 18.20:
PS C:\> sourceanalyzer -version
Fortify Static Code Analyzer 18.20.1071 (using JRE 1.8.0_181)
[error]: Your license does not allow access to Fortify SCA for Python
com.fortify.licensing.UnlicensedCapabilityException: Your license does not allow access to Fortify SCA for Python
at com.fortify.licensing.Licensing.getCapabilityConfig(Licensing.java:120) ~[fortify-common-18.20.0.1071.jar:?]
at com.fortify.licensing.Licensing.requireCapability(Licensing.java:63) ~[fortify-common-18.20.0.1071.jar:?]
at com.fortify.sca.frontend.Python3FrontEnd.runTranslator(Python3FrontEnd.java:158) [fortify-sca-18.20.1071.jar:
?]
at com.fortify.sca.frontend.FrontEndSession.runSingleFrontEnd(FrontEndSession.java:231) [fortify-sca-18.20.1071.
jar:?]
at com.fortify.sca.frontend.FrontEndSession.runFrontEnd(FrontEndSession.java:193) [fortify-sca-18.20.1071.jar:?]
at com.fortify.sca.Main$Sourceanalyzer.run(Main.java:527) [fortify-sca-18.20.1071.jar:?]


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
I also receive this. I was told that you needed a certain license to scan Python (it's quite expensive). Without this special license you'll get the error. I've gotten this error on every single version of SCA I've used since 4.3. I get this regardless of whether there's Python being scanned.


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
I have exacty the same error since testing with 18.20.
looks like some old issues returned in this version.