How to Install ConnectIt and Debug Issues.

INTERNAL: This is the official Technical instructions. If you have any points of detail to add since you are performing the task, please add to this article. This article is not for customers.

This article is not for customers.

Get the installer from

Connect to the customer.

Transfer the ConnectIt install over to clients server


  1. The Path to Sage folder. 
  2. The Sage user that has high enough permissions to access all the modules\tables.
  3. Sage "Companies" that will be used on the scanners.
  4. Log into Sage with your user and perform the task below. If you cannot complete these task you should ask the "Sage Administrator" to give you higher permissions. 
  5. Go into Library Master > Main > Company Maintenance > enter the Companies that will be used on the scanners. On the "Preferences" tab, make sure "Allow External Access" is enabled. If it is not, then ConnectIt will NOT be able to read\write to Sage tables.
  6. Go into Library Master > Setup > System Configuration > Security tab. See if ODBC security is enabled. If it is, you need to make sure the "Sage user" that you are putting into the ODBC connection is in a "Sage ROLE" that has permissions set to allow access to the tables through ODBC.        Go into Library Master > Main > Role Maintenence. Tab 5
  7. In File Explorer, make sure the MAS90 folder permissions include Local Services with Full Control.
  8. If Sage Premium [SQL], then you will use the SQL ODBC Driver. Instructions are below the PVX driver install instructions.
    If Sage Standard or Advanced [PVX], install the Sage 64bit ODBC Driver on the server. The path to that installer should be:
    • MAS90 > wksetup > Prerequisites > 64bit ODBC > Run “Sage ODBC 64-bit Installer” AS ADMIN
      • (If any issues during installation, close the "ODBC Data Source Administrator" window and try again)

Create ProvideX based [Standard or Advanced] ODBC DNS, screens below.

  • Data source name “RF64”
  • Description “Scanco”
  • Fill in Database Directory with the directory of the MAS90 folder.
  • Fill in Company code, default user id, and password.
  • Fill in Prefix for data files and path to view DLL.
  • Dirty Read, Burst Mode, Strip trailing spaces checked, and 4MB cache
  • Test connection

Create SQL based [Premium] ODBC DNS, screens below.

You will have to go into SQL Management Studio and create our SQL User and password AND it MUST be the same as the Sage user and password.

  • In the SQL Server Management Studio, open Object Explorer.
  • Click Server_instance_name > Security > Logins.
  • Right-click Logins and select New Login.
  • On the General page, in the Login name field, type the name for a new user.
  • Select SQL Server authentication.
  • In the Password field, type a password for the user.
  • In the left-hand panel, click Server Roles and enable 'sysadmin'

Create an ODBC Connection

SQL Native Client


Name: RF64 

Server: Choose the "Sage" instance of SQL.

Then use SQL Server Authentication 

Enter the Sage user and password

Then use the default database

Click Next and then test.


NEXT, you will get into the customers SQL Management studio and run the scripts located in

After everything is installed you will run Warehouse 100 to create a Header record and verify that everything works. If Warehouse 100 displays ERROR PopulateLogic  Unable to add Header Record then you did not apply the scripts to the correct database or possibly not at all, or the customer copied a company over the company that is being used on the scanner.


CUSTOMER record in portal.

  2. SEARCH for the customer before you create a new record. If the customer already exists, use that record. If the customer does not exist...
  3. Create a new customer in the portal.............................................................
  4. Enter the correct number of licenses and enabled ONLY the applications the install ticket says to enable. If your ticket does not include the detail, do only enable Standard and tell you did not have the details about what the customer purchased. These are buttons you can press to enable the correct applications.

Install the ConnectIt Service AS ADMIN

  • Server Setup Port 50000

    • "Sage 100" for ProvideX based [Standard or Advanced] 

    • "Sage 100 SQL" for  SQL based [Premium]

  • Customer "Code" from the portal. Example:
  • Connection String should be correct by default “DSN=RF64”
  • Login Info: Sage User and PASSWORD.
  • Next
  • Finish

OPEN REMOTE CONNECTIT on the customer's server.

and press the Chrome button.

I suggest you press Yes.

Enter the company they will use on the scanners. Run this process multiple times if they need multiple companies.

I suggest you press Yes.

When you see the text shown in the red box below you know the portal is being updated.

Profile first, then Users

now, in the portal, enable the companies and warehouse.

Create a profile.

Create users.


Get the client for what the customer bought  from

Unzip and run the exe.

Go into the portal > Devices tab and mark the client as Exempt (Scanco Use)

Log in to the client and at a minimum, test an item lookup.

NOTES and files on the customer system.

I always create a "Scanco" folder on the desktop and put every installer, file, notes in a notepad file, shortcuts, etc... into that folder. 



Knowledgebase article for Remote ConnectIt

If you have issues with clients talking to ConnectIt you are required to run Remote ConnectIt and review the logs. You should be able to see the issue and possibly solve it by checking all the steps above. If you have to report the issue to the product owner, you have to include the logging in your bug report and the answers to the questions below.

These details are required

What App?: WMS100, SalesApp, MFG100, DashPrint, DashBoard, Mobility.

What Company is being used on the device?

What User is logging in?  Password will be required if we need to duplicate the issue under that user.

What Program on device or Tab\View on the dash?: Shipping, Receiving by ORDER, etc...

What steps are you doing?: Batch#, SO#, Item, Bin, Qty then issue occurs. Include the details if you report an issue so the issue can be duplicated.

Can you duplicate the issue at will? If not, then it is probably a data issue so get data that does work and data that does not work.

Have you checked and documented the Debug and Error log?

NON-ISSUES can occur and be explained.

There are many times customers report issues because they have data in tables that should or should not be there.


1. should be there: Data collected on a scanner but not sent through the Barcode Import. 

Actual data from a customer system: The IM table shows 67 available and the Scanner data table shows 413 collected. 67-413 equals -346

2. should not be there: Allocations exist in many tables and sometimes the data is not correct. Example: SO#1 is allocated but SO#1 does not exist. The scanners read the allocations and subtract that quantity from the quantity available and that is completely correct. The data tables that contain invalid allocations must be corrected before the scanners will allow an item that is unavailable due to inaccurate allocations.


This article is not for customers.

Author: Keith R. Cseak