000015304 - RSA Authentication Manager 7.1 Service Pack 4 installation fails with locked database file errors

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000015304
Applies ToRSA Authentication Manager 7.1 on all supported platforms
Service Pack 4 (SP4)
Issue

RSA Authentication Manager 7.1 SP4 installation fails with the following error:
The installation has failed.
Check for locked Database files failed.



The patch_install.log file (default location c:\program files\RSA Security\RSA Authentication Manager\logs) shows the following error:
(Jan 17, 2011 7:43:45 PM), Install, com.installshield.rsa.ippi.install.actions.product.CheckOracleLockedFiles, msg1, Checking for locked Database files.
(Jan 17, 2011 7:43:47 PM), Install, com.installshield.rsa.ippi.install.actions.product.CheckOracleLockedFiles, msg1, Database File is locked: C:\PROGRA~1\RSASEC~1\RSAAUT~1\db\BIN\oraevrus10.dll
(Jan 17, 2011 7:43:48 PM), Install, com.installshield.rsa.ippi.install.actions.product.CheckOracleLockedFiles, err, Check for locked Database files failed.
(Jan 17, 2011 7:43:48 PM), Install, com.installshield.rsa.ippi.install.actions.product.CheckOracleLockedFiles, err, Check for locked Database files failed. Look at the log file C:/PROGRA~1/RSASEC~1/RSAAUT~1/logs/patch_install.log for details.
(Jan 17, 2011 7:43:48 PM), Install, com.installshield.rsa.ippi.install.actions.product.CheckOracleLockedFiles, err, ProductException: (error code = 601; message="err"; additional data = [Check for locked Database files failed.])
STACK_TRACE: 13
ProductException: (error code = 601; message="err"; additional data = [Check for locked Database files failed.])
at com.installshield.rsa.ippi.install.actions.product.CheckOracleLockedFiles.doInstall(CheckOracleLockedFiles.java:76)
at com.installshield.rsa.ippi.install.actions.product.RSATestableProductAction.install(RSATestableProductAction.java:14)
at com.installshield.product.service.product.PureJavaProductServiceImpl.installProductAction(Unknown Source)
at com.installshield.product.service.product.PureJavaProductServiceImpl$InstallProduct.getResultForProductAction(Unknown Source)
at com.installshield.product.service.product.InstallableObjectVisitor.visitComponent(Unknown Source)
at com.installshield.product.service.product.InstallableObjectVisitor.visitInstallableComponents(Unknown Source)
at com.installshield.product.service.product.InstallableObjectVisitor.visitProductBeans(Unknown Source)
at com.installshield.product.service.product.PureJavaProductServiceImpl$InstallProduct.install(Unknown Source)
at com.installshield.product.service.product.PureJavaProductServiceImpl$Installer.execute(Unknown Source)
at com.installshield.wizard.service.AsynchronousOperation.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

 
CauseThis is caused by third-party system monitoring software installed on the server. In this case, SNARE was locking oraevrus10.dll.
Resolution

The following methods resolve this issue:


  • Disable the SNARE service, along with any other third party applications that can lock files (such as Antivirus, backup agents, system monitoring or management, snapshots, etc), and reboot the server. Then apply SP4 again.
  • Renaming oraevrus10.dll prior to installation resolves this issue. For more information, see solution a53706.
Notes

To identify the executable file that is locking Oracle DLLs:


  1. Download Process Explorer from Microsoft.
  2. Launch Process Explorer.
  3. Press Ctrl-F, enter the DLL filename that was identified as being locked in the patch log or Oracle log.
    This identifies the *.exe file that is causing the upgrade failure.
Also see A53796
 
Legacy Article IDa53790

Attachments

    Outcomes