Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

FilePlanet error, "Could not initialize file" - HELP

Hi everyone. I've subscribed to FilePlanet for a few years and I've never once received the error message I've been getting since last week with the Vanguard beta client. The Download Manager software says "Could not initialize file...click here to retry" and I cannot get past that. I found reference to this same issue on another forum (I just did a Google search) and the poster stated that he thought it could be a problem with his FAT32 file system, which prevents downloads over 2 gigs in size. However, I confirmed that I am using the NTFS file system, and the Download Manager default folder is on a drive with 20 gigs of free space.

Could this just be a problem at FilePlanet because everyone is downloading the file? Did anyone else get this error, and if so, did you ever find a way around it? Thank you in advance for any assistance.

 

Comments

  • green13green13 Member UncommonPosts: 1,341

    I had this exact problem, and discovered the drive I was trying to download to it to has some pretty weird formatting problem. The drive had been formatted when I bought it (looked like someone had bought and returned it) and they did something truly weird with it that has made it effectively FAT32.

    Try these things.

    Uninstall FP's download manager and install Firefox (if you don't have it already). From Firefox you can download files without FP's download manager.

    Try to download it with another download manager. I found it failed using everything but Download Accelerator Plus.

    DAP proceeded to download the file fine but stopped at precisely 4 gig --> FAT32.

    My advice is if you can download other FP files but not the Vanguard beta client, and DAP is the only download manager that will download it, then you have a formatting problem.

    I switched the download to a different drive and FP's download manager (and all the others) worked just fine.

    I'd suggest converting your drive format to NTFS but so far that hasn't worked for me on my errant drive. At some point I'll have back everything up and reformat it.

Sign In or Register to comment.