What is the cause of this
What is the cause of this
I have seen a need to restart AM Server services on the primary when this happens.
There have been at least two Jira bugs reporting this behavior, and while agent upgrade has been mentioned as the fix, so has an incorrect policy and AM server restart. We think there is some certain set of circumstances that can trigger this, as we have seen it several times, but the agent upgrade to 7.3.3. is the starting place, I had one report where we still needed to restart AM services for what a customer insisted was a 7.3.3 agent. I could not verify agent version though.
AAWIN-2296 - AAWIN 7.3.0.26 OA download fails after initial success with “Failed to send day data” repeating every 2 seconds
Customer reported this problem was fixed with agent 7.3.1[40] back in Aug. 2016
AAWIN-2380 - CE Assist - AAWIN v.7.3.2.90 repeats Offline requests every 1 second even after failure
This closed because Policy mmistake found
In both cases, it appears that it was actually a restart of AM services that fixed this.
where do i find 7.3.3.103?
The link to the latest released 7.3.3[99] Windows agent build on the RSA Link community Web Site, which includes a full install kit
https://community.rsa.com/docs/DOC-76689
This 2nd link is for the 7.3.3[103] update, which is run on top of a 7.3.3 agent install as it does not include a full install kit. This is an update kit with the latest and very important last Offline fix.
Symptoms include;
DPS_DA_REQUEST_DATABASE_ERROR (212) - agents dasrv log
DA_REQUEST_DATABASE_ERROR - Server imsTrace.log
But especially the repeating ,,,,Received: Proof ... Proof validation failed ... Invalid proof in the imsTrace.logs or Real Time Authentication Monitor Details on the AM server, which indicate a definate need for agent update 7.3.3[103], and possible new Server or agent bug which is currently being investigated by CE and CS.
But we need to rule out fixed agent bugs in 7.3.3[103] in order to prove any new server or agent bug.
thanks, i have a number of agents exhibiting this behavior.
Please let us know if the responses you received from Edward Davis and Jay Guillette were able to help you resolve your issue.
Regards,
Erica
Hi, thank you. It's been mostly helpful. On clients that are spamming the console with the error it has cleared it up, in general. I have 1 or 2 clients, that despite being patched, still throw the error. They don't continuously throw but instead give it 5-10 times and then stop. Are there any newer patches available to try?
7.3.3[103] is very good, but the real fix for invalid proof every 1-2 seconds in Real Time Monitor is 7.3.3[114], which has not been QE tested yet, but you can get a copy if you call Support.
[103] fixes everything else, and restarting services tends to stop the invalid proof errors, but they can come back, so you may notice less of them, but they won't completely go away until you get 7.3.3[114] or later (probably will be 7.3.4)
Just deployed v7.3.3.123 (from v7.3.3.114) last week and for the first time the issue appears to be completely resolved. We deployed RSA SecurID about 5 years ago and have seen this issue from day one. I'm both relieved and a bit frustrated that it's taken this long to resolve.
Hi Ronald,
I have moved this thread to the RSA SecurID Access so that you can get an answer to your question.
You can post future questions and discussions directly to that community by clicking on the Ask a Question or Start a Discussion button on the RSA SecurID Access page.
Thanks,
Jeff