Archiving of database fails at 95%

[JPhillips]

Ryan,

I was able to archive the database in 2 parts. I then detached the original database and tried to move the files to another folder so I could replace the newly archived database with the original. But, when I do this the computer will not allow me to transfer the 2 mssql files from the folder of the original database. I get the "files cannot be moved" error. So, I tried to attach the newly archived database with the same mssql files from the original database but I do not get any trends when doing this.

Any ideas?

[Ryan.S]

The alarm/event can also be archived. I think you only need to archive the 2 data parts to the new database, and all the alarm/event to the new database, then you just use the new database. In lookout, modify the database path.

[JPhillips]

OK. So I do not need to replace the original 2 mssql files with the new ones? What do those 2 files contain?

[Ryan.S]

They are alarm/event database file. You don't need to manually copy those files. Just archive the alarm/event by MAX.

[erblock]

Ryan,

You mentioned a utility to repair a corrupt Citadel 5 database.  Could you please get that utility to me?

Ed

[Ryan.S]

Ed,

I did use an utility to fix a specific corrupt problem in Citadel 5. But we have the fix in Citadel. The Citadel 5 now is able to repair this kind of problem automatically, so that utility is no longer useful. The Citadel with Lookout 6.1 and even 6.0.2 already has this fix.

I see another post from you about the XP SP3. Do you have Citadel problem with XP SP3?