Versions Compared

Old Version 2

changes.mady.by.user Jon Delaney

Saved on

compared with

New Version Current

changes.mady.by.user Dan Sudduth

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

← Back to Technical Info page

...

Version

Type

Change Description

2122.31.0

General

Document created for the instructions to install AGRIS Version 2122.31.0

For Agris

...

22.

...

1.0 please note: It may be best to use the Edge or Internet Explorer browser as the Chrome browser may block the links.

Introduction

Purpose

The Installation Instructions assist you in performing new software installations of the AGRIS System Version 2122.31.0 software. Also use these instructions to upgrade AGRIS System Version 9.5.0 to this new version.
For information regarding running AGRIS on Microsoft SQL Server, please refer to the documentation here: AGRIS on Microsoft SQL Server

IMPORTANT:  Before upgrading your system to AGRIS 2122.31.0, read Appendix H – Tips, Known Issues, and Best Practices

IMPORTANT: Installing or upgrading AGRIS requires up to two (2) system restarts on all server and client machines, as detailed below.  Please take this into consideration when planning your installation or upgrade.

1.  A system restart after completing the .NET Framework installation program (this installation program will only run if the computer does not yet have the required version of the .NET Framework)

2.  A system restart after completing the AGRIS installation program

...

The following table summarizes the major hardware (HW) and software (SW) requirements changes relating to the maintenance and support of AGRIS 2122.31.0 (compared to the previous release of AGRIS).

Requirement

Added

Removed

HW-Hard-Drive

No changes.

No changes.

HW-RAM

No changes.*

No changes.

HW-CPU

No changes.

No changes.

SW – AGRIS Dataset Conversions

No changes.

No changes.

SW-Database Engine

No changes.

No changes.

SW-Database File Format

No changes.

No changes.

SW-Operating System

No changes.

No changes.

SW-Application Software

No changes.

No changes.

SW-Report Component

No changes.

No changes.

SW- Terminal Server

No changes.

No changes.

...

RetailWise customers cannot upgrade directly to AGRIS 2122.31.0 and must coordinate their upgrade to Store Manager ES and AGRIS 2122.31.0 with the Sales Team (800-393-0075). The AGRIS Integration Platform (AIP) for RetailWise, which is translates data between RetailWise and AGRIS, is not supported in AGRIS 9.5.0.7 and higher. Note that customers already running Store Manager ES are not impacted by this and are able to upgrade to AGRIS 2122.31.0.

Tips for Minimizing Downtime During the Installation

...

Greenstone provides support to all subscribing users of the AGRIS System Version 2122.31.0. You can contact our Technical Assistance Center in the following ways:
Email:  Mysupport@culturatech.com
Phone:  (800) 366-2474
Mail:  3820 Mansell Road, Suite 375. Alpharetta, GA 30022
Website:  http://www.greenstonesystems.com/
Knowledge Base https://culturana.force.com/s/login

...

      1. Create a network share (Example: \\servername\apps\AGRISDIST). All users need Read permissions to this share.
      2. The network administrator should save all the installation files to this share.
      3. If an update is available (update.exe), it should be copied to the same folder that contains the setup.exe, which was created in the previous step.
      4. Install AGRIS Version 2122.31.0 or later on all AGRIS servers, for example, component servers, database servers, etc. Also, apply updates, if they exist, for example, update.exe.
      5. Install AGRIS Version 2122.31.0 or later on all your AGRIS workstations. The AGRIS clients are now ready to detect updates from your servers. When you receive an update from AGRIS, you only have to update your Component Server(s) and application server(s). If you have not specifically set up a Component Server(s), then we assume the database server is the Component Server.


AGRIS

...

22.

...

1.0 Network Installation

Installation Checklist

Print this checklist to assist you in installing AGRIS 2122.31.0.

16
Step #SectionStep

1.

Sec 2.2

Verify your workstations and servers meet or exceed the system requirements and check their compatibility with current hardware requirements.

2.

Sec 2.3

Install any outstanding Windows Service Packs (if necessary).

3.

–

Install a supported version of Pervasive® PSQL™ Server on the database server(s) using the instructions available at https://culturana.force.com/s/article/ka036000000oLocAAE/AGRIS-Installing-Actian-PSQL-v12-SP1-and-Update-3?r=1

4.

–

Install a supported version of Pervasive® PSQL™ Client on any AGRIS client workstations, including Citrix or Terminal Servers using the instructions available at https://culturana.force.com/s/article/ka036000000oLocAAE/AGRIS-Installing-Actian-PSQL-v12-SP1-and-Update-3?r=1

5.

Sec 2.5

Set up a padmin user account.

6.

Sec 2.7

Create a COM+ Services user account.

7.

Sec 2.8

Set up network COM+ access on the AGRIS Server.

8.

Sec 2.10

Set up the AGRIS directory structure and permissions.

9.

Sec 2.14

IMPORTANT! Back up your datasets.

10.

–

Stop the Pervasive® PSQL™ services on the AGRIS server.

11.

Sec 3

Manually install AGRIS Server on the database server.

12.

Sec 4

Manually install AGRIS Server on any Citrix Servers/Terminal Servers.

13.

Sec 5

Manually install AGRIS Client on all your workstations.

14.

Sec 2.17

Download and manually install the latest AGRIS Service Pack on the database server and on any Citrix Servers/Terminal Servers.

15.

Sec 1.9

Use the Auto-Update feature to apply the latest service pack to all client workstations.

to apply the latest service pack to all client workstations.

  16.      –Configure the Cultura AGRIS SYS License Service.  Refer to the instructions on this page.

17.

–

Launch AGRIS from a client workstation to create the datasets folder and first database.

1718.

Sec 10

Update the licenses file and the extended options

19.

Sec 7

Install any standalone units that use oneWeigh.

20.

Sec 2.16

If necessary, set up Auto Blender configurations to include AGRIS User information.

...

Please consult the AGRIS Version 2122.31.0 System Requirements document before proceeding with the install. Please verify that all computers meet or exceed the minimum system requirements.
Note: The AGRIS installation will fail if minimum system requirements are not met.

...

  1. Stop the Auto Blender services.
  2. If you have not already done so, convert your first dataset to AGRIS 2122.31.0.
  3. From the AGRIS Main Menu, select AGY >> General Setup >> Automated Controls to display the Automated Blender Setup window.


    The Automated Blender Setup Window

  4. For each Auto Blender:
    1. Click the button to the right of the Auto Blender field to select an automated blender from the list.
    2. Click the button to the right of the AGRIS User field to select a user from the list. Be sure to select an AGRIS user with password permissions set to Never Expire.
    3. Click Apply to apply the changes.
  5. When you finish assigning users, click OK to close the Automated Blender Setup window.
  6. Restart the Auto Blender services.

Downloading the AGRIS

...

22.

...

1.0 Installation Program

  1. From the console of the server or standalone unit, click Start >> Run…
  2. Type  https://culturana.force.com/  >> click OK.  (NOTE: It may be best to use the Edge or Internet Explorer browser as the Chrome browser may block the links).
  3. Log on to the website
    1. If you are not already signed up for a user account, you can click the "Register" link to sign up. Account applications are reviewed and approved within 8 business hours.
  4. Click search for the AGRIS 2122.31.0 is Available Article and the Download setup.exe link for AGRIS 2122.31.0.
  5. Click Save when the "Do you want to run or save this file?" message displays.
  6. On the left side of the window, click Desktop, and then click Save on the bottom, right side to download the update (which may take a few minutes).
  7. WARNING: Due to enhanced security features in Windows, please ensure that the installer is unblocked prior to installation using the following steps:
    1. Right-click on the downloaded installation file and click Properties
    2. At the bottom of the General tab, look for a button that says "Unblock"
      1. If the button exists, click Unblock and then click OK
      2. If the button does not exist, click Cancel
  8. If necessary, you can request an AGRIS 2122.31.0 CD from the Technical Assistance Center (800-366-2474) or by emailing Mysupport@culturatech.com.

...

Install components in the following order:


AGRIS

...

22.

...

1.0 Server Installation


This section describes how to install the AGRIS System Version 2122.31.0 software in the supported configurations listed in the AGRIS System Requirements document. It assumes that all hardware and supporting software requirements are in place and operational.
The following prerequisites must be satisfied:

...

Citrix Server/Terminal Server Installation

Anchor
_Toc158618014
_Toc158618014
Anchor
_Ref190154932
_Ref190154932
Anchor
_Ref190154936
_Ref190154936
Anchor
_Toc478039010
_Toc478039010
AGRIS

...

22.

...

1.0 Citrix Server/Terminal Server Installation checklist

Install components in the following order based on the application server software being used:

Citrix Server

Windows Server 2012 R2 Terminal Services

Latest Windows Service Pack

No Service Pack

Install Terminal Services

Install Terminal Services

Install MetaFrame XP/Presentation Server or Citrix XenApp 6.5.0


Pervasive® PSQL™ 32-bit Client

Pervasive® PSQL™ 32-bit Client

AGRIS Server

AGRIS Server

Anchor
_Ref88362347
_Ref88362347
Anchor
_Toc158618015
_Toc158618015
Anchor
_Toc478039011
_Toc478039011
Installing AGRIS

...

22.

...

1.0 Server on Citrix Server/Terminal Server

  1. Log all users out of the Citrix/Terminal Server(s) and prevent additional users from logging on while installing AGRIS.
  2. Close all other applications and restart the server.
  3. Install a supported version of Pervasive® PSQL™ using the instructions available on the AGRIS Customer Portal site:
    https://culturana.force.com/s/article/ka036000000oLocAAE/AGRIS-Installing-Actian-PSQL-v12-SP1-and-Update-3?r=1 * = NOTE: It may be best to use the Edge or Internet Explorer browser as the Chrome browser may block the above links.
  4. Complete section 3.2 to install AGRIS.
  5. Manually set the AGRIS data path - see Section 13.1 for additional information.
  6. Save the AGRIS data path and restart the server.

...

Windows 8.1

Windows 10

No Service Pack

No Service Pack

Pervasive® PSQL™ 32-bit Client

Pervasive® PSQL™ 32-bit Client

AGRIS Client

AGRIS Client

Anchor
_Install_Pervasive_Client_Engine
_Install_Pervasive_Client_Engine
Anchor
_Toc6991042
_Toc6991042
Anchor
_Ref188851585
_Ref188851585
Anchor
_Ref188851602
_Ref188851602
Anchor
_Ref188937111
_Ref188937111
Anchor
_Toc478039015
_Toc478039015
AGRIS

...

22.

...

1.0 Client Installation Procedure

IMPORTANT:Before installing the AGRIS Client, install a supported version of Pervasive® PSQL™ on the client workstation using the instructions available at; at  
https://culturana.force.com/s/article/ka036000000oLocAAE/AGRIS-Installing-Actian-PSQL-v12-SP1-and-Update-3?r=1

...

Windows 8.1

Windows 10

No Service Pack

No Service Pack

Pervasive® PSQL™ Workgroup

Pervasive® PSQL™ Workgroup

AGRIS Standalone

AGRIS Standalone


Anchor
_Toc478039021
_Toc478039021
AGRIS

...

22.

...

1.0 Standalone Installation

  • Installing the .NET Framework:
    • For Windows 8.1 and Windows 10, part of the.NET Framework must be installed through the Programs and Features:
      • Click Start and type "Programs and Features", then click on the Programs and Features.
      • Click on the Turn Windows Features on or off link.
      • Checkmark the .NET Framework 3.5 (includes .NET 2.0 and 3.0) checkbox
      • Click OK to start the installation
      • Once the installation is complete, click Close
      • Close the Programs and Features
      • Proceed with the next step in the AGRIS installation.
    • For all other supported standalone operating systems, there are no extra steps for the .NET Framework.

...

  • The final step in the installation process takes place in a command window. Do not manually close this window. When complete, this command window will automatically close and the computer will restart.



The Command Window


Configuring the Cultura AGRIS SYS License Service

Depending on your configuration and installation type, you may need to configure the Cultura AGRIS SYS License Service.  Refer to the instructions on this page.

Anchor
_Toc478039022
_Toc478039022
Starting AGRIS

...

If you are converting from earlier versions of the AGRIS Business System to Version 2122.31.0, this is a simple process.

Note:If you are upgrading from AGRIS Version 9.4.6.x or earlier, please contact Greenstone Technical Support (800-366-2474). Conversions from V9.4.6.x or earlier are not supported in this upgrade.

Anchor
_Converting_from_Agris_1
_Converting_from_Agris_1
Anchor
_Toc6991049
_Toc6991049
Anchor
_Toc478039024
_Toc478039024
Converting to AGRIS

...

22.

...

1.0

  • Launch AGRIS 2122.31.0 and the Select Dataset screen will appear.
  • Choose the desired dataset and click Select.
  • A window appears describing that a dataset conversion is required.

...

Use the licensing setup to set the number of user licenses for each purchased package. The licensing setup for the AGRIS Business System is located in the main system menu under Help. Use this process along with the licensing diskette that accompanies the AGRIS 2122.31.0 installation CD. Load the licensing diskette during installation or if any package licenses are upgraded.
Note:Program module icons are not present until the package is licensed for use. An access code is required during this procedure, so perform this procedure during hours when the Technical Assistance Center (800-366-2474) is available. Tell them that you are performing the license update procedure and need an access code.

...

Note:  Extended options control access to selected package menu options. Upgrading to AGRIS 2122.31.0 requires application of initial extended option settings from the license file. All extended options are considered "off" until this process is complete. Skipping this process will block access to package menu options controlled by extended options.

...

If the current dataset has already been converted to AGRIS 2122.31.0 and this is the first time Extended Option System Default Settings have been updated, then elect to update the current dataset with the System Default Settings. Once Extended Option System Default Settings are set, they will be automatically applied to a dataset during conversion to AGRIS 2122.31.0, or when a package is initialized in a dataset.

...

    • The Target command, above, shows an example of allowing the shortcut to point to an alternate agris.ini file. This is accomplished by including the "/I" parameter, followed by the drive letter and full directory path, then the name of the agris.ini file. You can also use this new parameter within a .BAT file from DOS when launching the main AGRIS menu (SysMenu.exe). You can set up multiple desktop shortcuts or batch files and use the command line parameter to access the alternate agris.ini files. The contents of the alternate agris.ini file allow access to multiple sets of "dataset" directory and "userprog" directories with one installation of the Version 2122.31.0 system.
    • Add the current .ini file location and current SUPPORT and USERPROG path settings. Since you can access multiple INI files, the System Information Report was enhanced to show the currently active Userprog, Support and Data paths, and the currently active agris.ini file.

...

If your datasets require reformatting as part of the upgrade to AGRIS 2122.31.0, a new validation utility now allows you to scan these datasets for errors before converting them.
When starting a Dataset Conversion during the upgrade to Version 2122.31.0, the Select Dataset window will appear.

...

The following is a list of tips, known issues, and best practices for installing or upgrading to more recent Microsoft operating systems, Pervasive® PSQL™, and AGRIS 2122.31.0.

Anchor
_Toc236729441
_Toc236729441
Anchor
_Toc267308911
_Toc267308911
Anchor
_Toc478039049
_Toc478039049
Pervasive® PSQL™

...

RetailWise customers cannot upgrade directly to this version of AGRIS and must coordinate their upgrade to Store Manager ES and AGRIS 2122.31.0 with the Sales Team (800-393-0075). The AGRIS Integration Platform (AIP) for RetailWise, which is translates data between RetailWise and AGRIS, is not supported in AGRIS 9.5.0.7 and higher. Note that customers already running Store Manager ES are not impacted by this and are able to upgrade to AGRIS 2122.31.0.

If upgrading to Pervasive® PSQL™ v10 or greater, instead of uninstalling the previous version and installing the new version:
NOTE: If you have already upgraded to PSQL v10 or greater as part of a prior update, skip this procedure.
1. Open Pervasive PSQL.
2. Select Control Center >> Compatibility.
3. Set Create File to 9.5.
NOTE: If you don't set the Create Value parameter, Store Manager™ ES returns a Btrieve #24 error on transact.new when you try to convert the dataset.

After upgrading/installing Pervasive® PSQL™ v10 or greater on the Store Manager™ ES workstation, and prior to running Store Manager™ ES:
1. Open Pervasive PSQL >> Utilities >> Maintenance.
2. Click Options.
3. Select Show Information Editor.
4. Click Load Information.
5. Go to C:\Retailwise\Vertical\TDL.
6. Open sched.db.
7. Click Create File.
8. In the Create File window, click on the OK button. There are no records in this file, so the file is simply rebuilt.
9. Following the rebuild, click Load Information.
10. Go to C:\Retailwise\Vertical\TDL.
11. Open export.db.
12. In the Create File window, click OK. There are records in this file, so the file is simply rebuilt.
13. Go to C:\Retailwise\Vertical.
14.Open Log.db.
15.In the Create File window, click OK. There are no records in this file, so the file is simply rebuilt.
16.Go to c:\Retailwise\Vertical
17.Open LogClr.db
18.In the Create file windows, click OK. There are no records in this file, so the file is simply rebuilt.
19. Close Pervasive, open Store Manager™ ES and work as normal.
Note: If you do not perform this maintenance first, you will encounter an error on sched.db during your first daily close.

If the .db file format is incompatible or corrupt, you may receive a *Btrieve 46 error (access to file denied). This error could also affect any of the *.db files in the C:\Retailwise\Vertical folder.
Locate the file in Pervasive® PSQL™ by clicking Utilities >> Maintenance >> Options >> Show Information Editor.

A Store Manager™ ES Critical Error Example
In the example above, opening vend.db displays a file version of 3. The file is probably corrupt, since it was not converted when moved to PSQL 8.7.
RECOVERY:
Use BUTIL.EXE to recover records - the same as a file rebuild in AGRIS.
Note: You must recover, clone, and then load the database files.
Type the syntax for these commands from the DOS command prompt:
butil -recover <database file> <file.out>butil -clone <new database file.new> <original database file.db>butil -load <file.out (from recover)> <new database file.new>rename <original database file.db> <original database file.old>rename <new database file.new> <new database file.db>
You can use the same database file name, and just change the file extensions.
STRIPPING:
Use BUTIL.EXE to recover and remove records from files, or to strip the file. Carry out this procedure when you want to create an empty file.
Note: You must first clone the database files.
Type the syntax for these commands from the DOS command prompt:
butil -clone <new database file.new> <original database file.db>rename <original database file.db> <original database file.old>rename <new database file.new> <new database file.db>
You can also use the Rebuild option under Pervasive® PSQL™ to rebuild all the files to AGRIS V9.5 file format, or you can rebuild individual files through this utility, which provides a rebuild log.

...

Start all conversions on the Database server.

The Database Conversion utility creates a log entry for the conversion of each package in the dataset.
When reviewing the conversion log (convert.log) following a dataset conversion, you may see old dates in the log entries. This occurs when you have converted a dataset for an earlier upgrade. The log appends any new conversion entries to the end of the existing log, which can result in the same file appearing in the conversion log multiple times, with different conversion dates.

On workstations where both AGRIS and Fuel Connect™ are installed, you must stop the Fuel Connect service before upgrading AGRIS.
To stop Fuel Connect, click Start >> (All) Programs >> AGRIS Fuel Connect >> Stop Fuel Connect Server.
Press any key to close the window once these services are stopped.

When transferring data between datasets using either the DTR process or Imports, ensure that both datasets are already converted to AGRIS 2122.31.0 before starting the transfer process.

When validating datasets prior to conversion, a File not Found or Package not Found entry may appear in the error log. While this does not prevent the conversion process from running, you may need to rebuild some dataset files following the conversion. If necessary, call the Technical Assistance Center (800-366-2474) for further assistance.

If you receive an Auto Blender Log cannot create session message, it indicates that an invalid login attempt occurred for an auto blender.
When a login attempt fails, the remaining auto blenders will fail to log on as indicated by the Trapped error 91 log entry. To correct, assign a valid AGRIS user to all Auto Blender controls. If necessary, call the Technical Assistance Center (800-366-2474) for further assistance.

AgroGuide Data Scrub: This conversion automatically corrects any Farm, Field, or Crop Zone codes that end with characters other than 0-9, a-z or A-Z.
NOTE: If you've already upgraded to AGRIS 2122.31.0, this correction has already been performed on your data.
A report (Report ID: URLDataScrub) appears in the Report Spooler and indicates if any corrections were made (described as "New Code").
This conversion does NOT correct any Name IDs (i.e. Clients) ending with characters other than 0-9, a-z, or A-Z, but displays any Name IDs ending with an invalid character.
Greenstone recommends that you correct any invalid characters at your earliest convenience, as these codes may impact integrations with other systems, including AgLogic.
Use the Change Name ID utility in AGRIS to change these Name ID codes.

...