Steps to Do a Quick ABM Server Reinstall/Refresh

How to Perform SAS Activity-Based Management® Server 6.4Repair

When ABM Server Component becomes corrupt (due to updates done to the server since last install), you need to repair it by doing a quick ABM Server Reinstall procedureas outlined below.

Preliminary Step (if you use SAS OLAP instead of Microsoft Analysis Server to generate OLAP cubes)

At the end of the repair process, you need to specify the following parameters:

Metadata Server

OLAP Server

So one easy way to make a note of the parameters is by capturing a screenshot of the ABM System Information report (available through “Server Diagnostics”)

1. Backup ABM Databases (if you do not have any backups)

• If using Microsoft SQL Server:

Within SQL Enterprise Manager right click on the database (OEModels and OEAdmin) and find “Backup Database” – for more details on general SQL Server backup/restore procedures, check with your DBA.

• If using Oracle:

Backup the entire ABM Database User schema (typically it’s called “SASABMDBUSER”) – for more details on the general Oracle backup/restore procedures, check with your DBA.

2. Remove “SAS Activity-Based Management Server”

• Remove “SAS Activity-Based Management Server”

• ABM Uninstaller will ask you whether to delete the ABM database or not. Choose “Don’t Delete”.

• Once uninstall is done, reboot the ABM server.

3. Reinstall “SAS Activity-Based Management Server”

• From the ABM CD/Setup Folder, run start.exe and choose Install SAS Activity-Based Management

• Specify the same original location (i.e. C:\Program Files\SAS).
• On the following Window, specify any valid passwordthat complies with your security policy.

• On the following Window, check Skip database and user creation. They are already created.

• On the following Window, choose “Upgrade”. This option will keep your original database intact.

• You will finally reach the Setup Complete window – click Finish.

• If you use Microsoft Analysis server, choose Do not use Metadata server – otherwise, specify the Metadata Server parameter (see Preliminary Step section on top of this document).

• Server Unit Tests will display some test errors (Exception has been thrown by the target of an invocation).

• The above test errors are expected because your Windows Server may not able to start the SAS Remoting Service automatically. So start that service manually (Control Panel > Administrative Tools > Services).

• Once you re-run the Server Unit Tests and you get Total tests failed: 0, you did it!Good job.