External logging in SEPM with Failover configuration

I need a solution

My company has two SEPMs and we’re trying to configure External Logging.  We have the primary SEPM configured to export logs to a dump file and our SIEM agent is ingesting the logs in the dump files. As long as the SEMP in datacenter a is active it writes logs to the *.tmp files in the dump directory.  If the SEPM in datacenter b becomes active, it does not write logs to the *.tmp files in the dump directory.  How do we make sure that whichever SEMP is active write *.tmp files in the dump directory(C:Program Files (x86)SymantecSymantec Endpoint Protection Managerdatadump)?

0

Related:

XenApp/XenDesktop 7.15 LTSR CU2 and CU3: VDA Intermittently Blue Screens With BugCheck Code 0x50

VDA intermittently blue Screens With BugCheck Code 0x50.

Memory Dump Analysis shows:

Process ID [0]

Thread ID [0]

IDENTITY: NonPrimaryClient/NoIdentity.

Executing Processor Architecture is x64.

Debuggee is in Kernel Mode.

Debuggee is a kernel mode dump file.

Event Type: Exception.

Exception Faulting Address: 0xffffe002fa182a3e.

BugCheck Code: 0x50.

Exception Code: 0xC0000005.

Second Chance Exception Type: STATUS_ACCESS_VIOLATION (0xC0000005).

Exception Sub-Type: Write Access Violation.

Exception Hash (Major/Minor)

Hash Usage : Stack Trace:

Excluded : nt!KeBugCheckEx+0x0

Excluded : nt!MiSystemFault+0x10b2

Excluded : nt!MmAccessFault+0x219

Excluded : nt!KiPageFault+0x317

Major+Minor : wdica!MakeOnePacket+0x424

Major+Minor : wdica!SendSomeData+0xfe

Major+Minor : wdica!FlushManagement+0xf1

Major+Minor : wdica!TerminalChannelWrite+0xb2a

Major+Minor : wdica!WdChannelWrite+0xe

Minor : picadd!_IcaCallSd+0x2ba

Minor : picadd!IcaCallDriver+0x28b

Minor : picadd!IcaWriteChannel+0x724

Minor : PICAVC!PicaWriteVC+0x4a5

Minor : picadm!FileWriteStreamEx+0x43a

Minor : picadm!FileWriteStream+0x17f

Minor : picadm!FileWrite+0x3dc

Minor : picadm!PdmFsdWrite+0x3ce

Minor : picadm!OwWriteFsd+0x1c2

Minor : picadm!WriteMaximumIoSizeChunks+0x5b

Minor : picadm!NonCachedWrite+0x1ef

Minor : picadm!OwCommonWrite+0xada

Minor : picadm!OwFsdWrite+0x264

Minor : mup!MupiBypassMupAndCallUncProviderDirectly+0x36

Minor : mup!MupFsdIrpPassThrough+0xdb

Minor : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x25a

Minor : fltmgr!FltpDispatch+0xb2

Minor : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x25a

Minor : fltmgr!FltpDispatch+0xb2

Excluded : nt!IopSynchronousServiceTail+0x32b

Excluded : nt!NtWriteFile+0x694

Excluded : nt!KiSystemServiceCopyEnd+0x13

Unknown : 0x0000000077e22352

Related:

  • No Related Posts

How to Generate NSPPE Core Dump on NetScaler for High Memory issues

This article describes how to generate NSPPE core dump on NetScaler.

Background

When NetScaler, whether standalone or HA pair, runs into memory issues, you would generally generate NSPPE core dump. This triggers the device to restart while dumping the core which would help us with the RCA for high memory usage.

Related: