Quickbooks Enterprise on ClearOS

This guide covers the installation of the Quickbooks Database Monitoring engine on ClearOS. You will need to have root access to your server and be familiar with command line administration of your ClearOS server.

This howto covers Quickbooks Enterprise only. Due to limitations of Quickbooks Pro and other Intuit products, they cannot have their data hosted on anything but Windows. Please use virtualization methods or upgrate to Quickbooks Enterprise.


Prepare your server by creating a group for your accounting professionals. For this demonstration we have created a group called 'accounting'.

Create a flexshare for your Quickbooks data. For this demonstration we created a share called 'quickbooks' and we've mapped this using Windows Filesharing to the Q: drive on our workstations.

net use q: \\server\quickbooks /persistent:yes


Log into your server via command line as root. Download the package from Intuit.

Quickbooks Enterprise 2013

Download the following:

yum -y install wget

Install the package.

yum install qbdbm-23.0-1.i386.rpm

Add these two daemons as services:

chkconfig --add qbdbmgrn_23
chkconfig --add qbdbfilemon

Because the database manager is a 32 bit application, you will need to install the 32-bit libraries. Run the following if you are using a ClearOS 64 bit version:

yum --enablerepo=clearos-core install glibc.i686 libstdc++.i686 gamin.i686

Start the services:

service qbdbmgrn_23 start
service qbdbfilemon start

Verify that they are running:

service qbdbmgrn_23 status
service qbdbfilemon status


As per the instructions, please add the QB data paths to /opt/qb/util/qbmonitord.conf file.

vi /opt/qb/util/qbmonitord.conf

Replace the /QBData path with the appropriate flexshare directory and path. The File Monitor will NOT search subdirectories. List each directory on its own line.


Any time you update the qbmonitord.conf file, you will need to restart the qbdbfilemon daemon. It will index it automatically and should process the change without a restart but restart it anyways.

service qbdbfilemon restart

Finishing up

Be sure to restart the syslog service so that items get properly logged.

service syslog restart

Lastly, please make sure you are running a good backup of these files.

Upgrading from previous versions

Upgrading from previous versions is beyond the scope of this howto, please refer to the documentation contained within the link below.


Make sure that you can open the file and that it will go into multi-user mode.

If you have difficulty, make sure that the DNS, mapped network drive, unamd -a, and those names reported by QBES are absolutely right. The log file (/var/log/messages) will contain information about what the daemon thinks the server is. You need to make your mapped network drive connection to this resource (ie. \\system.clearos.lan\quickbooks).

Please note that the current Quickbooks Connection Diagnostic Tool, while extremely useful, is not certified for the Linux version of the Database Manager. In our testing it would report successes for everything but the 'DB Service Status' even when that service was working and configured properly.


mkdir /root/support /root/support/quickbooks
cd /root/support/quickbooks
rpm --import qbdbm-pubkey.asc
rpm -K qbdbm-20.0-5.i386.rpm
rpm -Uvh qbdbm-20.0-5.i386.rpm
chkconfig --add qbdbmgrn_20
chkconfig --add qbdbfilemon
echo "" > /opt/qb/util/qbmonitord.conf
service qbdbfilemon restart
service syslog restart



"qbdbmgrn_20"   => array("qbdbm",            "QBDBMgrN_20",   "yes",  DAEMON_LANG_QBDBM,        "no",  "quickbooks.php"),
"qbdbfilemon"   => array("qbdbm",            "qbmonitord",    "yes",  DAEMON_LANG_QBFILEMON,    "no",  "quickbooks.php"),


define("DAEMON_LANG_QBDBM", "Quickbooks Enterprise Manager");


content/en_us/kb_o_quickbooks_enterprise_on_clearos.txt · Last modified: 2016/07/20 15:05 by dloper