TopView FAQs

Email notifications

Notification messages sometimes display unexpected line breaks. This is usually due to an Outlook setting with a default behavior that many find unusual.

Issue

Outlook removes line breaks, by default, from plain-text email messages. From Microsoft’s support article on line break display in plain-text emails:

By default, the Auto Remove Line Breaks feature in Outlook is enabled. This causes the line breaks to be removed. Any two or more successive line breaks are not removed.

Solution

The article suggests two solutions:

  1. Disable the feature that removes extra line breaks
  2. Use HTML or Rich Text format

See the Outlook support base article for more details.

The following information provides details on using Gmail with TopView for both outgoing email (Notification) and incoming email (Alarm Acknowledge and information requests).

These details apply to TopView 6.9 and later which supports SSL for both outgoing and incoming email.

Google offers free Gmail accounts. They include the use of Gmail’s outgoing (SMTP) and incoming (POP) mail servers. TopView can use these 2 mail server to send and receive email. Note: a free Gmail account has a limit of 500 outgoing emails per day (24 hour period).

Signing up for Google Apps Premier allows significantly more per day.

In order to use Gmail’s mail servers from TopView, the TopView computer must have access to the Internet (gmail.com) and the SMTP and POP ports mentioned below must not be blocked.

Create a Gmail account (ex: xxx @gmail.com with password yyy)

Log into your Gmail account and enable POP (if you want to use incoming email in TopView – this is not required for email notification)

Settings

– Forwarding and POP/IMAPn

– POP Download…Enable for all mail

– SAVE

You may need to adjust Gmail’s setting to allow access for “less secure apps”.

TopView Configurator Email Notification Settings screen

Outgoing email

SMTP Server: smtp.gmail.com:587
This specifies a non-default port 587, although the default 25 usually works

  • [X] Secure connection SSL
  • [X] Use SMTP Authentication
  • User: xxx @gmail.com
  • Password: yyy
  • From: xxx @gmail.com (will be used regardless of what you put in this field)
  • [Send test email] to another email account to verify outgoing email settings
Incoming email settings (optional)
  • [X] Enable “Reply-to-email” Acknowledge
    AND/OR
  • [X] Enable “TopView Information Request”
  • POP3 Server: pop.gmail.com:995
    This specifies a non-default port 995
  • Username: xxx @gmail.com
  • Password: yyy
  • Authentication: Auto
  • [X] Secure Connection, Implicit
  • Check the mailbox and wait: 20 seconds (or desired check interval for processing incoming email)
  • [Test] to verify POP settings

Installation

Background

On newer Windows OS’s, the current user may not be allowed to install/start/stop services.  This may prevent the user from installing/starting/stopping TopView Engine Services.

The solution has been to run the Configurator “as Administrator” (right-click, “Run as Administrator”) and then perform the service install/start/stop.

Issue

User of the TopView Configurator cannot stop/start a TopView Engine Service and must close the Configurator and re-open “as Administrator” to get permission.

Example: error when trying to start a service (TopView configuration name is exampleconfig):

Desired solution: give the user permission to start/stop a TopView Engine Service

Solution

  • Install the TopView Engine Service by running the Configurator “as Administrator”
  • Close the Configurator
  • Download and install Microsoft tool SubInACL
  • Launch a command prompt “as Administrator”
  • Go to folder “C:\Program Files (x86)\Windows Resource Kits\Tools”:
    • cd \Program Files (x86)\Windows Resource Kits\Tools\
  • From the command prompt run: subinacl.exe /service servicename /grant=username=F
    where servicename is the name of the service and username is the name of the user (local user account)

    • Example: grant local user “abc” permission to start/stop TopView Engine Service for configuration named “exampleconfig”
      subinacl.exe /service topview_exampleconfig /grant=abc=F
  • If the command succeeds the user should now be able to start/stop service. If there are problems have the user log off/on and try again.

Permissions

“F” = Full control. If you want to set specific permissions you can add one or more of the following permissions:

  • F : Full Control
  • R : Generic Read
  • W : Generic Write
  • X : Generic eXecute
  • L : Read control
  • Q : Query Service Configuration
  • S : Query Service Status
  • E : Enumerate Dependent Services
  • C : Service Change Configuration
  • T : Start Service
  • O : Stop Service
  • P : Pause/Continue Service
  • I : Interrogate Service
  • U : Service User-Defined Control Commands

Due to Windows permissions, you may see an error message after attempting to run the setup application saying: “Error reading setup initialization file”.

To install TopView, right click on the setup application and select “Run As Administrator”.

As of TopView version 6.28, this is no longer an issue as the setup installer will automatically elevate its process.

Categories: Installation, TopView

During the TopView installation, the user selects a location for the TopView DataPath. The TopView DataPath is a folder (and sub-folders) where the users of TopView have read/write permission.

The DataPath stores configuration information, logs, audit trail, and possibly reports.

In some cases, the user may want to move the location of DataPath and preserve the information that already exists in DataPath. Reasons may include:

  • IT required changes to selected location
  • Desire to move DataPath to a file server in order to share the DataPath between a primary and fail-over TopView computer.

Steps for moving DataPath from folder DP1 to DP2

To view the current DataPath (DP1), select Start > Programs > Exele TopView > More > Open DataPath folder.

1. Copy all data files to the new location

  • Stop all TopView Engine instances and TopView applications
  • Copy all files and subfolders from DP1 to DP2

2. Change the data path in TopView’s configuration file

  • Select Start -> Run
  • Enter “%windir%\TopView.ini
    Notepad should open and display the contents of the file TopView.ini
  • TopView.ini should contain a setting in the [Environment] section for current DataPath (DP1)Example:
    DataPath=C:\ProgramData\Exele\TopView
  • Change this entry to point to DP2.

    Instead of deleting the current setting (DP1), add “#” to the start of the line to comment this setting, then add a new line for DP2.Example (comment DP1, add DP2):

    #DataPath=C:\ProgramData\Exele\TopView
    DataPath=C:\AllAppData\TopView

3. Update any settings that may still point to the previous data path

  • Run the TopView Configurator
  • Select “Configuration files” from the left menu
    • The “Current storage location” may show DP1\Config which is the old location. Click the [Set to default] button to change this to DP2\Config
  • For each configuration file, open it in the Configurator:
    • If you have any HTML Snapshot Reports that save the report to a subfolder of DP1, change the report settings to write the report to DP2
    • If you have any Scheduled Alarm Reports that save the report to a subfolder of DP1, change the report settings to write the report to DP2
    • If you have any RSS Feeds that save the RSS feed file to a subfolder of DP1, change the RSS Feed settings to write the report to DP2
    • If you are running this configuration as a TopView Service:
      • Select “Services” from the left menu.
      • Verify that the Service settings are correct (Startup type, LogOn account) and click [Re-install].
      • Verify that the configuration file listed for the Service is the one located in DP2
      • Modify any desktop or start menu shortcuts that you may have created to launch the TopView engine. The launch string contains the location of the TopView configuration file (it should be changed to the DP2 location)
      • Backup DP1 and remove the folder to prevent accidental usage of DP1
      • Restart the TopView Engine(s) interactively or as Services based on how you have been running TopView before the move.
Categories: Installation, TopView

If you intend to upgrade to a new version of TopView in addition to moving to a new computer, we recommend going through this migration process first, then following the upgrade instructions. The instructions to upgrade a version of TopView are provided as a link on the download page for that version.

To move an existing TopView installation to a new computer:

  • Old machine: Locate the TopView DataPath on the old machine
    The location of the DataPath can be discovered by running the application from Start…Programs…Exele TopView…More…Open DataPath
    The default location for DataPath is C:\ProgramData\Exele\TopView\
  • New machine: Decide on a location for DataPath on the new machine and create the DataPath folder. If possible, create the same location as the old machine.
  • Both machines: Copy all DataPath files and folders from the old machine to the new machine
  • New machine: Install TopView on the new machine (install the same version of TopView as the old machine)
    During the installation you will be prompted for the location of DataPath. Select the DataPath folder that you created on the new machine.
  • New machine: run the Configurator.
    • Open each configuration file and visually check the settings – alarm limits, email settings, etc – to make sure things look correct.
    • Test any notification settings to verify that the new computer can send notification.
    • Install any TopView Services on the new machine to match what was installed on the old machine.
    • If you are outputting TopView Performance Counters (available in v6.7 and later):
      • Click [Health] in the Configuration Settings section of the left menu
      • Under Performance Counters, click [Verify]
    • If you are using SQL Server for TopView outputs (alarm logging, Snapshot Output, …):
      • Click [Edit Global Options] in the Global Settings section of the left menu and select SQL Server screen.
      • Click [Connect and Verify Database] to verify connection to SQL Server
Categories: Installation, TopView

OPC

A common problem with TopView OPC is that the application works find when run interactively, but cannot connect to remote OPC Server(s) when you run TopView as a Service.

Interactive applications (non-Service) run under the account of the logged in user, services run under the configured logon account for the Service. Ensure TopView is running under the expected user account, especially after launching TopView from an elevated Configurator application.

The task manager’s process details will show the user account under which a process is running. Look for TopView.exe or TVConfig.exe.

OPC Servers use DCOM for the remote connection and often grants or refuses incoming connections from TopView based on the user account. The solution is to configure DCOM to allow connections from the TopView Service Logon account. Please see the following page for DCOM configuration information.

Categories: OPC, TopView

Note: the information below also exists as a PDF with screenshot images.

Background

If you install TopView OPC/SCADA on a Wonderware machine after installing the Wonderware OPC Server software, you may not be able to query to local OPC Servers (OPCENUM). The error returned is  0x80040153

This issue is known by Wonderware and can be caused by the installation of any OPC software, not just TopView.

Here is some information from Wonderware on this issue:

  1. http://esupport.wonderware.ch/Data/ReadMeIAS35.html
    L00115135:          In the OPCClient object, the installed DAServers are not listed under the Server Name. For the OPCClient object, the following error message is shown in the SMC log:
    .Net Editor Info – 17:35:14.3125809
    Failed to create instance of OPCEnum on server node COMPST01: 0x80040153
    As a workaround, if you invert the installation sequence by installing the OPC Server first and then the Bootstrap, the OPCEnum is installed without anonymous logon and a remote connection to the OPC Server is possible. You can also resolve this issue by deleting and creating the anonymous logon on the OPCEnum permission.
  2. https://wonderwarepacwest.com/uploads/2014/01/ReadMe.html
    FS Gateway 3.0 SP1 Readme Information: Known issues
    L00115135:          After installing a third-party OPC server on top of an already installed DAServer, OPC clients may not be able to browse for OPC servers using OPCEnum, and the client receives error 0x80040153. As a workaround, install the DAServer last.

Workaround/Fix

The first item referenced above from Wonderware states “You can also resolve this issue by deleting and creating the anonymous logon on the OPCEnum permission”.

This workaround does fix the issue. Here are the detailed steps for fixing the error by removing and adding Anonymous logon.

Remove/Add Anonymous Logon

On the Wonderware/TopView computer:

  • Run DCOMCNFG (Start…Run…DCOMCNFG)
  • Go to Component Services…Computers…My Computer… DCOM Config
  • Under “DCOM Config” find OPCENUM
  • Right-click OpcEnum and click Properties
    • Security Tab
      • Launch and access permissions: Customize should be selected
      • Click [Edit] next to Customize
      • Anonymous Logon is listed with all permissions checked
      • Click [Remove] to remove  Anonymous Logon
      • Click [Add]
      • Under “Enter the object names to select” enter Anonymous Logon and click [OK]
      • Re-enable the Anonymous Logon permissions for local and remote activation and launch
      • Click [OK] until all dialogs are closed
      • Close DCOMCNFG

Restart OPCENUM Service

  • Run the Windows Services app (Control Panel…Admin tools…Services)
  • Find OPCENUM in the list of Services
  • If the OPCENUM Service is stopped, right-click and choose “Start”
  • If the OPCENUM Service is running, right-click and choose “Restart”

You should now be able to query the local OPC Servers from TopView.

Categories: OPC, TopView

Service

Background

On newer Windows OS’s, the current user may not be allowed to install/start/stop services.  This may prevent the user from installing/starting/stopping TopView Engine Services.

The solution has been to run the Configurator “as Administrator” (right-click, “Run as Administrator”) and then perform the service install/start/stop.

Issue

User of the TopView Configurator cannot stop/start a TopView Engine Service and must close the Configurator and re-open “as Administrator” to get permission.

Example: error when trying to start a service (TopView configuration name is exampleconfig):

Desired solution: give the user permission to start/stop a TopView Engine Service

Solution

  • Install the TopView Engine Service by running the Configurator “as Administrator”
  • Close the Configurator
  • Download and install Microsoft tool SubInACL
  • Launch a command prompt “as Administrator”
  • Go to folder “C:\Program Files (x86)\Windows Resource Kits\Tools”:
    • cd \Program Files (x86)\Windows Resource Kits\Tools\
  • From the command prompt run: subinacl.exe /service servicename /grant=username=F
    where servicename is the name of the service and username is the name of the user (local user account)

    • Example: grant local user “abc” permission to start/stop TopView Engine Service for configuration named “exampleconfig”
      subinacl.exe /service topview_exampleconfig /grant=abc=F
  • If the command succeeds the user should now be able to start/stop service. If there are problems have the user log off/on and try again.

Permissions

“F” = Full control. If you want to set specific permissions you can add one or more of the following permissions:

  • F : Full Control
  • R : Generic Read
  • W : Generic Write
  • X : Generic eXecute
  • L : Read control
  • Q : Query Service Configuration
  • S : Query Service Status
  • E : Enumerate Dependent Services
  • C : Service Change Configuration
  • T : Start Service
  • O : Stop Service
  • P : Pause/Continue Service
  • I : Interrogate Service
  • U : Service User-Defined Control Commands

The TopView Service Manager command line application is a utility which provides the ability to list, install, and remove TopView services.

This is a particularly useful tool when changing the user account for each TopView service is necessary.

The utility’s help information can be displayed by executing the application with no arguments:

TVServiceMgr.exe

Example PowerShell scripts

These scripts are provided as is, with no guarantee of correct behavior, please verify that these will work for your system before executing them.

Assumptions:

1. These scripts are run with proper access (e.g. PS is running as Administrator)
2. The working directory is the TopView Program Path
3. “C:\ProgramData\Exele\TopView\CONFIG\” is the data path

The following script will remove existing TopView services:

.\TVServiceMgr.exe list | ForEach-Object { & .\TVServiceMgr.exe "remove $_" }

The following script will install all the services in the data path’s CONFIG folder:

Get-ChildItem C:\ProgramData\Exele\TopView\CONFIG\ -Filter *.cfg | Select-Object -ExpandProperty FullName | ForEach-Object { & tvservicemgr.exe "install --cfg=""$_""" }
Categories: Service, TopView

SMS

If TopView does not appear to receive text messages through a networked cellular modem, it may be because the SIM card does not have memory for message storage. This may occur in systems with the following characteristics:

  • TopView is using the MultiTech rCell 100 modem, connected via ethernet
  • Verizon is the carrier
  • No messages sent to the SIM’s number appear in the inbox in the modem’s administration site

This can occur because some Verizon SIM cards issued since Q1 2017 do not allow storage of messages to the SIM card.

To remedy this issue, you will need a SIM card that allows the storage of incoming messages. A new card can be ordered from Verizon. More information about this issue is available from MultiTech.

Categories: SMS, TopView

When sending TopView notifications via a carrier’s email-to-text gateway, you may see notifications come from many different numbers. In general, TopView has no control over numbers used by carriers to send text messages when sending messages through the carrier’s email-to-text gateway.

If AT&T is your carrier, using the email address “[number]@mms.att.net”, instead of the typical text gateway address (“[number]@txt.att.net”), will send from a consistent address.

See this post on AT&T’s forum for more information.

Categories: SMS, TopView

This issue happens under the following circumstances:

  • TopView version 6.29
  • MultiTech rCell 100 with firmware version 4.0.5
  • Multiple TopView engines, under different IP addresses, are sending SMS notifications through the same network modem

Explanation of the issue

The rCell 100 modem requires a logged in account to send text messages over the network and prevents log ins from another IP address while the modem is already in use by the same user. TopView can detect this behavior and forcibly log out the user from another IP address after some time.

TopView’s mechanism to log out the user from another IP address no longer works in version 4.0.5 of the rCell 100 firmware.

This issue surfaces as multiple “user is logged in from another ip address” errors followed by a failed attempt to log out a user. The log out attempt fails with an error message similar to the following:

[Timestamp]: WARN - GET:logout responded with "user [admin] has a higher permission level" (Status code: 401)

Workaround

Using the rCell modem’s administration web app, add one user account for each TopView engine that will be sending text notifications. Set each of these accounts to use the “administrator” role.

Then update each TopView configuration to use these new user accounts.

Long-term solutions

TopView 6.30 will be able to log out the user from another IP address using rCell firmware version 4.0.5.

Categories: SMS, TopView

TopView

Background

On newer Windows OS’s, the current user may not be allowed to install/start/stop services.  This may prevent the user from installing/starting/stopping TopView Engine Services.

The solution has been to run the Configurator “as Administrator” (right-click, “Run as Administrator”) and then perform the service install/start/stop.

Issue

User of the TopView Configurator cannot stop/start a TopView Engine Service and must close the Configurator and re-open “as Administrator” to get permission.

Example: error when trying to start a service (TopView configuration name is exampleconfig):

Desired solution: give the user permission to start/stop a TopView Engine Service

Solution

  • Install the TopView Engine Service by running the Configurator “as Administrator”
  • Close the Configurator
  • Download and install Microsoft tool SubInACL
  • Launch a command prompt “as Administrator”
  • Go to folder “C:\Program Files (x86)\Windows Resource Kits\Tools”:
    • cd \Program Files (x86)\Windows Resource Kits\Tools\
  • From the command prompt run: subinacl.exe /service servicename /grant=username=F
    where servicename is the name of the service and username is the name of the user (local user account)

    • Example: grant local user “abc” permission to start/stop TopView Engine Service for configuration named “exampleconfig”
      subinacl.exe /service topview_exampleconfig /grant=abc=F
  • If the command succeeds the user should now be able to start/stop service. If there are problems have the user log off/on and try again.

Permissions

“F” = Full control. If you want to set specific permissions you can add one or more of the following permissions:

  • F : Full Control
  • R : Generic Read
  • W : Generic Write
  • X : Generic eXecute
  • L : Read control
  • Q : Query Service Configuration
  • S : Query Service Status
  • E : Enumerate Dependent Services
  • C : Service Change Configuration
  • T : Start Service
  • O : Stop Service
  • P : Pause/Continue Service
  • I : Interrogate Service
  • U : Service User-Defined Control Commands

TopView provides a command line tool called the “TopView Service Manager” (tvservicemgr.exe) to query and manipulate the settings for TopView services. This is useful when you want to list, remove, or install services with common settings for each service. Using this tool, bulk editing is possible through the command line, scripts (batch, PowerShell, et al.), or external applications.

Our documentation explains it well (search for “TopView Engine Service Manager” in the documentation for more):

The TopView Service Manager provides another method for managing TopView Engine Services. This command-line tool allows the user to:

  • List the installed TopView Engine Services
  • Remove a TopView Engine Service
  • Install a TopView Engine Service

The TopView Service Manager can be used to perform bulk operations on TopView Engine Services when doing the same tasks from the Configurator would be possible but tedious.

Category: TopView

The TopView license includes a licensed number of data servers. For TopView PI, a data server is a PI Server.

Starting with TopView PI version 6.26, TopView PI supports accessing both PI tags and AF attributes.
Accessing the same PI Server through both a PI tag and AF attribute (PI tag reference attribute) is counted as 2 data servers. Here are the details:

A license for TopView PI allows the user to monitor PI tags and AF attributes using the PISDK and/or AFSDK.

  • Monitored PI tags: each monitored PI tag has an associated PI Server. TopView will count each unique PI Server of the monitored PI tags as one data server.
  • Monitored AF Attributes: each monitored AF attribute has an associated AF Server. If the AF attribute is a PI tag data reference, TopView will count each unique AF Server\PI Server of the monitored attributes as one data server.

Running engines display both connected servers as well as servers that count against the license. These can be viewed in the TopView Admin Tools application on the Overview screen.

Example

TopView is monitoring the following PI tags and AF attributes:

  1. PI tag ‘tag001’ on PI Server “piserver01’
  2. PI tag ‘tag002’ on PI Server “piserver01’
  3. PI tag ‘tag003’ on PI Server “piserver02’
  4. Attribute ‘\\afserver1\database1\element\att1’ with no data reference
  5. Attribute ‘\\afserver1\database1\element\att2’ with data reference to PI tag ‘tag004’ on ‘piserver01’
  6. Attribute ‘\\afserver1\database1\element\att3’ with data reference to PI tag ‘tag005’ on ‘piserver01’

Example Data Server count = 3:

  1. piserver01: accessed by PI tags (tag001, tag002)
  2. piserver02: accessed by PI tags (tag003)
  3. afserver1\piserver01: accessed by AF attributes with PI tag data references (att2, att3)
Category: TopView

Remote Viewer connection issues are often due to an engine being stuck in startup, or due to firewall issues. To diagnose the connection issue:

  1. Verify TopView is configured to allow Remote Viewer connections
  2. Verify the TopView Engine is running and fully started
  3. Verify the TopView Engine is listening for remote connections on the assigned port

Is TopView configured for Remote Access

Remote Viewer access can be enabled in the Remote Viewer & Dial-in section of the TopView Configurator application:

Find Remote Access in the left sidebar of the TopView Configurator application

Is the TopView Engine running and fully started?

The Admin Tools application is the best way to check the status of running TopView engines. Launch the Admin Tools application, then select the TopView Engine you wish to check at the top.

If the engine you are trying to connect to is not listed, then it is not running. Launch the engine, then try to connect from the Remote Viewer again.

If the engine is running, verify that it is not in “Startup” mode:

  • Click the “Overview Summary” link in the left sidebar
  • Check the “Operating State” field in the “Operating state and system information” grouping

The “Operating state” should be “Running”, not “Startup”.

  • If “Operating State” is not running (e.g. “Startup”), this is the issue. The engine does not listen for remote viewer connections until it is running.
  • If “Operating State” is “Running”, check the application log for errors listening on this port and address them

Is the TopView Engine listening for remote connections?

In Admin Tools, click the “Remote Viewer Connections” link in the left menu. “Listening” must be True on the “Selected TopView Configuration” tab.

If Listening is “True” and Remote Viewer connections do not work, the cause is probably a firewall blocking communications. The firewall could be on the TopView server or client-side. Ensure communication over the specified port is allowed on both systems.

If Listening is “False”, then you may not have a running and fully started TopView engine. Check the overview screen’s operating state, as described above, and check the application logs for errors that may be preventing the TopView engine from starting up.

Category: TopView

Yes, the format set for a value in TopView sets both the value used for display and the value used for comparison against the alarm conditions set for the row.

For example: a TopView row monitoring a float tag has a format for a whole number (i.e. “0”), if the row’s value is “120.056”, TopView will use the value “120” for comparison against the row’s alarm conditions.

Row formats are also be applied to any tags used as limit condition values.

Category: TopView

Yes! TopView 6.4 and later will run on Windows 64-bit operating systems.

Category: TopView

Due to Windows permissions, you may see an error message after attempting to run the setup application saying: “Error reading setup initialization file”.

To install TopView, right click on the setup application and select “Run As Administrator”.

As of TopView version 6.28, this is no longer an issue as the setup installer will automatically elevate its process.

Categories: Installation, TopView

The TopView Service Manager command line application is a utility which provides the ability to list, install, and remove TopView services.

This is a particularly useful tool when changing the user account for each TopView service is necessary.

The utility’s help information can be displayed by executing the application with no arguments:

TVServiceMgr.exe

Example PowerShell scripts

These scripts are provided as is, with no guarantee of correct behavior, please verify that these will work for your system before executing them.

Assumptions:

1. These scripts are run with proper access (e.g. PS is running as Administrator)
2. The working directory is the TopView Program Path
3. “C:\ProgramData\Exele\TopView\CONFIG\” is the data path

The following script will remove existing TopView services:

.\TVServiceMgr.exe list | ForEach-Object { & .\TVServiceMgr.exe "remove $_" }

The following script will install all the services in the data path’s CONFIG folder:

Get-ChildItem C:\ProgramData\Exele\TopView\CONFIG\ -Filter *.cfg | Select-Object -ExpandProperty FullName | ForEach-Object { & tvservicemgr.exe "install --cfg=""$_""" }
Categories: Service, TopView

During the TopView installation, the user selects a location for the TopView DataPath. The TopView DataPath is a folder (and sub-folders) where the users of TopView have read/write permission.

The DataPath stores configuration information, logs, audit trail, and possibly reports.

In some cases, the user may want to move the location of DataPath and preserve the information that already exists in DataPath. Reasons may include:

  • IT required changes to selected location
  • Desire to move DataPath to a file server in order to share the DataPath between a primary and fail-over TopView computer.

Steps for moving DataPath from folder DP1 to DP2

To view the current DataPath (DP1), select Start > Programs > Exele TopView > More > Open DataPath folder.

1. Copy all data files to the new location

  • Stop all TopView Engine instances and TopView applications
  • Copy all files and subfolders from DP1 to DP2

2. Change the data path in TopView’s configuration file

  • Select Start -> Run
  • Enter “%windir%\TopView.ini
    Notepad should open and display the contents of the file TopView.ini
  • TopView.ini should contain a setting in the [Environment] section for current DataPath (DP1)Example:
    DataPath=C:\ProgramData\Exele\TopView
  • Change this entry to point to DP2.

    Instead of deleting the current setting (DP1), add “#” to the start of the line to comment this setting, then add a new line for DP2.Example (comment DP1, add DP2):

    #DataPath=C:\ProgramData\Exele\TopView
    DataPath=C:\AllAppData\TopView

3. Update any settings that may still point to the previous data path

  • Run the TopView Configurator
  • Select “Configuration files” from the left menu
    • The “Current storage location” may show DP1\Config which is the old location. Click the [Set to default] button to change this to DP2\Config
  • For each configuration file, open it in the Configurator:
    • If you have any HTML Snapshot Reports that save the report to a subfolder of DP1, change the report settings to write the report to DP2
    • If you have any Scheduled Alarm Reports that save the report to a subfolder of DP1, change the report settings to write the report to DP2
    • If you have any RSS Feeds that save the RSS feed file to a subfolder of DP1, change the RSS Feed settings to write the report to DP2
    • If you are running this configuration as a TopView Service:
      • Select “Services” from the left menu.
      • Verify that the Service settings are correct (Startup type, LogOn account) and click [Re-install].
      • Verify that the configuration file listed for the Service is the one located in DP2
      • Modify any desktop or start menu shortcuts that you may have created to launch the TopView engine. The launch string contains the location of the TopView configuration file (it should be changed to the DP2 location)
      • Backup DP1 and remove the folder to prevent accidental usage of DP1
      • Restart the TopView Engine(s) interactively or as Services based on how you have been running TopView before the move.
Categories: Installation, TopView

If you intend to upgrade to a new version of TopView in addition to moving to a new computer, we recommend going through this migration process first, then following the upgrade instructions. The instructions to upgrade a version of TopView are provided as a link on the download page for that version.

To move an existing TopView installation to a new computer:

  • Old machine: Locate the TopView DataPath on the old machine
    The location of the DataPath can be discovered by running the application from Start…Programs…Exele TopView…More…Open DataPath
    The default location for DataPath is C:\ProgramData\Exele\TopView\
  • New machine: Decide on a location for DataPath on the new machine and create the DataPath folder. If possible, create the same location as the old machine.
  • Both machines: Copy all DataPath files and folders from the old machine to the new machine
  • New machine: Install TopView on the new machine (install the same version of TopView as the old machine)
    During the installation you will be prompted for the location of DataPath. Select the DataPath folder that you created on the new machine.
  • New machine: run the Configurator.
    • Open each configuration file and visually check the settings – alarm limits, email settings, etc – to make sure things look correct.
    • Test any notification settings to verify that the new computer can send notification.
    • Install any TopView Services on the new machine to match what was installed on the old machine.
    • If you are outputting TopView Performance Counters (available in v6.7 and later):
      • Click [Health] in the Configuration Settings section of the left menu
      • Under Performance Counters, click [Verify]
    • If you are using SQL Server for TopView outputs (alarm logging, Snapshot Output, …):
      • Click [Edit Global Options] in the Global Settings section of the left menu and select SQL Server screen.
      • Click [Connect and Verify Database] to verify connection to SQL Server
Categories: Installation, TopView

Description

Launching the TopView Configurator with a user account that may not have write permissions shows the following warning:

TopView Configurator warning message:

This warning is the result of TopView detecting that it may not have write permissions to the TopView Data Path, where TopView’s configuration and data files are located. Insufficient access rights will cause the Configurator to behave in unexpected ways.

Solutions

There are a few ways to grant the TopView Configurator access to its data files:

Run TopView Configurator under the Administrator’s account

There are a few ways to run the Configurator as an Administrator:

  1. By elevating the Configurator application: as of TopView 6.28, there is a button at the bottom left of the Configurator to do this:
    Run elevated button in the bottom left of the TopView Configurator application
  2. Setting the option to launch the application as an elevated user every launch. As of TopView version 6.28, there is a global option in the “Global Options” screen => “Applications” tab that will always run TopView Configurator under the elevated account. Clicking the link after “Running elevated” will bring up the relevant global options screen:
    Highlighting the link label stating
  3. By setting the application shortcut’s launch properties to “Run As Administrator”

Modify the TopView Data Path’s permissions in Windows Explorer

Modify the Data Path folder’s permissions to allow any user full control of the files and folders. For more information, see this MSDN article on Windows Files and Folder Permissions.
To find the TopView Data Path, find “Exele TopView” in the Windows start menu, then click the link to “Open DataPath Folder”.

Move the TopView Data Path

Move the TopView Data Path to a folder that has the permissions level you want. Here are some instructions on how to do this.

Category: TopView

TopView can utilize a number of ports to perform its job, configure your firewall to allow communication over the following ports:

  • Data source related ports
  • Notification-related ports
    • Email: any ports used for SMTP (default 25, possibly 587) and POP (default 110) communication
    • Any ports specified for SNMP communication
  • Remote Viewer ports
    • By default, we suggest 6150, but you will need to open the Remote Viewer port in your firewall per TopView Engine.
  • Web application ports
    • The Mobile Web Application serves over a user-specified port, make sure this port is open in your firewall per TopView Engine.
Category: TopView

Method 1: Use multiple tag groups with tag group notifications

The simplest way to send different notification messages through different media is to use tag group notifications. Each tag group can have an associated tag group notification and message template.

For example, if you want to get one alarm message delivered to a voice notification group, and an HTML email delivered to an email notification group use:

  1. A tag group, “Email notification” for example, configured to deliver to an email notification group with an Into Alarm send message set to your HTML notification message template.
  2. A tag group, named “Voice notification” for example, set to deliver to a voice notification group with an Into alarm send message set to your voice notification message template.

Then include the relevant TopView row into both tag groups. When an alarm occurs for that row, TopView will notify each group using the specified message template.

Method 2: Notification Templates and Recipient Exclusions

To get different notification messages for different notification media, use a combination of Notification Message Templates and Recipient Exclusions.

From the documentation, when using a notification message with a recipient exclusion in it:

If a recipient is excluded, they will receive the alarm message as the notification message.

For example, if you want to get one alarm message delivered to a voice notification group, and an HTML email delivered to an email notification group use:

  1. An alarm message catered to the voice notification group
  2. A notification message template with the HTML to be delivered in an email
  3. A recipient exclusion of “” in the body of the notification message template. This will exclude recipients that are not email addresses, meaning recipients with phone numbers will be excluded.

There are a number of different recipient exclusions that can be used, please see the documentation for available Recipient Exclusions. The documentation also provides more detail about Notification Message Templates.

 

Category: TopView

If TopView does not appear to receive text messages through a networked cellular modem, it may be because the SIM card does not have memory for message storage. This may occur in systems with the following characteristics:

  • TopView is using the MultiTech rCell 100 modem, connected via ethernet
  • Verizon is the carrier
  • No messages sent to the SIM’s number appear in the inbox in the modem’s administration site

This can occur because some Verizon SIM cards issued since Q1 2017 do not allow storage of messages to the SIM card.

To remedy this issue, you will need a SIM card that allows the storage of incoming messages. A new card can be ordered from Verizon. More information about this issue is available from MultiTech.

Categories: SMS, TopView

Voices provided by the Windows OS have improved over the years since Windows XP and are good voices to use for TTS.

Other voices can be purchased from 3rd parties and provide quality speech at reasonable prices, as well as support for non-English languages.

You can also download and test SAPI5 voices from http://www.cepstral.com before your purchase them ($29 each)

Hear demo: https://www.cepstral.com/demo/
Download voice for trial: https://www.cepstral.com/downloads/

Category: TopView

When sending TopView notifications via a carrier’s email-to-text gateway, you may see notifications come from many different numbers. In general, TopView has no control over numbers used by carriers to send text messages when sending messages through the carrier’s email-to-text gateway.

If AT&T is your carrier, using the email address “[number]@mms.att.net”, instead of the typical text gateway address (“[number]@txt.att.net”), will send from a consistent address.

See this post on AT&T’s forum for more information.

Categories: SMS, TopView

A common problem with TopView OPC is that the application works find when run interactively, but cannot connect to remote OPC Server(s) when you run TopView as a Service.

Interactive applications (non-Service) run under the account of the logged in user, services run under the configured logon account for the Service. Ensure TopView is running under the expected user account, especially after launching TopView from an elevated Configurator application.

The task manager’s process details will show the user account under which a process is running. Look for TopView.exe or TVConfig.exe.

OPC Servers use DCOM for the remote connection and often grants or refuses incoming connections from TopView based on the user account. The solution is to configure DCOM to allow connections from the TopView Service Logon account. Please see the following page for DCOM configuration information.

Categories: OPC, TopView

This answer is also included in the documentation shipped with TopView.

How many TopView Services can I run?

When Microsoft Windows starts, it reserves various areas of memory for tracking its resources. One of these is the relatively unknown desktop heap. When a large number of processes are running, this heap may run out of memory.

This has implications on the number of TopView Services that can be started. A symptom of insufficient heap size is: You have a number of services already running, when you start the next one (TopView_X), it fails to start. If you stop one of the running TopView Services, you are able to start TopView_X without any errors.

Note that you are more likely to have memory heap issue on older Microsoft Operating Systems (2003/XP).

Modifying heap size

To modify heap settings, you must modify the Windows Registry.
To start the Windows registry editor, click Start > Run, and enter: regedt32.
We suggest that you research and understand the implications of making any registry changes.

See Microsoft’s support article on modifying heap size or use the following instructions.

The registry entries that you should modify are different based on the LogOn settings of your TopView Services. You must reboot after making these changes.

If you are TopView running as a specific user account

Registry entry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
Manager\Memory Management\

Key: SessionViewSize, DWORD
Recommended value: 48 (decimal)

If you are running TopView Services as LocalSystem

Registry entry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems\
Key: Windows, EXPAND_SZ

The default data for this registry value will look similar to the following (all on one line):

%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,3072,512 Windows=On SubSystemType=Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=Off MaxRequestThreads=16

Recommended value: set the third SharedSection value (512 in above example) to 1024.

Category: TopView

This issue happens under the following circumstances:

  • TopView version 6.29
  • MultiTech rCell 100 with firmware version 4.0.5
  • Multiple TopView engines, under different IP addresses, are sending SMS notifications through the same network modem

Explanation of the issue

The rCell 100 modem requires a logged in account to send text messages over the network and prevents log ins from another IP address while the modem is already in use by the same user. TopView can detect this behavior and forcibly log out the user from another IP address after some time.

TopView’s mechanism to log out the user from another IP address no longer works in version 4.0.5 of the rCell 100 firmware.

This issue surfaces as multiple “user is logged in from another ip address” errors followed by a failed attempt to log out a user. The log out attempt fails with an error message similar to the following:

[Timestamp]: WARN - GET:logout responded with "user [admin] has a higher permission level" (Status code: 401)

Workaround

Using the rCell modem’s administration web app, add one user account for each TopView engine that will be sending text notifications. Set each of these accounts to use the “administrator” role.

Then update each TopView configuration to use these new user accounts.

Long-term solutions

TopView 6.30 will be able to log out the user from another IP address using rCell firmware version 4.0.5.

Categories: SMS, TopView

Notification messages sometimes display unexpected line breaks. This is usually due to an Outlook setting with a default behavior that many find unusual.

Issue

Outlook removes line breaks, by default, from plain-text email messages. From Microsoft’s support article on line break display in plain-text emails:

By default, the Auto Remove Line Breaks feature in Outlook is enabled. This causes the line breaks to be removed. Any two or more successive line breaks are not removed.

Solution

The article suggests two solutions:

  1. Disable the feature that removes extra line breaks
  2. Use HTML or Rich Text format

See the Outlook support base article for more details.

The following information provides details on using Gmail with TopView for both outgoing email (Notification) and incoming email (Alarm Acknowledge and information requests).

These details apply to TopView 6.9 and later which supports SSL for both outgoing and incoming email.

Google offers free Gmail accounts. They include the use of Gmail’s outgoing (SMTP) and incoming (POP) mail servers. TopView can use these 2 mail server to send and receive email. Note: a free Gmail account has a limit of 500 outgoing emails per day (24 hour period).

Signing up for Google Apps Premier allows significantly more per day.

In order to use Gmail’s mail servers from TopView, the TopView computer must have access to the Internet (gmail.com) and the SMTP and POP ports mentioned below must not be blocked.

Create a Gmail account (ex: xxx @gmail.com with password yyy)

Log into your Gmail account and enable POP (if you want to use incoming email in TopView – this is not required for email notification)

Settings

– Forwarding and POP/IMAPn

– POP Download…Enable for all mail

– SAVE

You may need to adjust Gmail’s setting to allow access for “less secure apps”.

TopView Configurator Email Notification Settings screen

Outgoing email

SMTP Server: smtp.gmail.com:587
This specifies a non-default port 587, although the default 25 usually works

  • [X] Secure connection SSL
  • [X] Use SMTP Authentication
  • User: xxx @gmail.com
  • Password: yyy
  • From: xxx @gmail.com (will be used regardless of what you put in this field)
  • [Send test email] to another email account to verify outgoing email settings
Incoming email settings (optional)
  • [X] Enable “Reply-to-email” Acknowledge
    AND/OR
  • [X] Enable “TopView Information Request”
  • POP3 Server: pop.gmail.com:995
    This specifies a non-default port 995
  • Username: xxx @gmail.com
  • Password: yyy
  • Authentication: Auto
  • [X] Secure Connection, Implicit
  • Check the mailbox and wait: 20 seconds (or desired check interval for processing incoming email)
  • [Test] to verify POP settings

As of TopView 6.25, we officially dropped support for voice notifications using TAPI modems. It is possible to continue using TopView to make voice notification calls via TAPI modem, but due to the dwindling hardware and OS-level support for these devices we can no longer offer full support of this notification method.

We recommend using VOIP over TAPI notifications due to the ease of setup and dramatic difference in reliability between the two. See TopView’s VOIP Notification page for more information on voice notification via VOIP, including making VOIP calls over an analog phone line.

TopView can send Voice Notification alarm messages over a phone line using a TAPI modem or via the network using VOIP. Alarm messages are converted to speech and spoken over the connection.

During voice notifications, the recipient can optionally acknowledge the alarm using the keypad on their phone.

Please check our modems page for the best performing modems we’ve found.

If test voice notifications via VOIP are experiencing difficulties, we recommend the following tests and procedures:

  • Verify that the authorization name and password are correct for the SIP server
  • Can a softphone installed on the same computer as TopView connect to the SIP server? Can it also make and receive calls from the VOIP system? One softphone you can use is the 3CX Phone 6 for Windows (use this one over newer versions, which restrict access to only 3CX servers).
  • Is it possible the firewall is blocking SIP calls? Test your computer’s firewall settings with the 3CX Firewall Checker client application.
    • Run the RemoteConnectionTest and verify that the registration test passes.
  • Make sure you’re running the most recent version of TopView available, along with any patches for that version.

We have a few general posts on TopView’s use of VOIP for voice notifications:

(TAPI for voice call-out is no longer officially supported by Exele, we recommend using VOIP instead)

The Way2Call Hi-Phone TAPI device can be used for TopView Voice Notification.

If you are installing this device, please read our installation instructions and tips page. See our recommended modems page, as well, for more information.

The TopView Application log may show the following error message:

Web server open error: HTTP could not register URL http://+:7170/. Your process does not have access rights to this namespace.

Background

The TopView Mobile Web App communicates to TopView’s embedded Web Server, which is built upon Windows HTTP Server API (AKA Http.Sys). When the user enables the Mobile Web App, they select the listen port for the web server (7170 in the above sample error message).

When the TopView Engine starts, it opens a listener on the configured web server port. If the user account of the TopView Engine (i.e. the logged in user if run interactively, or the Service LogOn account if run as a service) does not have permission to open the listen port for the web server, the above error occurs.

Fix

On Vista and later operating systems (Windows 7, Windows Server 2008, …), follow these steps:

  1. Launch a command prompt as Administrator or elevated privilege
  2. Enter the following command:
    netsh http add urlacl url=http://+:{port number}/ user={user account name}

    …replacing {port number} with the web server port, and {user account name} with the user.

    Example:

    netsh http add urlacl url=http://+:7170/ user=DOMAIN\user

Resources and more information

The command for registering a port for a user account is described in Microsoft’s Preregister URL prefixes and configure SSL section of its Http.Sys article.

For earlier operating systems and for more details about this issue, see the similar section on Configuring Namespace Reservations in Microsoft’s Configuring HTTP and HTTPS article.

Category: TopView

For many years TopView has supported voice call-out notification over traditional phone lines but, due to both hardware and software developments, voice notification via TAPI modems is much less reliable than it used to be (see the reliability section below for an explanation).

With TopView VOIP notification you can perform the same functions over your network without voice modems or TAPI devices.

Requirements

TopView VOIP notification requires a VOIP service that provides a SIP server and a network connection to that SIP server.

VOIP service options

A SIP server can be provided by:

Costs range from option to option, so investigate each option to see which one best fits your business’s requirements on functionality and cost.

Why is notification via TAPI less reliable?

TAPI notification is less reliable because the software systems are less reliable, on multiple levels:

  • Soon after its release, Windows 10 experienced TAPI issues for a year before they were fixed
  • TAPI hardware drivers may be highly dependent upon Windows versions and updates
  • Using USB devices on VMs can be problematic

We find that the time spent setting up, testing, and supporting TAPI hardware and software through its issues is far more expensive than VOIP.

If TopView detects that a notification template is missing, TopView will use the alarm message settings for notification.

An error will also be written to the Application logs. You can view these logs in the TopView Admin Tools application.

Category: TopView

TopView supports many different kinds of modems for different kinds of notifications.

The best resource for current recommendations is our recommended modems page.

Configuration settings and Global settings

Global and configuration-specific settings, edited in the TopView Configurator application, determine the behavior of a running TopView Engine. By default, the running Engine automatically applies global settings and does not automatically apply configuration-based settings.

Global items include:

  • Global Notification Groups
    Note: the Default Email, Modem, and Voice Groups are stored as part of the configuration file.
  • Schedules
  • Contacts
  • Notification Message Templates
  • Logic Functions (automatic application of logic function changes can be disabled, see below)

By default, TopView reads the information in the configuration file (including the Default Email, Modem, and Voice recipient groups) and will not re-read the configuration file unless the TopView Engine is restarted (stopped/started) or the user reloads the configuration in an interactive version of the TopView Engine.

This behavior allows changes to the configuration file without impacting the operation of a running TopView Engine until the user decides that the changes should take effect.

To apply configuration changes while running

You can change this behavior for a configuration by selecting “Apply configuration changes while running” on the “Engine Settings > General” screen in the TopView Configurator. If this option is selected, a running TopView Engine will reload the configuration each time the user saves the configuration file in the TopView Configurator.

Most changes to existing tags (e.g. alarm limit change) can be applied without impacting the current state of the TopView Engine. Other changes require an internal/soft restart. The Configurator will warn you when the changes require an internal/soft restart. During an internal/soft restart, TopView can persist the existing alarm, acknowledge, and disable states if the “Persist alarms, acknowledge, and disable state during internal restart” option is also selected.

Prevent automatic application of Logic functions

As of TopView version 6.28, a global option can be set to prevent the automatic application of logic function changes to running TopView Engines.

Category: TopView

Our recommended cellular modems for GSM require a SIM card with an SMS plan. US and Canadian customers can purchase a SIM card and SMS plan for TopView through GPRS SIM. If you are a US customer, you can purchase TopView SMS plans and SIM cards from GPRS SIM. For questions about GPRS SIM please contact Eddy Stevens.

Category: TopView

If you are receiving multiple notifications for the same alarm, the Global Option to to remove duplication notifications to the same recipient may be unchecked. This setting can be found in “Global Options” under the Notification tab.

If duplicate recipients are allowed, multiple notifications may be a result of Tag Group notifications combined with individual alarm notifications.

You can define notification for a Tag Group, and this notification applies, by default, to all tags/rows in the Tag Group. You can also define notification at the tag/row level (on the Alarms and Limits screen) for each alarm condition.

If both are defined, you may receive two notifications for a single alarm: one for the Tag Group, one for the tag/row.

Category: TopView

Note: the information below also exists as a PDF with screenshot images.

Background

If you install TopView OPC/SCADA on a Wonderware machine after installing the Wonderware OPC Server software, you may not be able to query to local OPC Servers (OPCENUM). The error returned is  0x80040153

This issue is known by Wonderware and can be caused by the installation of any OPC software, not just TopView.

Here is some information from Wonderware on this issue:

  1. http://esupport.wonderware.ch/Data/ReadMeIAS35.html
    L00115135:          In the OPCClient object, the installed DAServers are not listed under the Server Name. For the OPCClient object, the following error message is shown in the SMC log:
    .Net Editor Info – 17:35:14.3125809
    Failed to create instance of OPCEnum on server node COMPST01: 0x80040153
    As a workaround, if you invert the installation sequence by installing the OPC Server first and then the Bootstrap, the OPCEnum is installed without anonymous logon and a remote connection to the OPC Server is possible. You can also resolve this issue by deleting and creating the anonymous logon on the OPCEnum permission.
  2. https://wonderwarepacwest.com/uploads/2014/01/ReadMe.html
    FS Gateway 3.0 SP1 Readme Information: Known issues
    L00115135:          After installing a third-party OPC server on top of an already installed DAServer, OPC clients may not be able to browse for OPC servers using OPCEnum, and the client receives error 0x80040153. As a workaround, install the DAServer last.

Workaround/Fix

The first item referenced above from Wonderware states “You can also resolve this issue by deleting and creating the anonymous logon on the OPCEnum permission”.

This workaround does fix the issue. Here are the detailed steps for fixing the error by removing and adding Anonymous logon.

Remove/Add Anonymous Logon

On the Wonderware/TopView computer:

  • Run DCOMCNFG (Start…Run…DCOMCNFG)
  • Go to Component Services…Computers…My Computer… DCOM Config
  • Under “DCOM Config” find OPCENUM
  • Right-click OpcEnum and click Properties
    • Security Tab
      • Launch and access permissions: Customize should be selected
      • Click [Edit] next to Customize
      • Anonymous Logon is listed with all permissions checked
      • Click [Remove] to remove  Anonymous Logon
      • Click [Add]
      • Under “Enter the object names to select” enter Anonymous Logon and click [OK]
      • Re-enable the Anonymous Logon permissions for local and remote activation and launch
      • Click [OK] until all dialogs are closed
      • Close DCOMCNFG

Restart OPCENUM Service

  • Run the Windows Services app (Control Panel…Admin tools…Services)
  • Find OPCENUM in the list of Services
  • If the OPCENUM Service is stopped, right-click and choose “Start”
  • If the OPCENUM Service is running, right-click and choose “Restart”

You should now be able to query the local OPC Servers from TopView.

Categories: OPC, TopView

Voice notification

As of TopView 6.25, we officially dropped support for voice notifications using TAPI modems. It is possible to continue using TopView to make voice notification calls via TAPI modem, but due to the dwindling hardware and OS-level support for these devices we can no longer offer full support of this notification method.

We recommend using VOIP over TAPI notifications due to the ease of setup and dramatic difference in reliability between the two. See TopView’s VOIP Notification page for more information on voice notification via VOIP, including making VOIP calls over an analog phone line.

TopView can send Voice Notification alarm messages over a phone line using a TAPI modem or via the network using VOIP. Alarm messages are converted to speech and spoken over the connection.

During voice notifications, the recipient can optionally acknowledge the alarm using the keypad on their phone.

Please check our modems page for the best performing modems we’ve found.

If test voice notifications via VOIP are experiencing difficulties, we recommend the following tests and procedures:

  • Verify that the authorization name and password are correct for the SIP server
  • Can a softphone installed on the same computer as TopView connect to the SIP server? Can it also make and receive calls from the VOIP system? One softphone you can use is the 3CX Phone 6 for Windows (use this one over newer versions, which restrict access to only 3CX servers).
  • Is it possible the firewall is blocking SIP calls? Test your computer’s firewall settings with the 3CX Firewall Checker client application.
    • Run the RemoteConnectionTest and verify that the registration test passes.
  • Make sure you’re running the most recent version of TopView available, along with any patches for that version.

We have a few general posts on TopView’s use of VOIP for voice notifications:

(TAPI for voice call-out is no longer officially supported by Exele, we recommend using VOIP instead)

The Way2Call Hi-Phone TAPI device can be used for TopView Voice Notification.

If you are installing this device, please read our installation instructions and tips page. See our recommended modems page, as well, for more information.

For many years TopView has supported voice call-out notification over traditional phone lines but, due to both hardware and software developments, voice notification via TAPI modems is much less reliable than it used to be (see the reliability section below for an explanation).

With TopView VOIP notification you can perform the same functions over your network without voice modems or TAPI devices.

Requirements

TopView VOIP notification requires a VOIP service that provides a SIP server and a network connection to that SIP server.

VOIP service options

A SIP server can be provided by:

Costs range from option to option, so investigate each option to see which one best fits your business’s requirements on functionality and cost.

Why is notification via TAPI less reliable?

TAPI notification is less reliable because the software systems are less reliable, on multiple levels:

  • Soon after its release, Windows 10 experienced TAPI issues for a year before they were fixed
  • TAPI hardware drivers may be highly dependent upon Windows versions and updates
  • Using USB devices on VMs can be problematic

We find that the time spent setting up, testing, and supporting TAPI hardware and software through its issues is far more expensive than VOIP.

TopView supports many different kinds of modems for different kinds of notifications.

The best resource for current recommendations is our recommended modems page.