Argos Diagnostics and Health Pages

Argos application server has 3 "health pages" that you can view for installation and troubleshooting purposes. The goal is to give you a clear overview of the current state of the communication service, integration service, and the copy tracking gateway.  These pages can be viewed from any web browser on your network, and it is not required for any Argos software to be installed to view these pages.

Argos Communication Service Health Page


This is the most commonly used health page, as the communication service is the database's middle-man for desktop clients, print tracking, copy tracking, and Argos integration service.  It's health page is broken into four sections.  
The first section displays statistics about your Argos Communication Service.  It will tell you the version of Argos communication service you are running, the location of the service's log files (on the server), whether or not the service is syncing with the database, along with other general statistics about the service.  The most critical thing to look for here is the "Last jobs synchronization result".  If you see "postponed database connection" here, or anything other than "success", please ensure that your database is online, and that your service has the correct configuration information for the database.  Database connection information is stored at the following loction on your Argos App. Server:

 "C:\program files\sepialine\Argos7\ArgosDatabase.config"

The second section on the health page is a table of refresh intervals for the service's different caches.  These can all be adjusted in the service's configuration file.  Please contact Sepialine Support if you would like to make changes to these intervals.

The next section is an excellent tool for confirming and troubleshooting desktop client installations.  This table lists all Argos desktop clients that are connected to the communication service, along with user/workstation information.  If the user has any pending jobs to bill they will be displayed in the "Pending" column of this table.

It is important that the domain for a user listed in the table above (connected desktop clients) match the domain for the user in the fourth and final table, which contains the most recent 25 print, copy, or phone jobs.  There is a new feature in 7.1, called user merging that can be used if these do not match by default.  Another useful column in this table is the  "Billing" column.  It will let you now if the job was interactively or silently billed, and whether that was due to a device setting or a user setting.

Argos Integration Service Health Page


The integration service is responsible for automated, scheduled tasks within Argos. This includes pulling print/copy jobs from log files, project imports, data exports, and a variety of other important Argos functions.  Since you can have multiple integration services on your network, this is a good place to verify which tasks are assigned to the service on a given machine.  This will also tell you if you have unlicensed integration adapters, such as an Oce connector.  An Oce connector, or any other integration adapter, will not pull in plot/copy jobs if it is not licensed.  This page will also tell you the path to your IS log file, which communication service URL the integration service is posting to, and if the service is syncing with your Argos database.

Copy Tracking Gateway Health Page


If you have Sepialine express terminals, this page will tell you if they are connected to the copy tracking gateway.  The page will also show each action that the terminal performs in terms of posting data and pulling down user/pincode information.  If you see that the terminal has "requested properties" and the result is "succeed", then the terminal is able to connect to the gateway.

Have more questions? Submit a request


Please sign in to leave a comment.