cancel
Showing results for 
Search instead for 
Did you mean: 

NW 7.0 Installation getting jurisdiction policy error

Former Member
0 Kudos

I am getting the error below when installing my 7.0 Portal on an AIX server.

Do I simply update the local policy and US export files? The install did not prompt for these files, only the local java path:

i.e. java14_64 path

aused by: java.lang.ExceptionInInitializerError

at java.lang.J9VMInternals.initialize(J9VMInternals.java:218)

at javax.crypto.Cipher.a(Unknown Source)

at javax.crypto.Cipher.getInstance(Unknown Source)

at iaik.security.provider.IAIK.a(Unknown Source)

at iaik.security.provider.IAIK.addAsJDK14Provider(Unknown Source)

at iaik.security.provider.IAIK.addAsJDK14Provider(Unknown Source)

at com.sap.security.core.server.secstorefs.Crypt.<clinit>(Crypt.java:82)

at java.lang.J9VMInternals.initializeImpl(Native Method)

at java.lang.J9VMInternals.initialize(J9VMInternals.java:196)

at com.sap.security.core.server.secstorefs.SecStoreFS.setSID(SecStoreFS.java:158)

at com.sap.security.core.server.secstorefs.SecStoreFS.handleCreate(SecStoreFS.java:804)

at com.sap.security.core.server.secstorefs.SecStoreFS.main(SecStoreFS.java:1274)

... 6 more

Caused by: java.lang.SecurityException: Cannot set up certs for trusted CAs

at javax.crypto.b.<clinit>(Unknown Source)

at java.lang.J9VMInternals.initializeImpl(Native Method)

at java.lang.J9VMInternals.initialize(J9VMInternals.java:196)

... 17 more

Caused by: java.lang.SecurityException: Jurisdiction policy files are not signed by trusted signers!

at javax.crypto.b.a(Unknown Source)

at javax.crypto.b.a(Unknown Source)

at javax.crypto.b.access$600(Unknown Source)

at javax.crypto.b$0.run(Unknown Source)

at java.security.AccessController.doPrivileged(AccessController.java:246)

... 20 more.).

Thanks

Weyland Yutani

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

I replaced the two jar files at the unix level with the latest versions and it worked.

Thanks

Weyland

paul_power
Active Contributor
0 Kudos

Hello Weyland,

Usually this error occurs because the JDK policy files are not correct.

Therefore, please check SAP Note 739043 for further details about this.

regards,

Paul