APM Command Center unable to start after upgrade to 10.7

Document ID : KB000095311
Last Modified Date : 11/05/2018
Show Technical Document Details
Issue:
After upgrading from APM Command Center (ACC) from 10.5 to 10.7, ACC is not able to start up.  The following error is seen in ACC log 'apmccsrv.log':

WARN 4353 [WrapperListener_start_runner] --- ationConfigEmbeddedWebApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'appInitializationBean' defined in URL [jar:file:/opt/ca/apm/ccs/lib/acc-configserver-ui.war!/WEB-INF/classes!/com/ca/apm/acc/configserver/config/AppInitializationBean.class]: Invocation of init method failed; nested exception is java.lang.IllegalArgumentException: Bad artifact coordinates com.ca.apm.agent.bundles.java:Custom Backends:zip:2afe3ba4:2017.2.26.0, expected format is <groupId>:<artifactId>[:<extension>[:<classifier>]]:<version>

INFO 4353 [WrapperListener_start_runner] --- o.e.jetty.server.handler.ContextHandler  : Stopped o.s.b.c.e.j.JettyEmbeddedWebAppContext@28f1ca2a{/,jar:file:///opt/ca/apm/ccs/lib/acc-configserver-ui.war!/,UNAVAILABLE}

ERROR 4353 [WrapperListener_start_runner] --- o.s.boot.SpringApplication               : Application startup failed

 
Environment:
Upgrade ACC from previous versions to 10.7
Resolution:
The problem is with a bundle having a space in the name.

In this example 'Custom Backends:zip:2afe3ba4:2017.2.26.0', which is used for artifact coordinate when upgrading the database and the space has a special meaning.  

Deleting the bundle in UI before and after upgrade does not help --  as it just marks the bundle as deleted, but does not delete it from database <ACC Home>/data/acc_data_h2.mv.db.

A script is created to change the name of bundles to replace space with a hyphen before the upgrade.

Contact CA Support for the script.  The problem will be addressed in a future version.