Uninstallation procedure
The use of this document assumes an understanding of the products being used (Windows, Oracle, SQL Server, and so forth).
Do not proceed if this is not the case.
The information contained in this document is given for reference only and must be tested before its use in a live situation.
This document summarizes the main steps to uninstall a complete SAFE X3 solution on a Windows server.
The console is used to deconfigure the components and the solutions. This deconfiguration is used to return the components to the same status as after their installation with InstallShield or IzPack. Their status then becomes 'idle'. It is only after this deconfiguration step that it is possible to uninstall them with the Add / Remove program function.
It is absolutely necessary to start by deconfiguring the linked servers (Web server and Print server).
For the moment, the database server remains intact (for security reasons).
Stop the following services:
Warning: The AdxAdmin must be uninstalled last because it contains information that is necessary for the uninstallation of other components (the status, among others). Do not stop this component during the uninstallation of other components. Note: this component is common to the solutions 14x, version 5, version 6, and version 7.
Sage SAFE X3 Runtime Component - Name of the component.
SAFE X3 V2 Print Server
Sage X3 Application Component - Name of the component.
SAFE X3 V2 Management Console.
If SQL SERVER database: Remove the Microsoft SQL Server 2012 (SID) program. If you want to retain the instance you can delete the SAFE X3 database using the "Enterprise Manager" administration tool.
Sage SAFE X3 AdxAdmin: to uninstall last and only if there are no more version 14x, version 5, version 6, or version 7 solutions configured.
Delete the folders for the product components (database, folders, runtime, console, and so forth).