Skip to Content
0

BO 4.2 SP05 install error screenshot + licence

May 11 at 08:49 AM

93

avatar image
Former Member

Hi,

On one of our development environments ( 2 node cluster), updated bo from 4.0 SP08 to 4.2 SP05.

Got attached screenshot on first node when running the update process on the first node - error/warning log mentioned couldn't start the CMS ( cms was running at start of this).

install-screenshot.jpg

This looks to be due to fact that 4.0 and 4.2 different licence key and once 4.2 update ran on a node, cannot start cms on that node with 4.0 licence key.

Update shows as having been installed in control panel/add programs and looks to be working o.k/ - new features were showing in CMC after this ( could log into CMC using node 2 which was still at 4.0 SP08 as licence keys were 4.0)

Have a couple of questions

1) I assume fact listed in control panel/programs that it has fully installed as cms and servers now running on this node with updated 4.2 licence key and error just relates to this.

Is this the case?

I assume it bo cannot install update at all doesn't get registered in control panel/add remove programs

2) Wonder as to whether removing licence keys entirely before running any future update, then update then update licence key afterwards would remove such errors or would this remove ability to login to CMC entirely if no licence keys?

Thanks

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

3 Answers

Mohammed Ashraf
May 11 at 09:28 AM
0

Hi,

Click on the details to see what exactly is the error, is related to license key or other error.

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
  5. Enable all servers

Nice blog on New License Key Requirement when updating from BI40
https://blogs.sap.com/2016/01/13/bi42-new-license-key-requirement-when-updating-from-bi40bi41/

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member May 11 at 09:40 AM
0

Hi,

cms was running at start of install as required to run, just looks like install attempts to start cms at end which cannot due to licence key being a 4.0 licence and just been updated to 4.2

Also from theoreretical perspective what if node 1 had a cms but node 2 has ifrs/ofrs - understand ifrs+ofrs need to be running for update to happen?

Also, if attempt to run setup.exe for 4.2 sp05 after update I assume it would detect had been updated and woudl be no danger in doing so - is this the case?

exact message was below.

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>:6400'. Specify the correct host and port and check for network issues. (FWM 20030)
*#*_*FWM 20030|ERROR: Could not reach CMS '<SERVER>:6400'. Specify the correct host and port and check for network issues. (FWM 20030)|ERROR: Could not reach CMS '<SERVER>: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>:6400'. Specify the correct host and port and check for network issues. (FWM 20030)

Share
10 |10000 characters needed characters left characters exceeded
Joe Peters May 11 at 08:17 PM
0

Not certain it's related to your issue, but see this note: https://launchpad.support.sap.com/#/notes/2428876

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

Thanks for reply.

We have valid cluster licence as 4.0 currently clustered.

Do you know what would happen if removed licence keys before update and then would be no conflict between 4.2 system attempting to start with a 4.0 licence? I'm guessing cms would possibly not start and know at start of update the cms needs to be running thus at start seems at start would need a 4.0 licence but at end of update, cms attempts to restart when looks for a 4.2 licence key.

0

I found another note that appears to be closer to your issue, and it has specific steps for updating the license: https://launchpad.support.sap.com/#/notes/2367507

1
Former Member

Thanks for update

0