000039122 - Getting an error when accessing all Silverlight pages in RSA Archer

Document created by RSA Customer Support Employee on Jul 29, 2020
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000039122
Applies ToRSA Product Set: RSA Archer
RSA Version/Condition: 6.x
IssueIf some Silverlight pages work, this article likely does not apply but if all Silverlight pages in Archer throw the following error, this may help.

<E2ETraceEvent xmlns="http://schemas.microsoft.com/2004/06/E2ETraceEvent">
  <System xmlns="http://schemas.microsoft.com/2004/06/windows/eventlog/system">
    <EventID>0</EventID>
    <Type>3</Type>
    <SubType Name="Error">0</SubType>
    <Level>2</Level>
    <TimeCreated SystemTime="2020-07-10T20:18:09.2136771Z" />
    <Source Name="Archer.Web" />
    <Execution ProcessName="w3wp" ProcessID="10136" ThreadID="179" />
    <AssemblyVersion>6.8.200.1037</AssemblyVersion>
    <Computer>ServerName</Computer>
  </System>
  <ApplicationData>
    <TraceData>
      <DataItem>
        <TraceRecord Severity="Error" xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord">
          <TraceIdentifier>Archer.Web</TraceIdentifier>
          <LogReferenceId>071020-201809-2136</LogReferenceId>
          <Description>
              [HttpWebRequest_WebException_RemoteServer]Arguments: NotFoundDebugging 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.50918.0&File=System.Windows.dll&Key=HttpWebRequest_WebException_RemoteServer
          </Description>
          <AppDomain>/LM/W3SVC/1/ROOT-1-132388821562000248</AppDomain>
          <ContextData>
            <BaseUrl>http://BaseUrl/accesscontrol/LDAPSetup.aspx</BaseUrl>
            <PageId>LDAPSetup</PageId>
            <frameWidthHeight>1615,771</frameWidthHeight>
          </ContextData>
          <Exception>
            <ExceptionType>ArcherTech.Web.UI.ArcherException, ArcherTech.Web, Version=6.8.200.1037, Culture=neutral, PublicKeyToken=null</ExceptionType>
            <Message>
                [HttpWebRequest_WebException_RemoteServer]Arguments: NotFoundDebugging 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.50918.0&File=System.Windows.dll&Key=HttpWebRequest_WebException_RemoteServer
            </Message>
            <StackTrace>
                  at System.ServiceModel.AsyncResult.End[TAsyncResult](IAsyncResult result)
                  at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
                  at System.ServiceModel.ClientBase`1.ChannelBase`1.EndInvoke(String methodName, Object[] args, IAsyncResult result)
                  at ArcherTech.SL.ManageAppearance.Proxy.AppearanceThemeService.AppearanceThemeServiceClient.AppearanceThemeServiceClientChannel.EndGetActive(IAsyncResult result)
                  at ArcherTech.SL.ManageAppearance.Proxy.AppearanceThemeService.AppearanceThemeServiceClient.ArcherTech.SL.ManageAppearance.Proxy.AppearanceThemeService.IAppearanceThemeService.EndGetActive(IAsyncResult result)   
                  at ArcherTech.SL.ManageAppearance.Proxy.AppearanceThemeService.AppearanceThemeServiceClient.OnEndGetActive(IAsyncResult result)   
                  at System.ServiceModel.ClientBase`1.OnAsyncCallCompleted(IAsyncResult result)
            </StackTrace>
          </Exception>
        </TraceRecord>
      </DataItem>
    </TraceData>
  </ApplicationData>
</E2ETraceEvent>


 
CauseThe most common cause of this is a mis-configured web.config file. For example: If the web.config is configured for https and you access Archer over http it could throw the error on any Silverlight page.
ResolutionTo correct the issue you will need to update the web.config file with the correct http/https setting. 

The easiest way to do this is to use the web.config editor.

Once the web.config file has been updated and an IISreset has been performed, try again to see if it corrects the issue.

Attachments

    Outcomes