EVPlaceholderService.exe crash
Hello, We have the Placeholder service that stops working when we start an archive job. If there is no archiving task that runs the service works without problems. We see the following event: Faulting application name: EvPlaceholderService.exe, version: 12.2.3.1576, time stamp: 0x5a8d52dc Faulting module name: EvPlaceholderService.exe, version: 12.2.3.1576, time stamp: 0x5a8d52dc Exception code: 0xc0000005 Fault offset: 0x0003db6f Faulting process id: 0x1084 Faulting application start time: 0x01d46626ec40f61e Faulting application path: C: \ Program Files (x86) \ Enterprise Vault \ EvPlaceholderService.exe Faulting module path: C: \ Program Files (x86) \ Enterprise Vault \ EvPlaceholderService.exe Report Id: 454ce18c-d21d-11e8-80d0-005056826727 Faulting package full name: Faulting package-relative application ID: When running a DTrace on EvPlaceholderService, no trace of the service that stops. Have you ever experienced a similar case? - EV 12.2.2 on Windows Server 2012R2 - FSA Server in Windows Server 2012R2 with FSA Agent 12.2.3 Thank you so much !1.1KViews0likes2CommentsEnterprise Vault - Move live shared data + placeholders to new drive
Hi all, after some advice if possible. Due to space restrictions, I need to move all file share data from DRIVE1 to DRIVE2 on the same server. The data on DRIVE1 includes EV placeholders thatI need to make sure will still retrieve archived files once migrated to DRIVE2. I plan to robocopy data from DRIVE1 to DRIVE2 then swap the drive mappings around, keeping the current drive letter in place on the new DRIVE2, but I am unsure how to handle the EV part of the equation. Could I restore all current placeholder files within their current folder location to the new DRIVE2 before going live? As a test almost? What would be the recommended way to achieve this without any possibility of EV data corruption\issues retrieving files etc... Many thanks in advance.802Views0likes2Comments