2019-05-30 09:01 AM
Has anyone encountered this issue?
Under Respond->Alerts, noticed an odd attribute for Source, it appears as Missing translation: respond.alert.source.
2019-05-30 09:07 AM
This message could be because, in my example, you upgraded to 11.3 from a previous version 11.X version and the following post steps were not performed. Post Install Task 14 and Task 15 involving the Respond Service at the time of this writing.
https://community.rsa.com/docs/DOC-100381
Please note that applying this fix now does not retroactively fix what has already been received. It will only fix incoming data.
Does that fit your situation?
2019-05-30 02:12 PM
Hi Aaron,
Thank you for your reply!
The scenario may apply to my situation, but I cannot be certain that the post steps were implemented or not. Would this be the only cause and how can it be resolved?
~David
2019-05-30 02:22 PM
It is the case I have been seeing more and more lately for 11.3 upgrades. I have presently not heard of anything else at this point that does it. However, these scripts control the mapping of incidents and alerts in respond so more than likely this is the cause. If you don't have customization, it's safe to follow the steps I highlighted to you and restart the respond service. Otherwise, without restoring them, they will be lost until reapplied to the newly generated scripts.
If you are unsure and you want to talk about in a less public forum, feel free to open a support case and me or someone else will try to assist you.
2019-11-19 12:11 PM
When attempting to access the document I get an unauthorized page. Can this potential solution to an issue be posted somewhere customers can access? Thanks.
2019-11-19 12:37 PM
You're getting "Unauthorized” because that document no longer exists.
The solution here is in the Respond section of the Post-Upgrade Tasks that are included in the various <sourceVersion>-to-<targetVersion> upgrade guides, which can be found in each version's product documentation page: