[Merging QBWs] One workstation using a different company file than everyone else

Sorry, but all the attempts at showing the -6000 & -6190 popups have failed.

I can't upload images.

About the error message. Try running the Verify/Rebuild Data utility. Are there any unresolved error messages?

@Chrea Great suggestion.

I have interrupted their operations so much over this that I need to progress after hours. 

The disruption of having QB Support OTP with me while I have everybody off the company file(s) is something they are getting a bit upset about.

As always, these errors pop up without any updates, upgrades or anything, and plague the customer for days/weeks. And in the end, like I said, QB can offer no reason for the failure, which is the correct fix 'next time', or even a "to avoid this in the future, be sure to ...". 

For this reason, I will have to wait until tonight to do anything on the company file, after they close.

That is when I will do as you wisely suggest!

Thanks!

Thank you for providing such a detailed explanation of your situation, The-IT-Guy. It's nice to see you being able to upload images, as your screenshot has truly helped me assess this situation. Your thorough efforts in troubleshooting, including multiple reinstallations and reaching out to support, are commendable. It's clear you've invested significant time and energy into resolving this issue. Let's work together to address both the connectivity problem with your workstation and the challenge of synchronizing data between the temporary backup and the main company file. 

After reviewing the provided screenshot, it appears that the connectivity problem is caused by the error codes you encountered. Specifically, the codes 6190 and 816 refer to issues related to the multi-user network and not with the data file itself. If you've ensured all your users are accessing the company file through multi-user mode and it isn't located in a read-only network folder, you'll need to troubleshoot these errors to ensure that you can continue working on your company files. Let's begin with downloading and installing the QuickBooks Tool Hub on the affected workstation. Here's how you can proceed: 

1. Close QuickBooks.
2. Download the most recent version (1.6.0.3) of the QuickBooks Tool Hub. Save the file somewhere you can easily find it.
3. Open the file you downloaded (QuickBooksToolHub.exe).
4. Follow the on-screen steps to install and agree to the terms and conditions.
5. When the install finishes, double-click the icon on your Windows desktop to open the tool hub.
   
6. Once the QuickBooks Tool Hub is open, select Program Problems.
7. Select Quick Fix my Program.
8. Start QuickBooks Desktop and open your data file.

If you still see the same errors, I'd recommend restarting all of your computers and servers. You can follow these steps in order. If you use:
 

• QuickBooks Enterprise Hosting instead of a server computer, reach out to us through chat so we can help you restart the service.
• One of our affiliated Intuit Hosting Providers or another online service to host your company files, contact them to help restart the service.

1. Restart your server computer (the one hosting your company files).
2. Restart each workstation (the other computers connected to the network that don’t host your company files).
3. Open QuickBooks Desktop on your server computer.
4. Open QuickBooks Desktop on each workstation.
    

Moreover. if you still face the similar issue after performed the abovementioned processes, you can follow the Solution 3 on this article: How to fix Error 6189, 816 and 6190, 816. 

Regarding the error codes 6000, - 83, these appears when you're attempting to open, restore, or back-up your company files. In this case, we'll need to perform a few basic diagnostic procedures to rectify these problems. If you keep your company file on a Windows server, you'll first need to turn off hosting on your workstations. For those using network-hosted company files, ensure that the Host Multi-User Access feature is deactivated on all workstations - these are the networked computers that don't directly host your company files. It's crucial that only your server computer is set up for hosting. I'll show you how: 

1. Open QuickBooks on one of your workstations.
2. Don't open your company file. Instead, navigate to the File menu and hover over Utilities.
3. If you see the "Host Multi-User Access" option, don’t choose it. Move on to the next workstation. This one isn’t causing the problem.
4. If Stop Hosting Multi-User Access is an option, select it.
   
5. Repeat these steps on all of your workstations.

In the event that the error -6000,-83 persists, proceed to Solution 2 outlined in the article: How to fix Error 6000,-83. 

Alternatively, if your company file isn't on a server and you see Error -6000,-83, I recommend contacting our live support team for further assistance.
 

Finally, combining company files or QBW files isn't available. Since each company file is unique and contains specific information, such as transactions, accounts, and preferences. Combining two or more company files can result in data duplication, errors, and conflicts, which can lead to incorrect financial reporting, loss of data, and legal and financial issues. Therefore, it's recommended to manage multiple company files separately and use tools such as import and export to transfer data between them when necessary.

Your patience and persistence are key in this process, The-IT-Guy. If you have questions while following these instructions, share them in the comments section below. I'm committed to working alongside you until we get your QuickBooks system back to optimal functionality. Your business operations are important to us, and we understand the impact these technical issues can have on your day-to-day activities. Rest assured, we'll continue to support you throughout this troubleshooting process and beyond, ensuring you can return to smooth, efficient operations as quickly as possible.

@Chrea I did what you said once they all logged off tonight, and it found errors and fixed them. I was able to get all users logged in after that (me remoting to each). I tried to attach screenshot to this reply. I always get the ever-helpful: "Sorry, unable to complete the action you requested."

My larger, and more doom-inspiring issue, is to somehow merge or export/import transactions on another QBW file, done while on QB support to get that one client connected.

The outlook is not as sunny for this one...

Thanks so much for writing!

@The-IT-Guy 

You can use a migration tool. It's $299 one time license and you can get $100 cashback to purchase it via a partner.

https://get.transactionpro.com/qbd

@Erika_K Thank you for your response. That was quite a bit of information.

Luckily, all users are now logged in as they should be. I think this was due to a Verify and Rebuild, as I did nothing else and they all connected.

The remaining issue is much more sticky. As of now, I have:

1. A 'main' company file that all but one user has been updating.

2. A 'rogue' company file, separate from the main above, that one user kept using after it was accessed by me in a QB support session, trying to get the first/initial login issue fixed.

note: My first knowledge of this was when on 10/24 the lone user and a user of the main file said they could not see each other's transactions.

The second file has only this user's transactions in it for 10/23 and 10/24. Before that, as it was a backup, it should be easy to determine if inspected. This 'rogue' file is saved in a directory with it's associated meta files, inaccessible to all users.

The main file has all other user activity throughout this period.

Objective: Somehow (copy/paste, export/import, backup/restore, ?) get the rogue company file's activity (virtually all sales/invoices) into the main company file.

Although I have wrestled with QB for several years with a variety of versions and customers, this issue is foreign to me, and I have found no direct solutions in my topical search. I do know that a simple 'merge' is not only impossible, but if it were, it would be a disaster.

But the product has been around a while now, and I can't be the first to be in this pickle. I'm hoping there is a way to do this, especially since the 'missing' data is so clearly identifiable in it's own company file. What is simple to say likely means it will not be simple to do!

Again, many thanks to you for a thorough, non-boilerplate reply.

You've really done a great job troubleshooting the user access issues, The-IT-Guy. I understand you're now facing the challenge of linking the transactions from the rogue company file to your main company file. Let me provide additional information about merging your files with your workstations.

Since you’ve already resolved the other issues, which is great, it’s important to note that merging company files directly in QuickBooks is not possible. I recommend manually entering the data into your main company file so that all data entry will be accessible to other users.

Furthermore, you can consider looking into third-party applications that's designed for QuickBooks data migration.

Additionally, after you successfully access your workstations, you can export files to save a backup copy of your company files.

If you have any concerns or if you run into other challenges, feel free to ask. We're here to help you through this.

@The-IT-Guy  I haven't tried the second half of the functionality myself, but I am given to understand that it is possible to both export data from QuickBooks to Excel, and from Excel to QuickBooks.

Would be a good first option to look into.

Update re: Verify/Rebuild

Every single time I do a backup, I'm told there are errors. I'm working on the 'rogue' company file, and I'm the only one in it-employees aren't in, and company closed. This can be 2 minutes after a successful verify/rebuild. This is repeatable.

The repeatable part is after fixing the continuously 'broken' qbw, as long as I don't ask for a backup, any user can log in first, then others can. [I am aware of the 'hosting' option available on each desktop & server, and the need to have all OFF except the server instance.] For now, I have an awkward band aid in kicking all off, verify/rebuild, then log them back on. 

Customer reminds me that they just paid $7k to Intuit, and it is failing constantly... 

I have to let that problem go for now, and focus on those 2 days of transactions that aren't in the main company file. I can't see how to do an export->import, and support is closed until Monday.

If you still encounter errors after running the Verify/Rebuild Data utility, then you need a third-party service to fix it for good.

You can use IIF to migrate data between company files for free but it only supports limited transaction types. You will need to use the migration tool as I mentioned before. Another option, you can purchase a third-party service to merge both company files.