Program Updates

How to Update Program Files using the 212 Internet Updater

Please be advised that the Modules to Check option in the 212 Internet Updater is restricted to customers on a current maintenance support agreement. Customers who do not have a current support agreement are only eligible for the Free Updates option in the Internet Updater. If you are interested in our support plans, please go to our Support Plans page.

The following instructions apply to 321™. Customers using 212 versions 3.20™ or 3.10™ and users of CAManager and Maintenance Manager stand-alone should refer to the steps under the Implementation section for all updates.

Keeping the 212 program files for all of your users up-to-date in a networked environment can be challenging. 212 Software provides two mechanisms to update program files, the 212Internet Updater, and the Update Workstation from Server feature. But when is the appropriate time to use each, and who should be doing what?

Network Administrator – The Network administrator's responsibility is to update the server and the remote host server (if you have one and it is a different machine from the primary data server). The server should ALWAYS be the most up-to-date machine in your office. 212 Software recommends that you schedule the updates to run once per month (Starting 2007 updates will be released monthly). If you are updating manually, please ensure that you are logged in locally on the system with administrative rights. If you are not certain that you have administrative rights, run the "readon.bat" file under the TOPS 2000 directory on the server. If you do not have rights, a list of files stating "Access Denied" will appear on the screen.

If the updater fails to update some or all of the files that are slated to be updated, this is most likely because the non-updated files are locked open by a user. Ask all users to end their session, close 212 and then re-open it and run the updater again. This may resolve the problem, if it does not, reboot the server (to force Windows to release all file reservations) and then run the updater.

To Schedule the Updater to Run Automatically on Your Server(s)*:

Please Note, that the system on which the Scheduler is set to run must not be turned off, in hibernation mode or in sleep mode at the time that the job is scheduled to run. From the Calendar / Scheduler screen, click on Control Info then Scheduler Settings and make sure you have the "Use 212 Scheduler" option checked. Refer to the "Using Calendar/Scheduler" section in the User Guide located on our User Manual Downloads page. Procedure using Calendar / Scheduler:

1. Access your server where your 212 data resides.
2. In 212, click Automate > Scheduler > Schedule Tasks.
3. The 212 Scheduler will open after a moment.
4. Click the drop down in the upper left and select Internet Services.
5. Click the blue Add button in the upper right.
6. Set the Type to Internet Updater.
7. Enter a name, such as "Update 212 Program Files".
8. Set the Start Date to be the first day on which you wish to run this task. (The first day of each month recommended)
9. Set the Time to when you wish to have this task start. (This time should be very late or very early, when no users will be connected and logged in to the system.)
10. Click Next.
11. Set up Recurrences to Monthly on Day 1 of every 1 month.
12. Click Finish.

* If you are unable to run the scheduler on your server, you may set up the update schedule on a single workstation. This will automatically update both the server and that workstation.

Local Network User – Users who work in the same location as the Data Server (or use a hardware VPN) should perform passive updates. Each time the server is updated via the 212 Internet Updater, the user will be prompted when they log into 212: "Server files are newer. Select Yes to Update." The user simply clicks 'Yes' to receive the newer files from the server. It is unnecessary for an individual workstation to be updated via the updater. Certain occasions may call for it however, such as receiving a beta program, or performing a major version update.

A common issue that 212 Support encounters is unevenly distributed updates across a network, causing mismatched versions of the 212 Program files. In all cases, it is better to have the same version of 212 Files on the server and all workstations than it is to be completely up-to-date on a few machines.

zRemote Users – Users who connect from a location outside of the network (telecommuting, other offices, off-site, etc) should NOT run updates. Instead, it is the administrator's responsibility to make sure that each time the Primary Data Server is updated, the Remote Host Server be updated as well. If a remote user attempts to perform an update, 212 will attempt to update the entire remote host machine. This will often be unsuccessful if the user does not have the rights to overwrite files on the server, or if other users are also connected to the remote host, and using files that need to be updated.