SMART Connect error: Last download of changes was longer than 180 days ago

SMART Community Forum
1

Hi all,

I am facing an error when trying to sync with SMART Connect. It says that the last download of changes happened longer than 180 days ago. However, that is not true as I successfully downloaded data on the 3rd of October. The dates in SMART and in the server seem to be correct. Has anyone faced this before? Any advice?

I have pasted an extract of the log below.

Thanks!

!ENTRY org.wcs.smart.connect 4 0 2023-10-12 06:38:22.264
!MESSAGE Last download of changes was longer than 180 days ago. Replication is no longer supported. You must re-download the Conservation Area from SMART Connect.
!STACK 0
java.lang.Exception: Last download of changes was longer than 180 days ago. Replication is no longer supported. You must re-download the Conservation Area from SMART Connect.
at org.wcs.smart.connect.internal.server.replication.DownloadChangeLogEngine.downloadInstall(DownloadChangeLogEngine.java:91)
at org.wcs.smart.connect.ui.server.DownloadChangeLogHandler.downloadChangeLog(DownloadChangeLogHandler.java:82)
at org.wcs.smart.connect.ui.server.SyncChangeLogHandler.syncChangeLog(SyncChangeLogHandler.java:73)
at org.wcs.smart.connect.ui.server.SyncChangeLogHandler.execute(SyncChangeLogHandler.java:54)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:567)
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:58)
at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:319)
at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:129)
at org.eclipse.e4.tools.compat.parts.DIHandler.execute(DIHandler.java:52)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:283)
at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:97)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:567)
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:58)
at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:319)
at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:253)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:173)
at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:156)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:488)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:487)
at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:438)
at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:449)
at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.lambda$2(AbstractContributionItem.java:475)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4209)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1037)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4026)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3626)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1157)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1046)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:155)
at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:644)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:551)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:156)
at org.wcs.smart.SmartApp.start(SmartApp.java:47)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:401)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:567)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
at org.eclipse.equinox.launcher.Main.run(Main.java:1461)>

2

@Ana - will flag to the server support team. Haven’t seen that before.

3

@Ana have you confirmed the time/date settings on your computer are correct? And/or have you done any particular updates on your local computer since you last synced?

4

Hi,

Yes. The date and time in the computer is correct. That is the first thing that I thought of. There was a windows update the day before.

Ana

5

@Ana can you please provide a link to the server you’re using?

6

Hello,

Yes. This is the link: https://lionlandscapes7.smartconservationtools.org/server/connect/home

Thank you,

Ana

7

@Ana - Have flagged this to the team. We’ll get back to you ASAP.

8

The 180 day limit is per-computer. So if you were using 2 desktop computers say A and B. If you use computer A most of the time and update to Connect every week that is fine. But if desktop B specifically has not updated with Connect for more than 180 days that is still a problem, and the CA will have to be re-downloaded onto computer B only, A can keep working along as usual without any extra downloads.

Is it a different computer or maybe just a different copy of SMART than you use normally that caused this error?

FYI, the reason for this day limit is Connect only keep exact logs of all changes for 180 days, so once it has been longer than that for a specific desktop computer, we can’t re-create all the changes that happened in the CA anymore as we may miss some changes/updates that are >180 days old and have been cleaned up in the system to save space.

9

Mmm…thank you for the reply. It is strange because it was the same computer I used a week before and successfully downloaded data. The system must have gotten confused after the windows update somehow. I will try to redownload the CA.

Best,

Ana

10

Hi,

I’m starting this discussion again, because I’m having the same problem with my SMART system.
Each time, I have to reload the conservation zones on Connect.
Is there a solution to this problem?

11

Hi Vigny,

You mean that every time you log in you are asked to re-download the CA?

Does it mention the “180 days” in the error message?

This can also happen if multiple users are interacting with the CA and are modifying the database at the same time.

Also, are you using a Partnership-hosted server? If so, can you please share the URL for your Connect. Depending on your answers above we can request that this be looked at by the team.

Cheers,

Alex

12

Hi Alex,

This happens after a certain amount of time has passed (not exceeding two weeks) without working on certain conservation areas of our SMART system.

Each certification authority has a single user at site level and a central administrator at national level, who interact each time.

The message displayed mentions 180 days.

Here’s our Connect URL hosted by the SMART partnership :
https://congoconnect.smartconservationtools.org:8443/server

Thanks

13

Hi Vigny,

My first thought is to make sure you’re using SMART version 7.5.9 (desktop & Connect). If not, please use this form to request the upgrade of the Connect instance and perform the upgrade of your desktop software (File > check for updates).

If you are already using 7.5.9, please use this form to report your issue so the team can review the problem.

Cheers,

Alex

14

Hi Alex!

I’m currently using SMART 7.5.6.
I intend to migrate to 7.5.9 (Desktop and Connect).

Thanks for the link to the form and for your assistance.

Best,