Resolution:
Description:
============
TIBCO BusinessEvents engine fails at start up after applying hotfix.

Environment:
============
TIBCO BusinessEvents 5.1.1
All Operating Systems

Symptoms:
=========
After applying any hotfix, the following error is thrown at engine startup:
*************************************************
2013 Aug 28 14:00:21:779 GMT -5 PrivateIP Fatal [main] - [container.standalone] null
java.lang.AbstractMethodError
    at com.tibco.cep.studio.core.repo.emf.DeployedEMFProject.preload(SourceFile:295)
    at com.tibco.cep.studio.core.repo.emf.EMFProject.load(SourceFile:213)
    at com.tibco.cep.studio.core.repo.emf.DeployedEMFProject.load(SourceFile:207)
    at com.tibco.cep.runtime.session.impl.RuleServiceProviderImpl.initProject(RuleServiceProviderImpl.java:990)
    at com.tibco.cep.container.standalone.BEMain.jumpStart(SourceFile:146)
    at com.tibco.cep.container.standalone.BEMain.main(SourceFile:69)
*************************************************


When checking the installation log, the following Warning and Info can be found:
*************************************************
(08-28-2013.101238), ::INFO::, verifying C:\tibco-be\_installInfo\vcredistx642010_1.0.0.001_prodInfo.xml
(08-28-2013.101238), ::INFO::, installed version is: 1.0.0
(08-28-2013.101238), ::INFO::, required version is: 1.0.1.0
(08-28-2013.101238), ::WARNING::, installed version comparison failed., class com.tibco.installer.util.TIBCOCheckUIDExists
(08-28-2013.101238), ::INFO::, the feature dependency null is not currently installed.
(08-28-2013.101238), ::INFO::, setting wizard action property: featureUID=Process Modeler Hotfix 3_businessevents-hf
(08-28-2013.101238), ::INFO::, setting wizard action property: isEnabled=true
(08-28-2013.101238), ::INFO::, setting wizard action property: isVisible=true
(08-28-2013.101238), ::INFO::, setting wizard action property: isSelected=false
(08-28-2013.101238), ::INFO::, calling run method
(08-28-2013.101238), ::INFO::, featureUID = Process Modeler Hotfix 3_businessevents-hf
(08-28-2013.101238), ::INFO::, isEnabled = true
(08-28-2013.101238), ::INFO::, isVisible = true
(08-28-2013.101238), ::INFO::, isSelected = false
(08-28-2013.101238), ::INFO::, setting feature enabled: Process Modeler Hotfix 3 = true
(08-28-2013.101238), ::INFO::, setting feature visible: Process Modeler Hotfix 3 = true
(08-28-2013.101238), ::INFO::, setting feature selected: Process Modeler Hotfix 3 = false
(08-28-2013.101238), ::INFO::, sequence = post-selection
(08-28-2013.101238), ::INFO::, actionClass = com.tibco.installer.wizard.action.TIBCOSetFeatureStateWizardAction
(08-28-2013.101238), ::INFO::, conditionClass = com.tibco.installer.wizard.condition.TIBCOCheckDependencyWizardCondition
(08-28-2013.101238), ::INFO::, setting condition property: mustBeMet=false
(08-28-2013.101238), ::INFO::, setting condition property: uid=Process Modeler SP 1_businessevents-process
(08-28-2013.101238), ::INFO::, setting condition property: type=feature
(08-28-2013.101238), ::INFO::, setting condition property: version=1.0.1
(08-28-2013.101238), ::INFO::, setting condition property: mustBeInstalled=true
*************************************************

Cause:
============
When checking the intall info folder, you can find Process Orchestration 1.0.0 is installed but 1.0.1 is not installed. The hotfix installer would check for the service pack and that is probably why the Process jars for the hotfix did not get installed and are still referring to the older process jars from 1.0.0.


Resolution:
==========
Follow the steps below:

-Uninstall whatever Hotfix is installed.

-Install Process 1.0.1

-Re-install HF (and do a studio –clean –initialize after HF installation).

Or uninstall Process 1.0.0 if it's not required.

Note:
The files in _installInfo folder show the current state of TIBCO_HOME, showing which assemblies and products are present. Assembly files look like be-server_5.1.1.072_prodInfo.xml and product files look like businessevents-standard_5.1.1_prodInfo.xml. If the files are present, then that particular product/assembly will be present in that HOME directory. Given the above state of the TIBCO_HOME, the install log files should be analyzed to see what happened during install. In most cases the sections related to dependency check success or failure should be looked at. The file also shows the installer version used.