Upgrade Failure on Critical System Protection Due to Files In Use
|Article:TECH211011|||||Created: 2013-09-27|||||Updated: 2013-09-27|||||Article URL http://www.symantec.com/docs/TECH211011|
Upgrade failure Critical System Protection Agent using a install script or 3rd party tool. If the install is run in silent mode, no errors are thrown in the GUI. A side effect may be a blank \IPS\agent.ini file.
From the SISAgentSetup.log:
MSI (s) (A8:FC) [00:04:00:795]: Product: Symantec Critical System Protection Agent. The file C:\Program Files
MSI (s) (A8:FC) [00:04:01:981]: Product: Symantec Critical System Protection Agent. The file C:\Program Files
This behavior has been observed on various Windows platforms. May also occur on Unix if the CSP Daemons are automatically started by a 3rd party tool.
This can occur if the environment has 3rd party tools that prevent services from stopping, or automatically restart services that have been stopped. The SCSP upgrade process stops the agent services during the install, and if a 3rd party tool restarts the SCSP services during the install, the install will fail because the files will be in use.
Often, because many these 3rd party tools run a check for stopped services every X minutes, the installation can succeed on some machines, and fail on others in a large environment because the install may complete between the intervals in which the 3rd party tool runs.
Ensure that there are no service monitoring tools running during the upgrade process.
Article URL http://www.symantec.com/docs/TECH211011