Re-Installation (New or Failed Hardware)

Overview

NOTE: If you are running QB 2022 thru 2024, you must have QQube Version 10.0.590 or later to accommodate certain Intuit changes in its SDK. If you are in subscription, you can just request a new download link in the ticket.  If you are not, please visit QQube for QuickBooks Subscription Renewals to renew your subscription and receive a new License ID and Activation Code.

Use these procedures for situations where there is a:

• Re-install due to a machine crash
• Purchase of a new machine
• Move to another machine
• Migration from an old server to a new server

QQube is a read-only application. There is no path to migrate or recover existing data.

General Steps

STEP 1.
Find the QQube License ID and create a ticket in the support area to get it reset upon installation (or you will receive error 5103 when attempting to activate). If you can't find the License ID, then post the name of the company, or the date of the original purchase, or the purchase receipt number in the ticket.

STEP 2.
Choose the correct installation type, and use the applicable step by step instructions:

• Single User.  This is used when there is only user of QQube. All of the components - including the QQube database - will be installed on this machine. This type of installation can only be used on a desktop or laptop. You cannot install a single-user on a server or remote desktop environment.
• Multi-User in a Local Network (Server portion ONLY) The server is where the QQube database resides along with a CLIENT copy of QuickBooks and is shared on the network. NOTE: Do not install the multi-user client portion on the workstations, unless the release you are installing is later than version you are replacing. If you are installing the same version as the one you are replacing, see specific instructions below for pointing the existing client installation to the new server installation.
• Multi-User in a Hosted or Remote Desktop Environment.  If anybody is logging in remotely to use QuickBooks on your server, you must use this method to avoid synch issues.

If you are in a server environment, you MUST either uninstall the old QQube, or disconnect it from the network.  Not doing so will result in problems and reports not seeing the new database.

STEP 3.
When QQube was first installed, you would have created user(s) in QuickBooks to allow automatic login of QQube to QuickBooks. Pro and Premiere users will not need to do anything.  Enterprise Users will need to either know, or change the Custom Reporting User password, as that will be needed to connect QQube to QuickBooks.

STEP 4.
Confirm the creation of the necessary Connection Users, and that you have set the appropriate QuickBooks Preferences

STEP 5.
Run the QQube Configuration Tool Wizard.  If you have Multiple Companies do NOT synch your data but review the Multi-Company Setup guide and add any additional companies.

STEP 6.
Synch your data. 

STEP 7 (Only for in-house server with client/workstation connections).
If you are installing a newer version of QQube than the version you are replacing, then follow the instructions for installing the CLIENT portion in this guide.

If you are installing the same version of QQube than the version you are replacing, then go to each workstation and open up the QQube Configuration Tool.  You will get an error that it can't find the server:

Click the OK button to get this window:

It should locate the QQube server you just installed on the network.

IF a server is not found, first turn off the local windows firewall, second turn off the server firewall. This generally is not necessary, but conflicts can arise due to group policies, etc.

Then save the new engine name (it will fix the ODBC DSNs):

You will return to the Configuration Tool:

STEP 8.

Check your logs for any synch errors before attempting to run any existing reports.

STEP 9.
Test your reports. Remember that there are connection strings or manual configurations necessary to get your Excel or similar report to talk to QQube. The installation handles those procedures. All that is necessary is that you have the correct data models loaded, and that there are no synch errors.