The Enterprise Vault service is not available
ok so firstly tell your TSE that reinstalling the server is a terrible idea, i mean honestly it is horrifyingly bad.... ask them to escalate the case and get a TSA Net with MS and Symantec
Microsoft will request some trace logging through IIS and possibly some debugdiag outputs
You can either try and get these proactively or you can wait for what Microsoft suggests
WinHTTPTrace Config details can be found here:
http://msdn.microsoft.com/en-us/library/aa384119(v=vs.85).aspx
DebugDiag can be found here:
http://www.microsoft.com/downloads/details.aspx?FamilyID=28bd5941-c458-46f1-b24d-f60151d875a3
Make sure you download the x86 version regardless of whether you're on x64 or not, because the 64bit version of DebugDiag is diagnostic only, though some engineers may prefer you use ADPlus however debugdiag is more IIS Centric and a lot friendlier to use
So what i would do is the following
Download and install Debug Diag and the windows resource Kits
1. Download and install DebugDiag to your EV Server
2. Download and install the Windows Server Resource Kit
Configure DebugDiag
3. Open up DebugDiag
4. From the wizard choose "Crash" and press Next
5. Choose "A specific process" and press Next
6. From Selected Processes type "w3wp.exe" and press Next
7. From Action Type , choose "Log Stack Trace" and then put something like 10 instances
8. Press the "Exceptions" button and then press "Add Exception"
9. In Exception Code put in "8007276d"
10. For Action Type put "Full User Dump"
11. For Action Limit put in a number such as 10
12. Press OK and then press Save & Close
13. Press Next and then choose a suitable place for the memory dumps to be saved to
14. Press Next and then press "Do Not Activate The Rule At This " and press Finish
Configure WinHTTPTrace
15. Open a command prompt
16. CD to your Resource kit directory
17. type the following
Winhttptracecfg -e 1 -l E:\YourLogFileLocation\yourserver -d 0 -s 1 -t 1
18. -e 1 is to enable logging (0 = off, 1 = one)
19. -l is to specify the log location and the prefix, put this where your dumps are set to go
20. -d 0 is to write it to a file as opposed to a debugger
21. -s 1 is to show the calls in text as opposed to hex (though MS may change this)
22. -t 1 is to show top level functions that are called, more verbose the better at this point
23. Minimize the command promptConfigure DTrace
24. Open up another Command Prompt
25. CD to your \Program Files\Enterprise Vault directory
26. Type DTrace and press enter
27. Type "set w3wp v" and press Enter
28. Type "log <yourDebugDiagLocation>" and press enter
Now go back to DebugDiag where you have the rule set to not activated, right click the rule and then click "Activate Now"
Now replicate the behavior several times going to http://yourEVServer/EnterpriseVault/
Ensure that the Winhttp log file is being written to, ensure that debugdiag is dumping out full memory dumps
After this zip up the contents, and upload it to symantec.
If you're curious you can open up the debugdiag outputs and it will show you its best guess as to what is causing the issue to occur, though because this is not really an unhandled exception it may just show you the stack trace of what was occuring at that time
