RE: Server "not compatible" with Liferay Sync?

thumbnail
Steve Weiss, modified 5 Years ago. Regular Member Posts: 112 Join Date: 9/20/11 Recent Posts
I have Liferay 7.2 dxp installed and am now trying to get Sync set up. I deployed the sync plugin and in the app manager I see that it's installed. When I try to set up the desktop client on my Mac, I get a message "This server is not compatible with Liferay Sync" as soon as I enter the URL. In catalina.out I see this: 
2020-07-21 14:40:48.309 ERROR [http-nio-8080-exec-10][JSONWebServiceServiceAction:114] No JSON web service action with path /sync-web.syncdlobject/get-sync-context and method GET for sync-web

So as soon as I enter the URL in the client, it hits the server and the server sends back the "not compatible" response? Can someone help me here?
thumbnail
Steve Weiss, modified 5 Years ago. Regular Member Posts: 112 Join Date: 9/20/11 Recent Posts
I've also just noticed that when starting up LR there are errors, so it seems that Sync may not have deployed correctly. Fwiw, I have to LR 7.2 installations- one on OSX and one on an Ubuntu VM. The problems are occurring with both of them.

2020-07-21 15:43:58.561 ERROR [Framework Event Dispatcher: Equinox Container: 911a571a-1e60-46a4-b137-320338de9753][Framework:93] FrameworkEvent ERROR 
org.osgi.framework.BundleException: Could not resolve module: com.liferay.sync.oauth [1121]_  Unresolved requirement: Import-Package: com.liferay.oauth.model; version="[2.0.0,3.0.0)"_ [Sanitized]
    at org.eclipse.osgi.container.Module.start(Module.java:444)
    at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1682)
    at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1662)
    at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1624)
    at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1555)
    at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
    at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
    at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
thumbnail
Dennis Ju, modified 5 Years ago. Regular Member Posts: 228 Join Date: 9/30/10 Recent Posts
It sounds like the Sync Connector plugin is not installed. Please install the connector from the marketplace: link.
You will also need to install the prerequisite OAuth 1.0 Connector: link.
thumbnail
Steve Weiss, modified 5 Years ago. Regular Member Posts: 112 Join Date: 9/20/11 Recent Posts
I already installed the Sync Connector plugin, as I mentioned in the original post. I didn't know about the OAuth plugin, I've installed now that but when I restart the server I still get the same error: org.osgi.framework.BundleException:

Could not resolve module: com.liferay.sync.security [1122]_  Unresolved requirement: Import-Package: com.liferay.portal.kernel.exception; version="[8.1.0,9.0.0)"_ [Sanitized]

 When I try to connect using the desktop client it fails with this stack trace:

22-Jul-2020 13:46:24.151 SEVERE [main] org.apache.catalina.util.LifecycleBase.handleSubClassException Failed to destroy component [Connector[HTTP/1.1-8080]] org.apache.catalina.LifecycleException: Protocol handler destroy failed    at org.apache.catalina.connector.Connector.destroyInternal(Connector.java:1042)    at org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:322)    at org.apache.catalina.core.StandardService.destroyInternal(StandardService.java:548)    at org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:322)    at org.apache.catalina.core.StandardServer.destroyInternal(StandardServer.java:1063)    at org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:322)    at org.apache.catalina.startup.Catalina.stop(Catalina.java:708)    at org.apache.catalina.startup.Catalina.start(Catalina.java:669)    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)    at java.lang.reflect.Method.invoke(Method.java:498)    at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:350)    at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:492)Caused by: java.io.IOException: Thread signal failed    at sun.nio.ch.NativeThread.signal(Native Method)    at sun.nio.ch.ServerSocketChannelImpl.implCloseSelectableChannel(ServerSocketChannelImpl.java:292)    at java.nio.channels.spi.AbstractSelectableChannel.implCloseChannel(AbstractSelectableChannel.java:234)    at java.nio.channels.spi.AbstractInterruptibleChannel.close(AbstractInterruptibleChannel.java:115)    at sun.nio.ch.ServerSocketAdaptor.close(ServerSocketAdaptor.java:137)    at org.apache.tomcat.util.net.NioEndpoint.doCloseServerSocket(NioEndpoint.java:350)    at org.apache.tomcat.util.net.NioEndpoint.unbind(NioEndpoint.java:332)    at org.apache.tomcat.util.net.AbstractEndpoint.destroy(AbstractEndpoint.java:1246)    at org.apache.coyote.AbstractProtocol.destroy(AbstractProtocol.java:667)    at org.apache.catalina.connector.Connector.destroyInternal(Connector.java:1038)    ... 13 more
thumbnail
Dennis Ju, modified 5 Years ago. Regular Member Posts: 228 Join Date: 9/30/10 Recent Posts
You may need to upgrade to fix pack 2 or above. The Marketplace page indicates the minimum requirement for DXP 7.2 is FP2.