cancel
Showing results for 
Search instead for 
Did you mean: 

CMS not starting; CCM not working - Entry Point Not found

Former Member
0 Kudos

Hello community,



Currently we ar facing issue after updating BO BI 4.0 to SP2 Patch 10.



CMS is not starting automatically and CCM is showing up the following error message after starting it:

-

-




SvcMgr.exe - Entry Point Not Found

The procedure entry point ?HasPassport@SLogger@CXLib500@@YA_NXZ could not be located in the dynamic libray cxlibw-5-0.dll

-

-






I have updated all other installed components like BI client tools to same patch level, but this didn't solve the issue.
Crystal Reports cannot be updated to same patch level, because update procedure cannot find the installation, but in BO istallation directory there is a Crystal reports 2011 folder located.

-

-



These are the last entries of SIA trace:

|972063737E4A41FB9DA9F288D6B17A1C13|2012 01 24 15:42:29.083|+0100|==| | |SIA_sapbo4| 1540| 34|Thread-5 | ||||||||||||||||||||com.businessobjects.cad.syslog||

Server Intelligence Agent wird beendet.

|96ACB33EE79A455584D89A99FE5FD69B0|2012 01 24 15:50:18.915|+0100|==| | |SIA_sapbo4| 1132| 12|Thread-0 | ||||||||||||||||||||com.businessobjects.cad.syslog||

Server sapbo4

Anforderungs-Port

Veröffentlichte Adressen: sapbo4.ibsolution.local:6410.

Abhören von Port(s): 10.10.110.73:6410, :6410.

|96ACB33EE79A455584D89A99FE5FD69B1|2012 01 24 15:50:21.372|+0100|==| | |SIA_sapbo4| 1132| 12|Thread-0 | ||||||||||||||||||||com.businessobjects.cad.syslog||

Server Intelligence Agent wird ausgeführt.

|96ACB33EE79A455584D89A99FE5FD69B2|2012 01 24 15:50:23.488|+0100|==| | |SIA_sapbo4| 1132| 31|sapbo4.CentralManagementServer (Process Agent)| ||||||||||||||||||||com.businessobjects.cad.syslog||

Server Intelligence Agent: CMS sapbo4.CentralManagementServer wird automatisch gestartet.

|96ACB33EE79A455584D89A99FE5FD69B3|2012 01 24 15:50:23.555|+0100|==| | |SIA_sapbo4| 1132| 32|sapbo4.CentralManagementServer (Native Process Agent)| ||||||||||||||||||||com.businessobjects.cad.syslog||

Server Intelligence Agent: Server sapbo4.CentralManagementServer wurde gestartet.

|96ACB33EE79A455584D89A99FE5FD69B4|2012 01 24 15:50:24.405|+0100|==| | |SIA_sapbo4| 1132| 32|sapbo4.CentralManagementServer (Native Process Agent)| ||||||||||||||||||||com.businessobjects.cad.syslog||

Server Intelligence Agent: Server sapbo4.CentralManagementServer wurde mit Beendigungscode = -1.073.741.511 (0xc0000139) gestoppt.

|96ACB33EE79A455584D89A99FE5FD69B5|2012 01 24 15:50:24.407|+0100|>>|E| |SIA_sapbo4| 1132| 31|sapbo4.CentralManagementServer (Process Agent)| ||||||||||||||||||||com.businessobjects.cad.syslog||

Server Intelligence Agent: Server sapbo4.CentralManagementServer wurde unerwartet gestoppt.

|96ACB33EE79A455584D89A99FE5FD69B6|2012 01 24 15:50:24.411|+0100|==| | |SIA_sapbo4| 1132| 32|sapbo4.CentralManagementServer (Native Process Agent)| ||||||||||||||||||||com.businessobjects.cad.syslog||

Server Intelligence Agent: Server sapbo4.CentralManagementServer wurde gestartet.

|96ACB33EE79A455584D89A99FE5FD69B7|2012 01 24 15:50:24.439|+0100|==| | |SIA_sapbo4| 1132| 32|sapbo4.CentralManagementServer (Native Process Agent)| ||||||||||||||||||||com.businessobjects.cad.syslog||

Server Intelligence Agent: Server sapbo4.CentralManagementServer wurde mit Beendigungscode = -1.073.741.511 (0xc0000139) gestoppt.

|96ACB33EE79A455584D89A99FE5FD69B8|2012 01 24 15:50:24.441|+0100|>>|E| |SIA_sapbo4| 1132| 31|sapbo4.CentralManagementServer (Process Agent)| ||||||||||||||||||||com.businessobjects.cad.syslog||

Server Intelligence Agent: Server sapbo4.CentralManagementServer wurde unerwartet gestoppt.

|96ACB33EE79A455584D89A99FE5FD69B9|2012 01 24 15:50:24.445|+0100|==| | |SIA_sapbo4| 1132| 32|sapbo4.CentralManagementServer (Native Process Agent)| ||||||||||||||||||||com.businessobjects.cad.syslog||

Server Intelligence Agent: Server sapbo4.CentralManagementServer wurde gestartet.

|96ACB33EE79A455584D89A99FE5FD69Ba|2012 01 24 15:50:24.473|+0100|==| | |SIA_sapbo4| 1132| 32|sapbo4.CentralManagementServer (Native Process Agent)| ||||||||||||||||||||com.businessobjects.cad.syslog||

Server Intelligence Agent: Server sapbo4.CentralManagementServer wurde mit Beendigungscode = -1.073.741.511 (0xc0000139) gestoppt.

|96ACB33EE79A455584D89A99FE5FD69Bb|2012 01 24 15:50:24.474|+0100|>>|E| |SIA_sapbo4| 1132| 31|sapbo4.CentralManagementServer (Process Agent)| ||||||||||||||||||||com.businessobjects.cad.syslog||

Server Intelligence Agent: Server sapbo4.CentralManagementServer wurde unerwartet gestoppt.

|96ACB33EE79A455584D89A99FE5FD69Bc|2012 01 24 15:50:24.479|+0100|==| | |SIA_sapbo4| 1132| 32|sapbo4.CentralManagementServer (Native Process Agent)| ||||||||||||||||||||com.businessobjects.cad.syslog||

Server Intelligence Agent: Server sapbo4.CentralManagementServer wurde gestartet.

|96ACB33EE79A455584D89A99FE5FD69Bd|2012 01 24 15:50:24.508|+0100|==| | |SIA_sapbo4| 1132| 32|sapbo4.CentralManagementServer (Native Process Agent)| ||||||||||||||||||||com.businessobjects.cad.syslog||

Server Intelligence Agent: Server sapbo4.CentralManagementServer wurde mit Beendigungscode = -1.073.741.511 (0xc0000139) gestoppt.

|96ACB33EE79A455584D89A99FE5FD69Be|2012 01 24 15:50:24.509|+0100|>>|E| |SIA_sapbo4| 1132| 31|sapbo4.CentralManagementServer (Process Agent)| ||||||||||||||||||||com.businessobjects.cad.syslog||

Server Intelligence Agent: Server sapbo4.CentralManagementServer wurde unerwartet gestoppt.

|96ACB33EE79A455584D89A99FE5FD69Bf|2012 01 24 15:50:24.513|+0100|==| | |SIA_sapbo4| 1132| 32|sapbo4.CentralManagementServer (Native Process Agent)| ||||||||||||||||||||com.businessobjects.cad.syslog||

Server Intelligence Agent: Server sapbo4.CentralManagementServer wurde gestartet.

|96ACB33EE79A455584D89A99FE5FD69B10|2012 01 24 15:50:24.544|+0100|==| | |SIA_sapbo4| 1132| 32|sapbo4.CentralManagementServer (Native Process Agent)| ||||||||||||||||||||com.businessobjects.cad.syslog||

Server Intelligence Agent: Server sapbo4.CentralManagementServer wurde mit Beendigungscode = -1.073.741.511 (0xc0000139) gestoppt.

|96ACB33EE79A455584D89A99FE5FD69B11|2012 01 24 15:50:24.547|+0100|>>|E| |SIA_sapbo4| 1132| 31|sapbo4.CentralManagementServer (Process Agent)| ||||||||||||||||||||com.businessobjects.cad.syslog||

Server Intelligence Agent: Server sapbo4.CentralManagementServer wird als fehlgeschlagen betrachtet, da er innerhalb von 60 Minute(n) 5 Mal gestoppt wurde. Starten Sie den Server neu.

|96ACB33EE79A455584D89A99FE5FD69B12|2012 01 24 15:50:24.548|+0100|>>|E| |SIA_sapbo4| 1132| 31|sapbo4.CentralManagementServer (Process Agent)| ||||||||||||||||||||com.businessobjects.cad.syslog||

Server Intelligence Agent: CMS sapbo4.CentralManagementServer ist fehlgeschlagen, und der Server Intelligence Agent konnte keine Verbindung mit dem Cluster herstellen. Vergewissern Sie sich, dass die CMS-Port- und -Datenbankeinstellungen richtig sind.

-

-






Do you have any suggestions?



Thanks in advance for your help.



Kind regards,

Eric.

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Eric,

have you solved this issue? I have the same problem after installing SP2 patch 10.

I have copied ...\SAP BusinessObjects\InstallData\InstallCache\platform.services.cms.cpp.dbcheck-4.0-core-64\14.0.2.565\cxlibw-5-0.dll to directory ...\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64

Afterwards it was possible to open CCM but some BO servers failed to start.

Best regards,

Daniel

Former Member
0 Kudos

My company is experiencing the same issue except we updated from a working 4.0 system to SP2 patch 13.

I followed Daniel's suggestion of copying the .dll file to the win64_x64 location. I was able to open the CCM but I'm not able to connect to the CMS when trying to view the server listing.

We will probably be contacting SAP for assistance. I'll post a reply once we have new information.

Former Member
0 Kudos

Hi,

I ran into the same problem on my upgrade to Patch 13.

I copied the file cxlibw-5-0.dll to the respective folder, and My CCM started working, but I still couldnt login to the server, because it couldnt find my server.

The next thing I did:

2. Open Microsoft Windows Explorer and navigate to C:\Program Files\Crystal Decisions\Enterprise 9\win32_x86. Leave Windows Explorer open while performing the rest of this procedure.

3. Click 'Start', and then click 'Run'. The 'Run' dialog box appears.

4. In the 'Open' field, type "REGSVR32". Do not click 'OK' yet.

5. Drag Enterpriseframework.dll from the Windows Explorer window into the 'Open' field of the 'Run' dialog box behind REGSVR32.

You will see the following after you drag the DLL into the 'Open' field:

REGSVR32 "C:\Program Files\Crystal Decisions\Enterprise9\win32_x86\

Enterpriseframework.dll"

6. Click 'OK'.

The following confirmation appears:

"DLLRegisterServer in C:\Program Files\Crystal Decisions\Enterprise 9\win32_x86\Enterpriseframework.dll succeeded."

This seemed to have sorted this out for me for now.

The problem may stem from not having appropriate permissions to run the patch.

0 Kudos

Hi,

check if SAP Note - 1680450 helps you here.

Otherwise i would recommend you update to SP4 of BI4. There are a lot new features, functions and bugfixes included.

Especially when report off SAP Data sources.

Regards

-Seb.