Graphisoft Tech. Support got back to me and said this,
"Sorry to hear about this problem.
This error usually happens when saving to a file server or cloud-synced folder (i.e. Dropbox) because these solutions read and write to the file and cause corruption. Please make sure that wherever you saved is a location that is not actively monitored, running in backup, or part of a synced solution (most solutions will be easy to spot from the sync/green checkmark icons next to each folder and filename.
If you are running some sort of anti-virus and anti-malware application, these might also be monitoring and opening files, blacklisting files. In this case try turnign it off.
Let me know if you have any questions or if it still doesn't work. If you were able to save an Archive file after a while, at least that can save your work from being lost."
I've sent my message below back to Tech. Support...
Weāre not backing up to a cloud service. We have a local backup server that isnāt related to any cloud service that isnāt even attached to the internet. Even if that could still be causing problems, weāve been backing up to a local server for many years and havenāt had any problems till the late 2020. Thatās when this save problem came up. The server does back up to another server through the internet that is at the firm owner's house, but itās been that way for a 3 or 4 years now and weāve never had problems before. The office server backs up once at night, so I donāt see how that could be a problem related to this saving issue.
Even if I try to save to my desktop completely separate from the server, the file still wonāt save. I tried giving a separate name but the file wouldnāt save. The name of the un-savable file would change though to what I typed in.
We do have an external hard drive that backs up our Macās through the Time Machine app. Weāve been using those for a couple years now and we havenāt had any issues with saving files before.
This is a big issue though to us. This is the fourth time this has happened in our office in the past 2 or so months. This is the second time Iāve had this happen on the current project Iām working on and Iāve had the problem on another project. Someone else in the office has had this problem once too, so it aināt just me. Two of the times this problem happened to me was when someone else opened up a read-only file of the project I had open with full rights to save.
We are all running on Catalina, but we did that update a little while ago that didnāt cause any problems that weāve noticed after the install. I donāt remember exactly when we updated to Catalina, but it didnāt cause any problems close enough to the update that I can make a connection that Catalina is the problem. Plus, the 3rd person in the office isnāt having any problems with this. All three of us are on Catalina, we all save to the server, and we all have Time Machine running. So Iām not to sure how to make a connection to figure out the problem.
Iāve contacted Tech. Support before and they said to just make sure ArchiCAD is up-to-date. The first three times we had this problem, our ArchiCAD has been out-of-date. This is the first time it has happened when ArchiCAD has been up-to-date. This is a reoccurring problem that we wish could somehow stop. I'm not sure what to do about this either.
>ArchiCAD 23, 7000 USA FULL
>iMac, 27-inch, 2020, Processor: 3.8 GHz 8-Core Intel Core i7, Memory: 64 GB 2667 MHz DDR4, Graphics: AMD Radeon Pro 5500 XT 8 GB