Client/Server Upgrade Instructions from v12 and Older to Atrex 17

Taking the time to make sure that every Atrex system is mapped correctly BEFORE installing Atrex 17 will help make sure that the upgrade process goes as smoothly as possible.  While incorrect mapping worked in some scenarios in earlier versions of Atrex, those scenarios will NOT work properly in Atrex 17.

To check your mapping, open Options – System Information on each Atrex system and make sure that the Data Path and Central Path on EVERY Atrex system is EXACTLY the same.  If they are not, correct as needed under Options – Locations – Reports/Central Location or Options – Locations – Data Location.  Examples:

Scenario 1:  (Correct Client/Server)

  Server:

      Data Path:        Client/Server

      Central Path:        Client/Server

  Workstation-1:

      Data Path:        Client/Server

      Central Path:        Client/Server

  Workstation-2:

      Data Path:        Client/Server

      Central Path:        Client/Server

 

Scenario 1 is the perfect client/server setup.  All of the stations are mapped using client/server for both the Data and Central paths.

 

Scenario 2:  (Incorrect Client/Server)

  Server:

      Data Path:        C:\Atrex\Data

      Central Path:        C:\trex\Central

  Workstation-1:

      Data Path:        Client/Server

      Central Path:        Client/Server

  Workstation-2:

      Data Path:        Client/Server

      Central Path:        Client/Server

 

Scenario 2 will not operate correctly in Atrex 17.  The server is pointing directly to the local drive instead of using client/server which will cause locking errors when attempting to access the data.

 

Scenario 3:  (Incorrect Client/Server)

  Server:

      Data Path:        Client/Server

      Central Path:        C:\Atrex\Central

  Workstation-1:

      Data Path:        Client/Server

      Central Path:        C:\Atrex\Central

  Workstation-2:

      Data Path:        Client/Server

      Central Path:        C:\Atrex\Central

 

Scenario 3 will not operate correctly in Atrex 17.  While the Data paths are all correct, each system is pointing to the local drive for the Central path instead of using client/server which will cause locking errors when attempting to access the data.
 

 

Upgrading from Atrex 11 and 12 - Client/Server

                                       

In order for the Atrex Database Server Administrator to automatically convert your Atrex v11/v12 databases forward for use with Atrex 17, you must know the login information to the v11/v12 Database Server Administrator.  It is advised that you test this prior to beginning your conversion.  The default login password for the v11/v12 Database Server Administrator is located in step 7 below.

  1. Make 2 separate backups of your data, one to the hard drive and one to some type of removable media.
  2. Confirm your Data and Central paths (per instructions above) and correct as necessary.
  3. Close Atrex on all workstations.
  4. Install the Atrex 17 Database Server on the server computer.
  5. After installing the Database Server, verify in your firewall that connections will be allowed on port 12010.  This is a change from Atrex v11/v12.
  6. Start the Atrex Database Server Administrator.  The default username and password is:
      User Name: administrator
      Password: EDBDefault
  7. Select Quick Setup - Upgrade v11/v12 Server Installation.
  8. When prompted, enter the administrator login to the Atrex v11/v12 Database Server Administrator.  The default username and password is:
      User Name: admin
      Password: DBAdmin
  9. On the first system, install Atrex 17 directly over top of your previous Atrex installation.
  10. Start Atrex 17 and when prompted, start the data conversion.   Allow the data conversion to complete before continuing further.
  11. Enter the Atrex 17 registration key under Options – Enter Registration Information.
  12. Install Atrex 17 on the remaining systems.
 
In previous versions of Atrex email setup was entered on each workstation.  This is no longer the case in Atrex 17.  There’s a global email configuration as well as individual user configurations.  If you were previously using MAPI to send email from inside Atrex, or if you weren’t sending email from inside Atrex, no changes are necessary.  If you were using SMTP to send email from inside Atrex your email configuration must be re-entered.  Enter the global configuration under Options – Company Setup / Customization – Company Information and Settings – Email tab.  Optionally, enter individual user configurations under User – Edit User/Group.

Add Feedback