Vault Cache causes Outlook 2007 to crash and restart repeatedly
Hi All,
Not sure if anyone has experienced this problem, however I have a client who is currently on EV 8 SP1, with EV 8 Sp1 outlook add-in. The user experiencing the problem uses Windows 7 with Outlook 2007 and a whole lot of other add-ins (Typical Developer). Anyways when VC begins to synchronize the initial goes well, however as soon as it starts to download from the cache location, outlook crashes and restarts. Client trace in full mode not showing any unusual errors that I can see, and nothing in the user app logs, except for event id 1000. Thus far, I have disabled all non relevant add-ins, repaired office 2007, reset evclient, cleared vault cache and rebuilt as well as deleted the vault cache folder from the user's windows profile and rebuilt to no avail. As soon as the VC starts to download outlook bombs out.
Any assistance would be greatly appreciate.
Thanks
YellowFever
This is what the event id in the users app log looks like.
Comments
Hi YellowFever, I've not got
Hi YellowFever,
I've not got round to installing Windows 7 yet so can't really advise, but maybe this has a bearing on the issue? The only thing I can suggest is to do a search for the .MDC file (which is part of VC) and see if there is a permissions issue? Another thing to check is the Desktop Policy settings for Vault Cache;
Auto download pause - (increase to 120 seconds)
Download delay - (60 seconds)
Probably won't help YF but that's all I got :(
Thanks,
BZ
Try .................... Two
Try ....................
Two things that I'd tried.
a) Remove all the other add-ins.
b) Upgrade to the 8 SP 3 client.
I've been using Outlook 2007 SP 2 with Windows 7 x86 for MONTHS with vault cache, and have not had any issues. (even though it's not officially certified, yet)
Hope that helps,
Hi Guys, Thanks for you
Hi Guys,
Thanks for you thoughts around this. Have tried to disble the remaining add ins to no avail. I will try upgrading to 8 SP3 and see what happens. If that fails maybe I will have to log a support call for this. Weird thing is that only users are affected here. one running Windows 7 and one running Windows XP.
Thanks again for all your efforts, much appreciated.
Regards
YF
Was this eventually resolved?
Was this issue ever resolved? I have one user who experiencing the same thing. We've looked at 302477
and 300277 and neither helped. Preparing to open a support call.
David, are you experiencing
David, are you experiencing this on Windows 7 or ? Are you getting the exact same condition?
Hey, Rob. No slightly
Any insight would be appreciated. I'm trying to get a client trace together.
- David
System
- Provider
[ Name] Application Error
[ Qualifiers] 0
[ SystemTime] 2010-03-18T15:30:08.000Z
- EventData
OUTLOOK.EXE
12.0.6514.5000
4a89dc70
ntdll.dll
6.0.6002.18005
49e03821
c0000374
000afaf8
be8
01cac69c5cf4ec9c
Event Name: APPCRASH
Response: None
Cab Id: 814562699
P1: OUTLOOK.EXE
P2: 12.0.6514.5000
P3: 4a89dc70
P4: StackHash_ddde
P5: 6.0.6002.18005
P6: 49e03821
P7: c0000374
P8: 000afaf8
P9:
P10:
Faulting application OUTLOOK.EXE, version 12.0.6514.5000, time stamp 0x4a89dc70, faulting module ntdll.dll, version 6.0.6002.18005, time stamp 0x49e03821, exception code 0xc0000374, fault offset 0x000afaf8, process id 0xbe8, application start time 0x01cac69c5cf4ec9c.
More info
Also... The problem is intermittent. We have not been able to reproduce it reliably. User originally reported the problem while using Store in Vault. Comptuer originally not using cached mode - so does not appear that the OST is corrupt. Put the computer in cached mode and that does not resolve the problem. So my best bet is to set up a dtrace and hope it happens again soon.
The best thing for you to do
The best thing for you to do is download and install the debugging tools for Windows, from Microsoft's web site. Once installed on a system where this error is known to appear run something along these lines :-
cscript adplus.vbs -crash -pn outlook.exe -quiet -o c:\dumpfiles
This will capture a user mode process dump if Outlook crashes, which is a lot more useful than the event id 1000 listed above. If you capture one I'd be more than happy to take a glance at it for first ideas.
Hope that helps,
Would you like to reply?
Login or Register to post your comment.