Archer Cannot Package Findings Since the SecOps Package was Installed

[KB-Sync1]

Article Number

000033169

Applies To

Product(s): Archer, SecOps
Version(s): All Versions
Primary Deployment: On Premises/AWS Hosted/AWS SaaS

---

Description

Cannot package findings since the SecOps package was installed, as shown in the error below.

<E2ETraceEvent xmlns="http://schemas.microsoft.com/2004/06/E2ETraceEvent">
        </System>
    <ApplicationData>
        <TraceData>
            <DataItem>
                <TraceRecord Severity="Error" xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord">
                    <TraceIdentifier>Archer.Packaging</TraceIdentifier>
                    <UserId>183</UserId>
                    <Description>Unable to open a Repository File for this Module, either because it doesn't exist, or it is locked by another process. Please make sure this file exists in your configured Repository Files directory, or remove and re-add the Attachment for this Module.</Description>
                    <AppDomain>ArcherTech.JobFramework.Job.exe</AppDomain>
                    <Exception>
                        <ExceptionType>System.InvalidOperationException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType>
                        <Message>Unable to open a Repository File for this Module, either because it doesn't exist, or it is locked by another process. Please make sure this file exists in your configured Repository Files directory, or remove and re-add the Attachment for this Module.</Message>
                        <Source>ArcherTech.Kernel</Source>
                        <ContextData>
                            <FileRepositoryId>3851</FileRepositoryId>
                            <FileRepositoryName>xxx</FileRepositoryName>
                            <AttachmentName>xxxx</AttachmentName>
                            <Module>xxxxxxx</Module>
                        </ContextData>
                        <StackTrace>   at ArcherTech.Kernal.Brokers.Packaging.Generate.Actions.Generation.GeneratePackage.ThrowModuleRepositoryFileException(SessionContext sessionContext, Guid moduleGuid, RepositoryFile file, Exception innerException)
   at ArcherTech.Kernal.Brokers.Packaging.Generate.Actions.Generation.GeneratePackage.&lt;AddRepositoryFiles&gt;b__238(GenerateContext context, ExecuteActions`1 ignored)</StackTrace>
                    </Exception>
                </TraceRecord>
            </DataItem>
        </TraceData>
    </ApplicationData>
</E2ETraceEvent>

Cause

This issue occurs when document attachments were not placed in the File Repository upon package install.

Note from log:

<Module>Security Incidents</Module>
<AttachmentName>Security_Incidents_visualization.xml</AttachmentName>

<Module>Data Breaches</Module>
<AttachmentName>Breach_visualization.xml</AttachmentName>

<Module>Incident Investigations</Module>
<AttachmentName>IncidentInvestigations_visualization.xml</AttachmentName>

Resolution

• Deleting these document attachments allowed the application to be packaged. 
• File Repository was mapped, not a UNC path, causing the files to not be placed in File Repository.