Warning: Cannot Find Or open The File To Save Your Plan....

[HumbleChief]

I have Carbonite running most of the time and this has only happened on this one very large file. Perhaps a communications error between the software and Carbonite while its backing up? I dunno.

I haven't worked ion that file for a couple days and I've never seen it on any other file so it seems to be unique to that file. I'll recheck when I resume work on that file.

And as stated there seems to be no real consequences so I'll monitor.

And thank you very much for the replies and comments.

[Joe Carrick]

I have Carbonite running most of the time and this has only happened on this one very large file. Perhaps a communications error between the software and Carbonite while its backing up?

Larry,

Do you have Carbonite set to back up your Archive Files? That would explain it. I doubt that it's the actual file you are working on - most likely an automatic backup that Carbonite has the archive folder locked when Chief is trying to do an auto-backup.

[HumbleChief]

Larry,

Do you have Carbonite set to back up your Archive Files? That would explain it. I doubt that it's the actual file you are working on - most likely an automatic backup that Carbonite has the archive folder locked when Chief is trying to do an auto-backup.

It's not set to back up archive files Joe and I'm not that familiar with the technical aspects of how Carbonite works to comment much.

Again, only with this large (37meg) file. I can easily ignore it if it continues to cause no harm and it doesn't sound like it's an easy thing to track down.

[Joe Carrick]

If the message shows up again, click on "Details" to see if it says what file. "More Info" might also help. I'm just curious.

[HumbleChief]

Will do Joe.

[briem]

Larry,

Are you using SugarSync?

I've had the message a few times but I think it's maybe due to an archive file being locked. Really not sure since there's no detail.

I get similar messages. I am using Sugar Sync and have noticed that files are locked at various times and I can't open them up. If I wait a few minutes, it seems to sort itself out.

I have also had several complete lockups while I am using the program and have had to shut Chief down. I should have plenty of horsepower and memory that this shouldn't be happening.

[Doug Park]

When Chief saves a file it attempts to move the prior save to the archive directory first. If any other software has this file open for read the system can't move the file. It cannot delete the file to write over it either.

Interestingly this is a weakness of Windows that isn't a problem on Mac and pretty much every other operating system. Under Linux and Unix the file can be deleted from the filesystem so that it doesn't show up in the directory even if another process is using it. When the other process finishes with the deleted file it is then removed from the system. Under Windows the file system simply gives up.

It is an annoyance to me that the file system on Windows is so poor. It isn't even state of the art for 1980.

Sorry for the rant.

If you are going to run software to do backups it best to set it to run when you are not actively using the system.

It should be possible to create a more cogent error message.

[HumbleChief]

Here's the details. Same (and only) large file.

[Joe Carrick]

Here's the details. Same (and only) large file.

Interesting.....

I do not even have a folder p4sync so I don't know exactly what's going on with your system. I'll have to check mine the next time it happens. Maybe if you know what that folder is on your system it will give you an idea of what other program may be interfering with Chief in this regard.

IAE, it indicates that Chief is trying to save to a specific location and can't find it.

[HumbleChief]

Certainly no folder by that name here either. Oh well. Just this one file is afflicted.

[Joe Carrick]

I just saw the same error reported in regards to exporting to DWG. I think CA needs to look at this - it's something I've never seen before X5 so there must be something there. That's a path that some code in Chief is generating and it doesn't make a lot of sense for it to be doing so.

[Glenn Woodward]

Can it have something to do with this software?

http://www.perforce.com/products

[Joe Carrick]

Can it have something to do with this software?

http://www.perforce.com/products

Yes, it could - but I would think that it would be because CA was using that software internally and someone in the programming dept coded that specific path & file name for testing purposes. It shouldn't be in the X5 release.

[Ben Palmer]

I see that occasionally also when hitting Save, and using SugarSync...I hit save immediately following and it works fine and everything continues on.....

[Kelly K]

Larry,

I too have experienced this error message, but only once. It was on a plan that was started with X4, heavily modified, to create a 4th iteration from the original drawing.

At the time I didn't have an automatic online backup service (other than skydrive were I place completed drawings). This file will not auto save - period as you found out with your crash. I contacted support they suggested I do a saveas and change the filename slightly and that would solve the problem, it did not. I brought it forward to x5 again did a saveas but to no avail. I think sometimes a file just gets corrupted and there is no repair, at least, for a neophyte such as myself to make. I had too much work involved to discard the file, so my method of salvage is to make sure that I constantly manually save.

I'm sure I will be working on this plan in the future, the game plan will be to use an earlier version that does save and then see if I can copy/paste, or perhaps more correctly, cobble the file together from what I perceive to be the corrupted file.