SENTINEL Upgrade – SENTINEL Instructions

Target Audience: IT Manager
Article #: 13885

Summary

This Instruction Article explains how to upgrade SENTINEL. It is recommend to install the new version on a new application server dedicated to the installation of the new software.  This allows for side by side use, as well as testing of the new program, without affecting production. If this is not possible then the older version of SENTINEL would have to be uninstalled via Add/Remove Programs (Programs and Features) before installing the newer version.

Instructions

On the current production server:
  1. Create a backup folder of the SENTINEL and CODESOFT configuration files. Copy all of the existing Configuration Settings files (*.ini) and XML Document files (*.xml) located in the folders below:
    • For Windows 2000, Windows XP, or Windows Server 2003, the SENTINEL configuration files folder is located in:“C:\Documents and Settings\All Users\Documents\Teklynx\Sentinel”
    • For Windows Vista, Windows 7, Windows Server 2008/2012, the SENTINEL configuration files folder is located in: “C:\Users\Public\Documents\Teklynx\Sentinel”                         
    • For Windows 2000, Windows XP, or Windows Server 2003, the CODESOFT  configuration folder is located in:“C:\Documents and Settings\All Users\Application Data\Teklynx\CODESOFT” (Note: The Application Data folder is a “hidden” folder. Depending on the operating system, you may need to be logged in as the Administrator in order to view hidden files.)
    • For Windows Vista, Windows 7, Windows Server 2008/2012 the CODESOFT configuration folder is located in:“C:\ProgramData\Teklynx\CODESOFT” (Note: The Program Data folder is a “hidden” folder. Depending on the operating system, you may need to be logged in as the Administrator in order to view hidden files.)
  1. The CS.ini and User.ini files copied from the CODESOFT configuration folders are the only ones required to be copied.  These files should also be opened and edited using Notepad so that the proper version number is reflected in the files.  (I.e. if upgrading from CODESOFT version 9 to CODESOFT version 2014, then all of the line items that list CODESOFT 9 should be replaced with CODESOFT 2014.) Not doing so could cause CODESOFT to not launch properly on the new server.
On the new production server:
  1. Install and activate the new SENTINEL version.
  2. Start the Label Print Manager service from Windows Services.
  3. Start the SENTINEL Manager. This will allow the program to write its necessary configuration files to the system.
  4. Close the SENTINEL Manager.
  5. Stop the Label Print Manager service from Windows Services.
  6. Navigate to the above listed directories for the new installation of the software on the new production server.
  7. Replace the .ini and .xml files on the new application server with the backup files that were previously copied from the current production environment.
  8. Start CODESOFT to verify that it is working properly.
  9. Start the Label Print Manager service from Windows Services.
  10. Start the SENTINEL Manager. All of the old SENTINELS should be created, verify that they are correct.
    • Errors could be displayed when trying to start the SENTINELS on the new server.  This could be caused by the following: (Note: These are not the only possible problems, just the most frequent.  Please contact Technical support at 414-837-4777 for further assistance if more issues arise)
      • The Map File for the SENTINEL is not available on the new server. If this is the case locate the Map Files from the current production server and restore those files to the new server.
      • The input directory does not exist on the new server.  To resolve this, create the input directory or specify the new directory to be used:
        • Right-Click the SENTINEL > Properties > Input Tab > Settings.
  11. In the SENTINEL Manager verify that the printer drivers are all correct.
    • Right-Click the SENTINELProperties > Process Tab CODESOFT Printing > Settings.
    • The printers should be in the list, (copied over via the User.ini file) verify that they are correct.

Additional Comments

If you need further assistance, please contact us.

Author


Was this article helpful?

Related Articles