Versions Compared

Old Version 1

changes.mady.by.user Dan Sudduth

Saved on

compared with

New Version Current

changes.mady.by.user Iegor Gutyria (Unlicensed)

Saved on

Key

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

...

...

...

...

...

...

AGRIS™ Product Suite  |  Installation Instructions  |  Version 20.1.0

...

Image Added

Click here to go back to the Technical Info page

...

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 EngineNo changes.

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.

...

Please consult the AGRIS Version 20.1.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.

Anchor

...

_

...

Windows Service Packs are required for the following operating systems:

    • Windows Server® 2008 R2 Standard (64-bit) SP1
    • Windows® 7 Professional (32- and 64-bit) SP1

Anchor
_Toc158617994
_Toc158617994
Anchor
_Toc478038983
_Toc478038983
Active Directory-Integrated Domain Name Service (DNS)

...

  1. On the Component Server, typically the database server, click Start and type "Server Manager", then click on the Server Manager.
  2. Click on the Local Server in the selection tree.
  3. Scroll down to the ROLES AND FEATURES section
  4. In the TASKS dropdown, select Add Roles and Features
  5. On the Before you begin step, click Next
  6. On the Select installation type step, select Role-based or feature-based installation and click Next
  7. On the Select destination server step, ensure your server is selected and click Next
  8. On the Server Roles step, expand the Application Server option, checkmark COM+ Network Access, and click Next
  9. On the Features step, click Next
  10. On the Confirmation step, click Install
  11. Once the installation is complete, click Close to close the Add Roles and Features Wizard.

...

Granting Access to Component Services

Windows Server

...

2012 R2, Windows Server 2016, Windows Server 2019

  1. On the Component Server, typically the database server, click Start >> All Programs >> Administrative Tools >> and type "Server Manager", then click on the Server Manager.
  2. Click the Roles tree branch to display the Roles page.
  3. Click the Add Roles link to display the Add Roles wizard.
  4. Click Next to display the Select Server Roles page.
  5. On the Select Server Roles page, check the Application Server box to display the Add Required Features message.
  6. Click Add Required Features to add the required features.
  7. Click Next on the next two pages of the wizard to display the Select Role Services page.
  8. On the Select Role Services page, check the COM+ Network Access box
  9. Click Next to display the Confirm Installation Selections page.
  10. Click Install to install the Application Server role.
  11. Once the installation is complete, click Close to close the Add Roles wizard.

Granting Access to Component Services

Windows Server 2012 R2, Windows Server 2016, Windows Server 2019

  1. On the Component Server, typically the database server, click Start and type "Server Manager", then click on the Server Manager.
  2. From the Tools menu, select Component Services
  3. Double-click Component Services >> Computers.
  4. Right-click My Computer >> Properties.
  5. Click the Com Security tab.
  6. Click Edit Limits for the Launch and Activation Permissions.
  7. Click the Everyone group.
  8. Check the Remote Launch and Remote Activation options.
  9. Click OK >> OK.
  10. Close Component Services.

Windows Server 2008 R2 SP1

  1. On the Component Server, typically the database server, click Start >> (Settings) >> Control Panel >> Administrative Tools >> Component Services.
  2. From the Tools menu, select Component Services
  3. Double-click Component Services >> Computers.
  4. Right-click My Computer >> Properties.
  5. Click the Com Security tab.
  6. Click Edit Limits for the Launch and Activation Permissions.
  7. Click the Everyone group.
  8. Check the Remote Launch and Remote Activation options.
  9. Click OK >> Apply >> OK.
  10. Close Component Services.

...

Windows Server 2012 R2, Windows Server 2016, Windows Server 2019

  1. Double-click My Computer > C: (or the drive where the Apps folder resides).
  2. Right-click the Apps folder >> Properties
  3. Click on the Sharing tab
  4. Click Advanced Sharing… button.
  5. Click Caching button.
  6. Click No files or programs from the shared folder are available offline
  7. Click OK >> OK >> Close

...

2019

  1. Double-click My Computer > C: (or the drive where the Apps folder resides).
  2. Right-click the Apps folder >> Sharing and Security..Properties
  3. Click on the Sharing tab
  4. Click Advanced Sharing… button.
  5. Click Caching button.
  6. Click Files No files or Programs programs from the share will not be shared folder are available offline.
  7. Click OK >> OK. >> Close


Backing up AGRIS Data

IMPORTANT
You must back up all standalone workstations (including oneWeigh units) and servers storing AGRIS datasets to prevent loss of data. Back up the entire Apps folder and all subfolders on a daily basis (recommended).

    • The Apps\AGRIS\datasets\ folder contains setup information and data
    • The Apps\AGRIS\userprog\ folder contains user-defined reports and forms.
    • The Apps\AGRIS\support\ folder contains user-defined printer text drivers, custom logos and backgrounds if present.

...

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

...

Service Pack 1

Citrix Server

Windows Server 2012 R2 Terminal Services

Latest Windows Service Pack

No Service Pack

Install Terminal Services

Install Terminal Services

Install Terminal ServicesInstall 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 Server

AGRIS Server

AGRIS Server

Anchor
_Ref88362347
_Ref88362347
Anchor
_Toc158618015
_Toc158618015
Anchor
_Toc478039011
_Toc478039011
Installing AGRIS 20.1.0 Server on Citrix Server/Terminal Server

...

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 PackPervasive® PSQL™ 32-bit Client

Pervasive® PSQL™ 32-bit Client

Pervasive® PSQL™ 32-bit Client

AGRIS 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 20.1.0 Client Installation Procedure

...

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

...

Windows 8.1

Windows 10

Service Pack 1

No Service Pack

No Service PackPervasive® PSQL™ Workgroup

Pervasive® PSQL™ Workgroup

Pervasive® PSQL™ Workgroup

AGRIS Standalone

AGRIS Standalone

AGRIS Standalone


Anchor
_Toc478039021
_Toc478039021
AGRIS 20.1.0 Standalone Installation

...

Microsoft Operating Systems

Windows Server®

...

2012 R2, 2016, 2019

You cannot apply an Auto Update to a Windows Server 2008 R2, 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.

...