000039458 - Collection cannot be empty. Parameter name: fieldIds unexpected error when logging into in Archer

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

Article Content

Article Number000039458
Applies ToProduct Set: Archer
Product/Service Type: Archer (On-Premise)
IssueWhen logging into Archer, the Activity section of the Task Driven Landing page does not display and an "Unexpected Error" popup is displayed.

User-added image
Additionally, the below error is logged into the Archer w3wp logs:

<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="2020-10-27T14:57:38.6402699Z" />
    <Source Name="Archer.NET" />
    <Correlation ActivityID="{00000000-0000-0000-0000-000000000000}" />
    <Execution ProcessName="w3wp" ProcessID="3236" ThreadID="22" />
    <Channel />
        <TraceRecord Severity="Error" xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord">
          <Description>Collection can't be empty.
Parameter name: fieldIds
            <ExceptionType>System.ArgumentException, mscorlib, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType>
            <Message>Collection can't be empty.
Parameter name: fieldIds</Message>
            <StackTrace>   at ArcherTech.Kernel.Utility.BrokerHelper.ValidateEmptyCollectionParameter[T](IEnumerable`1 collection, String collectionName)
   at ArcherTech.Kernel.Brokers.FieldDefinitionBroker.GetInternal(IList`1 fieldIds, Boolean checkFieldPermission, Boolean checkLicensing)
   at ArcherTech.Kernel.Brokers.ContentBroker.GetHistoryLogForUser(Int32 maxNumerOfRecords)
   at ArcherTech.Kernel.Managers.UserActivityManager.Get(SessionContext sessionContext, Int32 maxNumberOfRecords)</StackTrace>

CauseIf the Archer History Log Cleanup maintenance job is currently in progress or has previously only partially completed, then this error is displayed during login of a user account whose activity has been partially cleaned up.
ResolutionThis issue will be fixed in a later release.
WorkaroundPlease run the out of the box History Log Cleanup job. This is an Archer maintenance job that is intended to run every day but may not be scheduling properly due to various reasons.

The steps to run this maintenance job are below.
  1. Archer Control Panel -> Plugins (top left) -> Job Engine Manager
  2. Job Engine Manager -> Menu button (top left) -> System Jobs
  3. Check "Content History Log Cleanup" -> Queue Job -> Run Job Now -> Submit.
  4. Please ensure this job goes into running jobs.

Note: In Archer versions prior to 6.8, the History Log Cleanup maintenance job may partially complete or fail in environments with extremely large data sets of history log.  The job will then go into "Failed Jobs"  (Ref: ARCHER-83557)  This can be resolved by upgrading to Archer version 6.8 or later.