Re: [Bacula-users] Column 'PoolId' cannot be null

2009-01-07 Thread Pieter (NL)
Updated to version 2.4.4 and the sql error from the migrate job, with no files to migrate, disappeared. Also the sql error PoolID seems to have gone aways. Thank you. Greetings, Pieter -- View this message in context: http://www.nabble.com/Column-%27PoolId%27-cannot-be-null-tp20898308p2132725

Re: [Bacula-users] Column 'PoolId' cannot be null

2008-12-10 Thread Pieter (NL)
Got another error today just like the poolid error: 10-Dec 06:10 backup-dir JobId 12988: No Oldest Volumes found to migrate. 10-Dec 06:10 backup-dir JobId 12988: No JobIds found to migrate. 10-Dec 06:10 backup-dir JobId 12988: Error: sql_update.c:194 sql_update.c:194 update UPDATE Job SET JobStat

[Bacula-users] Column 'PoolId' cannot be null

2008-12-08 Thread Pieter (NL)
When I do a restore I get the message "Column 'PoolId' cannot be null" did I miss a database update? The following is part of my logfile: 08-Dec 16:22 backup-dir JobId 12951: Start Restore Job RestoreFiles.2008-12-08_16.22.10 08-Dec 16:22 backup-dir JobId 12951: Using Device "FileStorage" 08-Dec