Have you tried opening the command prompt window to run as Administrator?

Hello, 

Yes, all of the steps are executed with administrator privileges.

Can you check what is the active code page on the server? Is it set to non-english by any chance?  Run the command "chcp" and it should return a code.  On my servers, it returns code 437 which is the one for US English.  

Best regards,

Antonio Borges

It's set to 850, it's fine sine I'm outside the US.

Known Problem OCTCR19G575929 (microfocus.com)

Hello Misaq, 

I tried the KM but unfortunately it didn't work, after updating the chcp to 437 and re-install I keep getting the same error:

Best would be to check with OpenText support for further guidance.

If you feel comfortable with OS and OA troubleshooting then can try other options like

Installing the Operations Agent on Platforms with Limitations - Operations Agent (microfocus.com)

or dig further in the troubleshooting section..

Installation - Operations Agent (microfocus.com)

There might be some pre-requisite conflict or OS related issue that may be visible in windows events log.

I had to dig further as it was bothering me why the locale is messing with IP address check...

So following script is responsible for validation...

<OA install media>/packages/WIN/Windows_X64/ValidateSetup.vbs

If I am not mistaking it is trying to get IP address validation form ipconfig /all  command and expecting "IPv6 Address" or "IPv4 Address" string  search?

My guess is that your output for above command is not of that in that format even after change per KB.

Hello,

The issue from OCTCR19G575929 was because of code page issues in cmd.exe which means output like this:

Windows IP ??

?????? ????? ???? ?????:

   ????? DNS ?????? . . . :
   IPv4 ???? . . . . . . . . . . : 10.10.10.56
   ????? ??? . . . . . . . . : 255.255.248.0
   ????? ?????? . . . . . : 192.168.178.10

..cannot be parsed by the script.  Changing the codepage to 437 means the output is shown correctly.  This might not be relevent.

This part of the validatesetup.vbs script uses UCase  which converts everything to upper case to work around any localisation issues:
If (InStr( UCase(StdOutStream), UCase(IPType & " Address")) <> 0 ) Then
If (InStr(UCase(Split(StdOutStream,": " )(1)),"(" )) Then
ip = Split(Split(StdOutStream,": " )(1), "(" ) (0)
End If

The error message you get is "IPv6/IPv4 address is not configured, check the oainstall.log at %TEMP% location" which is the output from validatesetup.vbs.  Do you have IPv6 installed?

What happens if you run:
netsh interface ipv6 show address

I think you should get an output like this:
Interface 1: Loopback Pseudo-Interface 1
Addr Type DAD State Valid Life Pref. Life Address
--------- ----------- ---------- ---------- ------------------------
Other Preferred infinite infinite ::1

Which means IPv6 has a configured loopback on Pseudo-Interface 1.

I'm not sure if a pre-requsite of OA12 is IPv6 at least configured, because ovbbccb uses ::1 to register some endpoints.

Hello Misaq, duncan,

Thank you a lot for taking your time to check this question, I checked the ValidateSetup.vbs script and indeed, it seems to validate through the output of "ipconfig /all" if the IPs are registered. I already went through the troubleshooting guide to no avail, sadly.

Duncan, I ran netsh interface ipv6 show address on the server and this is the output:

Interfaz 1: Loopback Pseudo-Interface 1

Tipo direc. Estado DAD Vigencia válida Vigencia pref. Dirección
----------- ----------- --------------- -------------- ------------------------
Otros Preferido infinite infinite ::1

Interfaz 12: Ethernet

Tipo direc. Estado DAD Vigencia válida Vigencia pref. Dirección
----------- ----------- --------------- -------------- ------------------------
Otros Preferido infinite infinite fe80::700e:3d1f:8c32:f926%12

The IPv4 as well as the IPv6 are seen in the ipconfig output

The only output on %TEMP%oainstall is the next: 

Thank you again for your help.