Product Update:
Product updates are provided quarterly and may include both product fixes and enhancements to the Sage 500 ERP application. Product updates are cumulative and include previous updates for the same version.
Hot Fix:
A hot fix is an unscheduled correction for an issue requiring immediate attention. It includes unique and accumulated functionality corrections and enhancements, with the accumulation of fixes originating from previous monthly updates and hot fixes. A hot fix update has a dependency only on application of a product update for the version being used, if one exists, but does not change the base version number. The hot fix, accompanied by release notes and installation instructions, is posted on the Sage 500 ERP support website.
Installation Issues:
Review the detailed installation instructions that are provided with the item posted on the Web site. The server portion or an update should be applied prior to application of the update to individual client machines. Sage 500 ERP performs a version compatibility check to ensure system integrity
An effective method to verify the integrity of an update on your system is to apply it to a test server, apply it to a test client, then connect to the server from the client to review functionality changes contained in the release notes.
Product updates and hot fixes generally do not affect the Sage 500 ERP Database Utilities, but do affect client programs, database objects or Internet applications pages and components.
Server Uninstall:
The only way to reverse the application of the server side product update is to restore the databases from backup. The backup must have been created before the application of the update. Both the application and system databases must be restored, at minimum. The files can be uninstalled by selecting the uninstall option for the component from within Control Panel, Add/Remove Programs.
Client Uninstall:
Product updates applied to a Sage 500 ERP client workstation cannot be removed individually. Instead, uninstall the Sage 500 ERP application and reapply the prior product updates to restore the application back to the point in time before the installation of the latest product update
General Information:
Product Updates are generally applied to the databases and clients. The versions must match since the client does check the database version for compatibility. Back up the databases before applying an update, and apply the update to a test database set prior to application to the production databases. When the database update is complete, apply the update to a single client workstation and test the application. Review the release notes that accompany the update for information on the issues corrected.
Occasionally, updates are also made available for the Internet applications. Review the release notes, but these generally require application to the IIS (Internet information server ) upon which the Internet applications have been installed.
The Web Reports Internet application is another form of the client software that has been engineered to display reports via a Web site. Whatever updates are applied to the databases must be applied to the Web Reports server. Generally, the Web Reports client produces an error message or hangs if the client version does not match the database version.
History:
A history of the application of update and upgrade activities is recorded in the tsmDBHistory and tsmDBHistoryDetl tables in the application database. To obtain this information, execute the following query in new query window against the application database.
Note: The following procedures assume certain knowledge of Microsoft SQL Server and/or Transact SQL. Sage Customer Support is not responsible for assisting with these procedures and cannot be responsible for errors that may occur when changes are made directly to the SQL server. Be sure to back up all pertinent databases before making changes. Contact an authorized business partner or database administrator for assistance.
Simple History:
SELECT *
FROM tsmDBHistory WITH (NOLOCK)
ORDER BY EventStartTime
Detailed History:
SELECT *
FROM tsmDBHistory a WITH(NOLOCK)
JOIN tsmDBHistoryDetl b WITH(NOLOCK)
ON a.DBHistoryKey = b.DBHistoryKey
ORDER BY a.EventStartTime
Customization Issues:
Prior to applying any update, review the release notes. This document contains information regarding issues corrected within the update. Also detailed are the objects, Crystal Reports, Visual Basic projects and T-SQL stored procedures in which the source code has been modified to accommodate the changes. The update generally overwrites the source code for the objects specified.
Crystal Reports:
If a Crystal Report that has been customized is mentioned in the release notes, rename the report on all client workstation or create a backup of the file before applying the update. After the client update completes, review any changes in the new report to determine if they must be incorporated into the customized report, then copy or rename the report back to its original location and test the modified report. Try comparing the reports using the File, Print, Export, Report Definition format within Crystal Reports.
VB Source Code:
Visual Basic(VB) source code modifications can be made by developers that obtain the Customization Tools and module source code. Again, examine the Release Notes to determine if changes have been made to any customized VB projects. Obtain the affected source code from the Web site to incorporate code changes into the customizations. After these changes are applied, and the source code has been compiled, apply the update, then copy and register the customized project and test the modified code.
SQL Procedures:
T-SQL procedure changes can be made within the database by developers or administrative users. Examine the release notes to determine if changes have been made to any customized stored procedures, triggers or schema. Obtain the source code from the Web site to incorporate code changes into the customizations. After these changes have been identified, either apply the update and recompile the modified procedures, or incorporate the customizations into the files installed with the server portion of the update then test the modified code.
Customizer Form Modifications and Scripts:
Form modifications and scripts completed within the Customizer module generally are not affected by the application of an update. Review the release notes to determine if any customized forms may be affected by the update. After applying the update, test the modified forms.
Errors:
If a problem is encountered in the application of an update at the server, the database version is set to a suffix of 999. The error would be contained in the log produced by the update, or can be reviewed in the database history (see above). Action is required since the client and server version would no longer match and users would not be able to log into Sage 500 ERP.
Depending on the nature of the issue, and the update being applied, restore the databases from backup. This is especially true with the application of service packs since they generally contain more extensive object, and sometimes schema updates. The database version is stored in tsmModule.VersionNo. If a non-fatal error has occurred, you can update this column with the client version and reapply the update using the following query. This update statement should be used only when a non-fatal error has occurred.
UPDATE tsmModule SET VersionNo = ''
Additional Information:
The versions accommodated by the server update installed are noted in the Program Files (x86)\Sage Software\Sage MAS 500 Server Update\DBUpdate.dat file. The Sage 500 folder ERP changes according to the update installed. The DBUpdate.dat file is text file that can be read with any text editor.
To check the version of the client, right-click \Program Files\MAS 500 Client\EnterpriseRes.dll, select 'Properties', and click the 'Version' tab