Versions Compared

Old Version 2

changes.mady.by.user Rudolph Jones

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.

...

Version

Type

Change Description

18.12.0

General

Document created for the instructions to install AGRIS Version 18.2.0

...

Occasionally, if users fail to completely exit from AGRIS prior to running the backup routine, the backup software fails to completely back up the AGRIS datasets. Due to the file relationships that AGRIS 18.1.0 maintains, the resulting, partially backed up datasets are often not useable if you need to restore the entire dataset.
To minimize this problem, an open file agent, such as Pervasive Backup Agent™, is recommended. Backup Agent increases the chances of a successful backup if files are held open while the backup is running and is compatible with most backup solutions. For additional information about the Pervasive Backup Agent, please contact the Technical Assistance Center (800-366-2474).

...

  1. Stop the Auto Blender services.
  2. If you have not already done so, convert your first dataset to AGRIS 18.12.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 18.

...

2.0 Installation Program

  1. From the console of the server or standalone unit, click Start >> Run…
  2. Type  https://culturana.force.com/  >> click OK.
  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 18.12.0 is Available Article and the Download setup.exe link for AGRIS 18.12.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 18.12.0 CD from the Technical Assistance Center (800-366-2474) or by emailing Mysupport@culturatech.com.

...

Configuring Anti-Virus Software

AGRIS 18.1.0 is compatible with a variety of anti-virus solutions, but additional configuration reduces the negative performance impact that the real-time anti-virus scanning may cause. Modify your real-time file scanning to exclude the entire AGRIS directory and sub-directories. Failure to configure the anti-virus properly may cause intermittent errors within AGRIS 18.1.0.
Real-time scanning also increases the time needed to install, or update to, AGRIS 18.1.0 and PSQL, and may even prevent PSQL from installing. To alleviate both issues, temporarily disable real-time file scanning during the installation.
Please consult the anti-virus documentation for instructions on how to exclude files and folders from the real-time scan and to temporarily disable the real-time file scanning.

...

Install components in the following order:


AGRIS 18.

...

2.0 Server Installation


This section describes how to install the AGRIS System Version 18.12.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:

...

Note: The existing version of the AGRIS System must be version 9.5.0 or higher. No earlier versions of the software can be directly upgraded to Version 18.12.0.

    • Ensure that you have a complete backup of your current version's software and data.
    • Purge any unnecessary data files to enhance dataset conversion performance.

...

Citrix Server/Terminal Server Installation

Anchor
_Toc158618014
_Toc158618014
Anchor
_Ref190154932
_Ref190154932
Anchor
_Ref190154936
_Ref190154936
Anchor
_Toc478039010
_Toc478039010
AGRIS 18.

...

2.0 Citrix Server/Terminal Server Installation checklist

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

Windows Server 2008 R2 SP1 Terminal Services

Citrix Server

Windows Server 2012 R2 Terminal Services

Service Pack 1

Latest Windows Service Pack

No Service Pack

Install Terminal Services

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

Pervasive® PSQL™ 32-bit Client

AGRIS 18.1.0 Server

AGRIS

18.1.0

Server

AGRIS

18.1.0

Server

Anchor
_Ref88362347
_Ref88362347
Anchor
_Toc158618015
_Toc158618015
Anchor
_Toc478039011
_Toc478039011
Installing AGRIS 18.

...

2.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 18.12.0.
  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
  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 7

Windows 8.1

Windows 10

Service Pack 1

No Service Pack

No Service Pack

Pervasive® PSQL™ 32-bit Client

Pervasive® PSQL™ 32-bit Client

Pervasive® PSQL™ 32-bit Client

AGRIS 18.1.0 Client

AGRIS 18.1.0 Client

AGRIS 18.1.0 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 18.

...

2.0 Client Installation Procedure

IMPORTANT:Before installing the AGRIS 18.1.0 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

...

Pervasive® PSQL™ 32-bit Client

Create a COM+ Services User Account

AGRIS 18.1.0 Server


Anchor
_Toc478039018
_Toc478039018
Installing A Separate Component Server

Install the Pervasive Client Engine in accordance with the instructions available at 
https://culturana.force.com/s/article/ka036000000oLocAAE/AGRIS-Installing-Actian-PSQL-v12-SP1-and-Update-3?r=1 
Install the AGRIS Version 18.1.0 Server in accordance with the instructions contained in section Server Installation.
Install the AGRIS Version 18.1.0 Client in accordance with the instructions contained in section Client Installation.

...

Windows 7

Windows 8.1

Windows 10

Service Pack 1

No Service Pack

No Service Pack

Pervasive® PSQL™ Workgroup

Pervasive® PSQL™ Workgroup

Pervasive® PSQL™ Workgroup

AGRIS 18.1.0 Standalone

AGRIS 18.1.0 Standalone

AGRIS 18.1.0 Standalone


Anchor
_Toc478039021
_Toc478039021
AGRIS 18.

...

2.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.

...

  • Anchor
    StandaloneNextStep
    StandaloneNextStep
    If you did not create a network share in section 2.10:
    • Insert the AGRIS 18.12.0 CD into the CD ROM. Use the Windows Start\Run utility to browse to setup.exe on the CD.

...

  • 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

Anchor
_Toc478039022
_Toc478039022
Starting AGRIS

...

To start AGRIS 18.1.0, select it from the Start/Programs/AGRIS, or double-click the AGRIS icon on the desktop.

...

If you are converting from earlier versions of the AGRIS Business System to Version 18.12.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 18.

...

2.0

  • Launch AGRIS 18.12.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 18.12.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 18.12.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 18.12.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 18.12.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 18.12.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.

...

Use this feature to test license performance. If noticeable delays are occurring while navigating the AGRIS 18.12.0 System, this utility helps diagnose the problem. Typically, it should take less than a second for the system to access a license, but there are instances where it could take longer. If times are consistently longer than a second, then the network configuration may need to be investigated. Typically, when these delays occur, they are caused by improper network configurations.
The licensing component is called after selecting most System Manager Menu options. It accesses a license and then compares the current count to the licenses purchased.
To access this utility from AGRIS:

...

If your datasets require reformatting as part of the upgrade to AGRIS 18.12.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 18.12.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 18.12.0.

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

If you are upgrading from Pervasive PSQL v8.X, uninstall that version of PSQL before installing a version supported by the new version of AGRIS.

If you already use Pervasive Back-up Agent™, you must purchase Back-up Agent 2.0 for use with Pervasive® PSQL™ v11 or v12. See the Pervasive web site for details.



NOTE: The Create File Version and the Limit Segment Size settings discussed in this section are applied automatically as part of the AGRIS install when you allow the system to apply optimization changes towards the end of the installation routine. The information below is provided for reference only.
If you are installing Pervasive® PSQL™ on a computer with a version of Pervasive® PSQL™ prior to v10.X already installed, open the Pervasive Control Center and, before opening AGRIS V18.1.0 and attempting to convert any datasets to AGRIS 18.1.0, set the File Version to 9.5.

The Workstation Properties Window

When converting datasets with split files (files that have split to .^01 or more on the files) to AGRIS 18.1.0, there is a possibility of overloading the Transaction Log file size allocation for files in that dataset. Uncheck the Limit Segment Size to 2GB option in the Pervasive® PSQL™ Control Center Workstation Properties window.

The Workstation Properties Window
Once this setting has taken effect, Pervasive® PSQL™ combines these split files during the conversion process and this problem no longer occurs.

...

RetailWise customers cannot upgrade directly to AGRIS 18.1.0 this version of AGRIS and must coordinate their upgrade to Store Manager ES and AGRIS 18.12.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 18.12.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.

...

You cannot apply an Auto Update to a Windows Server 2008 R2, Windows Server 2012 R2, nor Windows Server 2016 machine. All Service Pack installations must be carried out manually, while logged in as an Administrator.
1. Open Windows Explorer and locate the AGRIS 18.12.0 setup.exe file on your network.
2. Right click the setup.exe file to display the option popup menu.
3. Click Run as Administrator to display the User Account Control window.


The User Account Control Window
4. Click Allow to install AGRIS 18.1.0 on your workstation.

If you need to set up an ODBC connection for Junge® Automated Blenders in a 64-bit environment, you will need to open the ODBC setup via C:\Windows\SysWOW64\odbcad32.exe. The ODBC setup that opens through the Windows Control Panel (C:\Windows\System32\odbcad32.exe) has only one option (SQL Server).

Changing the color scheme from the Windows Server 2008 basic color scheme to either the Standard or Classic color scheme may cause some disabled AgroGuide fields to appear as though they are available.

...

CDMS Client Services Installation During the installation of the CDMS client services to be integrated with AGRIS 18.1.0 on Windows 7, you may encounter 2 or 3 messages indicating that certain files cannot be registered. Per instruction from CDMS, it is OK to click IGNORE on each message and continue with the installation of the client.

...

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 18.12.0 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 18.12.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 18.12.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.

...


The log files created by the AGRIS 18.1.0 installation are located in the following folders. These log files are helpful for troubleshooting any problems that may occur during the installation process.

...