MCM SP3, Desktop \IOS\Android clients.

[Former Member]

Hello

Som after implementing NW 7.4 and sp3 for MDocs I cannot use PC. iOS and Android clients. Web Browser interface works fine.

Am using Apache Reverse proxy

Logs from android (same for iOS) look like this :

2014-12-10 14:31:32.878 TRACE ApacheClientHttpInvoker: GET https://server/mcm/json/mydocuments/root?objectId=100900e4-6e1c-3110-3d83-8e6180a988da&cmisselector=... > Headers: {Date=[Wed, 10 Dec 2014 10:31:37 GMT], Server=[nginx], cache-control=[private, max-age=0], Transfer-Encoding=[chunked], Content-Type=[application/json;charset=UTF-8], content-encoding=[gzip], Connection=[keep-alive]} 2014-12-10 14:31:32.921 DEBUG SettingsAdapter: List item at position 7 is being rendered: 2131493071 2014-12-10 14:31:32.938 ERROR MetadataDownloadThread: Error ERROR_SESSION_EXPIRED in metadata thread processing task (repository mydocuments, Low, SyncedItemsRefresh, Folder: [100900e4-6e1c-3110-3d83-8e6180a988da]) org.apache.chemistry.opencmis.commons.exceptions.CmisPermissionDeniedException: INVALID_TOKEN_PROVIDED      at org.apache.chemistry.opencmis.client.bindings.spi.browser.AbstractBrowserBindingService.convertStatusCode(AbstractBrowserBindingService.java:257)      at org.apache.chemistry.opencmis.client.bindings.spi.browser.AbstractBrowserBindingService.read(AbstractBrowserBindingService.java:361)      at org.apache.chemistry.opencmis.client.bindings.spi.browser.ObjectServiceImpl.getObject(ObjectServiceImpl.java:278)      at org.apache.chemistry.opencmis.client.runtime.SessionImpl.getObject(SessionImpl.java:519)      at org.apache.chemistry.opencmis.client.runtime.SessionImpl.getObject(SessionImpl.java:497)      at com.sap.mcm.android.util.CmisUtil.getCmisObjects(CmisUtil.java:96)      at com.sap.mcm.android.sync.impl.SyncedItemsRefreshOperation.execute(SyncedItemsRefreshOperation.java:32)      at com.sap.mcm.android.sync.impl.MetadataDownloadThread.run(MetadataDownloadThread.java:158) 2014-12-10 14:31:33.071 DEBUG MetadataDownloadThread: Requeued failed task (repository mydocuments, Low, SyncedItemsRefresh, Folder: [100900e4-6e1c-3110-3d83-8e6180a988da]) 2014-12-10 14:31:33.074 DEBUG MetadataDownloadThread: Reconnecting session for repositor

And from my desktop client

2015-06-17 17:12:20,450 [main] ERROR com.sap.mcm.settings.Constraints  - No permission to read client settings! Using default constraints.

org.apache.chemistry.opencmis.commons.exceptions.CmisPermissionDeniedException: INVALID_TOKEN_PROVIDED

  at org.apache.chemistry.opencmis.client.bindings.spi.browser.AbstractBrowserBindingService.convertStatusCode(AbstractBrowserBindingService.java:257)

  at org.apache.chemistry.opencmis.client.bindings.spi.browser.AbstractBrowserBindingService.read(AbstractBrowserBindingService.java:361)

  at org.apache.chemistry.opencmis.client.bindings.spi.browser.ObjectServiceImpl.getObject(ObjectServiceImpl.java:278)

  at org.apache.chemistry.opencmis.client.runtime.SessionImpl.getObject(SessionImpl.java:519)

  at org.apache.chemistry.opencmis.client.runtime.SessionImpl.getObject(SessionImpl.java:497)

  at com.sap.mcm.settings.Constraints.updateFromServer(Constraints.java:98)

  at com.sap.mcm.util.Setup.readConstraintSettingsFromServer(Setup.java:75)

  at com.sap.mcm.gui.SAPMobileDocumentsClient.startApplication(SAPMobileDocumentsClient.java:151)

  at com.sap.mcm.gui.login.LoginController$2$1.run(LoginController.java:308)

  at org.eclipse.swt.widgets.RunnableLock.run(Unknown Source)

  at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Unknown Source)

  at org.eclipse.swt.widgets.Display.runAsyncMessages(Unknown Source)

  at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)

  at com.sap.mcm.gui.login.LoginController.stopWaitCursor(LoginController.java:632)

  at com.sap.mcm.gui.login.LoginController.onConnectButtonClicked(LoginController.java:371)

  at com.sap.mcm.swt.sync.configuration.LoginPanel$1.widgetSelected(LoginPanel.java:87)

  at org.eclipse.swt.widgets.TypedListener.handleEvent(Unknown Source)

  at org.eclipse.swt.widgets.EventTable.sendEvent(Unknown Source)

  at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source)

  at org.eclipse.swt.widgets.Display.runDeferredEvents(Unknown Source)

  at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)

  at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)

  at org.eclipse.jface.window.Window.open(Window.java:801)

  at com.sap.mcm.gui.login.LoginController.showLoginPage(LoginController.java:272)

  at com.sap.mcm.gui.login.LoginController.startLogin(LoginController.java:107)

  at com.sap.mcm.gui.tray.SystemTrayMenu.showLogonScreen(SystemTrayMenu.java:563)

  at com.sap.mcm.gui.tray.SystemTrayMenu$19.widgetSelected(SystemTrayMenu.java:460)

  at org.eclipse.swt.widgets.TypedListener.handleEvent(Unknown Source)

  at org.eclipse.swt.widgets.EventTable.sendEvent(Unknown Source)

  at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source)

  at org.eclipse.swt.widgets.Display.runDeferredEvents(Unknown Source)

  at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)

  at com.sap.mcm.gui.login.LoginController.stopWaitCursor(LoginController.java:632)

  at com.sap.mcm.gui.login.LoginController.onConnectButtonClicked(LoginController.java:371)

  at com.sap.mcm.swt.sync.configuration.LoginPanel$1.widgetSelected(LoginPanel.java:87)

  at org.eclipse.swt.widgets.TypedListener.handleEvent(Unknown Source)

  at org.eclipse.swt.widgets.EventTable.sendEvent(Unknown Source)

  at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source)

  at org.eclipse.swt.widgets.Display.runDeferredEvents(Unknown Source)

  at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)

  at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)

  at org.eclipse.jface.window.Window.open(Window.java:801)

  at com.sap.mcm.gui.login.LoginController.showLoginPage(LoginController.java:272)

  at com.sap.mcm.gui.login.LoginController.startLogin(LoginController.java:107)

  at com.sap.mcm.gui.tray.SystemTrayMenu.showLogonScreen(SystemTrayMenu.java:563)

  at com.sap.mcm.gui.tray.SystemTrayMenu$19.widgetSelected(SystemTrayMenu.java:460)

  at org.eclipse.swt.widgets.TypedListener.handleEvent(Unknown Source)

  at org.eclipse.swt.widgets.EventTable.sendEvent(Unknown Source)

  at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source)

  at org.eclipse.swt.widgets.Display.runDeferredEvents(Unknown Source)

  at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)

  at com.sap.mcm.gui.login.LoginController.stopWaitCursor(LoginController.java:632)

  at com.sap.mcm.gui.login.LoginController.onConnectButtonClicked(LoginController.java:371)

  at com.sap.mcm.swt.sync.configuration.LoginPanel$1.widgetSelected(LoginPanel.java:87)

  at org.eclipse.swt.widgets.TypedListener.handleEvent(Unknown Source)

  at org.eclipse.swt.widgets.EventTable.sendEvent(Unknown Source)

  at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source)

  at org.eclipse.swt.widgets.Display.runDeferredEvents(Unknown Source)

  at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)

  at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)

  at org.eclipse.jface.window.Window.open(Window.java:801)

  at com.sap.mcm.gui.login.LoginController.showLoginPage(LoginController.java:272)

  at com.sap.mcm.gui.login.LoginController.startLogin(LoginController.java:107)

  at com.sap.mcm.gui.login.LoginController.startLogin(LoginController.java:93)

  at com.sap.mcm.gui.SAPMobileDocumentsClient.main(SAPMobileDocumentsClient.java:138)

2015-06-17 17:12:20,461 [main] INFO  com.sap.mcm.gui.SAPMobileDocumentsClient  - after loading mime types...

2015-06-17 17:12:20,462 [MCM-Thread-Main] DEBUG com.sap.mcm.gui.SAPMobileDocumentsClient  - INITIAL FULL SYNC...

Please any help we be grateful........Thanks for helping.

[pvannest]

Hi JOhn,

we have the same issue. Did you receive any feedback from SAP concerning this?

regards

Peter

[Former Member]

Hello Peter,

I was able to fix the issue, I reinstalled the Application in a DMZ location and secured it with HTTPS.

SAP did not get back with a direct solution.

[pvannest]

So you've put the portal in DMZ.

What was the feedback from SAP? They told you to move portal in dmz?

[pvannest]

I think we found the issue, it was due to the loadbalancing of our reverse proxies

rg

[Former Member]

Hi peter ,

Good to know you found the solution around the load balancing of the reverse proxies, please can you share a sample format of the config file..

SAP did not recommend my approach , we only applied it as an alternative.

BR

John

[pvannest]

in our case it was config on our F5 loadbalancer. Is this relevant for you?

rg

[former_member186016]

Hi,

The clients are always backward compatible and hence they should work.

We need complete logs to analyse the issue.

Can you please create an OSS ticket and provide the logs there.

Thanks and Regards, Ashwani Kr Sharma