Quickbooks Enterprise 2024 multi-user issues

[HCHTech]

We replaced all of the computers at a small client yesterday, and had to install QB Enterprise 2024 (they have a 5-user license). Although this was my first time installing this particular version, I've setup QB lots of times in the past. It was working perfectly fine on their now-retired Windows 10 computers. The file itself was shared from the owner's computer. The other users had a Q: drive that mapped to the shared folder on the owner's computer (which was located on the root of the C: drive).

We setup it up just the same, installed the database manager on the owner's computer, and had it share the folder. That bit went smoothly, no errors or any sign of trouble.

The users can see the file and attempt to open it (they get the login box, so I know the sharing is working). The trouble is every other user is getting an "incorrect username or password" error when trying to open the file. Accessing the file ON the owner's computer using each of the other users name & password combination works fine, so I know we have the names & passwords correct. Also, the other computers cannot open the file using the admin name and password either.

I have tried:

• unsharing and re-sharing the shared folder - using "everyone" permissions
• confirming that all of the other users can browse and create files in the shared folder on the owner's machine
• Deleting and recreating one of the users from within Quickbooks
• Reboots of everything
• Confirming all installations are at the same Quickbooks update level (which is the latest)

Things I haven't tried yet because we ran out of time yesterday:

• Relocating the shared folder on the owners computer to somewhere other than the root of the C: drive - I remember that making a difference for some other client's LOB software in the past when we went from Windows 10 to Windows 11
• Uninstalling and reinstalling QB Database Manager
• I don't know, burning some sage?

 

[YeOldeStonecat]

Confirmed the quired two services for QB's are running in services.msc?
What if you run the QB Database mangler...scan...apply fixes?

 

[Markverhyden]

Things I haven't tried yet because we ran out of time yesterday:

• Relocating the shared folder on the owners computer to somewhere other than the root of the C: drive - I remember that making a difference for some other client's LOB software in the past when we went from Windows 10 to Windows 11

I stopped using folders at the root, aka C:, to store stuff not long after W7 came out. There was a big change in file security, etc under the hood and no way to really make changes or understand it. At least for me. Just too many random problems.

• I don't know, burning some sage?

I find chicken blood and cigar smoke work better.......

 

[HCHTech]

Moving the shared folder to inside of the user folder (Then pointing QBDM to that folder, then remapping the share on the other computers) fixed the problem. Imagine a world where error messages pointed even SOMEWHERE CLOSE to the right direction to allow you to know what the actual problem is.

 

[Sky-Knight]

I can't tell you how many QB Data folders I have at C:\QB Data, they work fine.

But I do make the share myself, then aim the manager at it.

I have far more annoyance with my service desk forgetting to install the XPS Document Writer, so QB doesn't pitch a fit about PDF printer errors.

 

[HCHTech]

I can't tell you how many QB Data folders I have at C:\QB Data, they work fine.

But I do make the share myself, then aim the manager at it.

That is the exact procedure we took. I have no idea why it didn't work, and the only error we got was "incorrect user name or password", which was neither actionable nor correct! Regardless, I'm changing our SOP to put the data folder inside of the user folder. I can't believe the amount of time wasted on this in retrospect, and I'd like to avoid that in the future. I have other installs out there with the shared folder on the root that are working, but I don't think any of those are 2024 Enterprise.

Along the same line, the Quickbooks error you get immediately after installation when you don't have XPS document writer installed states something along the lines of "a component is missing that lets Quickbooks create PDF files". It doesn't mention what component that is, which we only know about from experience. Quickbooks could just as easily install the thing itself during installation, or you know, just for tun, give you the name of the component it needs. I hate Intuit more than usual today.

 

[trevm999]

That's why using tools like Process Monitor is so valuable. In 30 seconds you can get the path or registry key it is looking for. Might not have helped with your original issue, but I can't tell you goe many time I've seen a "path not found" error with no indication of what path a program is looking for. But that's a dead easy problem with Process Monitor.

 

[Markverhyden]

where error messages pointed even SOMEWHERE CLOSE to the right direction to allow you to know what the actual problem is.

I can remember not long after W2K workstation was released. Back in those days MS really started shoveling all kinds of things into the Registry. Back then a business customer could actually speak to an real American/Canadian MS employee in North America. Several of them, when questioned about vagueness and inconsistencies of Reg changes, told me that in reality there was no person or group that could really understand the entire Registry ecosystem.