Flowable version upgrade issue

Hi Team

We have upgraded to 6.5.0 and nowhere mentioned 6.5.0.6. Few services are deployed and few services are not getting deployed. Please guide.

Error creating bean with name ‘flowableAppEngine’: FactoryBean threw exception on object creation; nested exception is org.flowable.common.engine.api.FlowableException: Could not update Flowable database schema: unknown version from database: '6.5.0.6’

Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name ‘processEngine’ defined in class path resource [org/flowable/spring/boot/ProcessEngineServicesAutoConfiguration$AlreadyInitializedAppEngineConfiguration.class]: Unsatisfied dependency expressed through method ‘processEngine’ parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘flowableAppEngine’: FactoryBean threw exception on object creation; nested exception is org.flowable.common.engine.api.FlowableException: Could not update Flowable database schema: unknown version from database: ‘6.5.0.6’

Hey @sameer.uppal,

This question looks identical to FlowableException: Could not update Flowable database schema: unknown version from database: '6.5.0.6'.

The explanation about the different versions is explained in FlowableException: Could not update Flowable database schema: unknown version from database: '6.5.0.6'.

By the looks of it it seems like you didn’t upgrade all your services to 6.5.0.

Cheers,
Filip

@filiphr - Information is not clear as mentioned in the above link. Can you suggest where it is mentioned database ‘6.5.0.6’. we have mentioned in the configuration as 6.5.0 only not ‘6.5.0.6’
Kindly support.
we are stuck and not able to progress.

6.5.0.6 is the internal database version. All 6.5.0 versions have 6.5.0.x as internal version, see https://github.com/flowable/flowable-engine/blob/master/modules/flowable-engine-common/src/main/java/org/flowable/common/engine/impl/FlowableVersions.java#L111

The exception indeed seems to indicate a library version that’s incompatible (older) than the version that was installed in the database version.