Knowledgebase: Server Administration
How to Upgrade Adams 5.5.1 or later
Posted by Diane Hancock on 17 March 2017 11:19 AM

Upgrade Steps

  1. Download the latest Updates release from: http://www.foray.com/support/downloads.php
    1. If you don't have a username and password then contact Support http://support.foray.com
  2. Prevent access to Adams from all users
    1. Block access to the database via the firewall
    2. Stop the AdamsAdmin pool
  3. Backup the repository
  4. Backup the database.
  5. Run Healthcheck.exe.
  6. Resolve any issues discovered by Healthcheck.exe.
  7. Update Configure Adams on the server running the database by running Configure ADAMS Setup.exe.
    1. If Adams Update Service is not running on that server and you are updating from 32-bit (i.e. pre-5.5) to 64-bit, copy the Foray.Adams.Config.xml from the 32-bit install location (e.g. C:\Program Files (x86)\Foray) to the 64-bit install location (e.g. C:\Program Files\Foray).
  8. Run Configure Adams
    1. If you get an Adams Admin error, try these steps to resolve it.
      1. In the Adams Admin bin directory (e.g. C:\inetpub\wwwroot\AdamsAdmin\bin), delete the Atalasoft.dotImage.WinControls.dll file if it exists.
      2. Restart the Adams Admin pool in IIS.  
      3. Close and reopen Configure Adams.
  9. Click Load Central Config
    1. If a database upgrade is needed then a message box will inform you and ask you to make sure you have a backup and that no one is using the system.
      1. If a backup has been done and if no one is using the system then allow the database upgrade to continue.
      2. After this database/repository upgrade no one will be able to use the system until their software has been upgraded to the current version.
    2. If a database has been updated or if an update is not needed a prompt may appear to upgrade the Repository
      1. Click OK
      2. You may continue with these instructions, and users may use the system, while the Repository is being upgraded.
    3. After any upgrades the central configuration will be displayed.
  10. Exit Configure Adams
  11. Delete all files and folders in the C:\Inetpub\wwwroot\AdamsAdmin\AdamsUpdates directory.
  12. Update Adams Admin on the server by running Adams Admin Setup.exe
  13. In IIS, stop the Adams Admin application pool (On some servers, it restarts after the installation)
  14. First, copy the Prerequisites folder and second, copy the EXE installer files to the C:\Inetpub\wwwroot\AdamsAdmin\AdamsUpdates directory. Note: This may be on a different server than the database.
    1. Do not copy any MSI files.  The Adams Admin installer installs the MSI's required.
    2. Do not delete any of the files and folders that the Adams Admin installer installed.
  15. Make sure that the update files have the correct permissions
    1. Right-click the AdamsUpdates directory and select Properties
    2. Select the Security tab
    3. Click Advanced
    4. Click "Change Permissions..."
    5. Check "Replace all child object permissions with inheritable permissions from this object"
    6. Click OK in all dialogs
  16. If the version upgrading from is pre-4.6, then in IIS, create a Virtual Directory called AdamsUpdates.  The physical location is the Adams Admin AdamsUpdates directory (e.g. C:\Inetpub\wwwroot\AdamsAdmin\AdamsUpdates).
    • If you see the following error in the Event log, then make sure the AdamsUpdates virtual directory was setup.
    • The Foray Adams transfer job: C:\Windows\TEMP\Foray Updates\Update Service Setup.msi encountered an error.

      Description: HTTP status 404: The requested URL does not exist on the server.

  17. In IIS, restart the Adams Admin application pool.  Note, anytime the prerequisites in the AdamsAdmin\AdamsUpdates folder are changed, the pool must be restarted in order for the changes to take effect.
  18. The Foray Adams Update Service, running on client and server machines, checks every 15 min for updates  
    1. To force a machine to download its updates either reboot the machine or re-start the Foray Adams Update Service.
    2. Note, the Foray.Adams.Config.xml used by the Foray Adams Update Service must specify an Adams Admin url or the service will write a warning to the Event log and terminate without updating anything.
  19. After Adams Web is updated, the applicable authentication mode needs to be re-enabled in IIS.  
    1. IIS > Sites > Default Web Site > AdamsWeb > IIS Authentication > select the Forms OR Windows authentication (whichever is the site's requirement) > Enable
    2. Recycle the AdamsWeb application pool

Troubleshooting

If an installation or automatic upgrade fails, get the log files.  Here's where to find them.

For a manual installation:
 
C:\Users\<username>\AppData\Local\Temp
 
You'll have to show hidden folders to see these folders.
 
For an automatic upgrade:
 
C:\Windows\Temp
 
Example of log file names for Configure Adams on an x64 machine: 
 
Foray_Configure_Adams_<datetime_info>_Setupx64.log
 
Foray_Configure_Adams_<datetime_info>.log
 
Sort by "Date modified" to get the latest log.  If there is more than one around the same time, get all of them.  Get the log with the "Setupx64" suffix and without.

Comments (0)