Direct links to fixes
Tivoli Storage Productivity Center 5.2.7 (select fixes from group)
IBM Spectrum Control V5.2.8 (December 2015)
IBM Spectrum Control V5.2.9 (February 2016)
IBM Spectrum Control V5.2.10 (May 2016)
IBM Spectrum Control V5.2.10.1 (July 2016)
IBM Spectrum Control V5.2.11 (August 2016)
IBM Spectrum Control V5.2.12 (November 2016)
IBM Spectrum Control V5.2.13 (March 2017)
IBM Spectrum Control V5.2.14 (May 2017)
IBM Spectrum Control V5.2.15 (August 2017)
IBM Spectrum Control V5.2.15.2 (November 2017)
IBM Spectrum Control V5.2.16 (March 2018)
IBM Spectrum Control V5.2.17 (May 2018)
APAR status
Closed as program error.
Error description
Those upgrading to TPC 5.2.x on Windows when at WAS component upgrade, there's still at least one WAS process that holds a lock on a file/folder under <TPC_installation_dir>\ewas. This can happen especially if Windows Event Viewer is open (or third-party tools which provide a similar function) and is browsing WebSphere-related entries in the Windows Event Log. Due to that Windows Event Viewer, sometimes the file <TPC_installation_directory>\ewas\bin\WASServiceMsg.dll (e.g. C:\Program Files\IBM\TPC\ewas\bin\WASServiceMsg.dll) becomes locked, which causes the "Sharing violation" error from below. If the customer encounters something like this in the installer log file (latest lax-out or traceTPCInstall.log) then it's almost sure that it's the same issue as the one in the APAR. date and time Execute:Java13CommandLauncher: Executing 'cmd' with arguments: '/c' 'xcopy' '/e' '/i' '/q' '/y' '/h' 'drive letter:\temp\TPC_5.2.5.1\TPC\was\ewas\*' 'drive letter:\IBM\TPC\ewas' The ' characters around the executable and arguments are not part of the command. date and time Sharing violation date and time ERROR StatusUpdater targetFinished org.apache.tools.ant.BuildException exec returned: 4 drive letter:\IBM\TPC\config\install\tpcwas.xml:81: exec returned: 4
Local fix
The problem can be resolved by: 1. Rename the current <tpc_home>\ewas directory to ewas_orig 2. Copy the entire <installation_media>\was\ewas directory into <tpc_home>. 3. Copy/Replace the contents of the renamed <tpc_home>\ewas_orig directory into the newly created <tpc_home>\ewas directory. This restores configured and customized files into the generic ewas necessary to build the profiles. 4. Restart the TPC installer. The installer should continue as expected.
Problem summary
**************************************************************** * USERS AFFECTED: * * Those upgrading to TPC 5.2.x on Windows when at WAS * * * * component upgrade, there's still at least one WAS process * * * * that holds a lock on a file/folder under * * * * <TPC_installation_dir>\ewas. * **************************************************************** * PROBLEM DESCRIPTION: * * Those upgrading to TPC 5.2.x on Windows when at WAS * * * * component upgrade, there's still at least one WAS process * * * * that holds a lock on a file/folder under * * * * <TPC_installation_dir>\ewas. * * This can happen especially if Windows Event Viewer is open * * (or third-party tools which provide a similar function) and * * is browsing WebSphere-related entries in the Windows Event * * Log. * * Due to that Windows Event Viewer, sometimes the file * * <TPC_installation_directory>\ewas\bin\WASServiceMsg.dll * * (e.g. C:\Program Files\IBM\TPC\ewas\bin\WASServiceMsg.dll) * * becomes locked, * * which causes the "Sharing violation" error * **************************************************************** * RECOMMENDATION: * * Apply fix maintenance when available. * ****************************************************************
Problem conclusion
The fix for this APAR is targeted for the following maintenance package: refresh pack | 5.2-TIV-TPC-RP0007 - target August 2015 http://www-01.ibm.com/support/docview.wss?&uid=swg21320822 The target dates for future refresh packs do not represent a formal commitment by IBM. The dates are subject to change without notice.
Temporary fix
The problem can be resolved by: 1. Rename the current <tpc_home>\ewas directory to ewas_orig 2. Copy the entire <installation_media>\was\ewas directory into <tpc_home>. 3. Copy/Replace the contents of the renamed <tpc_home>\ewas_orig directory into the newly created <tpc_home>\ewas directory. This restores configured and customized files into the generic ewas necessary to build the profiles. 4. Restart the TPC installer. The installer should continue as expected.
Comments
APAR Information
APAR number
IT09588
Reported component name
TPC
Reported component ID
5608TPC00
Reported release
524
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-06-29
Closed date
2015-06-29
Last modified date
2015-06-29
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
INSTALL
Fix information
Fixed component name
TPC
Fixed component ID
5608TPC00
Applicable component levels
Document Information
Modified date:
05 October 2023