How to troubleshoot RESTful login problem ?

[Former Member]

Hello,

I hope it's the best place to get a solution because I'm becoming crazy !

My environment is :

# Client

Windows Server 2008R2 SP1

MS Office 2010 32-bit

Live Office 4.1 SP7

# Server

Windows Server 2008R2 SP1

Tomcat 7.0.59 + JRE 8_66

BO BI 4.1 SP7

I've upgraded to BO BI 4.1 SP7 and when I try to login from "Live Office", I've got  "LO 02049" error for WinAD and Enterprise authentication modes.

In CMC, I have:

RESTful URL: http://servername:6405/biprws => in browser: no answer !?!

Web service URL: http://servername:8080/dswsbobje   => in a browser, gives me Axis2 welcome page

WACS is ON, with RESTful in its parameters, and restarted many times

IT seems to be a problem with RESTful service: http://servername:6405/biprws/logon/long => in Chrome browser: Unreachable page - ERR_CONNECTION_RESET

No firewall problem :

6405 destination port tested from client : listening

and I reproduce the ERR_CONNECTION_RESET even on BI 4.1+Tomcat server.

In Live Office log, I find:

"Une erreur s'est produite lors de la demande du jeton du service REST"

= An error occured during the request of the token of the REST service

Very helpful message ! What kind of error ???

Any idea to solve this problem ?

I read many many posts without success.

Regards,

Stephane.

[Former Member · Accepted solution]

Hi all,

Yeees ! Problem solved... only in part... in HTTP for data and HTTPS for authentication. I'm fighting now to get HTTPS everywhere for "Live Office".

Did somebody manage to do that: WACS+RESTful Service+Web Service ALL in HTTPS/TLS ?

But for this first promising result, thanks to all for your suggestions.

Yet it's quite difficult to give a precise solution: I've done so many things...

Let's try to summarise:

- upgrade from Tomcat 7.0.59 to 7.0.67 (inspired from SAP note 2232191) => clean web app installation

- stop a max. of servers (Explorer, Crystal, Dashboard..) to narrow perimeter and speed up starting !

- remove RESTful Service from WACS (right click...)

- add new RESTful Service to WACS

- reset ALL the default settings of WACS

- auto asign port for ALL servers

- restart VM (many, many times each time I changed something ! )

EDIT:

Just two helpful info :

In CMC/Applications, I have now:

Properties: RESTful Web Service

URL: http://vm-bobi41:6405/biprws

Properties: Web Service

URL :http://VM-BOBI41:6405/dswsbobje

NB: the question is not fully answered but I'm going to open a new thread, this one being already too long.

Done here: 

Regards,

Stéphane.

[former_member639828]

You can try to add the BO Server IP to your computer's host file.

Regards!

[Former Member]

More info...

After starting WACS, although no warning in CMC (all is green!), I can see some worrying things in wacs log file :

--------------------------------

com.sap.security.saml2.cfg.SAML2GlobalConfigImpl||Could not initialize SAML2 global configuration

com.sap.security.saml2.cfg.exceptions.SAML2ConfigurationException: Could not load trusted Identity Providers

    at com.sap.security.saml2.cfg.SAML2TrustedIdPsConfigImpl.loadAllTrustedIdPs(SAML2TrustedIdPsConfigImpl.java:151)

    at com.sap.security.saml2.cfg.SAML2TrustedIdPsConfigImpl.<init>(SAML2TrustedIdPsConfigImpl.java:73)

    at com.sap.security.saml2.cfg.SAML2ConfigImpl.initConfigurationObjects(SAML2ConfigImpl.java:79)

    at com.sap.security.saml2.cfg.SAML2ConfigImpl.<init>(SAML2ConfigImpl.java:55)

    at com.sap.security.saml2.cfg.SAML2GlobalConfigImpl.initGlobalConfiguration(SAML2GlobalConfigImpl.java:98)

    at com.sap.security.saml2.cfg.SAML2GlobalConfigImpl.<init>(SAML2GlobalConfigImpl.java:69)

    at com.sap.security.saml2.cfg.SAML2GlobalConfigImpl.createInstance(SAML2GlobalConfigImpl.java:85)

    at com.sap.security.saml2.cfg.SAML2GlobalConfigImpl.getInstance(SAML2GlobalConfigImpl.java:78)

    at com.sap.security.saml2.cfg.SAML2CfgFactory.getSAML2GlobalConfig(SAML2CfgFactory.java:24)

    at com.sap.security.saml2.cfg.ljs.SAML2LJSConfiguration.updated(SAML2LJSConfiguration.java:64)

    at org.eclipse.equinox.internal.cm.ManagedServiceTracker$1.run(ManagedServiceTracker.java:181)

    at org.eclipse.equinox.internal.cm.SerializedTaskQueue$1.run(SerializedTaskQueue.java:36)

Caused by: com.sap.security.saml2.cfg.storage.CfgStorageException: Could not obtain sub configurations for cfg path: default/trusted_providers/trusted_idps

    at com.sap.security.saml2.cfg.ljsadapters.filestorage.CfgFileStorage.getSubCfgNames(CfgFileStorage.java:307)

    at com.sap.security.saml2.cfg.storage.CfgObject.getSubCfgPaths(CfgObject.java:136)

    at com.sap.security.saml2.cfg.SAML2TrustedIdPsConfigImpl.loadAllTrustedIdPs(SAML2TrustedIdPsConfigImpl.java:121)

    ... 11 more

Caused by: com.sap.security.saml2.cfg.storage.CfgStorageException: SAML 2 configuration directory (set to "null") is incorrect! Use system property "sys.global.dir" to specify it the correct one!

    at com.sap.security.saml2.cfg.ljsadapters.SAML2LJSAdapters.getConfigurationRoot(SAML2LJSAdapters.java:46)

    at com.sap.security.saml2.cfg.ljsadapters.filestorage.CfgFileStorageAccessor.getReadableConfiguration(CfgFileStorageAccessor.java:38)

    at com.sap.security.saml2.cfg.ljsadapters.filestorage.CfgFileStorage.obtainReadableConfiguration(CfgFileStorage.java:408)

    at com.sap.security.saml2.cfg.ljsadapters.filestorage.CfgFileStorage.getSubCfgNames(CfgFileStorage.java:287)

. . .

com.bo.aa.layout.DashboardManager||underlying implementation doesn't recognize the attribute

java.lang.IllegalArgumentException: Feature 'http://javax.xml.XMLConstants/feature/secure-processing' is not recognized.

    at org.apache.xerces.jaxp.DocumentBuilderFactoryImpl.setAttribute(Unknown Source)

    at com.bo.aa.layout.DashboardManager.setDocBuilderFeaturesForXXE(DashboardManager.java:134)

    at com.bo.aa.layout.DashboardManager.<clinit>(DashboardManager.java:162)

    at com.bo.aa.impl.DBServerImpl.<clinit>(DBServerImpl.java:399)

    at com.bo.aa.servlet.AFBootServlet.InitServers(AFBootServlet.java:80)

    at com.bo.aa.servlet.AFBootServlet.init(AFBootServlet.java:47)

    at com.businessobjects.http.servlet.internal.ServletRegistration.init(ServletRegistration.java:81)

    at com.businessobjects.http.servlet.internal.digester.WebXmlRegistrationManager.loadServlets(WebXmlRegistrationManager.java:127)

    at com.businessobjects.http.servlet.internal.digester.WebXmlRegistrationManager.registerRest(WebXmlRegistrationManager.java:209)

    at com.businessobjects.http.servlet.internal.ProxyServlet.readXml(ProxyServlet.java:368)

    at com.businessobjects.http.servlet.internal.ProxyServlet.registerInternal(ProxyServlet.java:395)

    at com.businessobjects.http.servlet.internal.ProxyServlet.register(ProxyServlet.java:317)

    at com.businessobjects.http.servlet.config.WebXmlConfigurator.register(WebXmlConfigurator.java:60)

    at com.businessobjects.bip.core.web.bundle.CoreWebXmlActivator.start(CoreWebXmlActivator.java:66)

    at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:782)

    at java.security.AccessController.doPrivileged(Native Method)

    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:773)

    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:754)

    at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:352)

    at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:280)

    at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:272)

    at com.businessobjects.http.servlet.Activator.startBundle(Activator.java:129)

    at com.businessobjects.http.servlet.Activator.start(Activator.java:116)

    at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:782)

    at java.security.AccessController.doPrivileged(Native Method)

    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:773)

    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:754)

    at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:352)

    at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:370)

    at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1068)

    at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:557)

    at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:464)

    at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:248)

    at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:445)

    at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)

    at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:330)

|BE1C95FEB2934911935E6342EC58CF041|2016 01 17 19:39:22.440|+0100|Error| |==|E| |wacs_VM_BOBI41.WebApplicationContainerServer|10484|  81|Start Level Event Dispatcher| ||||||||||||||||||||com.bo.aa.util.jsp.AnalyticUtils||ParserConfigurationException Feature 'http://javax.xml.XMLConstants/feature/secure-processing' is not recognized.

---------------------------

Any idea to fix these errors ?

Thanks.

Stéphane.

[János_at_SAP]

Hi Stépahne,

I am writing now the full troubleshooting steps here, only with Enterprise authentication.(if enterprise authentication works, and others not, than this is an authentication issue).

Troubleshooting steps:

0. The BIP platform and LO client must be on the same patch level if you upgraded your BI platform to 4.1 SP 7 the LO client must be on the same.

1. Narrow down that the issue is located to the installation or runtime:

• a, Can you connect to BI Server from another client where LO is installed? if yes, this is an installation issue,
• b, If any computer cannot connect from the network with LO client, this can be a server issue or a firewall issue

SERVER ISSUE

2. from 4.1 SP6 the LO connection is handled by Restfull Webservice, so it must be up and running.

goto CMC->Servers->WACS-> Metrics, and check restfullwebservice is installed & up and running or not.

Please note: it could happen, when you upgrading a system the resustfull webservice
and restfull webservice was not installed on prevoius version, it will be not installed with the upgrade

3. Open on the BI server any type of browser,

• a,  goto CMC->Applications->Restfullwebserive  and copy the URL address to the browser which is on the server. (by default it is http://[servername]:6405/biprws). if it is resulted not found (404) or timeout it means, the service is not running, you must go back to steps (2) and check the metrics
• b, goto CMC->WebService and copy the URL Address o the browser which is on the server. (by default it is http://[servername]:8080/dswsbobje).  if it is resulted not found (404) or timeout or error it means, the service is not running or congfigured incorrectl, you must troubleshoot this error
• c, test the following URL in a browser on the BI server: http://<web app server>/dswsbobje/services/session this should work. if it is not working, situation is the same as point b)

4. As a Next step, check all (3) points from a browser on a client machine where LO is installed. if you cannot connect from the client to these services (got 404) this push you the direction of network/firewall issues since it was working locally on BI Server.

4. As a next step if each 3 is ok before it, please turn on LO logging by KBA 1308364 and check the log files

5. Also download and install fiddler and capture the web traffic/ http trace and analyze it.

INSTALLATION ISSUE

lo client requires .NET framework 2.0 so if the instalaltion is not successfull, you may have broken the inheritance in the .net machine config as per KBA 1749924.

Hints:

If you use Load balancer, please skip during the test, or test step-by-step the web services.

In your case please download and install fiddler, and monitor the network traffic.

Cheers

János

[Former Member]

Hello Janos,

Waow! Nice job !

I thought one moment I had the solution : a conflict on port 6405 (you can add this possible case to your troubleshooting guide) but after setting a new port and restarting SIA+Tomcat, I still have a problem.

In fact, now, netstat -a shows me that nothing is listening on port 6405, the RESTfull service port that I see in CMC !

Metrics of WACS are:

------

Common Server Metrics   

Machine Name     VM-BOBI41.cloud.xyz

Name Server     VM-BOBI41.cloud.xyz:6400

Registered Name     com.seagatesoftware.img.osca.pjs."VM-BOBI41"-VM_BOBI41.WebApplicationContainerServer

Operating System     Windows Server 2008 R2 (6.1)

Local Time     Monday, 18 January 2016 23:09:38 o'clock CET

Version     14.1.7.1853

Start Time     Monday, 18 January 2016 22:51:21 o'clock CET

PID     11920

Host Name     VM-BOBI41.cloud.xyz

Host IP Address     12.34.56.78

Request Port     6417

Busy Server Threads     1

Adaptive Processing Server Metrics   

Available Processors     4

Maximum Memory (MB)     1,820.5

Free Memory (MB)     191.863

Total Memory (MB)     693.5

CPU Usage Percentage (last 5 Minutes)     0%

CPU Usage Percentage (last 15 Minutes)     1%

Percentage of stopped system during GC (last 5 Minutes)     0%

Percentage of stopped system during GC (last 15 Minutes)     0%

Number of page faults during GC (last 5 Minutes)     0

Number of page faults during GC (last 15 Minutes)     0

Number of Full GCs     0

JVM Lock Contention Count     0

JVM Debug Info     STATE_NOT_ACTIVE

JVM Version Info     SAP Java Server VM (6.1.066 24.55-b13 May 7 2014 18:40:24 - 61_REL - optU - windows amd64 - 6 - bas2:217766 (mixed mode) compressed oops)

JVM Deadlocked Threads Counter     0

JVM Trace Flags     { }

Services     Business Process BI Service, Mobile BI Web Application Service, Mobile Configuration Web Application Service, Query Builder Service, SDK Services Web et service QaaWS, Service Web de type RESTFul, Service conteneur d'applications Web, Service d'audit, Service de journal de suivi, Service de l'application Web BOE

Threads in Transport Layer     9

Transport Layer Thread Pool Size     9

Auditing Metrics   

Current Number of Auditing Events in the Queue     0

Web Application Container Server Metrics   

List of Running WACS Connectors     HTTP

Logging Service Metrics   

Logging Directory     C:/Program Files (x86)/SAP BusinessObjects/SAP BusinessObjects Enterprise XI 4.0/logging/

------

Is it enough to see (in bold) in "Services" section : RESTful web service ?

That shows RESTful web service is present (installed) and should start ?

Obviously, it is not since nothing is listening on 6405 port... but WHY ??? 

Are there other things to check ?

Logs of WACS are quite similar to my 2nd post.

TESTS of URL

-3-

a) http://VM-BOBI41:6405/biprws

On standalone BI 4.1 SP7 server => "Connection failed" (normal since nothing is listening on this port)

On client side : same thing

b) http://vm-bobi41:8080/dswsbobje/

server : Axis2 welcome page OK

client : Axis2 welcome page OK

c) http://vm-bobi41:8080/dswsbobje/services/Session

On both client & server:

  <Exception>org.apache.axis2.AxisFault: The endpoint reference (EPR) for the Operation not found is /dswsbobje/services/Session and the WSA Action = null. If this EPR was previously reachable, please contact the server administrator. at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:102) at org.apache.axis2.engine.Phase.invoke(Phase.java:329) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:262)

...

Any idea to understand why RESTfull service does not start ?

Regards,

Stephane.

[martin_dingeldey]

Hi Stephane,

check if the configuration in WACS "bind to all IP Adresses" is checked?

If not I think it will only be listening on 127.0.0.1(localhost):6405.

Regards,

Martin

[Former Member]

Hi Martin,

"bind to all IP Adresses" is well checked.

I have default properties for WACS except a value for "On demand port".

netstat -a shows me that WACS is well listening on this port.

My problem seems to be RESTful service does not start (nothing is listening on port 6405).

Is it possible to just reinstall RESTful service ?

Should I reinstall WACS and RESTful service will be reinstalled too?

Regards,

Stéphane.

[János_at_SAP]

Hello Stéphane

More homework in the case, can you check the followings?

1. What is address for Web sevice:

http://[servername]:8080/dswsbobje

or http://[servername]:8080/dswsbobje/

The EPR (end point reference error) is displayed, when you have an additional / at the end of the URL Address so the first is the correct, second not.

2. Are you using proxy server? if yes, are you sure that all the hosts are excluded?

3. if point (1) or (2) is checked, please check the tomcat log (catalina.out) to see any errors inside.

Try also with IP Address instead of DNS resolution.

Regards

János

[martin_dingeldey]

Hi Stephane,

which value do you mean by on demand port? (Request Port of the WACS Server?) And which value do you use there?

If it is the 6405 and is the same as the HTTP Port in the configuration below "bind to all IP Adresses" than you would use the Port two times and then he cannot correctly come up because you can only use a port once.

Regards

Martin

[Former Member]

Hello Janos,

In CMC,  "Applications/Web Service" properties, I have:

http://VM-BOBI41:8080/dswsbobje

Client and server are in a same domain.

There is a proxy but I think I don't go through it (internal tests for the moment).

I'll check Tomcat logs sooner and post errors here.

Regards,

Stéphane.

[Former Member]

Hello,

Yes

WACS:

Request Port: 6417

About 2 years ago, I had to set "Request port" for all BO servers for security reason (need to open a small range of ports on firewall: 6400-6425).

It is certainly not needed for all servers but I had too few time to perfectly identify servers opened to external access.

Now, no server is using port 6405 since it is reserved for RESTful service.

When all the BO servers are started and enabled, netstat -a shows that nothing is listening on port 6405.

That's the actual problem I'd like to understand and solve...

Regards,

Stéphane.

[former_member197386]

Hello Stéphane,

Can you just ping the server where WACS is installed?

Did you try to access to WACS from the server machine itself?

Regards,

Anthony

[Former Member]

Hello Anthony, hi all,

ping from client to server is OK.

WACS is started and enabled, listening on fixed port 6417:

>netstat -a | findstr 6417

  TCP    0.0.0.0:6417           VM-BOBI41:0            LISTENING

  TCP    10.66.52.132:6417      VM-BOBI41:50420        ESTABLISHED

  TCP    10.66.52.132:6417      VM-BOBI41:64818        ESTABLISHED

  TCP    10.66.52.132:50420     VM-BOBI41:6417         ESTABLISHED

  TCP    10.66.52.132:64173     VM-BOBI41:6409         TIME_WAIT

  TCP    10.66.52.132:64175     VM-BOBI41:6404         TIME_WAIT

  TCP    10.66.52.132:64178     VM-BOBI41:6417         TIME_WAIT

  TCP    10.66.52.132:64179     VM-BOBI41:6418         TIME_WAIT

  TCP    10.66.52.132:64506     VM-BOBI41:6417         TIME_WAIT

  TCP    10.66.52.132:64818     VM-BOBI41:6417         ESTABLISHED

  TCP    [::]:6417              VM-BOBI41:0            LISTENING

I've cleaned Tomcat dswsbobje folders (temp, work) and then redeployed dswsbobje

http://vm-bobi41:8080/dswsbobje/

On server : Axis2 welcome page OK

On client : Axis2 welcome page OK

http://vm-bobi41:8080/dswsbobje/services/Session

On server : Please enable REST support in WEB-INF/conf/axis2.xml and WEB-INF/web.xml

On client : Please enable REST support in WEB-INF/conf/axis2.xml and WEB-INF/web.xml

In C:\Program Files\apache-tomcat-7.0.59\webapps\dswsbobje\WEB-INF\conf\axis2.xml

I set:

<parameter name="disableREST" locked="true">false</parameter>

On server & client:

http://vm-bobi41:8080/dswsbobje/services/Session

gives:

<Exception>org.apache.axis2.AxisFault: The endpoint reference (EPR) for the Operation not found is /dswsbobje/services/Session and the WSA Action = null. If this EPR was previously reachable, please contact the server administrator.

    at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:102)

    at org.apache.axis2.engine.Phase.invoke(Phase.java:329)

    at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:262)

    at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:168)

    at org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngine(RESTUtil.java:144)

    at org.apache.axis2.transport.http.util.RESTUtil.processURLRequest(RESTUtil.java:139)

    at org.apache.axis2.transport.http.AxisServlet$RestRequestProcessor.processURLRequest(AxisServlet.java:837)

    at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:273)

    at javax.servlet.http.HttpServlet.service(HttpServlet.java:620)

    at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)

Still nothing listening on 6405 port !

How can I check that RESTful service is actually installed ?

How can I reinstall only it ?

Thanks.

Regards,

Stéphane.

[martin_dingeldey]

Hi Stephane,

only an idea:

Try http://servername:6417/biprws

Perhaps he uses your fixed port.

I think you can check this also by searching somthing like "http-bio-0.0.0.0-6417" in the WACS logs.

You can check if it is installed by starting the Change/Repair Routine from the first full install from "ControlPanel\Programs and Features" and check if it is checked in the feature list.

I don't know if reinstalling only the Restful is possible but perhaps a repair could do the work you need if there are some files missing. You can reach it also from the Change/Repair Routine in Control Panel. But I would do a snapshot before.

Regards,

Martin

[former_member197386]

Hello Stéphane,

RESTful webservices:

WACS server has is own Tomcat server embedded, running by default 6405 but you changed it to 6417. RESTful webservices are running into WACS, so they will be available through this port in your environment.

Try:

http://servername:6417/biprws/raylight/v1/about

SOAP webservices :

SOAP webservices are running in the app server (Tomcat by default, port 8080). There is no link with WACS server: they are two separate servers running on their own HTTP port.

In your case, it is normal that nothing is running on port 6405, since you've changed the WACS listening port to 6417, right?

RESTful webservices are installed into WACS, that's done by default.

Does this help?

Regards,

Anthony

[Former Member]

Hello,

Do you mean if I fix the port for WACS to 6417:

I must change it in "RESTful Web Service" properties too ???

Are you sure 6417 is an HTTP port ?

This architecture is fully new for me and I didn't understand WACS port and RESTful port are the same port...

I sounds strange...

Regards,

Stéphane.

[former_member197386]

Bonjour Stéphane,

You can see WACS like a "hidden/builtin Tomcat", RESTful webservices are deployed into it.

6417 is the HTTP port where WACS is listening.

It seems that when you updated the HTTP port of WACS, the RESTful webservice access URL property has not been updated properly. That's the confusion. You have to update it manually, according to your real WACS settings.

So: http://VM-BOBI4;6417/....

Thanks and regards,

Anthony

[martin_dingeldey]

Hi Stephane,

could you please check if the restservice really is listening on port 6417 by using the URL

http://vm-bobi4:6417/biprws

because there is an additional configuration for the HTTP Port than the WACS Request Port

By Default it is auto-assign for request port and 6405 for HTTP Port.

So perhaps if you redefine the request port to 6417 he automatically changes theb HTTP Port.

So please try first if the the URL mentioned above is working.

Regards,

Martin

[Former Member]

Anthony, Martin,

I've changed port, in in "Access URL" of properties of RESTful service, from 6405 to 6417.

I restarted the VM, waited enough time (20 min.).

When I test this URL on client or server

http://vm-bobi41:6417/biprws/raylight/v1/about

I briefly get (very hard to capture) these few characteres

before error "Address not found" .

Do you see what I see ??? GIOP !!! ...instead of HTTP !?!

This port does not seem to be an HTTP port.

Regards,

Stéphane.

[daniel_paulsen]

how about trying the following:

On the Server where WACS is installed, open a browser and try the following, which should just return some xml with the BOE version:

1. http://localhost:6405/biprws/raylight/v1/about
2. http://vm-bobi41:6405/biprws/raylight/v1/about
3. http://<IPAddress>:6405/biprws/raylight/v1/about

do any of these work?  In theory they should all be the same, but localhost should remove any potential network/proxy issues.

If they all fail, remove your reqeustport and use "auto assign" on WACS and try again after restarting WACS.  There is also a WACS setting "Show Error Stack" which, if communications to the server work, will show a stack trace rather than just an error number.

Let us know the results,

Dan

[Former Member]

Hi Daniel,

None of the 3 URL works on the server ("connection failed") even if I use "auto assign" port.

netstat -a | findstr 6405

=> nothing listening on port 6405.

What log file could I post to help you to understand the problem ?

Regards,

Stéphane.

[daniel_paulsen]

It sounds to me as if the WACS is disabled, though you did mention earlier that it was enabled.

the SAML errors you get in the WACS logs are some I'm not familiar with.  Have you set up any special authentication or do you log onto BOE using Enterprise authentication?

there is a Landscape Report Tool that is extremely helpful in creating a report of your entire landscape and it can also point out potential configuration problems.  You can find the details in SAP Note: 2138275.

Use this tool to see if any anomalies show up. (based on the Corba GIOP error I suspect a port conflict there.  The tool will show you all of the configured ports on your system).

Don't attach the report here as it will have internal information about your landscape

Dan

<edit> I checked my own startup logs and the same SAML errors are there as well.  this is because it is not configured </edit>

[martin_dingeldey]

Hi Stephane,

you have 4 different configurations for the WACS/RestFul Webservice/Webservice that are used by LiveOffice..

1. The request port configuration of the WACS (internal Tomcat for Hosting Services like REST/Default auto-assign)

  this port is only used indirectly/internally.

2. The HTTP Port of WACS (Default 6405)

This is the port the WACS should be listening on and should be in the RESTful WebService Access URL.

3. Access URL of RestWebService

This is the URL someone is directed to when requesting somthing from RESTful Service.

Live Office uses this for authentication and Report stuff.

The used port should be the HTTP Port from configuration 2.

4. Access URL of WebService (this Service is hosted on the normal Tomcat Default port 8080)

This was the old webservice that was used till SP06 for LO and something still Needs it.

So I think as Daniel mentioned you should reset the mentioned configurations to the default Settings. Then restart the complete machine for freeing all ports and test if then something is listening on port 6405 (perhaps deactivating all Firewall stuff in Windows).

Hope that helps to understand the relations between the ports and configurations.

Regards,

Martin