Hello everyone.

I have just installed the Bacula File Daemon on a windows 7 machine. I 
did this on 3 other machines before and they are all being backed up.

For some reason i cannot start the file daemon service on this new (new 
to the backup system) computer. I keep receiving error 1067 when 
attempting to start.
Also for some reason the file daemon is looking for its config file in 
the folder "ProgramData" instead of its installation path.
The config-file itself should be fine. I can start the bacula-fd.exe, if 
I move the config, but then I only start it as a process, not a service.

Any ideas, what might cause this behavior?

Regards,

Florian S.

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users