Versions Compared

Key

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

AGRIS Product Suite  |  Installation Instructions  |  Version 20.1.0

...

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

MSSQL 2019 Standard, Cumulative Update 4

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.

...

Install components in the following order based on the workstation operating system:

7

Windows

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 Client

AGRIS Client

AGRIS Client

...

Install components in the following order based on the workstation operating system:

7Service Pack 1

Windows

Windows 8.1

Windows 10

No Service Pack

No Service Pack

Pervasive® PSQL™ Workgroup

Pervasive® PSQL™ Workgroup

Pervasive® PSQL™ Workgroup

AGRIS Standalone

AGRIS Standalone

AGRIS Standalone


Anchor
_Toc478039021
_Toc478039021
AGRIS 20.1.0 Standalone Installation

...

You cannot apply an Auto Update to a Windows Server 2012 R2, Windows Server 2016, nor Windows Server 2019 machine. All Service Pack installations must be carried out manually, while logged in as an Administrator.
1. Open Windows Explorer and locate the AGRIS 20.10 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 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.

Windows® 7

Image Removed

CDMS Client Services Installation During the installation of the CDMS client services to be integrated with AGRIS 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.

Dataset Conversions

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

...