Initial Reason For Post: Trying to update to Sage Accounting Quantum 2023 this evening and ran into "Write Locator File failed, D:\PPA\company is SHARING_VIOLATION" error on the server. I click OK and the installer cancels. Failed install breaks current Sage 50 installation.

Update (11/8/22): I can't repair the Sage 2022 installation apparently. Kicking up an error: Error Installing Actian Zen.

Update (11/8/22): I tried to uninstall Sage 2022. Wouldn't do it. I tried to uninstall Actian, wouldn't do it. I ended up using a MS troubleshooting tool to remove everything one at a time. Now I'm trying to reinstall Sage 2022 from scratch. Looks like I got it reinstalled. Gonna leave 2023 alone for now.

Update (11/9/22): Something is still wrong with our server install. Going to try to repair the database after work today.

Update (11/9/22): I uninstalled Sage on all the clients and the server completely and recreate a new company folder. Then reinstall everything from scratch. I chose to install 2023 instead of 2022. After the server and the first 7 clients the installs started hanging up at Set Up Security. I just left them alone and they eventually completed their installs.

Update (11/10/22): I don't recommend installing Sage 2023.

Update (11/11/22): I think I've got everything working again. Will find out in the AM. Initial report is somehow Sage installed on the server without installing Actian. Also had some sharing conflicts. Will give more info soon.

Update (11/11/22): There is still something wrong with the database. Clients are extremely laggy and lock up in Sage. I'm going to try to uninstall sage from the server again after hours. Sharing issues are resolved from what I can tell from the Sage Advisor tool.

Update(11/11/22): Batch printing payroll & AP checks hangs. It took about 4 mins. for one payroll check to print and we never did get the AP check to print. Some things like inventory valuation are much faster than 2022 but some things are way slower to unresponsive than in 2022.

Update (11/11/22): I had Sage support remoted in all afternoon today. Currently we are running a Purge of the company because bulk printing checks just wouldn't work no matter what they tried.

Update (11/12/22): The Purge crashed with file system error number 10 in file: JRNLHDR.DAT. I guess I have to wait till Monday to get support back on the line.

Update (11/12/22): Ran the purge again from the server purging 5 years and older and it completed properly. No change to bulk check printing unresponsiveness. I tired installing the server onto a completely different server in the rack that is running W10Pro currently. No change in outcome with payroll checks. Currently, I plan to uninstall  2023 off everything and go back to 2022. We'll see how that goes this evening.

Update (11/13/22): Experiencing same problems in 2022 as 2023 now. MS issued a bunch of .NET updates recently. If they affect this I have no way to tell. I opened another case in the portal this evening. Had a successful purge earlier but didn't affect performance. Trying data verification now.

Update (11/14/22): Data verification found no errors. Using the other option under Verification to verify the connection being workstation and server showed no errors. I just contacted a Cloud Hosting provider this morning. I'm going to see if they can help us with this. If I can get workable performance hosting elsewhere I'm going to do that.

Update (11/14/22): Got Sage Hosting going and it is a little slow to load in some areas but it is workable for the employees. I'm going to rebuild the company in 2 days. I'm waiting because I'm exhausted, I need a break & and my employees need to get caught up with their work. 

Update (11/15/22): Moving server offsite has not solved the issue. I just tried rebuilding the company on our localserver in 2023 and it errored. Waiting on Sage to call back to see if they have a expedited rebuild process. The show goes on apparently.

Update (11/16/22): Rolled remote host back to Sage 2022 and all is working at pre-initial upgrade speeds. They are installing our email client and tax updates now. Sage wouldn't help me with the rebuild error this morning; only offered their data service. We are not going to pay for a rebuild. Since we do have a large database I've been instructed to contact Sage about upgrading to Sage 100 if it will perform better than what we have now and into the future.

Update (11/29/22): We are not going to Sage 100 because its 10x the cost of Sage 50 to get it going. Then for us it'd be roughly 3x the yearly cost of Sage 50. Sage 50 2022 is still working and now it seems Sage has acknowledged issues with 2023. Here's hoping that they fix it asap.

Reflection: In hindsight I figure the initial error and subsequent manual removal of the software from the server corrupted any further chance of getting back to original Sage 2022 performance for us. Even after reinstalling 2022 we didn't get our performance back which led me to eventually take the server offsite after I exhausted every other option with my onsite installation. My only regret at this point is not going offsite sooner. I had employees sitting with no way to work for days and within 3 hours of contacting an offsite host they had us going in 2023 but still with a performance problem. Within the next 48 hours we were able to work with the host to get our software downgraded to 2022 and updated with all of our required tax updates, email client, etc. and my people are working right now. I'm left trying to figure out what got screwed up in my local server that continues to cause Sage 2022 to be constantly unresponsive.

Update (3/8/23): I made this post almost 4 months ago and these Sage problems are still not resolved as per all the other users posting in these forums. smh