Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3377
  • Last Modified:

Quickbooks Aborting users Randomly

We have a virtual machine running Quickbooks 2012.  The DBs are normally used in multi-user mode and generally runs 2 seperate .qbw (company) files (although we have 6 different .qbw files that may be opened with the latter 4 belonging strictly and accessed by the owners of the company).  

Many of our users experience being aborted at random intervals with no logging of disconnections in the Windows event logs.

Anyone have an idea where to start with these diagnostics?
0
PriorityResearch
Asked:
PriorityResearch
  • 2
1 Solution
 
JohnBusiness Consultant (Owner)Commented:
Make sure the QBW files are local to the QB application or on a Local Area Network. Quick Books does not function well remotely, so make sure that is not happening.

Make sure the user closes the QBW file before closing QuickBooks (File Close Company).

Make sure the network connection to the QBW file is solid. Check it. A flaky network connection can cause this.

.... Thinkpads_User
0
 
PriorityResearchAuthor Commented:
All of the suggestions are true Thinkpads_User except one which I'm trying to prove or disprove now.  

What I'm investigating is this:

We have a Netgear 724T acting as a server switch to the two hosts in our VMWare VSA environment.  Each host has 4 ports on the NIC, all Gb.  On ESXi the hosts are teamed,  but there is no current LAG setup on the Netgear switch.  This is causing the MACs from the connected ports to be displayed as being accessible from both ports in the switches address table instead of being accessible from a LAG.  

I believe this may be causing an issue but I've also been unable to setup a functioning LAG between ESXi and this Netgear switch.  The ESXi host always starts to cycle connection to the vCenter Server located on another device attached to the switch.

I will also say there are VLANs on this device to separate out the production environment from the backend VSA but there's only the two. The LAGs are set to the proper VLANs
0
 
JohnBusiness Consultant (Owner)Commented:
A flaky network (very brief disconnect) will cause QB to abort because the QB database is very chatty. So the network connection must be 100% solid.

Try your ledger (QBW File) on a local machine to test that it is work.

Also, do a verify / rebuild because disconnections can damage the database. Do this only on a local machine.

.... Thinkpads_User
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now