The following message might appear in the SAS Deployment Wizard configuration logs if the configuration of the middle-tier server fails and you restart it without removing the configuration from the SAS^® Metadata Server:

[echo] INFORMATION: Metadata Deployment process started at Tue Aug 25 14:18:37 GMT+08:00 2009.
[echo] INFORMATION: The following object did not meet the restriction IsUnique (SAS Web Infrastructure Platform)
[echo] INFORMATION: Metadata Deployment process ended at Tue Aug 25 14:18:38 GMT+08:00 2009.
[echo] Return Code: 4

For example, this message might appear in the log file that is named webinfpltfm_configure_yyyy-MM-dd-hh.mm.ss.log.

To prevent this failure and message, you must revert the server tier back to the state that it was before you started the middle-tier configuration, as follows:

1. Stop all of the SAS processes on the server tier.
2. Delete the Lev1 directory on the server tier.
3. Reconfigure the server tier.
4. Once reconfiguration is complete, back up the Lev1 directory on the server tier.
5. Start all SAS servers on the server tier.
6. Stop all of the SAS processes on the middle tier. Examples of such processes include the following:
• the JBoss application server
• the Oracle WebLogic application server
• the IBM WebSphere application server
• SAS Remote Services
7. Delete the Lev1 directory on the middle-tier server.
8. Restart the SAS Deployment Wizard.
9. Configure only the middle tier.

Operating System and Release Information