MKnafve (Community Member) asked a question.
I am scanning my software using Veracode on a daily basis (using TeamCity plug-in). The last couple of builds has hanged in status "Pre-Scan Submitted".
If I navigate to the scan in the Veracode UI it tells me that:
* The scan status is "Request Incomplete"
* The latest entry in the activity log is 'Static prescan verification started for "MySoftware Version"'
* The TeamCity Veracode plug-in tells me status is "Pre-Scan Submitted"
If I click "Review modules", it tells me that "Prescan in Progress...".
It has been in this state for 2 hours. Same thing happened yesterday. I deleted the scan after 2 hours, and then re-run it but the result was the same.
Is there some way to troubleshoot this which does not involve setting up a meeting with Veracode? It seems very strange to me that the scan is just hanging without any feedback. According to the Veracode status page all systems are operational.
.png){kind=logo}
I don't recall seeing this issue in recent memory with our submissions. If you haven't already done so, this is one where I think you will have to open a support ticket to have the support team look at the specifics going on in your case. I am suspecting a Veracode platform issue of some sort just based on your description. However, if you get details on the cause, and it's related in some way to your package, I think it's also a good idea to share that here in case others have the problem in the future.
You can open support tickets from with the Community, using the Contact Support menu item under your profile icon in the top right.
Thanks. I have submitted a support case to Veracode.
After ~27 hours, the stuck scan moved to status "Module Selection Required", which is also seems incorrect since we provide the module selection as part of uploading the software to Veracode (the TeamCity plug-in provides the module selection via the Veracode API, so we never select it manually in the UI).
I did try to scan the same binaries in separate sandbox 3 times and those were all successful. So right now it looks like a temporary glitch.
I am seeing the same thing. Can you tell me how this was resolved? Thank you.
I am facing same issue. Have we got solution for above issue?