000038724 - Unable to upload attachments in RSA Archer after upgrade: The cryptographic operation has failed

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

Article Content

Article Number000038724
Applies ToRSA Product Set: RSA Archer
RSA Version/Condition: 6.5.0.7+, 6.6.0.6+ and 6.7.0.4+
 
IssueAfter upgrading Archer to one of the following versions:
  • 6.5.0.7 and later
  • 6.6.0.6 and later
  • 6.7.0.4 and later

Uploading attachments no longer work. 
User-added image

The Archer w3wp logs will contain the following error:
 

<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-03-31T09:02:58.3174068Z" />
        <Source Name="Archer.Web" />
        <Correlation ActivityID="{00000000-0000-0000-0000-000000000000}" />
        <Execution ProcessName="w3wp" ProcessID="11796" ThreadID="30" />
        <AssemblyVersion>6.5.700.1008</AssemblyVersion>
        <Channel />
        <Computer>SERVERNAME</Computer>
    </System>
    <ApplicationData>
        <TraceData>
            <DataItem>
                <TraceRecord Severity="Error" xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord">
                    <TraceIdentifier>Archer.Web</TraceIdentifier>
                    <LogReferenceId>033120-090258-3174</LogReferenceId>
                    <Description>The cryptographic operation has failed!</Description>
                    <AppDomain>/LM/W3SVC/1/ROOT/RSAarcher-4-132300984671841037</AppDomain>
                    <ContextData>
                        <BaseUrl>https://servername/RSAarcher/ArcherAsyncUploadHandler.ashx</BaseUrl>
                        <type>rau</type>
                    </ContextData>
                    <Exception>
                        <ExceptionType>System.Security.Cryptography.CryptographicException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType>
                        <Message>The cryptographic operation has failed!</Message>
                        <Source>Telerik.Web.UI</Source>
                        <StackTrace>   at Telerik.Web.UI.CryptoExceptionThrower.ThrowGenericCryptoException[T]()
   at Telerik.Web.UI.CryptoExceptionThrower.ThrowIfFails[T](Func`1 function)
   at Telerik.Web.UI.AsyncUploadHandler.GetConfiguration(String rawData)
   at Telerik.Web.UI.AsyncUploadHandler.EnsureSetup()
   at Telerik.Web.UI.AsyncUploadHandler.ProcessRequest(HttpContext context)
   at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
   at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)
   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&amp; completedSynchronously)</StackTrace>
                    </Exception>
                </TraceRecord>
            </DataItem>
        </TraceData>
    </ApplicationData>
</E2ETraceEvent>


 
CauseThis error is caused by some new settings missing in the web.config file. Starting in the above versions of Archer, some additional Telerik settings have been added. If the settings do not exist in your web.config file perhaps something failed when the installer tried to update it or an old file was copied in place after the upgrade.
ResolutionTo correct the issue the web.config file located in the IIS folder where Archer is hosted needs to be updated. Here is an example location of the file:

C:\inetpub\wwwroot\RSAarcher\web.config



There are a few options to perform this update:
  1. Remove or rename the web.config file then rerun the Archer installer. This should lay down a new file. You will then need to modify it with any custom changes that have been added.
  2. Use the web.config editor to create a new file.  Web.config Editor 3.0 

You will then need to modify it with any custom changes that have been added. It is also a good idea to review the risks of creating a new generic web.config file. Review Web.config Editor tools - why you should edit existing file vs. replacing.


  1. Manually edit the web.config file.
    1. Search for </appSettings> and add the following line right before it.


<add key="Telerik.Upload.AllowedCustomMetaDataTypes" value="ArcherTech.Web.Configuration.ArcherAsyncUploadConfiguration" />


 


User-added image


  1. Search for </assemblyBinding> and add the following lines right before it.


<dependentAssembly>
    <assemblyIdentity name="Telerik.Web.UI" publicKeyToken="121fae78165ba3d4" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-2020.1.114.45" newVersion="2020.1.114.45" />
</dependentAssembly>


User-added image


  1. Save changes to the file.
  2. Perform an IIS reset once the web.config modifications are complete.

Attachments

    Outcomes