Upgrading Teamsite 7.2 to 16.2 on Windows server 2012

I am upgrading Teamsite from version 7.2 to 16.2 on Windows Server 2012. All the war file are getting deployed at /standalone/deployments folder except "wcm-service.war". I got the below error on server.log:

ERROR org.springframework.web.context.ContextLoader () - Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'createEStudioCache' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Invocation of init method failed; nested exception is com.hp.wcm.blc.BranchConfigCSException: Branch Config CSException:
WFLYCTL0186: Services which failed to start: service jboss.undertow.deployment.default-server.default-host./wcm-service

Has anyone experienced this before and if so can you please help me in resolving the issue. I have looked through the devnet and couldn't find a complete solution for the current version. Thank you in advance

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

All comments

nipper

Did you install EStudio ?

Try running the install again and see if there are other components you need to add.

I would also open a ticket with support as not many people go from 7.2 to 16.2 and I am not certain that is a valid upgrade path.

Prashanth Shetty

Rajesh, did you find a resolution to this error?

HeatherH

16.2 has a required QSU (WCM-7504) unless you install a service pack (16.2.0.1, 16.2.0.2, etc). EStudio should also be installed.
If that does not resolve the issue, I'd recommend opening a support case.
Also: 7.2>16.2 is not supported, you would have to migrate the content on a fresh install, which I assume is what was done, since you're running on Win2012 (not supported as far back as 7.2).

Prashanth Shetty

This was a content store issue. It got resolved once we remigrated a store from current TS 7.5 server to new 16.3 TS server. Probably it didn't get copied properly first time.

Paul_Anderson

Hi - we too are affected by this - copying (via a robocopy /MIR) a content store from 7.2.1 and 7.4.1.4 onto new infrastructure Windows 2012 rigs running Teamsite 16.2.0.1 inc QSU10177.

We may also try recopying the store (as we have a copy from 7.4.1.4 which experienced no issues at all when moving to 16.2.0.1)

At first the symptom was WCM-Service.war failing to deploy due to issues unable to locate directories in the eStudio branch (which is missing in 7.2 default store)

Working on a support ticket OT asked us to run the following CLT's which re-created the eStudio branch and folder structure - however, it didn't cure the issue.

\Autonomy\WCMService\install_scripts\estudio_global_project_install.bat -i \Autonomy\TeamSite \Autonomy\WCMService
\Autonomy\WCMService\install_scripts\estudio_global_project_blc_config.bat \Autonomy\Teamsite \Autonomy\WCMService

We then saw that we were getting permission denied errors on folders such as ..

/iwconfig/main/wwwsites/WORKAREA/iw-wa/estudio/estudio.properties

and additional errors in the WCM-Service.log below (having run and imported iwidmap) :

Caused by: com.interwoven.cssdk.access.CSInvalidUserException: Unknown Hopi error(No such user)

Paul_Anderson

sorry should have said failures for branch missing were when running make_toolkit or build.bat

nipper

That is basically running this:

$IW_HOME/iw-perl/bin/iwperl $IW_HOME/install/install_archive.ipl $param $WCMSERVICE_HOME/spar/EStudioGlobal.spar /default/main/EStudioGlobal/WORKAREA/default

You can try to run that on a different branch.

I assume you were running that as Administrator. Looks like a permissions issue.

Prashanth Shetty

Paul, in our case it was a store issue. As you mentioned support asked to run those scripts to create EStudio Global branch. When we tried to run that script it created global branch in the backend but UI could not read that branch. We could view global branch through file system but could not access anything inside it.
We also tried creating a test branch from UI and it came back with a blank screen on UI. So we decided to remigrate the store, validate and run these scripts to resolve this issue.