I'm having a hard time after migrating QB data from my 2016 server to my 2019. Here are the details I hope someone can help. Database Server manager Error and Error Codes (-6190, -816)
2016 Hyper-v server i disconnected the D:\ and attached it to a 2019 hyperv server as D so i didn't have to migrate the data. I created a CNAME of the old server name in DNS so my users wouldn't have to remap drives and installed QB on C:\ under the default path. It may be important to note my QB files are on the D:\ drive and the server manager is running in the default path as mentioned above from C:\. Some articles say this isn't a great idea but it was working on the previous server I migrated from.
I get the following message in QuickBooks Server Manger on the Database Server tab:
"Unable to retrieve connected files and logged in user list." I see the QuickBooks files on the first tab when I scan the directory. I also have the D:\ drive selected under the scan drives tab.
Also, when the second user tries to connect to the QuickBooks data file on the server, they receive the error:
"Quickbooks is unable to open the company file. It may have been opened by another user. You should ask that user....."
Error Codes (-6190, -816)"
I found the following article in my search for a solution before posting:
It indicates my CNAME work-around isn't supported so I remapped both of their drives with the FQDN and tried again. And again they received the Error Codes above and multi-user mode is still not working.
Additional troubleshooting steps included removing the ND and TLG files and letting them get recreated so the appropriate IP address is listed in the ND file. Did not resolve the issue.
I also tried copying the QuickBooks folder from the default common files install to D:\Quickbooks, installing a new QBMonitoringServices.exe as a service and ran the QBServerUtilityMgr.exe from the D:\ so my files that were being hosted on the D:\ wouldn't have issues because the service and Utility Manager were running from the same drive. Also didn't resolve the issue.
Hello there, @CaleL.
I appreciate you for sharing the troubleshooting steps you've already performed. .Since you're still getting the same error, let me route you to the best available support so we can further check its root cause.
The Community page is a public forum, I'd recommend contacting our Technical Support Team. They have the tools to securely access your account and further help you via a secured remote access sessions. Here’s how you can contact us:
Just a reminder, due to the ongoing COVID-19 pandemic, we have made changes to our operating hours. You can request a callback from one of our representatives or use our live messaging option from 6:00 AM to 6:00 PM on weekdays and 6:00 AM until 3:00 PM on Saturdays. You can read through this article to learn more about the schedule of our available support: Support hours and types.
Let me know how it goes. I want to make sure you're taken care of, and I'll be right here if you need anything else. Have a nice day!
I'm back to make sure everything works fine, @CaleL.
Making sure you're able to migrate your QuickBooks data server seamlessly is my priority. Were you able to speak with one of our phone representatives using the steps I've shared?
I'll be around if you need more help with your concern. Wishing you all the best.
Yes,I spoke with a rep via the phone. We tried several things I had already attempted and mentioned in my original post however, the fix was to move the .qbw files to the same drive (c:\) that the server manager was running on.