Wednesday 16 May 2012

upgrade-profile BUILD FAILED create-resource-environment-provider-custom-property

I upgraded the CF level to CF12 on IBM WebSphere Portal 7.0.0.2  after WASPostUpgrade and database validation and connection task.
But the ConfigEngine.bat upgrade-profile  task failed on the following line:


create-resource-environment-provider-custom-property:
Tue May 15 14:28:53 EDT 2012
     [echo] ,people.api/common,wp.search.webscanner
     [echo] ,prereq.wcm
     [null] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!   ERROR !!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!
     [null] The extension create-resource-environment-provider-custom-property i
s registered for component prereq.wcm but the implementation does not exist.
     [null] The component prereq.wcm must implement the target action-create-res
ource-environment-provider-custom-property-applyMIGStatic-prereq.wcm
**********************************************************************
Migration extension 'create-resource-environment-provider-custom-property' execu
tion failed
**********************************************************************

BUILD FAILED
C:\IBM\WEBSPH~1\PORTAL~1\installer\wp.migration.framework\config\includes\mig_cf
g.xml:85: The following error occurred while executing this line:
C:\IBM\WebSphere\wp_profile\ConfigEngine\config\actions\adv_cfg_mgr.xml:1789: Co
mponent prereq.wcm is missing implementation target action-create-resource-envir
onment-provider-custom-property-applyMIGStatic-prereq.wcm

Total time: 19 minutes 59 seconds
FAILURE_LOG_DIR=null
isIseries currently set to: null
uploading registry
CELL: DefaultNode
NODE: DefaultNode
Websphere:_Websphere_Config_Data_Type=Registry,_Websphere_Config_Data_Id=cells/D
efaultNode|registry.xml#Registry_1247599550767,_WEBSPHERE_CONFIG_SESSION=anonymo
us1337106535621
 

update-registry-sync-property:
Tue May 15 14:28:56 EDT 2012
     [echo] updated RegistrySynchronized in file wkplc.properties with value: tr
ue
Return Value: 1



Solution:
After upgrading to CF12 we need to run upgradeConfigEngine.bat again. This will resolve the issue.

No comments:

Post a Comment