000016969 - Address System.OutOfMemoryException when running an Archer to Archer data feed

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

Article Content

Article Number000016969
Applies ToRSA Archer
Version 5.x
IssueAddress System.OutOfMemoryException when running an Archer to Archer data feed
Data feed goes to a faulted state every time it is run.
Produces the following stack trace:
<Description>Error processing job '7767f9f1-ee87-41d5-996b-83c1e8512d03'.</Description>
                    <AppDomain>ArcherTech.JobFramework.Job.exe</AppDomain>
                    <Exception>
                        <ExceptionType>System.OutOfMemoryException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType>
                        <Message>Exception of type 'System.OutOfMemoryException' was thrown.</Message>
                        <Source>mscorlib</Source>
                        <StackTrace>   at ArcherTech.JobFramework.Job.JobRunner.OnServicesExceptionNotHandled(Object sender, ServicesExceptionNotHandledEventArgs e)
   at System.Workflow.Runtime.WorkflowRuntime.RaiseServicesExceptionNotHandledEvent(Exception exception, Guid instanceId)
   at System.Workflow.Runtime.Hosting.WorkflowRuntimeService.RaiseServicesExceptionNotHandledEvent(Exception exception, Guid instanceId)
   at System.Workflow.Runtime.Hosting.ManualWorkflowSchedulerService.RunOne(Guid workflowInstanceId)
   at System.Workflow.Runtime.Hosting.ManualWorkflowSchedulerService.RunWorkflow(Guid workflowInstanceId)
   at ArcherTech.JobFramework.Job.JobRunner.RunJob(JobDescription jobDescription)
   at ArcherTech.JobFramework.Job.JobProcessor.RunJob(WorkflowInstance job, JobDescription jobDescription)
   at ArcherTech.JobFramework.Job.JobProcessor.ProcessJob(Guid jobId, String instanceName)
   at ArcherTech.JobFramework.Job.Program.Main(String[] args)</StackTrace>
CauseThis is caused by invalid characters in the report ID
ResolutionThis is the result of using the report GUID as the ID and leaving the curly braces({ }) around the alphanumeric string.  Remove the braces, leaving just the alphanumeric characters, to fix the memory exception
Legacy Article IDa63721

Attachments

    Outcomes