cancel
Showing results for 
Search instead for 
Did you mean: 

CMS initialization failure after update to SAP BO 4.1 (Reason: The port number specified must be > 0 and < 65535)

slavomr_kysel
Explorer
0 Kudos

Dear SAP BO experts,

Our SAP BO infrastructure is one server SAP BO 4.0 SP05 on AIX 6.1 with

Oracle database. Our goal is to update to SAP BO 4.1 SP02 or higher due

to functionality of REST Web services and access the BW data from

external system (MS Power Pivot).

In last week we did several updates with no success:

BO 4.0 SP05 -> BO 4.1 SP04

BO 4.0 SP05 -> BO 4.1 SP02

BO 4.0 SP05 -> BO 4.0 SP08 -> BO 4.1 SP02

BO 4.0 SP05 -> BO 4.1

All updates to 4.1 finished "succesfully", but after update CMS is not

able to start and finishes with initialization failure:

35101   The root server reported an error Initialization Failure.

(Reason: The port number specified must be > 0 and < 65535.).

Connection to CMS database works fine.

Please, what about is this error? Did anybody update to SAP BO 4.1 from 4.0 on AIX successfully?  

Thanks for help,

Slavomir Kysel

Accepted Solutions (1)

Accepted Solutions (1)

denis_konovalov
Active Contributor
0 Kudos

You can't upgrade from 4.0 to 4.1 SP04 then revert back and do upgrade to 4.1 without restoring CMS DB to original pre first upgrade status first.

the actual error might mean that your CMS or SIA do not have a port number assigned.

Use serverconfig.sh to verify CMS/SIA ports.

slavomr_kysel
Explorer
0 Kudos

Hello Denis,

Of course, between each update run we fully restored SAP BO installation including CMS database.

After startservers command, SIA is running.

ccm.config seems be correct, it was not touch by update process.

#!/bin/sh

BOBJEDIR="/usr/sap/sap_bobj/"

BOBJEINSTALLLOCAL="user"

BOBJELANG="en"

BOBJELICENSEKEY=""

BOBJEUSERNAME="bodadm"

BOBJEVERSION="XI 4.0"

CLUSTER_NAMESERVER="bodev"

CLUSTERPORTNUMBER="6400"

CMSCLUSTER="no"

CMSNAMESERVER="bodev"

CMSPORTNUMBER="6400"

CONNECTORPORT="8080"

DATABASEUID="cms"

DBTYPE_AUDIT="oracle"

DBTYPE="oracle"

DEFAULT_NAMESERVER="no"

INSTALL_DIR="/usr/sap/sap_bobj/"

INSTALLMYSQL="no"

INSTALLTYPE="custom"

LOCALNAMESERVER="bodev"

MYSQLHOSTNAME_AUDIT="no"

MYSQLHOSTNAME="no"

NAMESERVER="bodev"

PIDDIR="/usr/sap//sap_bobj/serverpids"

PRODUCTID_NAME="BusinessObjects"

PRODUCTID_VER="14.0"

REDIRECTPORT="8443"

REGFILE="/usr/sap//sap_bobj/data/.bobj"

REINIT="1"

SERVICENAME_AUDIT="BOEXI40"

SERVICENAME="BOEXI40"

SERVICEPORT="no"

SHUTDOWNPORT="8005"

SIANODENAME="BOD"

SIAPORTNUMBER="6410"

FIPSModeValue="undefined"

BODLAUNCH='"/usr/sap/sap_bobj/enterprise_xi40/generic/bobjrestart.sh" -protect "/usr/sap/sap_bobj/enterprise_xi40/generic/javalaunch.sh" "-Dbobj.product.languages.dir=/usr/sap/sap_bobj/enterprise_xi40/Languages/" -Djava.net.preferIPv4Stack=false -Djava.awt.headless=true "-XX:+ExitVMOnOutOfMemoryError" "-XX:+HeapDumpOnOut

OfMemoryError" "-XX:+PrintGCTimeStamps" "-XX:+PrintGCDetails" "-XX:LogGcMaxFileCount=3" "-XX:LogGcMaxFileSize=5m" "-XX:HeapDumpPath=/usr/sap/sap_bobj/logging/" "

-XtraceFile=/usr/sap/sap_bobj/logging/BOD_jvm_@PID.log" "-XX:GCHistoryFilename=/usr/sap/sap_bobj/logging/BOD_gc.prf" "-Xloggc:/usr/sap/sap_bobj/logging/BOD_gc.log" "-XX:ErrorFile=/usr/sap/sap_bobj/logging/BOD_dump_%p.log" -jar "/usr/sap/sap_bobj/enterprise_xi40/java/lib/SIA.jar" -boot "/usr/sap/sap_bobj/enterprise_xi40/a

ix_rs6000_64/_boe_BOD.bootstrap" -port "6410" -pidFile "/usr/sap/sap_bobj/serverpids/BOD.pid" -loggingPath "/usr/sap/sap_bobj/logging/" -traceinipath "/usr/sap/sap_bobj/enterprise_xi40/conf/BO_trace.ini" -name "BOD" -dbinfo "/usr/sap/sap_bobj/enterprise_xi40/aix_rs6000_64/_boe_BOD.dbinfo" -piddir "/usr/sap/sap_bobj/serverpids/" -noauditor '

Error file is genereted error_boe_cmsdbodev.vse.sk.log:

35101   The root server reported an error Initialization Failure. (Reason: The port number specified must be > 0 and < 65535.).

Slavo

slavomr_kysel
Explorer
0 Kudos

Hello Denis,

The problem is solved by using serverconfig.sh and option Modify where I corrected the port number, where was instead of port number "6400" server name "bodev.vse.sk".

This incorrect attribute was already before the update, so it isn't the 4.1 update problem. It's some historical issue on version SAP BO 4.0, where this incorrect attribute doesn't cause any problems.

For next update (test/productive system) the solution is to correct this attribute before the update to 4.1.

Best regards,

Slavo

Answers (0)