1985362 - BI 4.0 - RAS stuck in "Starting" mode

Symptom

The Report Application Server (RAS) stays in "Starting" mode
Tracing of the RAS shows output similar to this

2014 02 12 09:59:36:822|+0000|Information| |==| | |rptappserver_NodeName.RAS|11206874|   1|| ||||||||||||||||||||||SResourceSource::LoadString 45213
2014 02 12 09:59:36:822|+0000|Information| |==| | |rptappserver_NodeName.RAS|11206874|   1|| ||||||||||||||||||||||SResourceSource::LoadString %1 started
2014 02 12 09:59:36:822|+0000|Information| |==| | |rptappserver_NodeName.RAS|11206874|   1|| ||||||||||||||||||||||SResourceSource::LoadString 35100
2014 02 12 09:59:36:822|+0000|Information| |==| | |rptappserver_NodeName.RAS|11206874|   1|| ||||||||||||||||||||||SResourceSource::LoadString %1
2014 02 12 09:59:36:822|+0000|Information| |==| | |rptappserver_NodeName.RAS|11206874|   1|| ||||||||||||||||||||||SIServerController::run: Before initialize
2014 02 12 09:59:36:822|+0000|Information| |==| | |rptappserver_NodeName.RAS|11206874|   1|| ||||||||||||||||||||||(sidaemon.cpp:417) SUNIXDaemon::init: starting
2014 02 12 09:59:36:823|+0000|Information| |==| | |rptappserver_NodeName.RAS|11206874|   1|| ||||||||||||||||||||||SUNIXDaemon::init: redirecting stdio to /dev/null
2014 02 12 09:59:36:823|+0000|Information| |==| | |rptappserver_NodeName.RAS|11206874|   1|| ||||||||||||||||||||||(sidaemon.cpp:210) installing fg terminiation handler
2014 02 12 09:59:36:823|+0000|Information| |==| | |rptappserver_NodeName.RAS|11206874|   1|| ||||||||||||||||||||||(sidaemon.cpp:221) installing abnormal sys handler
2014 02 12 09:59:36:823|+0000|Information| |==| | |rptappserver_NodeName.RAS|11206874|   1|| ||||||||||||||||||||||(siservercleanup.cpp:90) Abnormal signal handling is disabled.
2014 02 12 09:59:36:824|+0000|Information| |==| | |rptappserver_NodeName.RAS|11206874|   1|| ||||||||||||||||||||||(sidaemon.cpp:513) SUNIXDaemon::init: finished
2014 02 12 09:59:36:824|+0000|Information| |==| | |rptappserver_NodeName.RAS|11206874|   1|| ||||||||||||||||||||||SResourceSource::LoadString 50209
2014 02 12 09:59:36:824|+0000|Information| |==| | |rptappserver_NodeName.RAS|11206874|   1|| ||||||||||||||||||||||SResourceSource::LoadString Starting Crystal Reports Application Server : %1
2014 02 12 09:59:36:824|+0000|Information| |==| | |rptappserver_NodeName.RAS|11206874|   1|| ||||||||||||||||||||||SResourceSource::LoadString 35740
2014 02 12 09:59:36:824|+0000|Information| |==| | |rptappserver_NodeName.RAS|11206874|   1|| ||||||||||||||||||||||SResourceSource::LoadString Daemon message from %1: %2.
2014 02 12 09:59:36:827|+0000|Information| |==| | |rptappserver_NodeName.RAS|11206874|   1|| ||||||||||||||||||||||**daemon: NO customer cleanup!
2014 02 12 09:59:36:828|+0000|Information| |==| | |rptappserver_NodeName.RAS|11206874|   1|| ||||||||||||||||||||||(sidaemon.cpp:544) SUNIXDaemon::run: waiting to stop and uninitialize...

While using truss on the RAS, the following error can be seen

vmwlm: [19:55:43] error VMWLM0301: License server not found
You are attempting to execute code that was built with Visual MainWin without a Deployment license.
This code will execute only if a Mainsoft license manager is available to authorize execution.
If you received this application from a vendor, please contact the vendor for assistance.
If you are the vendor developing or testing this application, possible reasons for this failure are:
* The Mainsoft license manager is not running - start the license manager by issuing the command 'msoftlmsrv start'
* A Mainsoft license manager is running but could not be reached - in this case you can set the environment variable MSOFTLM_HOST to point to the host location (e.g. '@blue')

Running the mwadm executable manually provides further information on the issue

$ cd sap_bobj
$ ./setup/env.sh
$ ./enterprise_xi40/aix_rs6000/crpe/mw/bin/mwadm stop
/usr/sap/BPO/sap_bobj/enterprise_xi40/aix_rs6000/crpe/mw/bin/tools/private_core_services[57]: /usr/sap/BPO/sap_bobj/enterprise_xi40/aix_rs6000/crpe/mw/bin/../bin/tools/core_services.common: not found
Failed to stop Core Services.

Environment

SAP BusinessObjects Business Intelligence Platform 4.0 (BI 4.0)
SAP BusinessObjects Business Intelligence Platform 4.1 (BI 4.1)
IBM AIX, Suse/RedHat Linux, Sun Solaris

Product

SAP BusinessObjects Business Intelligence platform 4.0 ; SAP BusinessObjects Business Intelligence platform 4.0, feature pack 3 ; SAP BusinessObjects Business Intelligence platform 4.1

Keywords

KBA , BI-BIP-DEP , Webapp Deployment, Networking, Vulnerabilities, Webservices , BI-BIP-CRS , SAP Crystal Server , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.