HELP! As of yesterday, I've been unable to save any file from either my laptop or workstation. The files are on my NAS and have been working fine from both devices until yesterday.

This is the error message I get:

"Unable to open file '//NAS_2/data/Steve/KMyMoney/2021_COPY.kmy' for writing, C:\_\9b0777e7\kmymoney\kmymoney\plugins\xml\xmlstorage.cpp:517"

I've tried using different files and from backups but keep getting the same error message on all of them. Can anyone please help?

Steve

EDIT:
I just updated from 5.1.1 to 5.1.2 but it's just the same.

Do I understand that correctly, that you used KMyMoney 5.1.1 successfully and then out of a sudden it stops with the said error message? And if you upgrade to 5.1.2 it just shows the same behavior? If so, I don't suspect this to be a KMyMoney problem since it worked before. Here's what you can check:

• Can you save the data to a local drive (e.g. C:)?
• Is the number at the end of the error message (the source code line number) the same in both cases or does it differ?
• What are those numbers in both cases?

I am asking, because line 517 somehow does not make sense when looking at the code of either 5.1.1 or 5.1.2. Anyway, the error message is only shown in case KMyMoney cannot open the file for writing. Please check that you have write access to the file.

ipwizard wrote:Do I understand that correctly, that you used KMyMoney 5.1.1 successfully and then out of a sudden it stops with the said error message? And if you upgrade to 5.1.2 it just shows the same behavior? If so, I don't suspect this to be a KMyMoney problem since it worked before. Here's what you can check:

• Can you save the data to a local drive (e.g. C:)?
• Is the number at the end of the error message (the source code line number) the same in both cases or does it differ?
• What are those numbers in both cases?

I am asking, because line 517 somehow does not make sense when looking at the code of either 5.1.1 or 5.1.2. Anyway, the error message is only shown in case KMyMoney cannot open the file for writing. Please check that you have write access to the file.

Hi Ipwizard,
Thanks for your input.
I just tried what you suggested and it is saving as a local file.
I have full control permissions on the entire NAS, as I need to access files from any location and it has been working fine since I switched form Quicken in April - so I don't understand why/how it suddenly changed.

What else did you change in your environment? Updates/Settings? Also, my 2nd and 3rd question are still unanswered.

I've just opened one of the files from the NAS on the workstation and when saving I'm getting 510 as the error

Doing the same from my laptop, I'm getting 517

I'm not aware of any updates yesterday

EDIT:

I've just discovered I can no longer connect between LT & WS and vice versa - which is really weird, as I always access files between the 2 devices

Line 510 makes sense for KMyMoney 5.1.2. It's exactly the location in the code that tries to open the file for writing. That part of the code has not been changed in years, so I really suspect some change in your environment that is causing the problem now. Are you using GPG encryption or unencrypted (compressed) storage?

ipwizard wrote:Line 510 makes sense for KMyMoney 5.1.2. It's exactly the location in the code that tries to open the file for writing. That part of the code has not been changed in years, so I really suspect some change in your environment that is causing the problem now. Are you using GPG encryption or unencrypted (compressed) storage?

So... Not being able to connect the 2 devices got me investigating all the network settings (although they were both connecting to the NAS and the internet okay). Low-and-behold! The Workstation had somehow switched the Network group back to Windows default "WORKGROUP"!!!!

After renaming it back to what I WANTED the 2 machines are talking again!

I have yet to determine if that was creating the issue with KMM (although, I can't see how because it was only the WS that had been altered) but I've wasted enough time on this for today. I'll let you know how get on with the original issue as and when!

regards, Steve

Great. Good to see that you experience some progress.