Clean Install of BI4.3 SP1 win2016 VMware giving "Logon Failed for RESTful Web Services"

[hwilson06]

I've installed BI4.3 SP1 on a single windows 2016 VM using the out of the box defaults all the way.

As the server is VMware VM and has two different IP addresses I've followed SAP note 2576124 and updated the RESTful Access URL to be http://<External_IP>:8080/biprws

I've also tried it with http://<Server_FQDN>:8080/biprws

WACS server is running and enabled. The server details are in the hosts file. DNS is working. VM is English locale.

Using IE11 on the VM itself I launch BI Launchpad and get the error "Logon Failed for RESTful Web Services" using Administrator userid.

I have the same out of the box install working fine on a VM where it's a workgroup VM (also VMWare and has two IP addresses) but not for this one which is in a domain (hence using external IP rather than FQDN).

I've had our Windows infrastructure specialist looking at it and there are no firewalls or ports being blocked.

Can anyone suggest a resolution please?

Thanks

Heidi

[hwilson06]

Hi Bernhard,

Thank you for taking the time to reply. You are correct about the architecture. I am using Tomcat for the RESTful services.

I have actually resolved this particular server issue by installing FP300 and now it is working externally using http://<server_name>:8080/BOE/BI with the RESTful access URL of: http://<server_name>:8080/biprws

I am going to put up a reverse proxy server and try your suggestion out though.

Thanks again.

Kind regards,

Heidi

[bernhard_keimel]

do you use the WACS as REST server or tomcat? first thing to make sure. you do not need a running WACS if there is the tomcat configured for biprws.

i am not sure about your network architecture. what i think to understand is that you have an external access with domain names that do not work internal, even the external IPs cannot be accessed internally right? so if that is the case it is a problem because when you setup the RESTful URL in CMC you can configure your system either be accessed from external or internal, but not both.

You would then need a (reverse) proxy like apache for the external access that forwards the URL to the internal IP. just an idea ...