When you apply a hot fix for SAS Marketing Automation 6.7 or SAS Marketing Optimization 6.7 on Windows, the Deploy Web Applications task in SAS^® Deployment Manager might fail with a configuration failure message.

Even if you select the Allow the application server to stop option during deployment, one or more web applications fail to deploy.

As a result, an error similar to the following occurs:

The following problem was encountered while configuring SAS Customer Intelligence Studio:

sas.customerintelligencestudio.war cannot be renamed.

Additional details might indicate that the WAR file is currently in use:

The file <ConfigDir>\Lev1\Web\WebAppServer\SASServer6_1\sas_webapps\sas.customer
intelligencestudio.war cannot be renamed. Please make sure this file is not in use.

The configuration failure window prompts the administrator to resolve the issue and click Retry.

Cause

During the Deploy Web Applications process, SAS Deployment Manager attempts to stop the application server before updating and deploying the web applications.

In some cases, on Windows, the SASServer6_1 service remains running even though you select the Allow the application server to stop option.

When the application server continues to hold locks on deployed WAR files, SAS Deployment Manager cannot rename or replace the existing files, which results in the configuration failure.

Resolution

1. Open the Windows Services console.
2. Locate the following service: SASServer6_1.
   
3. Confirm whether the service is still running.
   1. If the service is running, stop it manually.
4. Return to the configuration failure window in SAS Deployment Manager.
5. Click Retry.

The deployment should continue successfully once the file lock is released.

Verification

After the Deploy Web Applications task completes, do the following:

• Verify that all web applications deploy successfully.
• Confirm that the SASServer6_1 service restarted.
• Review the deployment logs for additional errors.
• Launch SAS^® Customer Intelligence Studio and confirm normal application access. 

Support Guidance

If the deployment fails with errors similar to the following during a hot fix deployment on Windows, verify whether the SASServer6_1 service was successfully stopped.

   <application>.war cannot be renamed

   or

   Please make sure this file is not in use.

In most scenarios, manually stopping the service and clicking Retry allows the deployment to continue without restarting the entire hot fix process.