User is already logged in, but they aren't

default_wasabi_u6 · ‎December 10, 2018

Raywhite28 · ‎December 10, 2018

Try restarting the computer that is hosting the file. That should make it rest who is logged on.

Raywhite28 · ‎December 10, 2018

Try restarting the computer that is hosting the file. That should make it rest who is logged on.

Techineer · ‎December 10, 2018

This is not an acceptable solution. I'm using QB 2017 Pro and run into this frequently. I am seriously regretting my 'upgrade' from QB2012, and would go back to it if it was feasible without having to re-enter every transaction. Intuit has made significant changes to the appearance and usability of the program and seriously degraded its operability. They need to get someone to resolve this issue.

jlobianco · ‎December 10, 2018

This is 100 percent not an acceptable solution. Restarting the Quickbooks DB every time someone gets locked out of their company file is not practical.

Techineer · ‎December 10, 2018

I have found a workaround that is a bit more palatable.

The problem is caused by the Quickbooks Messenger Service.  When you log out of the company file, the QB messaging app is not terminated properly.  You can close it without restarting your computer.

Use CTRL-ALT-DEL and select the Task Manager.  Under the Processes tab, look for multiple instances of QuickBooksMessagine (32 bit).  Select each one and press Delete to terminate the process.  Close the task manager and log into Quickbooks.  It should now open the company file.

scolby22 · ‎December 10, 2018

Thank you. You can also disable Quickbooks Messenger.

Disable QuickBooks Messenger:
In multi-user mode, sign in as Admin.
Go to File > Utilities.
Click Disable QuickBooks Messenger.
Log out of the company file and then log back in for the setting to take effect.
QuickBooks Messenger - QuickBooks Learn & Support
<a rel="nofollow" target="_blank" href="https://community.intuit.com/articles/1494942-quickbooks-messenger">https://community.intuit.com/art...>

Buttercup376 · ‎December 10, 2018

Are there any other viable solutions?

I have multiple company files, but I am only seeing this in ONE file. I have ran the QBFD, but still no luck. I know for a fact the user is not logged in, but it says they are.

crenegarjr · ‎December 10, 2018

We use Enterprise Version 18 and this is an issue. It seems to definitely be the Messenger service that causes this. If you try to use the Task Manager to kill the service it restarts itself so you need to rename the exe (I just put a .old at the end of it) then kill all instances of the service. Amazing how many stupid things like this Intuit can't seem to get right.

Raywhite28 · ‎December 10, 2018

@Buttercup376

Try to restart the server. That’s the computer that hosts the data file.

Anonymous · ‎December 10, 2018

Since you have just updated from QB2012 there may be other issues to consider ..

The newer versions of QB desktop are tuned to newer versions of Windows - if you are still using the old PCs and/or if those PCs are running different versions of Windows then you can get some serious grief in making and holding network connections between users. Then when an active user loses their network connection without logging off first, QB may appear to think they are still logged in when they try to reconnect.

The best setup is to have all users plus any data host all using the same version of windows - for QB 2017 I think that should be Windows10. You may seem to be able to get it working on older platforms, but you then run into reliably problems as you have described.

kboroumand · ‎March 11, 2019

You don't need to restart the server just restart the QuickBooksDB service.

SpahnLF · ‎April 30, 2019

this solved the issue for me. QB Pro 2019

Uwe · ‎April 30, 2019

This worked great!

Thanks for this answer.

eToner · ‎June 06, 2019

This worked for me, much more palatable!

eToner · ‎June 06, 2019

This worked, and was much more palatable. I ended the process Quikbooks Messenger from the host machine, went and logged back in and it worked.

MT_OG · ‎June 14, 2019

Thank you! This was the solution that worked for me!

MorganB · ‎June 14, 2019

I'm glad to hear this worked for you, MT_OG. Please don't hesitate to reach out if you ever need assistance again in the future.

eolsen_cwm · ‎July 10, 2019

Restarting a server, to fix one error in a program, is a terrible and impractical solution, and you are a Pro Adviser?

Intuit needs to fix the issue with their QuickBooks Messenger not terminating properly. This has been an issue for many releases now...

We have disabled the QuickBooks Messenger in all of our company files until a fix can be found.

Rose-A · ‎July 10, 2019

Hi, eolsen_cwm.

Allow me to help and provide you with additional information regarding QuickBooks Messenger issues in QuickBooks Desktop.

It may be worthwhile speaking to our QuickBooks Desktop Team about this, I'd be interested to see if they can identify any issues on their end. I'll be available to have this case escalated to the appropriate channels so you're able to reach a point of resolution as quickly as possible

As soon as an update is received, I will be happy to update this thread and let everyone know so that you can get back to business.

For now, I'd suggest reaching out to our QuickBooks Desktop Support to have this re-investigated.

Within your QuickBooks Desktop, click Help at the top menu bar.
Click Contact us.
To route you to the correct support expert, we need to know what type of question you have. Give a brief description of your issue and click Continue.
We’ll provide you a few options. You choose which one is best for you.

You may find the following articles helpful:

You can always get back to me if you have additional questions about QuickBooks Messenger. Have a good one.

jmak · ‎July 16, 2019

This solutions worked perfectly. Thank you for the advice!

SoundEmperor · ‎July 31, 2019

This USED to be a solution. It doesn't work any longer! I am the administrator and can't get in to work or fix any one else's problems! INTUIT, you need to fix this now!

ShiellaGraceA · ‎July 31, 2019

Hi SoundEmperor,

We can configure your Database Server Manager to its default setting to get this fixed. Let me guide you through the steps.

Open the Windows Start menu.
Type “Services” into the search and open Services.
Click and open QuickBooksDBXX (XX is the version number).
Go to the General tab and find the Service status section. If it's Started or Running, select Stop.
From the Startup type drop-down menu, click Automatic.
Go to the Log on tab. Click the Local System account option.
Go to the Recovery tab. Click Restart the Service from each of these drop-down menus: First failure, Second failure, and Subsequent failures.
Go back to the General tab. Click Start to restart Database Server Manager.

Also, make sure you've set your firewall permission. Please refer to this article for the steps: Configure firewall security settings for Desktop.

Once done, try to log in again.

If it doesn't work, please perform the following:

Reboot your server.
Reinstall using a clean install.

You might also want to check this handy article for future reference: Account management.

Let us know if you have additional questions. We're here to help.

Denise Z · ‎September 16, 2019

I freakishly have found something that has worked for me. I tried all of the suggestions above ( accept restarting the server ) and none worked. While everyone is logged into quick books, Switch to Single-User Mode .. using the messenger it will alert everyone and automatically disconnect anyone logged in. Then sign in again, as normal.

Quaid24 · ‎November 25, 2019

That works! Thank you so much. I have always struggled with this and we keep our QB on our server, which required us to restart our entire system.

CloseTheFrontDoor · ‎July 20, 2020

if you are using windows you can also go to Services and looks for any service that starts with name Quickbooks, right click and restart the service, i did not need to restart the computer. worked for me.

Topics

Training

Community

Resources

User is already logged in, but they aren't