Error in SDK-Script after Upgrade to BIP 4.2 SP5

[former_member596929]

Hi,

after the upgrade of the BIP to 4.2 SP5 our SDK-Script isn't running anymore.
First of all i have updated the old jars and added the new ones.
Now I'm getting this error:

Exception in thread "Thread-0" java.lang.ExceptionInInitializerError

at com.businessobjects.bcm.BCM.<clinit>(BCM.java:1144)

at com.crystaldecisions.enterprise.ocaframework.BCMInitializer.run(BCMInitializer.java:29)

at java.lang.Thread.run(Unknown Source)

Caused by: java.lang.SecurityException: Algorithm not allowable in FIPS140 mode: FIPS186Random

at com.rsa.cryptoj.o.cc.j(Unknown Source)

at com.rsa.cryptoj.o.ci.j(Unknown Source)

at com.rsa.cryptoj.o.cj.newSecureRandom(Unknown Source)

at com.rsa.jsafe.JSAFE_SecureRandom.a(Unknown Source)

at com.rsa.jsafe.JSAFE_SecureRandom.getInstance(Unknown Source)

at com.businessobjects.bcm.internal.BcmRsaLib.createPRNG(BcmRsaLib.java:140)

at com.businessobjects.bcm.internal.BcmRsaLib.initialize(BcmRsaLib.java:277)

at com.businessobjects.bcm.internal.BcmRsaLib.<clinit>(BcmRsaLib.java:289)

... 3 more

Exception in thread "main" java.lang.NoClassDefFoundError: Could not initialize class com.businessobjects.bcm.BCM

at com.crystaldecisions.sdk.occa.security.internal.ConfidentialChannelService.establishConfidentialChannel(ConfidentialChannelService.java:175)

at com.crystaldecisions.sdk.occa.security.internal.ConfidentialChannelService.createConfidentialChannel(ConfidentialChannelService.java:145)

at com.crystaldecisions.sdk.occa.security.internal.CCMap.locateCCItem(CCMap.java:63)

at com.crystaldecisions.sdk.occa.security.internal.LogonService.doUserLogon(LogonService.java:845)

at com.crystaldecisions.sdk.occa.security.internal.LogonService.doUserLogon(LogonService.java:805)

at com.crystaldecisions.sdk.occa.security.internal.LogonService.userLogon(LogonService.java:210)

at com.crystaldecisions.sdk.occa.security.internal.SecurityMgr.userLogon(SecurityMgr.java:166)

at com.crystaldecisions.sdk.framework.internal.SessionMgr.logon_aroundBody0(SessionMgr.java:454)

at com.crystaldecisions.sdk.framework.internal.SessionMgr.logon_aroundBody1$advice(SessionMgr.java:512)

at com.crystaldecisions.sdk.framework.internal.SessionMgr.logon(SessionMgr.java:1)

at com.wuerth.sap.bi.CGMain.main(CGMain.java:761)

What can I do now? Do I have to create a new certificate with PKCS12 Tool with parameter -disableFIPS as described in this KBA?

2519468 - Setting up STS per SAP note 2437674 fails with certificate errors in BW

Thanks in advance

Christoph

[Former Member]

Hi Christoph,

No, you need to delete all old one and need to keep only new one. There are lot changes between version so mixing of jar files will give you lot of issues and it is also not supported way.

-Kedar

[former_member596929]

I have done this right now and the error ist still the same.