20 Replies Latest reply: Apr 30, 2012 2:33 PM by Bartlomiej Pietraszuk RSS

Unable to launch SAP BO - ccm.sh

Bartlomiej Pietraszuk
Currently Being Moderated

Hi all I have no idea how to fix SAP BO issue. After launching startservers script I go:

[sapbodev@pcsapbo sap_bobj]$ ./startservers
Starting all servers...
Starting pcsapbodev...
[sapbodev@pcsapbo sap_bobj]$ 

It seems to be okay but there are no error logs in logging folder and no sevrverpids in serverpids folder also.I tried to restart Tomcat and SIA servers but it didn't help me.  My ccm.config file:

#!/bin/sh
BOBJEDIR="/home/sapbodev/BOE40/sap_bobj/"
BOBJEINSTALLLOCAL="user"
BOBJELANG="en"
BOBJELICENSEKEY="licenseKey"
BOBJEUSERNAME="sapbodev"
BOBJEVERSION="XI 4.0"
CLUSTER_NAMESERVER="pcsapbo"
CLUSTERPORTNUMBER="6400"
CMSCLUSTER="no"
CMSNAMESERVER="pcsapbo"
CMSPORTNUMBER="6401"
CONNECTORPORT="8081"
DATABASEUID="sap_bo_dev"
DBTYPE_AUDIT="oracle"
DBTYPE="oracle"
DEFAULT_NAMESERVER="no"
INSTALL_DIR="/home/sapbodev/BOE40/sap_bobj/"
INSTALLMYSQL="no"
INSTALLTYPE="default"
LOCALNAMESERVER="pcsapbo"
MYSQLHOSTNAME_AUDIT="no"
MYSQLHOSTNAME="no"
NAMESERVER="pcsapbo"
PIDDIR="/home/sapbodev/BOE40//sap_bobj/serverpids"
PRODUCTID_NAME="BusinessObjects"
PRODUCTID_VER="14.0"
REDIRECTPORT="8444"
REGFILE="/home/sapbodev/BOE40//sap_bobj/data/.bobj"
REINIT="1"
SERVICENAME_AUDIT="BOEXI40"
SERVICENAME="BOEXI40"
SERVICEPORT="no"
SHUTDOWNPORT="8006"
SIANODENAME="pcsapbodev"
SIAPORTNUMBER="6411"
FIPSModeValue="undefined"
pcsapbodevLAUNCH='"/home/sapbodev/BOE40/sap_bobj/enterprise_xi40/generic/bobjrestart.sh" -protect "/home/sapbodev/BOE40/sap_bobj/enterprise_xi40/generic/javalaunch.sh" "-Dbobj.root.internal=/home/sapbodev/BOE40///sap_bobj" -Djava.net.preferIPv4Stack=false -jar "/home/sapbodev/BOE40/sap_bobj/enterprise_xi40/java/lib/SIA.jar" -boot "/home/sapbodev/BOE40/sap_bobj/enterprise_xi40/linux_x64/_boe_pcsapbo.bootstrap" -cmspath "/home/sapbodev/BOE40/sap_bobj/enterprise_xi40/linux_x64/boe_cmsd" -cmsdir "/home/sapbodev/BOE40///sap_bobj" -port "6411" -pidFile "/home/sapbodev/BOE40//sap_bobj/serverpids/pcsapbodev.pid" -loggingPath "/home/sapbodev/BOE40/sap_bobj/logging" -name "pcsapbodev"-dbinfo "/home/sapbodev/BOE40/sap_bobj/enterprise_xi40/linux_x64/_boe_pcsapbo.dbinfo" -piddir "/home/sapbodev/BOE40//sap_bobj/serverpids" '

If I want log into CMC or InfoView I got error: Error: Server nameOfTheServer:6401 not found or server may be down (FWM 01003) null.  Is it possible to fix this issue? This instance of SAP BO stores quite important objects, so I would not like to re-install it - I have to backup them.

  • Re: Unable to launch SAP BO - ccm.sh
    Frederique Le Bihan
    Currently Being Moderated

    Hi,

     

    You can first make sure your cms is running by running

    ps -ef | grep cms

     

    If it's not running, there's no point trying to log into CMC.

    Check your database, make sure it's started correctly and that there's no connection issue between your boe server and your database server.

     

    Frederique

    • Re: Unable to launch SAP BO - ccm.sh
      Bartlomiej Pietraszuk
      Currently Being Moderated

      Hi.

      Thank you for response.

      CMS is not running in this environment.

      However, CMS in TEST environment (same machine, same connection to DB) works perfectly.

      So I think there is no connection issue.

       

      boe_cmsd_ncs.trc:

       

      -


      trc file: "boe_cmsd_ncs.trc", trc level: 1, release: "720"

      -


      M

      M Wed Apr 25 10:47:35 2012

      NCS trace timer thread is successfully triggered

      Trace dispatcher thread is successfully triggered

      NCS data timer thread is successfully triggered

      Data dispatcher thread is successfully triggered

      NCS library version 2.3.8 (unicode) loaded

      NCS_ProcInit API invoked

      M

      M Wed Apr 25 10:47:37 2012

      NCS_ProcExit API started

      Timer threads are successfully finished

      Data sending threads are successfully finished

      ***LOG Q0I=> NiPConnect2: 127.0.0.1:59818: connect (111: Connection refused)

      *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 1/sock 12

          (SI_ECONN_REFUSE/111; I4; ST; 127.0.0.1:59818)

      *** ERROR => NI raw handle failed to be initilized for the first time, connection to agent destination failed to be established  in agent 1

      Performance or Resource Data Detected

      *** ERROR => NI raw handle failed to be initilized for the first time, connection to agent destination failed to be established  in agent 1

      NCS_ProcExit API invoked




      Edit:
      Ok, now I'm getting error running cmsdbestup.sh:


      err: Error:  Failed to get cluster name. (STU00165)
      err: Error description: Failed to decrypt object 100 using cryptographic key ID: 4.

       

      Any ideas?

       

      • Re: Unable to launch SAP BO - ccm.sh
        Denis Konovalov
        Currently Being Moderated

        If you have another instance of SAP BI4.0 running on the same server, how is this instance separated from the other one ?
        What OS is this  exactly?

         

        Sounds like the installation was not succesfull or 2 instances are interacting with each other.

        • Re: Unable to launch SAP BO - ccm.sh
          Piotr Rosiak
          Currently Being Moderated

          We have on unix (centos) two different users: sapbo(test environment) and sapbodev(dev env).

          On the first one we have installed SAP BO at ports 6400 and 8080.

          Then we start installation on second user and use 6401 and 8081.

          That idea works perfectly since few months.

          Apart from launching dev env, recently we have another problem. Free disk space decreases rapidly. One month ago we have 20GB, but now it is max 1GB.

          We constantly remove logs from logging folder.

          • Re: Unable to launch SAP BO - ccm.sh
            Denis Konovalov
            Currently Being Moderated

            couple points :

            1. CentOS is not a supported OS per PAR. This means product was not tested on it and you might experience weird issues.

            2. This server better have 16+ CPU's and 32gb+ Memory to handle this....

            3. Port ranges are too close....

            4. On disk space - you'll need to identify where its being eaten and if it's logs - that can be changed (tracing/logging settings are described in Admin guide).

  • Re: Unable to launch SAP BO - ccm.sh
    Piotr Rosiak
    Currently Being Moderated

    I'm sorry. We have RedHat.

    • Re: Unable to launch SAP BO - ccm.sh
      Sebastian Wiefett
      Currently Being Moderated

      Hi,

       

      it could be that the insufficient Disk space is causeing this issue. Stop both BI4 instances, delete or backup all .log files from the logging directories and try to start both instances again.

       

      Regards

      -Seb.

      • Re: Unable to launch SAP BO - ccm.sh
        Piotr Rosiak
        Currently Being Moderated

        We tried but we have only 400M of free space after deleting all log files. There must be another files, which takes so much space. After stopping all instances, I tried to start dev - not working. What is interesting, test env started normally despite 400M of free space.

        • Re: Unable to launch SAP BO - ccm.sh
          Piotr Rosiak
          Currently Being Moderated

          Maybe there is another idea to backup universes and reports when servers nor running?

          We will try to dump database, install new instance, and then restore database.

          All informations about unv and reports are saved in db? I think that there must be also files responsible for this.

          • Re: Unable to launch SAP BO - ccm.sh
            Sebastian Wiefett
            Currently Being Moderated

            Hi,

             

            400 MB is not that much. Can you increase the HDD size?

             

            Check if there are *.core files in the installation directory - if yes delete them. Or if there are any other Dumps.

             

            Propably the Filestore is the directory with the most amount of Files. This is also a place which you should back up. If you want to restore your system you need a synchron backup of your CMS DB and the Filestore.

             

            Regards

            -Seb.

          • Re: Unable to launch SAP BO - ccm.sh
            Denis Konovalov
            Currently Being Moderated

            there could be many possible areas which migh utilize high disk space.... search index, processing servers cache and session files, logs, java core dumps, process server core dumps etc...

             

            You will need to identify where this happens first.

             

            As tot he backup/restore -- Metadata is stored in CMS DB, actual files/reports/instances - in the FileStore.  Please see Admin guide for details.

            • Re: Unable to launch SAP BO - ccm.sh
              Bartlomiej Pietraszuk
              Currently Being Moderated

              Where is the FileStore?
              Is it the correct path: [INSTALL_DIR]/BOE40/sap_bobj/data/frsinput ?

               

              Now I want to copy all files from old DEV File Store to new one - will I see all my objects?

              • Re: Unable to launch SAP BO - ccm.sh
                Romain Anselin
                Currently Being Moderated

                Hi,

                 

                Im giving a shot in the dark here, but in previous versions, we've seen scenarios where a binary would not start if there was a .pid associated to that executable in the serverpids folder.

                 

                Not sure this is still valid though.

                 

                Also, you may want to have a quick look in the /var/log/messages or equivalent to confirm if the issue is reported and why.

                 

                Regards

                • Re: Unable to launch SAP BO - ccm.sh
                  Bartlomiej Pietraszuk
                  Currently Being Moderated

                  Thank you for response.
                  I've checked it. There are no files in serverpids folder.

                  • Re: Unable to launch SAP BO - ccm.sh
                    Romain Anselin
                    Currently Being Moderated

                    Hi again,

                     

                    Two things here:

                    1- the crypto error you get in CMS DB setup script. If it is still there, you may want to try and reset the cluster key:

                    https://service.sap.com/sap/support/notes/1639053

                    https://service.sap.com/sap/support/notes/1613058

                    2- any info when looking into the syslog if cms startup still fails? (var/log/messages on Linux)

                     

                    Message was edited by: Romain Anselin (clarified the modification and added another KB explaining the error)

                    • Re: Unable to launch SAP BO - ccm.sh
                      Bartlomiej Pietraszuk
                      Currently Being Moderated

                      Thank you for previous advices.
                      1. After cluster key resetting I got two logs in logging folder:

                       

                      SIA_pcsapbodev2_27875_2012_04_28_10_41_11_937_trace.glf

                      FILE_TYPE:DAAA96DE-B0FB-4c6e-AF7B-A445F5BF9BE2

                      ENCODING:UTF8

                      RECORD_SEPARATOR:30

                      COLUMN_SEPARATOR:124

                      ESC_CHARACTER:27

                      COLUMNS:Location|Guid|Time|Tzone|Importance|Severity|Exception|DeviceName|ProcessID|ThreadID|ThreadName|ScopeTag|MajorTick|MinorTick|MajorDepth|MinorDepth|RootName|RootID|CallerName|CallerID|CalleeName|CalleeID|ActionID|DSRRootContextID|DSRTransaction|DSRConnection|DSRCounter|User|ArchitectComponent|DeveloperComponent|Administrator|Unit|CSNComponent|Text

                      SEVERITY_MAP: |Information|W|Warning|E|Error|A|Assertion

                      HEADER_END

                      |F79A1E1410EB48EFAEFAFC66482546680|2012 04 28 10:41:11.953|+0200|>>|E| |SIA_pcsapbodev2|27875|  14|InfoStore Agent | ||||||||||||||||||||com.businessobjects.cad.log||The Install + Enterprise Node objects for Enterprise Node with CUID FgWo6E673gEAvioAAEBZ0UUASFs5EqTT were not found.

                      |F79A1E1410EB48EFAEFAFC66482546681|2012 04 28 10:41:11.972|+0200|>>|E| |SIA_pcsapbodev2|27875|  14|InfoStore Agent | ||||||||||||||||||||com.businessobjects.cad.log||The Install + Enterprise Node objects for Enterprise Node with CUID FgWo6E673gEAvioAAEBZ0UUASFs5EqTT were not found.

                       

                      cms_pcsapbodev2.CentralManagementServer_trace.000001.glf:

                      FILE_TYPE:DAAA96DE-B0FB-4c6e-AF7B-A445F5BF9BE2

                      ENCODING:UTF8

                      RECORD_SEPARATOR:30

                      COLUMN_SEPARATOR:124

                      ESC_CHARACTER:27

                      COLUMNS:Location|Guid|Time|Tzone|Importance|Severity|Exception|DeviceName|ProcessID|ThreadID|ThreadName|ScopeTag|MajorTick|MinorTick|MajorDepth|MinorDepth|RootName|RootID|CallerName|CallerID|CalleeName|CalleeID|ActionID|DSRRootContextID|DSRTransaction|DSRConnection|DSRCounter|User|ArchitectComponent|DeveloperComponent|Administrator|Unit|CSNComponent|Text

                      SEVERITY_MAP: |Information|W|Warning|E|Error|A|Assertion

                      HEADER_END

                      deploy.cpp:6416:-: TraceLog message 1

                      |733912e3-05c9-7444-57ac-fd2ac11c8a18|2012 04 28 10:41:04:948|+0200|>>|A| |cms_pcsapbodev2.CentralManagementServer|28292|47534877113760|| ||||||||||||||||||||||assert failure: (deploy.cpp:6416). (0 : CDeploy::BuildObjectTypeGraph: Plugin CrystalEnterprise.ObjectPackage references unknown type CrystalEnterprise.Report).

                      deploy.cpp:6416:-: TraceLog message 2

                      |f1b29c61-beb0-3e7d-c448-f470339b8c27|2012 04 28 10:41:04:949|+0200|>>|A| |cms_pcsapbodev2.CentralManagementServer|28292|47534877113760|| ||||||||||||||||||||||assert failure: (deploy.cpp:6416). (0 : CDeploy::BuildObjectTypeGraph: Plugin CrystalEnterprise.ObjectPackage references unknown type CrystalEnterprise.Webi).

                      deploy.cpp:6416:-: TraceLog message 3

                      |7eac160c-71a5-0e92-3b4b-45a0f80df42b|2012 04 28 10:41:04:949|+0200|>>|A| |cms_pcsapbodev2.CentralManagementServer|28292|47534877113760|| ||||||||||||||||||||||assert failure: (deploy.cpp:6416). (0 : CDeploy::BuildObjectTypeGraph: Plugin CrystalEnterprise.Publication references unknown type CrystalEnterprise.Webi).

                      deploy.cpp:6416:-: TraceLog message 4

                      |fd1ea7b9-001b-1562-be8b-67ce716bbdf7|2012 04 28 10:41:04:949|+0200|>>|A| |cms_pcsapbodev2.CentralManagementServer|28292|47534877113760|| ||||||||||||||||||||||assert failure: (deploy.cpp:6416). (0 : CDeploy::BuildObjectTypeGraph: Plugin CrystalEnterprise.Publication references unknown type CrystalEnterprise.Report).

                      deploy.cpp:6416:-: TraceLog message 5

                      |439e20c9-702e-6537-acf2-7d51c3efbd5e|2012 04 28 10:41:04:952|+0200|>>|A| |cms_pcsapbodev2.CentralManagementServer|28292|47534877113760|| ||||||||||||||||||||||assert failure: (deploy.cpp:6416). (0 : CDeploy::BuildObjectTypeGraph: Plugin CrystalEnterprise.Universe references unknown type CrystalEnterprise.Overload).

                      deploy.cpp:6416:-: TraceLog message 6

                      |e2c4f219-12cd-c56f-0a0f-24d98d12efa7|2012 04 28 10:41:04:953|+0200|>>|A| |cms_pcsapbodev2.CentralManagementServer|28292|47534877113760|| ||||||||||||||||||||||assert failure: (deploy.cpp:6416). (0 : CDeploy::BuildObjectTypeGraph: Plugin CrystalEnterprise.ScopeBatch references unknown type CrystalEnterprise.Report).

                      deploy.cpp:6416:-: TraceLog message 7

                      |161016ca-efce-10b4-b7d5-246e38235a7c|2012 04 28 10:41:04:953|+0200|>>|A| |cms_pcsapbodev2.CentralManagementServer|28292|47534877113760|| ||||||||||||||||||||||assert failure: (deploy.cpp:6416). (0 : CDeploy::BuildObjectTypeGraph: Plugin CrystalEnterprise.ScopeBatch references unknown type CrystalEnterprise.Webi).

                      auditsubsystem_impl.cpp:1523:-: TraceLog message 8

                      |84f6a2ab-766d-4794-d4fc-0a455fd620e2|2012 04 28 10:41:05:913|+0200|>>|A| |cms_pcsapbodev2.CentralManagementServer|28292|47534877113760|| ||||||||||||||||||||||assert failure: (auditsubsystem_impl.cpp:1523). (cuidToIdMap.Lookup( auditCUID, auditId ) : Auditor::CreateRecordsForServer - the AuditingService seems to be missing from this deployment.).

                      oscafactory.cpp:1931:-: TraceLog message 9

                      |afdd0a73-94f3-c019-7547-62f1a2140646|2012 04 28 10:41:06:026|+0200|>>|A| |cms_pcsapbodev2.CentralManagementServer|28292|47534877113760|| ||||||||||||||||||||||assert failure: (oscafactory.cpp:1931). (false : There are no port allocations to report.).

                       

                      I have checked CUID FgWo6E673gEAvioAAEBZ0UUASFs5EqTT and row with this CUID already exists on DB (table: CMS_INFOOBJECTS7).

                       

                       

                      2. /var/log/messages:

                      Apr 28 11:11:10 pcsapbo boe_cmsd[1433]: Central Management Server started

                      Apr 28 11:11:16 pcsapbo boe_cmsd[1433]: Server cms_pcsapbodev2.CentralManagementServer Name Service Port

                      Apr 28 11:11:16 pcsapbo boe_cmsd[1433]: Server cms_pcsapbodev2.CentralManagementServer Request Port Published Addresses: pcsapbo:51941. Listening on port(s): 10.132.220.98:51941.

                      Apr 28 11:11:16 pcsapbo boe_cmsd[1433]: CMS startup: completed!

                       

  • Re: Unable to launch SAP BO - ccm.sh
    Piotr Rosiak
    Currently Being Moderated

    I've removed all *.log and *.core files. Now we have 3GB of free space.

    But startservers script not working.

  • Re: Unable to launch SAP BO - ccm.sh
    Bartlomiej Pietraszuk
    Currently Being Moderated

    Ok, I have installed third SAP BO instance and it seems to work fine.

     

    Next question is: where are universes, reports and other SAP BO objects stored?
    I have copied all files from old SAP BO instance ([INSTALL_DIR]/BOE40/sap_bobj/data/frsinput and [INSTALL_DIR]/BOE40/sap_bobj/data/frsoutput) to new one but I can not see any objects.
    Any resolution?

     

    I wanted to launch boe_reposcan.sh but it is impossible. Error: Failed to decrypt object 100 using cryptographic key ID: 4

     

    According to note 1639053 I have changed cluster key and created second node. It did not help me.

    • Re: Unable to launch SAP BO - ccm.sh
      Denis Konovalov
      Currently Being Moderated

      Your question indicates that you are not familiar with the current BOE architecture.

      The Admin guide will be a very important document to get familiar with it.

      In current Architecture, BOE repository has 2 components CMS DB and FRS file Store.

      The CMS DB contains all the metadata (object names, relationships, properties), FRS contains physical objects (reports, instances, universes).

       

      One cannot exist without the other.

      To move objects from one system to another in BI4.0 you need to either use LCM or CMSDBCopy option (.cmsdbsetup.sh on UNIX) + FRS copy.

Actions