000016390 - Unable to start/restart RSA Archer Queuing service after intermittent stoppage

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

Article Content

Article Number000016390
Applies ToRSA Archer
IssueUnable to start/restart RSA Archer Queuing service after intermittent stoppage.
RSA Archer Queuing service may stop and start intermittently.
No errors are observed in Queuing.Service.log.
Errors observed in Windows Application event logs:

Error #1

 

Source: Application Error 

Event ID: 1000 

Faulting application name: Archer.Services.Queuing.exe, version: x.x.xxxxx.xxxx, time stamp: 0x51803494 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x000007ff00161a1f Faulting process id: 0x1538 Faulting application start time: 0x01ceaf1fd5e7369f Faulting application path: C:\Program Files\RSA Archer\Services\Archer.Services.Queuing.exe 

Faulting module path: unknown 

Report Id: 15fd407b-1b13-11e3-b472-005056b121e7 


Error #2


Source: .NET Error 

Event ID: 1026 

Application: Archer.Services.Queuing.exe Framework Version: v4.0.30319 

Description: The process was terminated due to an unhandled exception. 

Exception Info: System.NullReferenceException 

Stack: 

at ArcherTech.Services.Queuing.SqlServerAsyncDispatcher.Process() 

at System.Threading.ExecutionContext.runTryCode(System.Object) 

at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode, CleanupCode, System.Object) 

at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) 

at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) 


at System.Threading.ThreadHelper.ThreadStart() 



 
CauseThis issue occurs when RSA Archer Queuing service is unable to write a log file. Issue is particularly seen when RSA Archer logging location resides on a Network Attached Storage (NAS) or a remote network storage with intermittent performance issue ( caused by anti-virus scanning, network interruption etc.)
ResolutionTo fix this issue:
 

Option #1 

Rectify network storage performance issues.

 

Option #2

Move RSA Archer logging local to Archer servers.
Legacy Article IDa63523

Attachments

    Outcomes