Solved

Quickbooks database server manager problems.

Posted on 2016-10-31
14
24 Views
Last Modified: 2016-11-20
I'm having a lot of problems with QB data files stored on Win Server 2012 and 2012 R2 across a variety of clients.

I constantly have to stop the DNS and Windows Firewall services, run the DB Server manager to scan the files, then start DNS and Firewall.  If I dont stop those services the scan fails saying the firewall is blocking the manager.

All proper ports are allowed through the firewall.

Really dont know what to do anymore.  Qb support is absolutely no help.
0
Comment
Question by:Bullfrog28
  • 7
  • 5
  • 2
14 Comments
 
LVL 20

Expert Comment

by:masnrock
Comment Utility
Which version of Quickbooks? (Let's start with one client, then we can start to discuss others)
0
 

Author Comment

by:Bullfrog28
Comment Utility
Ok the easy client, version 2016.  2 desktops, datafile hosted on Win Server 2012.
0
 
LVL 20

Expert Comment

by:masnrock
Comment Utility
So to confirm, these ports are open on the server: 8019, 56726, 55368-55372

And you also don't have either of the workstations trying to act as the machine to share? (I've seen that be a major screw up before)

Also, what else is running on the server?
0
 

Author Comment

by:Bullfrog28
Comment Utility
Yes, confirmed all of those ports are open

It's their Domain Controller and file server.
0
 
LVL 20

Expert Comment

by:masnrock
Comment Utility
Sounds about right. I'm guessing that Quickbooks is in its own share... What AV is running on the server?
0
 

Author Comment

by:Bullfrog28
Comment Utility
Yes it's in it's own share.

AV: ESET File Security for Microsoft Windows Server
0
 
LVL 20

Assisted Solution

by:masnrock
masnrock earned 500 total points (awarded by participants)
Comment Utility
Have you tried creating an exclusion for QB Database Manager? There are times where ESET will cause nightmares for applications. I don't recall specifically having to do so in the past, but things do change with Quickbooks versions.
0
Top 6 Sources for Identifying Threat Actor TTPs

Understanding your enemy is essential. These six sources will help you identify the most popular threat actor tactics, techniques, and procedures (TTPs).

 

Author Comment

by:Bullfrog28
Comment Utility
I'll take a look, I doubt that was done.  I'll add the exception and test.

Will let you know tomorrow.

Thanks.
0
 
LVL 90

Expert Comment

by:John Hurst
Comment Utility
QB 2016 works fine on Server 2012 with the QB Server Manager. We use Symantec Endpoint Protection. We had to make exclusions for QB, so try that here as suggested above.
0
 

Author Comment

by:Bullfrog28
Comment Utility
I put the exclusion in and this morning the users seem to be operating fine.  Multiuser and switching db files is working without having to re-scan and restart the services.

Now here's the monster.....

Another client is an accounting firm.  They use QB 2008 through to 2017.  They are constantly experiencing the same issue.  There are literally hundreds of customer datafile's in different directories.

Do I need to be running the every version of the DB server manager or should the most current just work?
0
 
LVL 20

Assisted Solution

by:masnrock
masnrock earned 500 total points (awarded by participants)
Comment Utility
I had to deal with a less complex, but similar scenario before. You can use the latest one. Just make sure you have the firewall ports of each QB version open.
0
 
LVL 90

Expert Comment

by:John Hurst
Comment Utility
You should only have ONE server manager on the server. The newest version will work backward though quite a few versions, but to V2008? I am not certain. It is out of support anyway.

So encourage your clients to get up to date.
0
 
LVL 20

Accepted Solution

by:
masnrock earned 500 total points (awarded by participants)
Comment Utility
It's just about the databases themselves. Like I've mentioned, you only need the latest Database Server Manager. Just make sure that you have the appropriate firewall ports for each version of QB open on the server itself.

Here's a list of ports for all of those various versions:
  • 2017: 8019, 56727, 55373-55377
  • 2016: 8019, 56726, 55368-55372
  • 2015: 8019, 56725, 55363-55367
  • 2014: 8019, 56724, 55358-55362
  • 2012: 80, 8019, 56722, and 55348-55352
  • 2011: 80, 8019, 56721, and 55343-55347
  • 2010: 80, 8019, 56720, and 55338-55342
  • 2009: 80, 8019, 56719, and 55333-55337
  • 2008: 10180
0
 
LVL 20

Expert Comment

by:masnrock
Comment Utility
Questions answered sufficiently
0

Featured Post

6 Surprising Benefits of Threat Intelligence

All sorts of threat intelligence is available on the web. Intelligence you can learn from, and use to anticipate and prepare for future attacks.

Join & Write a Comment

We recently endured a series of broadcast storms that caused our ISP to shut us down for brief periods of time. After going through a multitude of tests, we determined that the issue was related to Intel NIC drivers on some new HP desktop computers …
The article will show you how you can maintain a simple logfile of all Startup and Shutdown events on Windows servers and desktops with PowerShell. The script can be easily adapted into doing more like gracefully silencing/updating your monitoring s…
In this Micro Tutorial viewers will learn how to use Boot Corrector from Paragon Rescue Kit Free to identify and fix the boot problems of Windows 7/8/2012R2 etc. As an example is used Windows 2012R2 which lost its active partition flag (often happen…
This tutorial will walk an individual through the process of installing the necessary services and then configuring a Windows Server 2012 system as an iSCSI target. To install the necessary roles, go to Server Manager, and select Add Roles and Featu…

728 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

10 Experts available now in Live!

Get 1:1 Help Now