Skip to Content
0

Update error messages when installing update of 4.2 SP05 (cms not starting and tomcat)

May 01 at 11:08 AM

100

avatar image
Former Member

Hi,

We have installed the 4.2 SP05 update on a 4.0 SP08 node (we have 2 nodes in cluster) on our development system and got the error messages below in errors and warnings log.

Mentions missing tomcat web.xml and cannot start cms- all was fine before including tomcat working and network connectivity o.k no firewalls and

Had a look for server dfo related errors but nothing obvious .

We had web.xml before so not sure why would go missing - not sure where could source a web.xml and the mentioned java.reg.key - possibly if look to extract 8.51.13 tomcat version to my own pc but reckon these unrelated to issue of cms not starting.


Would this solve our tomcat issue?

searched for cms not starting but we haven't firewall or network stopping it - was all o.k immediately before update.

Any thoughts on how can solve cms not starting issue?

errors below.

Errors/Warnings found during the installation are as follows 10:13:31.267 Error: Exception in Poco SpecialPropertybank 10:13:31.299 Error: Exception in Poco SpecialPropertybank 10:13:31.314 Error: Exception in Poco SpecialPropertybank 10:13:31.377 Error: At least one tomcat 6 config file was found, but not all tomcat 6 config files were found. Is tomcat corrupted? 10:13:31.377 Error: BackupTomcat6Config can't find tomcat6 web.xml ERROR: Could not establish a connection with any CMS. 10:31:27.678 *#*_*|ERROR: Could not establish a connection with any CMS.|ERROR: Could not establish a connection with any CMS.*_*#* ERROR: An unexpected internal error occurred. The CMS has terminated unexpectedly with exit code 0. (FWM 23025) *#*_*|ERROR: An unexpected internal error occurred. The CMS has terminated unexpectedly with exit code 0. (FWM 23025)|ERROR: An unexpected internal error occurred. The CMS has terminated unexpectedly with exit code 0. (FWM 23025)*_*#* 10:32:46.201 ERROR: Could not reach CMS '<server_name>:6400'. Specify the correct host and port and check for network issues. (FWM 20030) *#*_*FWM 20030|ERROR: Could not reach CMS 'BIDEV01:6400'. Specify the correct host and port and check for network issues. (FWM 20030)|ERROR: Could not reach CMS '<server_name>:6400'. Specify the correct host and port and check for network issues. (FWM 20030)*_*#* ERROR: Could not establish a connection with any CMS. ERROR: An unexpected internal error occurred. The CMS has terminated unexpectedly with exit code 0. (FWM 23025) 10:35:21.867 ERROR: Could not reach CMS'<server_name>:6400'. Specify the correct host and port and check for network issues. (FWM 20030) 10:35:22.257 Error: MigrateSSLWebXmlTo7 - missing source file: C:\bo4\tomcat6ConfBackup\web.xml 10:35:22.257 Error: syncUpTomcatMemorySettingsOnWindows - missing file: C:\bo4\tomcat6ConfBackup\tomcat6.java.reg.key Refer SCN link and SAP Notes for DFO related Errors Contact system administrator for other errors

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

6 Answers

avatar image
Former Member May 01 at 11:18 AM
0

When use central configuration manager on node 2 (as yet unupdated) can see that other services on node 1 have started successfully just the central management server service which failing to start for some reason

node2.jpg


node2.jpg (103.8 kB)
Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member May 01 at 11:27 AM
0

Looks like sap note below may apply regarding cms as clustered with 2 nodes but not sure about the Exception in Poco SpecialPropertybank message

2367507 - After updating SAP BI 4.x to BI 4.2 SP2 or afterwards, one of CMS servers cannot be started in a clustered environment

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member May 01 at 12:57 PM
0

Hi,

Reading the blog mentioned in the sap note suggest need to apply the update to all nodes first

https://blogs.sap.com/2016/01/13/bi42-new-license-key-requirement-when-updating-from-bi40bi41/


After finishing the update you need to update your license key within the Central Management Console. If you have a clustered system, you need to install the BI4.2 SP2 Update on all systems before proceeding with the next step.


Currently we have only updated node 1


If try login to node 2 which currently updated get meassge below.


com.crystaldecisions.sdk.exception.SDKException$PluginNotFoundAtCMS: The 422 plug-in does not exist in the CMS (FWM 02017)

Reckon we need to apply update to node 2 first of all before trying to update licence keys do you agree?

Thanks





Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member May 01 at 02:36 PM
0

Hi,

Just to advise, I stopped and restarted node 2 server which hadn't been updated.

This then allowed me to login to the CMC and remove the 4.0 licence keys and insert the 4.2 licence keys.

Now proceeding to update node 2 server.

Just need to deal with the tomcat issues which mentions missing web.xml file - we have a backup before install but not sure how this will differ to tomcat 8.5.13 version.

This just leaves the 3 issues below

1 ) 10:13:31.299 Error: Exception in Poco SpecialPropertybank

- anyone know what this is?

2) can we use the web.xml from tomcat 6? Not sure if any major diffs between this and tomcat 8.5.13 as yet

3)

10:35:22.257 Error: syncUpTomcatMemorySettingsOnWindows - missing file: C:\bo4\tomcat6ConfBackup\tomcat6.java.reg.key

not sure what this file is - cannot see in backup area in first place.

Thoughts on this one

Thanks

Share
10 |10000 characters needed characters left characters exceeded
Jawahar Konduru May 01 at 12:45 PM
0

Did you add the license and tried?

Show 1 Share
10 |10000 characters needed characters left characters exceeded
Former Member

However note further down blog mentions – thus bit confused if we should attempt node2 update yet.

However cannot login to node 2 to update licence key due to 02017 error mentioned

Applying BI4.2 SP2+ in a clustered environment

If you are updating your existing BI4.0 or BI4.1 Clustered deployment, please follow the steps as mentioned below to ensure a successful deployment of the BI4.2 update..

  1. Determine you primary system (running a CMS)
  2. Stop all other nodes within your deployment
  3. Update you primary system, delete the old 4.0/4.1 license key and add the 4.2 license key.
  4. Start other nodes and update them accordingly

Enable all servers

0
Jawahar Konduru May 01 at 03:39 PM
0

Did you stop Node2 while updating Node1?

Show 2 Share
10 |10000 characters needed characters left characters exceeded
Former Member
don't recall doing so - is this why had to stop and restart node 2 to get it to work?

0

These are the best practices. if we don't follow them, there is a chance system will get corrupted.

0