I totally hope you get this message.... It's only 10 months late. I feel your pain as an IT Administrator. We just upgraded to Windows Server 2025 - on a VM server using QB Desktop Enterprise 2024 with 1-30 users around 20 company files on Term Serv and sharing data on DC/Data Server and have been struggling with both for awhile and had on our previous server as well. Hence we upgraded thinking hardware and resources were the issue. New server - same issues - hosting / sharing / crashing; running dbmanager and scanning constantly; shared drives dropping. I called QB Enterprise support as we paid a lot of money for 1 year to have all of these issues. I was told that this was not a supported way to run QB using the DBMgr and data on the data server while hosting the QB app on Term server. They don't support using Term server at all... (What?? It's not Enterprise if you can't host it for lots of users inside and outside your business - Why sell it then - Hello!) I was told to move my files from the Data server to over to the Term Server with the company files located in root folder C:
While the crashing and hosting issues stopped, the sharing and admin permissions started. We started giving everyone, objects and services everything (db mgr, files and qb app need admin permission) - and were still getting 1 person everyday or so that needed "admin permission to run quickbooks". I almost made them all admins to make it stop. It seemed as though once you log in as admin on the TS for 1 person - everyone else's worked - until it didn't. Sound familiar?
One of the notes online in this forum somewhere said to give the QB app "admin permissions" in the Properties of the QB app itself. I tried that and then everyone received the DB screen shots you provided when opening QB. Although we are allowing QB to run as an admin, they were logging into the TS with a different user and password but they still needed to log into the app with the admin credentials. GroundHog Day - everyday.... all day (this is the part where I am rolling my eyes up into my head and contemplating a new career path) We removed the run as admin permissions by the way.
I looked on the Intuit website - the resources tab to see if I could find someone to help as I am beyond getting anywhere with how to resolve this issue and my boss is stalking me constantly about an update to this issue. I started looking for an outside QB advisor on the Intuit site to help - anyone - besides Intuit that knows anything about hosting QB Enterprise. I checked the "resources tab in the support ribbon and filtered by QB Desktop Enterprise" and found a few outside vendors to contact for support. I called one and he was extremely helpful. Like 10 mins helpful he gave me the meaning of life - or life with QB.
I have not tried this yet, as I can't make one more change to QB or files or the app today without my entire office walking out, but it makes sooo much sense. I am not sure if you have already done this but he said to move the actual QB Company files on the Term Server to: "Users / Public / Documents / Intuit / QB / Company Files". You don't even need to create the folder, it already exists! The permissions in public are not stringent so access permissions are very minimal. Eureka! I wish someone would have shared this with me earlier. I did not see anything in the install / migration anywhere about this. Meanwhile I have to go tell everyone in my office that their shortcuts aren't going to work and there's another modification coming soon. Yay me!
I really hope this solves your issue if you are still fighting this.
Cheers!
