ConnectionServer32 stays in Initialitizing state

[david_stach]

Hello,

after installation BI Platform everything seems to be OK, only ConnectionServer32 in CMC is still in "initializing" status.

I tried to find solution on sap.com, but nothing helped.

What we tried:

1) doublecheck ODBC 32bit

2) check license

3) restart ConnectionServer32

4) duplicate ConnectionServer32 and start the duplicity (same issue)

5) manualy set port of ConnectionServer32

All these I found as possible reason for the issue, but nothing helped.

In the log of ConnectionServer32 I found a lot of these records:

server.cpp:845:void __thiscall CSServer::InitServerSession(const class CXLib500::SWCharString &): TraceLog message 45

|834485d9-5dba-8b84-1951-2ba03d6fbb29|2016 02 24 12:36:46:379|+0200|Error| |<<|E|X|connectionserver_CBSTBPVIEWDEV01.ConnectionServer32_2| 8824|3800|| |0|0|0|0|-|-|-|-|-|-||||||||||||Uncaught Exception in SilentScope: [CS] CSServer::InitServerSession: 0

factory.cpp:125:void __thiscall CSSvcFactory::SIServerTokenNotification(const class CXLib500::SWCharString &): TraceLog message 46

|d2d3b62d-acc0-9784-b9e8-04c0247f999e|2016 02 24 12:36:46:379|+0200|Error| |<<|E|X|connectionserver_CBSTBPVIEWDEV01.ConnectionServer32_2| 8824|3800|| |0|0|0|0|-|-|-|-|-|-||||||||||||Uncaught Exception in SilentScope: [CS] CSSvcFactory::SIServerTokenNotification: 0

.\oscafactory2.cpp:3220:-: TraceLog message 47

|26f3078b-b20e-1414-48ef-61aa8e953a21|2016 02 24 12:36:46:379|+0200|Error| |>>|E| |connectionserver_CBSTBPVIEWDEV01.ConnectionServer32_2| 8824|3800|| ||||||||||||||||||||||assert failure: (.\oscafactory2.cpp:3220). (false : OSCASimpleFactory2::triggerStateChangeNotifications - Unexpected exception).

.\isgenadm.cpp:315:-: TraceLog message 48

|de953a36-e1ca-20a4-a82d-7ec7aef74355|2016 02 24 12:36:46:379|+0200|Error| |>>|E| |connectionserver_CBSTBPVIEWDEV01.ConnectionServer32_2| 8824|3800|| ||||||||||||||||||||||assert failure: (.\isgenadm.cpp:315). (false : CISGeneralAdmin_impl::setParamEx - caught unexpected model state exception).

What can be other step to try?

Thanks for help.

[former_member756182]

Hi David,

Trust this message finds you well.

I am also facing the same issue and tried the steps mentioned by you in description already.

Can you please share the work around that helped you to solve this issue.

Many Thanks.

[david_stach]

As it is already 7 years back I do not remember the solution. What I learned is that if you cannot solve the problem in one day and it is possible, re-install the system from scratch.

[pavan_k11]

Go for installation repair.

If that does not help then enable HIGH level tracing for connectionserver32 and attach the relevant part of logs here or send it to SAP for analysis.

[former_member263415]

Hi David,

-Check the event viewer for any error messages.

-Navigate to the following directory <Install Dir>\SAP BusinessObjects\setup\packagestemp

Are there any  .dfo files present here?

What is the BI product version and Server Operating System?

Regards,

Sharvari

[onkarvelhals]

HI David,

License key seems to be expired.

Please validate it from CMC> License keys. Check expiry date.

Try using temporary license key.

Regards,

Onkar

[david_stach]

Hello Onkar,

thank you for your reply, but as I wrote license is OK, in CMC I can see exactly the same key as you attached for BI Platform.

David

[onkarvelhals]

Hi David,

In a unusual scenario, side-by-side installation of different products that perform real-time encryption on server machine lock cryptocme2.dll which is used by connectionserver32 (you can find yourself using process explorer on server machine and maneuvering through referenced dlls while connectionserver32 is initializing). This thus creates a conflict while initializing connectionserver32.

In most cases, re-registering those conflicting dlls helps connectionserver32 to start normally. However, repairing existing installation does exactly that (possibly in a better way!).

Therefore, you can repair existing installation and reboot machine to test this issue.

Hope this helps.

Regards,

Onkar