QUICNET PRO 2.

0 INSTALLATION

Client Installation Instructions

Last Revised: April 20th, 2015 by Alain Hungerford
QuicNet Pro 2.0 Installation and Configuration

• Run the “QNProSetup.exe” file. Hit “Next”, select your installation directory, and hit “Next”
again. Select “Client Components Only”, and hit “Next”.
• Choose a location for your start menu shortcuts, or simply click “Don’t create a start menu
folder” and hit “Next”.
• Select your options for Desktop and Quick Launch icons if desired, and hit “Next”.
o Hit “Install”. The install will begin its process.
o A prompt will appear for the Borland Database Engine installation; leave this directory at
default and simply hit “OK” to continue. Select “OK” after the BDE installation has
completed.

o Click “Finish” to exit the setup; we must now move on to configuring QuicNet to point to
its working database and SQL instance directories.
• Launch QuicNet from either the desktop, start menu, or its physical installation directory, which
is labeled “QuicNet.exe”. QuicNet will prompt you for a software license; this license file should
be included on your QuicNet installation CD or digital download. Select “Yes”, and browse for
the “license.xml” file. This file may also be labeled “McCain.xml”, or the name of your agency.
Select your license file, and hit “Open”.

• You will be prompted with an error stating “Unable to Connect with Comm Processor”. Simply
hit “OK”; you will be prompted with a second error, stating “QuicNet could not connect with the
Communications Processor. Try to connect again?” Select “NO”.
• QuicNet will now open; however, all options will be greyed out. This is because no configuration
currently exists for QuicNet to access its working data and SQL database directories. At the top
of the window, select “Tools -> Options”. From here, we will be able to specify the working
directories and the server that the communications processor resides on. The following fields IN
BOLD ARE REQUIRED.
o COMPUTER: Server hostname or IP address of the QuicNet server
o IP PORT: IP Port used by QuicNet to communicate with the QuicNet server; this is
almost always default at 4001.
o SQL SERVER: The server name AND instance that your QuicNet databases reside upon.
In this example, the server was ahungerford2\sqlexpress; “ahungerford2” being the
server name, and “sqlexpress” being the SQL instance name.
o DATA DIRECTORY: The path directing QuicNet to the server’s Data directory. This can
be achieved by creating a mapped network drive on the client machine to the server’s
data directory, or by manually entering the IP/share name of the data directory, i.e.
\\192.168.26.1\data.

 After entering the required configuration information, simply click OK, and close QuicNet.
• Next, we must configure QuicNet’s BDE and ODBC driver configuration. To configure ODBC
source information:

o The ODBC editor can be found in one of two locations depending on if the computer is
32 or 64 bit. On 32 bit machines, the ODBC editor can be found under Start -> Control
Panel -> Administrative Tools -> Data Sources (ODBC).

32-bit ->

o On 64-bit machines, we must launch the 32-bit ODBC editor. This can be found in:
C:\Windows\SysWow64\odbcad32.exe.

64-bit ->

o Navigate to the “System DSN” tab. Here we will create two ODBC sources for QuicNet’s
SQL databases.

o Click “Add” on the right.

o Scroll all the way down the list of available drivers and select “SQL Server”, and hit
“Finish”.

o Name the source “QNProHistory”. Under the “Server” field, enter the server name
followed by the instance, typically “servername\sqlinstance”. Hit next. Again, if the SQL
Server instance resides on the same computer as the communications processor,
servername will not be necessary.

o Click the “With SQL Server Authentication” bubble. Check the box for “Connect to SQL
Server” and enter the following login information, then click “Next”:

▪ User: QuicNet4
▪ Password: QuicNet4.1
 o Check the box for “Change the default database to:” and select “QNProHistory”. Hit
“Next”.

o Hit “Finish”. Hit “OK” at the dialogue box that appears.

o Repeat this process for the “QNProSystem” database.

• Now that we have verified ODBC sources, there is one last piece of configuration to generate.
Navigate to Start -> Control Panel -> BDE Administrator (32-bit). IF YOU ARE INSTALLING
QUICNET ON A 64-BIT MACHINE, YOU MUST LAUNCH THE BDE ADMINISTRATOR FROM
C:\WINDOWS\SYSWO64\BDEADMIN.CPL. (RIGHT CLICK AND RUN AS ADMINISTRATOR)

32-bit ->

64-bit ->

o On the “Object” menu, select “Options”.

o Uncheck the “Virtual” box and hit “OK.

o Click on the “Configuration” tab, and expand “Drivers -> ODBC”.

o Right click on “ODBC” and hit “New”. For the driver name, enter “ODBC_QNProSystem”.
Select “QNProSystem” from the Data Sources box, and hit “OK”.
 o In the “Definition” window on the left, enter “QNProSystem” in the “ODBC DSN” field,
and hit ENTER.

o The “Configuration” tab on the left should now appear like so (green arrows), indication
that unsaved changes have been made.

 Repeat this process for the “QNProHistory” database. (i.e. ODBC_QNProHistory)

o When complete, close the BDE Administrator, and hit “Yes” when prompted to save all
edits.

• At this point of the procedure, QuicNet should be able to launch without issue. Attempt to
launch QuicNet. Please see the “Troubleshooting” section of the guide below if any errors occur.
Troubleshooting

• After completing the steps above, if and error is encountered while launching QuicNet, several
things may be preventing the client from opening. These are usually related to configuration
typos or incorrect network information.
• The first step is to re-verify configuration information. Navigate to the QuicNet Pro installation
directory, and open the QuicNet4.ini file.

o Under the “[Database]” section of the document, verify that the “Server=” string reads
the correct network location of the SQL Server, typically “servername\sqlinstance”. If the
SQL Server resides on the same computer as the communications processor, the
hostname is not required – you may simply enter the SQL instance like so:
“Server=sqlexpress”.

• If all configuration strings appear accurate, verify the ODBC and BDE sources you created earlier.
Check for typos and misconfigurations. If you still cannot open QuicNet, contact McCain
Technical Support at (760)-734-5052, or email us at support@mccain-inc.com.