cancel
Showing results for 
Search instead for 
Did you mean: 

Problems after an Upgrade Inplace from SAP BO 4.2 SP 8 to SAP BO 4.3 SP 2 Patch 9

ralphkornack
Participant
0 Kudos
886

On a Windows Server 2019 with a SAP BO 4.2 SP8 and the two AddIns for AfO and Lumira an Upgrade Inplace with the One - Installer to the version SAP BO 4.3 SP2 Patch 9 was executed. Before the upgrade AfO and Lumira were uninstalled, because there are corresponding newer versions.

After this Upgrade Inplace the Connection Server of the SAP BO remains in the initialization with an error loop.

Extract from the trace - log:

server.cpp:733:-: TraceLog message 1

|dff3e03e-a1dd-2724-f8fb-a80b9b6b4d8d|2023 04 20 11:12:17:472|+0200|Error| |<<|E|X|connectionserver_TBWA9747.ConnectionServer| 7000|10044|| |0|0|0|0|-|-|-|-|-|-||||||||||||Uncaught Exception in SilentScope: [CS] CSServer::SetServerObjectProperties: 1.923‑

factory.cpp:125:-: TraceLog message 2

|792986cc-2e75-10d4-f966-187868670ca7|2023 04 20 11:12:17:474|+0200|Error| |<<|E|X|connectionserver_TBWA9747.ConnectionServer| 7000|10044|| |0|0|0|0|-|-|-|-|-|-||||||||||||Uncaught Exception in SilentScope: [CS] CSSvcFactory::SIServerTokenNotification: 2.781‑

oscafactory2.cpp:3220:-: TraceLog message 3

|be1af31a-6434-9864-0835-6fc9c3521651|2023 04 20 11:12:17:474|+0200|Error| |>>|E| |connectionserver_TBWA9747.ConnectionServer| 7000|10044|| ||||||||||||||||||||||assert failure: (oscafactory2.cpp:3220). (false : OSCASimpleFactory2::triggerStateChangeNotifications - Unexpected exception).‑

isgenadm.cpp:311:-: TraceLog message 4

|665bbbed-4a8a-94c4-798e-9e3801e69b3d|2023 04 20 11:12:17:475|+0200|Error| |>>|E| |connectionserver_TBWA9747.ConnectionServer| 7000|10044|| ||||||||||||||||||||||assert failure: (isgenadm.cpp:311). (false : CISGeneralAdmin_impl::setParamEx - caught unexpected model state exception).‑

These error messages repeat cyclically.

It does not help to create a new Connection Server. This runs into the same error loop.

Unfortunately, I can't really get to these servers anymore, because no configuration changes are accepted during the initialization phase.

Are there any ideas how this problem can come about?

How can this problem be solved?

Accepted Solutions (1)

Accepted Solutions (1)

ayman_salem
Active Contributor
0 Kudos

Check your license if you have the right one for 4.3

ralphkornack
Participant
0 Kudos
I have to correct myself here. In fact, it was the licenses for SAP BO 4.3 that finally solved the problem.

Answers (3)

Answers (3)

ralphkornack
Participant
0 Kudos

Hello Ayman Salem

This is indeed an error possibility as I have not been able to import a valid license yet. However, it is not the first time that I have upgraded from a SAP BO 4.2 to a SAP BO 4.3 version. But it is the first time that the connection service and therefore also other services that depend on the connection service show this error pattern.

many greetings
Ralph Kornack

ayman_salem
Active Contributor
0 Kudos

I'm surprised you said you upgraded from SAP BO 4.2 to SAP BO 4.3 without changing the license and after that it works without any problems.

Basically the license for SAP BO 4.3 is not the same as for SAP BO 4.2 and you must have the right one.

So it is NOT a possible error, it is the root cause of the problem you are having.

ralphkornack
Participant
0 Kudos

Hello Ayman Salem

Thank you for the hint. So I know in the future, where I can find appropriate hints.

But that does not help here at all. Before the upgrade I uninstalled the AddIn for AfO and for Lumira. So they are not present in the system during the upgrade.

I know that I have to install new versions for AfO and Lumira. That's why these AddIns were uninstalled before the upgrade.

The problem is still that the connection server com BO 4.3 SP2 Patch 9 brings this error and I don't know how to fix it.

Many greetings

Ralph Kornack

ayman_salem
Active Contributor
0 Kudos

Check your license if you have the right one for 4.3

ayman_salem
Active Contributor
0 Kudos