Invalid JRE Type/path while installing Policy server. 12.52 SP1

[Legacy User]

Hi All,

 

I'm installing policy server ca-ps-12.52-sp01-win32 on windows 2008 R2 64bit.
The java version is 32 bit and i've tried all the possible paths i know to jvm.dll .

Environment variables are correctly set
I have installed and tried with both 32bit jdk and 64bit jdk nothing seems to work.

 

and when i just put the path as C:\Program Files(x86)\Java\jre1.8.0 , i get the following error:-

 

Anything i might be missing?

[Ujwol]

jdk 1.8 is probably not supported with 12.52SP1.

Try jdk 1.7 32 bit and give path to the jre inside jdk during install.

[mayank.agarwal.1]

Hello Ujwol,

 

I am facing the issue. Below is the java version.Policy server is R12.52sp1 32 bit.My java is 32 bit only

 

PATH value is C:\Program Files (x86)\Java\jdk1.7.0_76:C:\Program Files (x86)\Java\jdk1.7.0_76\jre:C:\Program Files (x86)\Java\jdk1.7.0_76\bin

 

Error:

 

Can you please help me here.

[Ujwol]

Have you tried reinstalling jdk?

May be capture processmonitor and check which JVM it is trying to load. That should also give hint if there is any isssues

[mayank.agarwal.1]

Yes, I tried reinstalling it. Still the same problem. Below is the snapshot for the process monitor. It is using correct JVM.

 

[Ujwol]

did jdk 1.7 worked? I did check PSM and confirmed that jdk 1.8 is indeed unsupported with 12.52SP1.

[Legacy User]

I reinstalled the same jdk and it worked.
But the concern still remains the same,i.e. while entering the ip details in configuration mode, it throws an error .
Below is the error we have been facing since last week in our production.

here is the error i'm getting while configuring the policy server details 

Thinking this might be an LDAP error. Please point me in the right direction 

[Ujwol]

I will suggest installing supported jdk.

For the ldap error 52e, its invalid password error:

https://ldapwiki.com/wiki/Common%20Active%20Directory%20Bind%20Errors

[Legacy User]

I'll install the supported jdk
As for the ldap error 52e is pointing towards invalid credentials, but the production environment started getting this error.
I have confirmed that he password i am using is correct and for this i have re-registered that ui.
Apart from this the applications that were protected are also not accessible by any userid and password that were being used.
My first analysis was that the policy store has some connection issues with LDAP.

[Ujwol]

Please open a support ticket. 

Identifying and this as CA sso or LDAP issue first is what we need to do and can be done easily over the remote session.