000034271 - RSA Archer Caching service fails to start and the error "No available configuration matches current machine." is logged

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

Article Content

Article Number000034271
Applies ToRSA Product Set: Archer
RSA Product/Service Type: Archer
RSA Version/Condition: 6.1
Product Description: Archer Platform
IssueThe RSA Archer Caching Service refuses to start and the following error can be found in the Archer.ArcherTech.Services.CachingService log file:
<E2ETraceEvent xmlns="http://schemas.microsoft.com/2004/06/E2ETraceEvent">
    <System xmlns="http://schemas.microsoft.com/2004/06/windows/eventlog/system">
        <SubType Name="Error">0</SubType>
        <TimeCreated SystemTime="2016-10-26T18:16:39.1933057Z" />
        <Source Name="Archer.NET" />
        <Correlation ActivityID="{00000000-0000-0000-0000-000000000000}" />
        <Execution ProcessName="ArcherTech.Services.CachingService" ProcessID="9064" ThreadID="5" />
        <Channel />
                <TraceRecord Severity="Error" xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord">
                    <Description>No available configuration matches current machine.</Description>
CauseWhen caching service is attempted to be started on a server other than what has been configured in the installation settings tab of the Archer Control Panel, the caching service will refuse to start and log an error.
  • Configure caching service in the Installation Settings tab of the Archer Control Panel
  • Click Save in the top left
  • Only attempt to start the caching service on servers that have already been configured to be a caching server in the Archer Control Panel