The same server has backup exec 2010 r3sp1 installed on it and as far as i know should not need to have the remote agent installed on. The same backup without activating ADBO runs fine with no errors. Heure de début de l’application défaillante : 0x%10Ĭhemin d’accès de l’application défaillante : %11Ĭes fichiers sont peut-être disponibles ici :Ĭ:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_beserver. snapshot backups via backup exec 2010 r3 fail I am trying to set up backups to use the san snapshots for zero impact during production days. Nom du module défaillant : MSVCR80.dll, version : 7.4940, horodatage : 0x4ca2b4dd Nom de l’application défaillante beserver.exe, version. Without the GUI, beserver.exe seems ok (at least 45 mns) (Valentine's day bug ! lol)īeserver stops after a few minutes if I launch the GUI console. I have the same problem with the same environment (Windows 2008 R2 and BackupExec 2010 R3 SP4). Now, after an hour with no client interface open the service still alive. When the client interface is open the service crash like above (in less than 5-10 minutes). Percorso del modulo che ha generato l'errore: %12 Percorso dell'applicazione che ha generato l'errore: %11 Ora di avvio dell'applicazione che ha generato l'errore: 0x%10 ID processo che ha generato l'errore: 0x%9 Nome del modulo che ha generato l'errore: MSVCR80.dll, versione: 7.4940, timestamp: 0x4ca2b4dd
Nome dell'applicazione che ha generato l'errore: beserver.exe, versione.
When I specced this up last year, I ignored 2010 and focused on Backup Exec 12.5, since it's a mature product. No automaticcally windows update (disabled). Backup Exec 2010 has just dropped, and I'm about to implement a new BEWS infrastructure, complete with CALs and new central servers. Hi, same problem here from the same day(it start in 15 feb).
0 kommentar(er)
