Interesting issue. I’d love to see a dump file from this crash.
Are you getting the Windows crash dialog? Or does store.exe simply disappear from the list of running processes?
BTW wouldn’t it be possible to get a remote desktop access to the server?
Unfortunately there’s no crash. I’m usually RDP’d to the server when I restart the services, and no pop-ups appear. When I look in the services applet, the Information Store is no longer ‘started’. When I look in the eventlog, I only see the error I sent previously.
I’ve tried restarting the services on my test server (very little load) and had no problem. I’m going the remove Avast and install the latest full version at our next planned outage.
Dont know if this is relaited but even since being “forced to upgrade” to Exchange 2007 I havent been able to use Avast Exhange/SMTP plug-ins… If I try it the Exchange Informations store (store.exe) goes offline and I have to shut down Avast and restart EIS services. Exchange 2007 isnt supported yet !!!
I use ADNM and manage my network that way… great but seriusly lacking Exchange support…
We have the same problem on one of our clients servers:
It actually appeared after we migrated the server to new hardware. Store.exe was constantly crashing. After reinstalling Avast (SBS edition) it only happens when the machine is (re-)booted.
Several messages appear in the application logs:
Faulting application store.exe, version 6.5.7638.2, stamp 434353c1, faulting module avexvxx2.dll, version 4.7.1098.0, stamp 47556974, debug? 0, fault address 0x00005b7e.
Faulting application store.exe, version 6.5.7638.2, faulting module AvExVxx2.dll, version 4.7.1098.0, fault address 0x00005b7e.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Error initializing session for virtual machine SBS. The error number is 0x8004011d. Make sure Microsoft Exchange Store is running.
For more information, click http://www.microsoft.com/contentredirect.asp.
Also to note, Exchange is 2003 on a Windows SBS 2003
I am having the same issue and have received terrible support from Avast Support. I am now 11 days into this issue with Avast Support and have received 1 reply, 10 days in. The issue has shown “solved” twice after receiving no response with ideas to fix the issue. The only thing they said was to look at this post for a solution, but I see none.
I ask, do any of you have solutions other than downgrading?