PANTHEON™ Help

 Toc
 PANTHEON Help - Welcome
[Collapse]PANTHEON
 [Collapse]Guides for PANTHEON
  [Expand]Guide for PANTHEON
  [Expand]Guide for PANTHEON Retail
  [Expand]Guide for PANTHEON Vet
  [Expand]Guide for PANTHEON Farming
 [Collapse]User Manuals for PANTHEON
  [Collapse]User Manual for PANTHEON
   [Collapse]Getting Started
     Dictionary of terms
     First steps with PANTHEON
    [Expand]Using PANTHEON at Tecta, a fictional company
    [Expand]Instructions for Ensuring Compliance of PANTHEON with SAS
    [Collapse]PANTHEON Installation
      Installation process
      Computer configuration
     [Expand]PANTHEON Licensing
     [Expand]PANTHEON Cloud
     [Expand]On-Premise
     [Collapse]Upgrade and uninstall
       Changing PANTHEON version
       .ini Configuration file
       Removing (Uninstalling) PANTHEON
       Migrating PANTHEON to a new server
    [Expand]PANTHEON System
    [Expand]PANTHEON Basics
    [Expand]PANTHEON Help
    [Expand]Materials and Goods Movements
    [Expand]Assigning Identifiers
    [Expand]Frequently asked questions about Pantheon (F.A.Q.)
    [Expand]Archive
   [Expand]User Manual for eBusiness
   [Expand]Settings
   [Expand]Orders
   [Expand]Goods
   [Expand]Manufacturing
   [Expand]Service
   [Expand]Help
   [Expand]Personnel
   [Expand]Financials
   [Expand]Analytics
  [Expand]User Manual for PANTHEON Retail
  [Expand]User manual for PANTHEON Vet
  [Expand]User Manual for PANTHEON Farming
[Collapse]PANTHEON Web
 [Collapse]Guides for PANTHEON Web
  [Expand]Guide for PANTHEON Web Light
  [Expand]Guide for PANTHEON Web Terminal
  [Expand]Guide for PANTHEON Web Legal
  [Expand]Old products Archive
 [Collapse]User Manuals for PANTHEON Web
  [Expand]Getting started PANTHEON Web
  [Expand]User Manual for PANTHEON Web Light
  [Expand]User Manual for PANTHEON Web Terminal
  [Expand]User Manual for PANTHEON Web Legal
  [Expand]Old products Archive
[Collapse]PANTHEON Granules
 [Collapse]Guides for PANTHEON Granules
  [Expand]Personnel Granule
  [Expand]Travel Orders Granule
  [Expand]Documents and Tasks Granule
  [Expand]Dashboard Granule
  [Expand]B2B Orders Granule
  [Expand]Field Service Granule
  [Expand]Fixed Assets Inventory Granule
  [Expand]Warehouse Inventory Granule
 [Collapse]User Manuals for PANTHEON Granules
  [Expand]Getting started
  [Expand]Personnel Granule
  [Expand]Travel Orders Granule
  [Expand]Documents and Tasks Granule
  [Expand]B2B Orders Granule
  [Expand]Dashboard Granule
  [Expand]Field Service Granule
  [Expand]Fixed Assets Inventory Granule
  [Expand]Warehouse Inventory Granule
  [Expand]Archive
[Expand]User Site

Load Time: 406.2484 ms
"
  1004745 | 217237 | 375252 | Updated
Label

Changing PANTHEON version

When you upgrade PANTHEON, the program version is usually automatically changed. However, it may be necessary to manually change the PANTHEON version due to various reasons.

WARNING

The build and the database version must be in sync, otherwise the login will be disabled or the run of the program will be interrupted.

 

To be able to manually change the program version, the user must have the following:

  • A file archiver, such as 7-Zip (a file archiving and compression program);

  • Information about which data structure (builid) and which version of PANTHEON is used, in order to download the correct archive from Datalab's FTP server (web address of the FTP server: http://ftp.datalab.si/upgrade/si/release/);

  • Knowledge about the path to the program (usually C:\Program Files\DataLab) where the program is located;

  • Administrator permissions and full control over the folder where the program is located.

This is done in the following steps.

Table of contents

  1. Checking that the program version and the database version match
  2. Installing a file archiver (optional)
  3. Information about the program version and the database build
  4. Location of the PANTHEON program
  5. Changing the file

1. Checking that the program version and the database version match

In the PANTHEON toolbar, the user selects Help | About.

Changing the version (or changing the ".exe" file)

Check »Build# (program)« and »Build# (base)«.

Where the two pieces of information do not match, you are likely to encounter problems at login. To find a solution, follow the steps below.

2. Installing a file archiver (optional)

To successfully change the PANTHEON version, the user must have a file archiver and compressor on their computer. The user can find it on the 7-Zip website and install it by clicking Download and Install.

3. Information about the program version and the database build

In case there is inconsistency between the database version and the PANTHEON version, the program will report an error at login.

In the example below, the local PANTHEON program reports an error because the »Build#« of the data is lower than the »Build#« of the program.

Based on this information, the user can download the correct archive from Datalab's FTP server: ftp.datalab.si/upgrade/si/release/

  • For local installation and PANTHEON Cloud: in the FTP server list, the user searches for the version of the ».exe« file (dlPantheon_SQL_SI_SI_xxxxxxxxx.7z, in this case dlPantheon_SQL_SI_SI_1001030), and downloads it to the disk. The, the user copies the downloaded file to the location where PANTHEON is installed.

  • For PANTHEON Farming: in the FTP server list, the user searches for the FA version of the ».exe« file (dlPantheonFA_SQL_SI_SI_xxxxxxxxx.7z).

  • For the RT license of PANTHEON: in the FTP server list, the user searches for the version of the ».exe« file (dlPantheonRT_SQL_SI_SI_xxxxxxxxx.7z).

Further procedures for changing the ".exe" file are the same.

4. Location of the PANTHEON program

When a user does not know where PANTHEON is installed, the following image can help.

5. Changing the file

The user can change the file once they have the downloaded file (in this case dlPantheon_SQL_SI_SI_1001030.7z) in the folder where PANTHEON is installed. The user extracts the file and at the same time replaces the existing file with the one downloaded from the FTP server.

WARNING

PANTHEON must be closed, otherwise the file ».exe« will not be replaced.

 

The user confirms the file change by clicking the Yes For All button.

After changing the .exe file, the Build# of the program and the Build# of the database must match.


 

Rate this topic
Was this topic usefull?
Comments
Comment will also bo visible in forum!