Copybix BUG (Full Version)

All Forums >> [Archiving & Fax] >> GFI MailArchiver



Message

latrobeit -> Copybix BUG (21.Jun.2009 8:36:35 PM)

The program copybix.exe fails to copy more than 32767 bix files.

Thought I could add more info. This is the error below. looks like a int was used where long might help.

Unhandled Exception: System.IO.IOException: The directory or file cannot be created.
  at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
  at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite)
  at System.IO.File.Copy(String sourceFileName, String destFileName)
  at copybix.Program.CopyBix(String path)
  at copybix.Program.CopyBix(String path)
  at copybix.Program.Main(String[] args)



mherberg -> RE: Copybix BUG (26.Jun.2009 3:10:58 AM)

latrobeit,

thanks for letting us know. We'll try to reproduce this issue and investigate further.



Michael Alexieff -> RE: Copybix BUG (29.Jun.2009 1:53:37 PM)

I do not think this is a limit of the amount of emails that can be copied as I am *sure* I have performed copies larger than 32K+ emails before. The "The directory or file cannot be created" error seems to lead to something interfering with the process. Any AV scanning the source and destination paths? What about backups? Also if you remove 100 bix files, move them to another folder, does the same error occur?



latrobeit -> RE: Copybix BUG (29.Jun.2009 7:46:01 PM)

In answer to your questions.

There is no AV on this pre production server. There is no backup in process when running copybix.

I had to delete the source bix files up to where it stopped and the rerun copybix with a diferent destination.

I had to create bix1 to bix13 folders each stopped at 32767 emails. for a firebird database containing 425971 emails

I justed checked if I could created a text file in the folder. I could not. So I checked the format of the external drive I was using to store the temp bix files. Yes it it FAT32 not ntfs. So I have found the problem, make sure users use ntfs drives when migrating to SQL.

Thanks for your help your questions prompted me to check the format of the drive.



Page: [1]