This section helps you remedy common problems and understand how better to use the Veracode XML APIs and plugins.
|Any API||I received a HTTP 401 or Access Denied error. I do not have access to the APIs or I am unsure what kind of access I need.||You need to have specific API roles assigned to your user account by your Veracode administrator. See Understanding API Access for more information.|
|Any API||I cannot log in to Veracode when using the APIs.||Verify that your IP address is in the list or range of addresses in the Allowed IP Addresses field of your user account login settings. If the IP range is set incorrectly, edit the Allowed IP Addresses field to include the IP address of the location of your login.|
|Any API||The scan stopped after prescan||To determine why a scan that started from an API failed after prescan, review the response code returned from the beginscan.do API call. When your script calls beginscan.do, the API returns a status code that confirms the scan successfully started, or provides an error message to explain why the scan did not start.|
|Any API||I received cURL error 35.||If you receive the cURL error 35: "Unknown SSL protocol error in connection to ...", you need to update your version of cURL. Alternatively, you can pass the option -3, which forces cURL to use SSL version 3 when negotiating with a remote SSL server.|
|Any Integration||I have received one of the following messages:
||If you are using an integration that attempts to connect over TLS 1.0, you may receive one of these error messages. Read more about our TLS support.|
|Archer API||Invalid IP address range.||Ensure that you are attempting to connect from an IP address that is allowed by the IP address restrictions for the login you are using.|
|Archer API||Invalid login type.||Ensure that you are providing credentials for an API class login with the Archer API role.|
|Archer API||Invalid or null token.||Each login account is limited to using five tokens at a time to download Archer reports. The last five of generated tokens are valid. All tokens expire after 30 days whether used or not. Using invalid tokens returns HTTP status code 403.|
|Archer API||Incorrect date format.||The date format used by the date_from and date_to fields is dd-mm-yyyy, meaning, date then month and year.|
|Archer API||The report not ready.||If you try to call downloadarcherreport.do before generatearcherreport.do has completed, you receive HTTP status code 204 to indicate no content is available. Try to download the report at a later time. If after an excessively long time, the report still is not returned, please contact Veracode Support.|
|Archer API||The results file is too large.||When attempting to fetch the Archer feed for a large number of applications at once, the Veracode Platform may return HTTP status code 500. It is best in these cases to fetch the data using the optional arguments for the Archer API to limit the scope of the data being pulled (e.g. using scan_type and/or a date range). Once all the historical data is in place, use one of the period arguments ( yesterday , last_week , or last_month ) to pull data on a scheduled basis.|
|Eclipse Plugin||I experience a PKIX path building failure when installing the plugin from Eclipse.||Add the following lines to the eclipse.ini file in your
-vmargs --Djavax.net.ssl.trustStore="path for cacerts" --Djavax.net.ssl.trustAnchors="path for cacerts"
|Jenkins Plugin||I receive one of these messages:
|Jenkins Plugin||The following message appears in the console output: The policy status 'Did Not Pass' is not passing. Unable to continue.||This message indicates that you selected the Wait for scan to complete checkbox in your job configuration and the scan failed to pass your policy. If you want builds for scans that fail policy to complete, you must deselect that checkbox.|
|Jenkins Plugin||The test connection action fails. There is no success message.||
|Jenkins Plugin or Java API Wrapper||The following message appears: Requested array size exceeds VM limit.||This error indicates you are attempting to upload an archive that is too large for the current limit (in GB). Check the content and size of the files or archives you are uploading to verify you are using the correct files.|
|Jenkins Plugin or Java API Wrapper||
The following message appears:[16.01.11 14:28:39] java/net/HttpURLConnection.setFixedLengthStreamingMode(J)V Build step Upload and Scan with Veracode marked build as failure Finished: FAILURE
|This message indicates that the Java version you are using is not Java 7 or later as required by the Veracode Jenkins Plugin and the Veracode Java API wrapper.|
|JIRA Plugin||If you need to troubleshoot any issues, turn debug logging on.
You can review the logs at <JIRA home directory>/Application Data/JIRA/log/atlassian-jira.log.
|Maven Build Script||The following message is returned: java.lang.ClassNotFoundException: Cannot find the specified class com.ibm.websphere.ssl||The IBM WebSphere environment may prevent a Veracode UploadandScan target from executing if the Maven build script dependencies with the Java class path are missing. To resolve this, generate two pom.xml scripts, using one specifically for the Veracode upload.|
|Results API||The getappbuilds.do call is slow to deliver information.||Veracode recommends that you use getapplist.do to generate a list of all applications and getbuildlist.do to generate a list of all builds for an application. You can then use getappinfo.do and getbuildinfo.do to retrieve the information about specific applications and builds.|
|Upload API||I do not know if the prescan is complete or successful.||To check the prescan results in the Upload API, call getprescanresults.do.|
|Upload API||My scan does not complete due to non-fatal errors.||If you want to ensure the scan completes even though there are non-fatal errors such as unsupported frameworks, make sure you use the scan_all_top_level_modules parameter when you use the beginscan.do call.|
|Any Plugin, Any API||When using either a Veracode plugin, the Veracode API wrappers, or a custom script, I see this returned in the output text: App not in state where new builds are allowed.||This message indicates that a previous static scan did not succeed for the specific application. Log into the Veracode Platform and review the application's current scans to determine if the previous scan did not successfully complete. A previous scan may still be in progress. If a previous scan is still running due to an error, select Delete. You can then use the plugin to submit a new scan request.|
|Visual Studio Extension||I received a download error that says No applications exist for the specified user's account.||Using the Visual Studio Veracode menu, you may have attempted to download results after selecting a specific application for which you do not have permission to access. You must be a member of each team associated with an application to be able to access that application's data.|
|Visual Studio Extension||The Upload Build menu does not populate the Application dropdown list or allow me to complete the Build text box.||This message indicates that you do not have the required role to either create a new application or build.|
|Visual Studio Extension||I receive this message Support Issue: No precompiled files were found for this ASP.NET web application.||Use the Veracode Visual Studio Extension to prepare your .NET application for uploading to Veracode. For information on how to use this extension, go here.|
|Veracode Azure DevOps Extension||The Veracode Release Summary report is not displaying in the TFS on-premise extension.||If you rename the build step task Upload and Scan, the extension cannot find and execute the task, and no Veracode Summary Report is created.|
|Any IDE Plugin or Extension||I am having problems with my credentials and am prompted to enter them multiple times.||
For assistance with errors you receive while compiling your application, see the Troubleshooting Precompilation Errors page.
If you cannot find the solution to your problem on this page, please contact Veracode Support.