Forum Discussion

james14's avatar
james14
Level 3
10 years ago

EV Storage Crawler Errors and event ID 1000

Hi All, We recently deployed 2x new EV servers, one file and one mail. Both are VM's with the following specs: OS: Server 2012 R2 (Latest patches as of 07/07/2014) Ram: 16GB CPU: 8x vP...
Enterprise Vault
Information Governance
Windows Server (2003-2008)
  • MassimoVagli's avatar
    MassimoVagli
    10 years ago

    Hello James, 

    I think the best action would be for you to open a support case, this because of the complexity of the troubleshooting and the kind of data analysis.

    Support would collect and analyze a memory dump of the StorageCrawler.exe together with the dtrace of the StorageCrawler.exe; eventually also the DVSs being re-indexed at the time of the crash.

    The analysis of the above would definitely help in the root cause understanding.

    Massimo

james14's avatar
james14
Level 3
10 years ago

I have attached another dtrace log file. Can someone please take a look?

I have managed to get rid of all the errors under symantec logs by doing plain txt conversion instead of html which appears to have helped. Our users never use explorer for file previewing so no point doing html conversion when it's faster and we save space doing plain txt.

So now I am not getting any more sandbox errors under symantec logs, but still getting error 1000 application logs listed. I was thinking about re-install the C++ librarys?

Thoughts?

Faulting application name: StorageCrawler.exe, version: 10.0.4.1189, time stamp: 0x51dd972f

Faulting module name: MSVCR90.dll, version: 9.0.30729.8387, time stamp: 0x51ea24a5
Exception code: 0xc0000417
Fault offset: 0x00059e63
Faulting process id: 0x443c
Faulting application start time: 0x01cfcd87fa804b1e
Faulting application path: D:\Program Files (x86)\Enterprise Vault\StorageCrawler.exe
Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.8387_none_5094ca96bcb6b2bb\MSVCR90.dll
Report Id: 38e20949-397b-11e4-80d5-005056a9664b
Faulting package full name: 
Faulting package-relative application ID: