Versions / Builds Affected
GFI Eventemanager 2013 SR1 Build 20130606Status
OpenProblem Summary
CSV text logs are not getting collectedTT / JIRAID
549How to Identify
The W3celffcollectorplugin_*.csv log shows that the folder set up for the collection has been accessed fine but the logs cannot be collected with the following error displayed:
2015-07-10, 14:26:40, 689, 9, 454, c74, info, W3CelffCollectorPlugin.dll, ScanComputer, Attempting to connect to folder D:\CSV LOGS\*.* ...
2015-07-10, 14:26:41, 251, 9, 454, c74, info, W3CelffCollectorPlugin.dll, ConnectToFolder, Successfully connected to remote path \\localhost\D$\CSV LOGS
2015-07-10, 14:26:41, 251, 9, 454, c74, info, W3CelffCollectorPlugin.dll, ScanComputer, Connected, getting file list
2015-07-10, 14:26:41, 579, 0, 454, c74, error, W3CelffCollectorPlugin.dll, GetFilesToProcess, Get files to process failed: Object reference not set to an instance of an object.
2015-07-10, 14:26:41, 579, 0, 454, c74, error, W3CelffCollectorPlugin.dll, GetFilesToProcess, Stack trace is:
at GFILog.LogError(String message, Object[] args)
at W3CelffCollectorPlugin.NetFileManager.GetFilesToProcess(String mask, String machineName, String machineAddress, Boolean recurse)
at W3CelffCollectorPlugin.Scanners.MachineScanner.ScanComputer(String jobId, ComputerInfo compInfo)
at W3CelffCollectorPlugin.TextLogsCollector.ProcessData(String dataProtocol, Object inputObject, Boolean expectResults, String senderName, Boolean sync)
at ServiceProvider.ThreadProc(Object task)
at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()Workaround / Fix Details
N/ARequired Actions
Contact the PSG for further instructions