Thursday, January 10, 2013

QuickBooks error -6123, 0, and my solution

I was troubleshooting error -6123, 0 with QuickBooks Pro 2008, finally solved the problem and thought I'd share.

The text of this error message was something to the effect of "cannot connect to database server," however, mine was a single user installation with the company file residing locally. I realize QuickBooks may use a database server to connect to even a local database, but the knowledge base article on Intuit's website for error -6123, 0 was aimed at situations that did not apply to me. I was not using the company file over the network, I was not in multi-user mode, nor was I restoring a backup.

I went through a bunch of things, including the use of the QuickBooks File Doctor, which said my database was perfect. I disabled Windows firewall, and was using no other. I restored a backup of the company file using Windows Previous Versions. I checked QuickBooks services but found nothing that jumped out at me. I was stymied.

I started thinking about how I had the system set up. The computer is joined to a domain, so I logged in as Domain Administrator, tested QuickBooks, and it worked. The user I have set up to use QuickBooks doesn't have local admin, and I'd rather avoid giving it to her if possible. So I started Googling and ended up finding another Intuit knowledge base article for "Configuring multi-user access requires Windows Admin rights". Even though I'm not in a multi-user scenario, I decided to see if the information was helpful anyway, and it turns out it was.

Solution: For QuickBooks Pro 2008, there is a Windows user account called "QBDataServiceUser18" which I added to the local Administrators group. That did the trick and now my user can access QuickBooks without that pesky error anymore, and without admin rights!

7 comments:

  1. Hi.

    I had the same issue. I have added my QBDataServiceUser17 to the administration group but this did not resolve my issue.

    When I tried to open Quickbooks Database Server Manager is stated that I need to turn on hosting (Open Quickbooks and click File, Utilities, and then click Host Multi-User Access). When I opened this, it already stated that the Multi-User access is enabled, do I want to disable it? I then chose yes to disable and once it was disabled, I was able to open my quickbooks again.

    Just thought to share my situation and how I have solved it.

    ReplyDelete
  2. My issue was that the service QBCFMonitorService was stopped. I just had to start it up and it was fine. Happened after upgrading to windows 10.

    ReplyDelete
  3. I am running QB Pro 2016 on a Win10 workstation with Win Defender as the malware/antivirus software. I went into Defender and excluded the .QBW file plus the Intuit folder from Defender, Voila! I am now able to get into my QB company file! If you are running McAfee, you should be able to do the same exclusion.

    ReplyDelete
  4. Had the same error, with the message to the effect that "could not contact the database". I am also running QB in single-user mode with the company file on the same drive as the QB application. I solved my problem after spending 1/2 day on it!

    I attribute the solution to one of two things (or both). I saw an article in the intuit user forum about renaming the "nd" file (network file) associated with the company file. I did that but still had the error. Then I opted to reinstall. Step 1 to reinstall is to uninstall the existing version of QB through Control Panel. It would NOT uninstall because it said the application was open (but I had closed it). Task Manager showed be several QB associated files open, which I closed through Task Manager. It occurred to me that this error was occurring because QB somehow believed I was in multi-user mode when I was not, and that there may have been another instance of QB running. Also suspecting that the shortcut from the QB open dialogue may be corrupt, I then located my QB company file and right-clicked to open the file with QB. Voila, success! It could have been the rename of the "nd" file. It could have been closing down all QB files in Task Manager. It may have been both.

    I have another company file that was giving me the same error. I will report further if there is anything different.

    ReplyDelete
  5. Not having the same good fortune with my second company file. One step I neglected to mention above was that I had run Quickbooks File Doctor on the file I eventually successfully opened (but the Doctor did not appear to solve the problem). I ran the same utility on the second company file and it is reporting that this second company file is corrupt and irreparable. I'm on a different track to fix it. I am pondering how the problems with the two files could have occurred. I notice that the database manager and Intuit personal database manager are starting as background services registered in Task Manager, though I am not running in multi-user mode. On one occasion tonight, there were two instances of database manager running. I'm not sure that any database manager should be running and the answer to that question does not seem easily answered.

    ReplyDelete
  6. To get started, you need to figure out your true purpose. Whether you really want to delete zoosk account permanently or just deactivate zoosk account for some time, it matters a lot. Because once you delete Zoosk account, all your subscriptions, contacts and matches will be deleted at the same time. And you can't find them back. But if you only want to get rid of Zoosk temporarily or you are not sure, then deactivating your Zoosk account would be a better option.

    ReplyDelete
  7. There have been countless influential thinkers throughout the ages, but some of the most brilliant minds make a more lasting, significant impact than others. One man who is famous for his intellectual achievements is none other than the influential physicist Albert Einstein. Einstein was not only known for his clever theories and mathematics, Einstein had a way with words as well. We have the 50 best quotes from Albert Einstein!

    ReplyDelete