


4062, fault address 0x0000bee7.I've re-applied the settings for the user the service runs as. 134, faulting module kernel32.dll, version. This is the only error in the event log:Faulting application bengine.exe, version. By the time that happens the backup exec job engine service has stopped again. If I wait long enough it errors would with a communication problem with the media services. I can then start a backup job, it runs for about 25 minutes or so then the status changes to "communication stalled". No backup job has run successfully since then!When the machine first boots, the backup exec job engine service isn't running.

Up until recently Backup Exec has worked pretty well.
