I'm using the latest version of HP Fortify Static Code Analyzer, 4.21. The batchfile "bin\fortifyclient.bat" with the argument uploadFPR, gives a "An unexpected error occurred" and the exitcode is -12000.
The uploadFPR has worked before (previous week) on the same computer with the same source.
So I don't know what is causing this error. I have tried to use a new AnalysisUploadToken, but that makes no difference.
I cannot find what this particular Fortify exit code -12000 means. Does anybody know what it means?
I hit this same error when I upgraded my SCA client.
I believe the error indicates that the FPR file was generated with a version higher than the installed Fortify SSC server.
After downgrading my client, and creating a new FPR file, it uploaded correctly.
Update: After more faults, it appears this error is more of a general processing fault of the FPR file. Your best bet is to look at the SSC server logs for processing exceptions that might reveal the reason the processing failed.
not sure if the SCA and fortify utility share the same error code. For the sourceanalyzer, error [12000]=ASP/VBScript Translation Fidelity: ; Indicates how much of the classic asp and VBScript was translated successfully. Fix parse errors to increase.
Related
Recently I have installed Xtext and tried to run the default Hello world! code using the tutorials available on youtube. However, when I try to run the code I am getting 44 errors.
I am new to using Xtext as well as eclipse. I have tried to reinstall eclipse a lot of times. I have tried with normal version, enterprise version and DSL tools version. But every time I am getting the same errors. Please help me resolve this issue. I tried to find out what these errors meant and how to resolve them over the eclipse community forums but did not find any solution.
All the errors are repetitions of the following two errors.
Description Resource Path Location Type
Duplicate field InternalMyDslParser.FOLLOW_ InternalMyDslParser.java /org.xtext.example.mydsl.ide/src-gen/org/xtext/example/mydsl/ide/contentassist/antlr/internal line Java Problem
and
Description Resource Path Location Type
Syntax error on token "?", delete this token InternalMyDslParser.java /org.xtext.example.mydsl.ide/src-gen/org/xtext/example/mydsl/ide/contentassist/antlr/internal line Java Problem
Please Help me resolve this issue.
I have a fairly involved 1.0 dart app I'm trying to upgrade along with another programmer, and we keep being stumped by silent errors.
Just in time compilations fail with no information other than just "Build Failed". Running build_runner in verbose mode shows that there is an AssetNotFoundException in dartdevc.module itself, but no actaul useful errors (such as what asset in particular can't be found).
Is there any way I can get actually useful information out of this?
You can try running the build with --verbose to get more details and a stack trace. If there are cases with error messages that are not effectively pointing to the problem you can file an issue at https://github.com/dart-lang/build/issues - ideally with a reproduction case. If your project is open source and we can access the repo we should be able to use it as a reproduction case to check.
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.
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.
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.
We just set up TFS 11 for the first time. Running a gated check in, it succeeds but returns this message:
'srctool.exe' returned an unexpected exit code: '-1'. An error
occurred when opening a file "CustomDllName.dll": Assembly
"CustomDllName.dll" is not a valid .NET assembly and will be skipped
for analysis.
Well, it's right: that file is a legacy Visual Basic 6 DLL that we don't have much control over. It's included in the project for COM access to some of the methods.
Is there a way to instruct srctool.exe/TFS to skip that file when doing the inspection? Or another way to attack this?
Here is the solution that ultimately worked for me
A member of the TFS 11 team at Microsoft mentioned to me that the problem is due to a change in behavior that the Windows 8 team made to the srctool.exe tool.
By copying this file from the Windows 7 SDK (WinDBG) toolkit and overriding the one included in TFS 11 Beta, I was able to successfully run a build without any errors.
Is this a srctool.exe error from the shipped IndexSources activity? srctool.exe in this activity does one thing, which is to list the source files information in the pdb. I am not a srctool expert so I don't know why it fails in this case. I do know that srctool.exe has some behavioral changes in version 11, most of those are fixes from the previous version.
There is a workaround which requires udpating the build template. It is not very nice but it works. Srctool.exe is run (inside IndexSources activity) for each pdb file in the SymbolFiles collection. Now that you know which pdb fails, you can update the build template to add a RemoveFromCollection activity before the IndexSources activity that remove the troubled pdb from the SymbolFiles collection. This is by far the most straightforward workaround I can think of.
Alternatively, you can edit FindMatchingFiles activity's search pattern to exclude the pdb files you don't want to have sources indexed.
Based on the error message you got, it doesn't seem to be related to the known issue Ed mentioned. We fixed this issue for the next release, so if it's related, it should be fixed :-)
Let me know if you have any issue with VS11 Beta around the build templates.
Thanks.
I had OpenCV lib installed on my machine and all was working fine, until I decided to try the new version of the lib 1.1pre. Since that moment I get the following error:
Unhandled exception at 0x10012c5d (highgui110.dll) in foo.exe: 0xC0000005: Access violation reading location 0x719b3856.
I've tryied to uninstall and reinstall the lib....same thing happen.
What can I do? How can I fix this problem?
I'm using VS 2005 Express Edition on a Windows Vista OS.
Two solutions:
Revert back to the OpenCV lib that worked for you and wait for a non-pre release. Pre-releases are often a bit unstable.
Get the sourcecode of OpenCV from the sourceforge page. Compile the DLL in debug mode.
If the crash happends again you'll be able to see the source where it happend. That may or may not give you a hint what went wrong. Maybe you accidently passed a wrong parameter or it's a bug in OpenCV.
If it's something simple, fix it yourself and submit a patch. Otherwise I suggest that you file a bug-report at the OpenCV project page.
Btw: The bug-tracker is here: https://sourceforge.net/tracker/?atid=376677&group_id=22870&func=browse