CODEWITHSUNDEEP
fortify
ridi
ridi

Reputation: 61

Fortify 4.2 SSC Error Processing

I’m using fortify 4.2 (SCA version: 6.2). I’m having hard time to upload an fpr file to the SSC. I always get “Error Processing” and I cannot tell what the problem is. I’ve opened the fpr file with auditworkbench and checked the Certification: it is valid.
Furthermore, I have a plenty of Scan errors and the majority is labeled with error code 1103 with the following description: Translator execution failed. Translator returned status 139.
Any leads?
PS: I’m scanning a large application which includes different modules written in C, C++ and JAVA.

Upvotes: 1

Views: 3548

Answers (2)

jwright
jwright

Reputation: 1

The 139 error usually means that you are using a newer version of C/C++ than Fortify supports. Currently we are using C++14 or higher and getting the error with 19.2.

Upvotes: 0

SBurris
SBurris

Reputation: 7448

Based on your comment about the two files:

  • myFile.h
  • myFile.H

I am suspecting that the database in the back-end of SSC is case-insensitive?

Starting with Fortify 4.30 (or possibly 4.40) SSC started enforcing that database collation be case-sensitive (before this time it was stated it should be but was not enforced).

You need to upgrade the version of Fortify that you are using to one of the newer versions (current latest is 16.10). The SSC install documentation will contain instructions on migrating your SSC database from case-insensitive to case-sensitive.

Upvotes: 2

Related Questions