On Wed, May 12, 2010 at 10:53:44PM +1000, James Harper wrote: > > > > On Wed, May 12, 2010 at 10:14:52PM +1000, James Harper wrote: > > > > > > > > For me, both the 32 bit and 64 bit windows bacula-fd.exe 5.0.2 > > > downloaded from > > > > bacula.org are crashing straight away. > > > > That is, they crash when I try to start them. I don't get as far > as > > > actually > > > > trying to run a backup. > > > > > > > > I tracked the problem down to the exchange plugin. > > > > When I delete exchange-fd.dll, I can start bacula-fd.exe. > > > > > > > > Has anybody else had this problem? > > > > > > > > > > Can you tell me what version of Windows and Exchange you are using? > A 64 > > > bit version of Exchange will require a 64 bit version of Bacula, but > as > > > you have tried both I don't think that is your problem. > > > > > > In the registry there is a key called > > > HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore\DLLPaths > containing > > > a value called esebcli2. This should contain the path to the > > > esebcli2.dll Exchange API. Please confirm that the registry entry > > > exists, and that the DLL is where the registry says it should be. > > > > None of this is relevant to the problem. > > The bacula client crashes at start up, not when any backups are kicked > off. > > I think another post has probably identified the license mismatch error > so it probably doesn't matter, but the exchange plugin loads that dll at > startup and if it wasn't right it could cause a crash.
The licence thing looks ok to me, but I just noticed that src/lib/plugins.c has changed how it closes things between 5.0.1 and 5.0.2. I'm going to try a test where I use the 5.0.1 plugins.c in 5.0.2. ------------------------------------------------------------------------------ _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
