This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Every time we reboot Exchange server, PureMessage won't start

Hi,

Every time we reboot our Exchange server the PureMessage service won't start.  Uninstall / Reinstall gets it back up and running.  Is this a known issue?  Exchange 2010.

thanks,

Nicholas

:20359


This thread was automatically locked due to age.
  • This is the error in the event log after rebooting:

    Event ID: 1000

    Source: Application Error

    Faulting application name: SavexSrvc.exe, version: 4.1.0.0, time stamp: 0x4bb37f85

    Faulting module name: ntdll.dll, version: 6.1.7601.17514, time stamp: 0x4ce7c8f9

    Exception code: 0xc0000005

    Fault offset: 0x000000000004e4b4

    Faulting process id: 0x1c60

    Faulting application start time: 0x01ccc9efa4a3622f

    Faulting application path: C:\Program Files\Sophos\PureMessage\Bin\SavexSrvc.exe

    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

    Report Id: e3d8aea3-35e2-11e1-8eeb-00259027cc2d

    :20361
  • Hi,

    If you set the service to manual start, reboot, then manually start it after the reboot does it work?  Is it a start-up timing issue, I.e. something that isn't available when it tries to start?

    If this helps, maybe you could try setting the service to delayed auto start if you're on 2008+?

    Regards,

    Jak

    :20363
  • Jak,

    Thanks for the reply.  We have tried manually starting the service and get the same error.  However, that is after allowing it to autostart.  We will try again after setting the service to manual.

    Nicholas

    :20387
  • Keep us posted with what happens after you've made that change to the service.

    Do you see any Puremessage-associated errors in the Application Log Viewer? What happens when you try to start either the service manually or open the console? And have you always had this problem with Puremessage or was something updated recently on this system to cause this behaviour?

    If you haven't already, do consider opening a case with our support team if we need to investigate more deeply into this problem. Uninstalling/reinstalling Puremessage is an unfortunate workaround after a reboot.

    :20457