Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About easi

  • Rank
  1. We have a crashing problem with newest version of Retro Multi Server backup. This is a clean install, no previous Retro version installed. Environment is Win2003 Server Std SP2 x64 (DC role) with EX2007 SP1 installed. Latest updates naturally. When I simply close the main program I have two identical erros that simply ask me to send this information to EMC or not and continue. Assert_log.utx simply states following: [...] OS: Windows Server 2003 version 5.2 (build 3790), Service Pack 2, (64 bit) Application: C:\Program Files (x86)\Retrospect\Retrospect 7.6\Retrospect.exe, version 7.6.123 Driver Update and Hot Fix version Exception occurred on 27.2.2009 at 11:46:39 Exception code: c0000005 ACCESS_VIOLATION Fault address: 100018b7 0001:000008b7 (null) [...] Module Fn (symbol or seg:offset in DLL) Args =============== ================================= ======================================================================= ex2k7bridge.dll 0001:000008b7 'epiP' 0 24 8 f 64415c0b 3947ba0 12fd48 Retrospect.exe 0001:706f7453 [...] I then have also done the special RBU service user for Retro (http://kb.dantz.com/display/2/articleDirect/index.asp?aid=9633), made EX-mailboxes visible to Retro (this part is working) and backups are working when runned interactively, but it seems that Retro Launcher service does not work or ever try to run scheduled scripts. I'm not using proactice backup. This might have something to do with the constant and always happening crach for main program when exiting. Launcher service is not craching, it stays simply in 'Started' state but does nothing. Scheduled backups start to run like they should when main program in running. I have tested this same version in an different EX2007SP1 environment where the same server is not a DC, makes no difference. Same problem. Any ideas from where to look? =========== Update: When I release EX-licence, program is running fine and not crashing when exited. Something to do with Exchange 2007 support...