Back to

EverServ (iSiva) POS: Installation Guide


Technical Teams, Account Teams, and Client's POS programmer   

Description of issue:

Olo is not installed on the EverServ computer and we would like to get Olo integrated with EverServ.


This document outlines the process for installing the OLO EverServ Siva Integration Service onto a computer.

System Requirements

  • Windows XP or higher (although Windows 2000 should work it is no longer supported by Microsoft and is not recommended)
  • Microsoft .NET Framework 2.0
  • POS Firewall Requirements:

POS Firewall Requirements

If your store networks allow all outgoing traffic by default, there is no need to read further. This only applies if you deny outgoing traffic by default.

The store computer needs to be able to make DNS lookups and outbound HTTPS and TCP connections to Olo’s servers. (Olo’s agent does not require any incoming firewall rules. Network connections are always initiated from inside the store network.)

Olo’s in-store software agent requires TCP ports 443 and 9292 to be open for egress traffic. Additionally the Olo Dashboard requires browser access on port 443.

If you still use Windows XP at any stores, you will additionally need to ensure access to (or its 9 assigned IP addresses, if your firewall does not support FQDN rules.)

All POS-integrated stores require access to on port 443 and - on port 9292. The new IP addresses for these are provided in the table below.



TCP Port

New IP Addresses

POS Connectivity







POS Connectivity
(additional endpoint needed for Windows XP/2003 only)


Olo Dashboard

(if used in-store)



  • OLO EverServ Integration Service installer (OLOEverServService_live_v3.0.0.971.msi)
  • Vendor-specific OLO username and password for use during the installation process 

Installation Procedure (basic store install)

Step 1: Confirm store is “Offline” on the Olo Dashboard

The purpose of this step is mainly to confirm that you have dashboard permission to view the store, and since the store will connect automatically and disappear from the “Offline” list, it is a nice way to confirm that your installation has succeeded.

Log into the Olo Dashboard at and click “See Offline Vendors” button. The store will be listed below.

Step 2: Generate the POS Password

Since it takes 2 minutes or so for the password to register with the POS connection servers, it makes sense to generate it for the store before running the installation tool.  

Tip: If you forget to generate the password upfront and instead generate it right before entering it into the installation tool, you may see an “Invalid Username or Password” error. Simply wait a few minutes for the newly generated password to register and then try it again.  

From the Offline list click on the store’s name to go to the Settings page for the location. Click on POS Settings link.

Click on “Generate a New Password” button.  Confirm the warning dialog and a password will be generated. Mouse-over the box to see the password for the username listed above the warning message. Keep this page open as you move to the store computer for installation. 

Step 3: Download the Installer from the Olo Dashboard

  1. Go to Brand section on the left control list

  2. Select POS Downloads


  3. Select PAR EverServ (for iSiva)

      4. Click the button to download the most current version of the Olo EverServ Agent

      5.  Run the installer after downloading

 Step 4: Follow the Instructions in the Install Wizard

  1. Click Next to begin the process.
  2. Click Next for the destination folder.
  3. Enter the Olo username and password (the one generated on the Olo Dashboard in Settings).
  4. Click Install and then Finish when it is done.

Important Tip (!): You will have to start the installation over if the values entered here are incorrect. Be sure to double-check these entries to be sure you get them right the first time!


If any problems are encountered after the installation, e.g. a test order placed to the store fails, take the following steps:


Confirm that the services are running

  1. Open a run box by keying [Win]+R (or the [Start] button, then Run...)
  2. Type services.msc and click [Enter]. This opens the Windows Services list.
  3. Verify that the two OLO services named OLO EverServ Service and OLO Update Service are in the list with status Started.


If they aren’t, right-click each and select Start from the context menu.

If test orders continue to fail, proceed to the next step.

Run the Olo EverServ Tester

This is a small utility that runs some tests against the system to make sure everything is configured properly.

Once the services are stopped, run the Olo EverServ Tester located at:

C:\Program Files\OLO\OLO EverServ Integration Service 1.0\Run OLO EverServ test.bat

A command window will either display a fail message and an exception, or state that the system test passed. 

If the test fails, examine the exception. In this scenario, it is most likely to be a POS configuration error related to, for example, the way the Web Employee is set up, or Start of Day having not been run.

If the system test passes, and the Integration Service continues to throw errors when placing test orders, the next step is to check the logs for anything unusual. 

Check the logs for errors

The services’ log files are located at:

C:\Program Files\OLO\OLO EverServ Integration Service 1.0\Logs\

There are two log files, one for the Integration Service itself, and one for the Update Service which handles upgrading the Integration Service when new versions become available. Most often, the Integration Service log is the one that will be most useful. The Integration Service log is formatted:


While the Update Service log is formatted:


Open the Integration Service log with the correct date (today’s date) and look for exceptions - doing a text search (CTRL + F) for the actual term “exception” is a good strategy.  The general rule of thumb is that if the exception came from the POS, it will be formatted:

TWebTransSrv: <Exception Message>

An example POS exception message is: 

TWebTransSrv: Invalid Open Date - the system is off hours

These are errors that occur at the POS level itself, and generally indicate some kind of misconfiguration. An example of a non-POS-generated error looks like this:

System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

This particular error indicates that the Update Service can’t connect to the internet, which is usually indicative of a network problem at the store location. 

It isn’t possible to list every scenario, but generally the error message will offer some clue as to where the problem lies. The main candidates are POS itself, the internet connection, and the Integration Service. Other less common environmental configuration issues may also present themselves, but should be made clear by the specific error message from the log.




Didn't find what you need?

Submit a request to our Help Team and someone will
get back to you shortly.

Submit a request

Copyright © 2019 Olo. All rights are reserved.