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

[Joe Carrick]

This just appeared - I was not attempting any save so it must be a result of an archive save attempt internal and automatic by Chief. There is no such folder on my C-Drive.

It would be nice if someone at CA could do a source code search for p4sync to determine what's causing this.

My guess is a leftover development debug code snippet.

[David J. Potter]

I agree with Joe's observation in that I have seen this on my PC (client's PC's too) and have so far ignored it as nothing "bad" has occurred due to my "handling", it is annoying and wasting of clicks, you doughnut guys need to clean house a little, me thinks in the next patch.

DJP

[Joe Carrick]

Tech Support tried to imply that it was due to opening or saving to a thumb drive or a network drive that's no longer present. I have not been doing that.

[lbuttery]

Joe:

this is why I stopped using external HD's with Chief after fighting with tech support over this issue with ver 9.5 and 10

I now let Chief install and save where it wants to and do my own "save as" for my plans and layouts

If you don't follow their "bouncing rubber ball" mother chief tends to get upset
and tech support refuses to assist

Lew

[Joe Carrick]

Joe:

this is why I stopped using external HD's with Chief after fighting with tech support over this issue with ver 9.5 and 10

I now let Chief install and save where it wants to and do my own "save as" for my plans and layouts

If you don't follow their "bouncing rubber ball" mother chief tends to get upset
and tech support refuses to assist

Lew

Lew, I am and always have followed Chief's "BOUNCING RUBBER BALL"

[VHampton]

Today's message...

Not a big deal since it can be turned off. My guess is a simple conflict with any kind of back up software.

[Joe Carrick]

Today's message...

Not a big deal since it can be turned off. My guess is a simple conflict with any kind of back up software.

It can only be turned off during the current session !!!!!!!

[HumbleChief]

It can only be turned off during the current session !!!!!!!

True that.

[Dave Pitman]

My guess is a simple conflict with any kind of back up software.

I have not seen these messages (yet) and my Chief files are in a Dropbox folder. Not that I'm complaining...

[VHampton]

It can only be turned off during the current session !!!!!!!

!!!!!!!

I see your point. Turning the message off permanently rather than just for the session would be much better.
As you can see, there's no solution to this at the moment according to tech support.

At the end of the day it's a small thing to have to put up with.

[David J. Potter]

Joe wrote:

Lew, I am and always have followed Chief's "BOUNCING RUBBER BALL"

Just not quietly or complacently, dare I add.

DJP

[Joe Carrick]

Joe wrote:

Just not quietly or complacently, dare I add.

DJP

Since Lew had obviously not read my previous post - I thought I had to be just a little bit loud.

[lbuttery]

Joe:

I was responding to the "no longer present"

once tech support gets their mind on an "escape clause"
they refuse to let go and there is no reasoning with them

so my comments were aimed at them not you

sorry for not being clear about that

they assume you are "not following the rubber ball" because you once failed to do so

Lew

[Joe Carrick]

I did some checking on the web.

Perforce (p4sync) is a software version control system. I did not see Chief Architect listed as a customer but that is probably just because the customer list hasn't been updated.

IOW, Chief Architect is evidently using Perforce internally as a part of their software development. If that's correct then these messages are left over garbage in the code that should be blocked in the released version.

Can someone at CA please explain why this is happening and how/when it can be fixed? The last thing I want to happen in front of a client is for the software to pop up an error message that's not supposed to be there.

[Doug Park]

This error occurs when a write of a plan or layout fails.

There are a number of cases where we go through this code as follows:

1) Normal save of a plan.
2) Auto save.
3) Writing files for undo.
4) Copying data to the clipboard for edit area.

I'm will look into making the message have more information for X6.

In any case what this means is that one of the above operations failed.

In cases 1-3 it is likely due to a number of issues.

1) Another application has the file you are attempting to write to open preventing access. This is consistent with the use of applications that backup data as you work. It is also consistent with the presence of malware. It could also be due to another copy of Chief having access to that file. It is also consistent with writing directly to a removable device that has been removed from the system.

Because Chief files tend to be big the probability of an application like this still having access to a file the next time you need to access it is high, especially if you save frequently. This is an unfortunate limitation of the Windows file system that is not shared by Linux and Unix based systems. Definitely one argument in favor of Mac.

2) Your disk has a serious problem. Run chkdsk to verify that it is OK.

In case 4 (Edit Area Copy) the possible causes are different. Possibly out of memory or some other serious issue.

In any case this is a potentially serious problem.