000033617 - In RSA Archer 6.x, browsing to Microsoft Silverlight page using HTTPS fails: An unexpected error has occurred in the system

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

Article Content

Article Number000033617
Applies ToRSA Product Set: Archer
RSA Product/Service Type: Archer
RSA Version/Condition: 6.x
 
IssueWhenever you try to access Silverlight pages with HTTPS, you will get “An unexpected error has occurred in the system. The error Log Reference ID is: MMDDYY-HHMMSS-XXXX. Please try your request again.   If problems persist, please contact your system administrator.”
Sample error from w3wp log:
<ApplicationData>
  <TraceData>
    <DataItem>
      <TraceRecord Severity="Error" xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord">
        <TraceIdentifier>Archer.Web</TraceIdentifier>
        <LogReferenceId>052815-140634-1571</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.40416.0&File=System.Windows.dll&Key=HttpWebRequest_WebException_RemoteServer</Description>
       
<AppDomain>/LM/W3SVC/1/ROOT/RSAarcher-1-130772951733443985</AppDomain>
        <ContextData>
          <BaseUrl>https://XXXXXXXXXXXX/RSAarcher/Integration/DataImportManager.aspx</BaseUrl>
          <PageID>ManageDataImport</PageID>
          <Module>ModuleId: 149, ModuleName: Business Unit, ModuleStatus: ActiveInProduction, ModuleType: Application</Module>
          <IsEndUserView>true</IsEndUserView>
        </ContextData>
        <Exception>
          <ExceptionType>ArcherTech.Web.UI.ArcherException, ArcherTech.Web, Version=6.0.0.1271, 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.40416.0&File=System.Windows.dll&Key=HttpWebRequest_WebException_RemoteServer</Message>
         
<Source>
          </Source>
          <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>

 
CauseConfiguration error with Web.Config file.
ResolutionMake the following 4 changes in C:\inetpub\wwwroot\RSAarcher\web.config file:
  1. Search for httpGetEnabled attribute and change from <serviceMetadata httpGetEnabled="false" /> to <serviceMetadata httpsGetEnabled="true" />
  2. Search for <security mode="Transport" /> and uncomment it
  3. Search for <httpTransport maxReceivedMessageSize and change from <httpTransport maxReceivedMessageSize to <httpsTransport maxReceivedMessageSize
  4. Search for <httpTransport transferMode="StreamedRequest" and change from <httpTransport transferMode="StreamedRequest" to <httpsTransport transferMode="StreamedRequest"

After applying the changes, all the Silverlight pages are accessible with HTTPS without any issues. Verified in all browsers.

NotesNOTE: Silverlight pages are working fine with HTTP.

Attachments

    Outcomes