The Connection Server does not start after an upgrade to BO4.1 SP3

[Former Member]

Hello guys,

The Connection Server does not start after an upgrade to BO4.1 SP3

We are in process to upgrade our Business Objects environments to BO4.1 SP3

The first 2 environments , the upgrade went fine. But the third environment de connection server won’t start.

When I always try to start it returns me a failed status and shows me that the server is considered failed because it has stopped 5 time(s) in 60 minute(s).

Our OS is AIX

Uncaught Exception in SilentScope: [CS] Ser

verInitialization::InitManager::Initialize: 0.007^^

The CS initialization failed within the CS server. Aborting

trc file: "connectionserver_BIO.ConnectionServer_ncs.trc", trc level: 1, release: "720"

Gerd

[Former Member]

Gerd,

We've hit this before with other patch versions in regards to upgrade efforts. We were able to resolve in one of two ways.

1) Run the installer in repair mode on this third server. It is very possible that you received a upgrade successful message but a component was still not deployed correctly. Repair mode gives you the best chance to correct this.

2) The other, and somewhat less common item to check is to see if you have configured a specific port for the server. We ran into issues with this in the past where a server locked down to a specific port did not start after the upgrade but when we set the server to dynamically assign a port number, it did work.

Just a pair of thoughts here based on lessons learned.

Hope this helps.

Tim

[Former Member]

Hi,

Please try this:

• Locate the boconfig.cfg file e.g. /home/bi4/BI4/setup/boconfig.cfg
• Check if the boconfig.cfg file is corrupted. If it is 0 byte or contains
  only a few lines it is most definitely corrupted.
• Copy the boconfig.cfg file from a working BI4 system and make sure you amend
  the paths and filenames to match your current system

If the issue still persist, try to create a new connectionserver and chek if you get the same behavior.

Regards,

Amine.

[Former Member]

Hi Amine

The File seems ok

File from the failing connection server

-rw-rw---- 1 bioadm bosys 43993 Apr 11 11:29 boconfig.cfg

File from our test system

-rw-rw---- 1 bitadm bosys 43892 Apr 14 10:56 boconfig.cfg

I created a new connectieserver(by the copy function), but the new server won't start.

Regards

Gerd

Log

|89d4a6e0-2a89-7a05-3020-a51d517ab872|2014 04 14 11:54:30:113|+0200|Error| |>>|E| |connectionserver_BIO.ConnectionServer|28246236|3097|| |0|0|0|0|-|-|-|-|-|-||||||||||||[CS] Unhandled exception raised during CS initialization.

init_srv.cpp:95:-: TraceLog message 3

|4dcf04b1-1e1d-df13-48ad-a67f06e29864|2014 04 14 11:54:30:113|+0200|Error| |<<|E|X|connectionserver_BIO.ConnectionServer|28246236|3097|| |0|0|0|0|-|-|-|-|-|-||||||||||||Uncaught Exception in SilentScope: [CS] ServerInitialization::InitManager::Initialize: 0.003

|77ad78f4-37f7-3013-3b50-85cce9fbe7b8|2014 04 14 11:54:30:113|+0200|Error| |>>|E| |connectionserver_BIO.ConnectionServer|28246236|3097|| |0|0|0|0|-|-|-|-|-|-||||||||||||[CS] The CS initialization failed within the CS server. Aborting.

[Former Member]

Check what would be the behavior of a newly created connection server for the same box.

Also we should have look into the upgrade logs that were generated.

Do look for var logs and find the inconsistencies you observe during the upgrade process.

It might have happened during the upgrade process the connection server of existing node got deleted.