000017610 - Exception when selecting Add New in some types of Notification builders in RSA Archer

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000017610
Applies ToRSA Product Set: Archer
RSA Product/Service Type: Archer
RSA Product Version: 5.2.x to 5.5.x
IssueException occurs when clicking Add New from Manage Subscription Notifications, Manage Scheduled Report Distributions, Manage On Demand Notification Templates, and Manage XML Notifications.

Sample exception from Archer Logs:
<ApplicationData>
  <TraceData>
    <DataItem>
      <TraceRecord Severity="Error" xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord">
        <TraceIdentifier>Archer.Web</TraceIdentifier>
        <LogReferenceId>051314-195039-2266</LogReferenceId>
        <Description>[Arg_KeyNotFound]Arguments: Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=5.1.30214.00&File=mscorlib.dll&Key=Arg_KeyNotFound</Description>
        <AppDomain>/LM/W3SVC/1/ROOT/FRAME-1-130444841795216845</AppDomain>
        <ContextData>
          <BaseUrl>http://localhost/Archer/notification/ManageSubscriptionNotifications.aspx</BaseUrl>
          <PageID>ManageSubscriptionNotifications</PageID>
        </ContextData>
        <Exception>
          <ExceptionType>ArcherTech.Web.UI.ArcherException, ArcherTech.Web, Version=5.4.10300.1020, Culture=neutral, PublicKeyToken=null</ExceptionType>
          <Message>[Arg_KeyNotFound]Arguments: Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=5.1.30214.00&File=mscorlib.dll&Key=Arg_KeyNotFound</Message>
          <Source>
          </Source>
          <StackTrace> at ArcherTech.SL.Common.DependencyManager.&lt;&gt;c__DisplayClassc.&lt;OnCompleted&gt;b__a()</StackTrace>
        </Exception>
      </TraceRecord>
    </DataItem>
  </TraceData>
</ApplicationData>
CauseAn Application or Questionnaire failed to copy completely leaving the module in a corrupt state.
ResolutionDelete the bad Application or Questionnaire.  Unfortunately, there is not an easy way to locate the bad module.
  1. From Manage Applications or Manage Questionnaires, try opening any copied modules.  
  2. If an exception occurs, delete the module.
  3. Try creating a new Subscription Notification.  
  4. If an exception occurs, repeat steps 1 - 3 again.
Legacy Article IDa65683

Attachments

    Outcomes