Solved

Quickbooks database server manager problems.

Posted on 2016-10-31
14
184 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 7
  • 5
  • 2
14 Comments
 
LVL 29

Expert Comment

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

Author Comment

by:Bullfrog28
ID: 41867376
Ok the easy client, version 2016.  2 desktops, datafile hosted on Win Server 2012.
0
 
LVL 29

Expert Comment

by:masnrock
ID: 41867386
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
Ready to trade in that old firewall?

Whether you need to trade-up to a shiny new Firebox or just ready to upgrade from whatever appliance you're using now, WatchGuard has the right appliance for you! Find your perfect Firebox today with appliance sizing tool!

 

Author Comment

by:Bullfrog28
ID: 41867444
Yes, confirmed all of those ports are open

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

Expert Comment

by:masnrock
ID: 41867449
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
ID: 41867455
Yes it's in it's own share.

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

Assisted Solution

by:masnrock
masnrock earned 500 total points (awarded by participants)
ID: 41867458
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
 

Author Comment

by:Bullfrog28
ID: 41867460
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 96

Expert Comment

by:Experienced Member
ID: 41867549
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
ID: 41868388
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 29

Assisted Solution

by:masnrock
masnrock earned 500 total points (awarded by participants)
ID: 41868400
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 96

Expert Comment

by:Experienced Member
ID: 41868554
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 29

Accepted Solution

by:
masnrock earned 500 total points (awarded by participants)
ID: 41869373
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 29

Expert Comment

by:masnrock
ID: 41894652
Questions answered sufficiently
0

Featured Post

Get 15 Days FREE Full-Featured Trial

Benefit from a mission critical IT monitoring with Monitis Premium or get it FREE for your entry level monitoring needs.
-Over 200,000 users
-More than 300,000 websites monitored
-Used in 197 countries
-Recommended by 98% of users

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Sometimes drives fill up and we don't know why.  If you don't understand the best way to use the tools available, you may end up being stumped as to why your drive says it's not full when you have no space left!  Here's how you can find out...
An article on effective troubleshooting
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…
In this Micro Tutorial viewers will learn how to restore their server from Bare Metal Backup image created with Windows Server Backup feature. As an example Windows 2012R2 is used.

631 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