Leadership Synchronization Problem?

Please excuse me, but I have been a lurker to date but I have a question about data sync. I am a ward clerk. Today, the bishop came to me and asked me why so many of our members callings had not been updated. There as a huge list. I logged in to MLS to fix things and none of what he reported was there. The data was as it was for the last few weeks. So then I asked him where he got his information. Turns out he got it from his iphone running LDS Tools. So I grabbed my iPhone, deleted the data and did a sync. Sure enough, the date represented in the iPhone did not match the leadership data in MLS. I am running the latest released version of Tools.

Is this a bug?

The place to check is the CDOL. MLS updates the CDOL and from there it syncs to all the other sites except for the Classic LUWS. That one has to be done by hand by a site admin.

Note that there's very little time lag between MLS send/receive and CDOL. From CDOL to the rest, it can take a day or two.

Assuming the CDOL is incorrect, you may wish to follow the Correcting duplicate or missing callings procedure.

RussellHltn wrote: From CDOL to the rest, it can take a day or two.

From CDOL to LDS.org Directory it is immediate for the leadership display. For access rights it is a day or two.

Maybe I didn't explain good enough. MLS was updated several weeks ago with many new callings and a lot of releases. The data shows up correctly in MLS, but after several weeks the LDSTools data has not caught up. Is this normal?

No, it is not normal. But the first step in troubleshooting is to look at the CDOL.

And after checking the CDOL check Leader Tools from a PC browser. The same data from CDOL feeds both the mobile apps as well as the on-line PC LDS.org apps.

Has he tried updating his LDStools? Every time my stake leaders start getting after me it is because they haven't updated the information on the phone. Somewhere there is an option to refresh/resync/update/etc.

crislapi wrote:Has he tried updating his LDStools? Every time my stake leaders start getting after me it is because they haven't updated the information on the phone. Somewhere there is an option to refresh/resync/update/etc.

Good point, but the OP stated that he duplicated the issue with a fresh sync.

Does CDOL store all callings, not just leadership? Most of the callings not updating seem to be things like ward missionary, relief society board member, and other callings that are not presidencies.

ammonihah wrote:Does CDOL store all callings, not just leadership? Most of the callings not updating seem to be things like ward missionary, relief society board member, and other callings that are not presidencies.

Yes it does. You should be able to look at your unit in CDOL and see what it has. Once you sign in search on your unit name or number and then click on show all positions.

Hum... guess I will have to check later. When I try to log into CDOL I get this:


Error page exception
The server cannot use the error page specified for your application to handle the Original Exception printed below. Please see the Error Page Exception below for a description of the problem with the specified error page.


Original Exception:

Error Message: Filter [CdolLoggingFilter]: filter is unavailable.
Error Code: 500
Target Servlet: Faces Servlet
Error Stack:
javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: Cannot open connection
at org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl.java:637)
at org.hibernate.ejb.AbstractEntityManagerImpl.persist(AbstractEntityManagerImpl.java:226)
at sun.reflect.GeneratedMethodAccessor253.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.springframework.orm.jpa.ExtendedEntityManagerCreator$ExtendedEntityManagerInvocationHandler.invoke(ExtendedEntityManagerCreator.java:358)
at $Proxy105.persist(Unknown Source)
at org.jboss.seam.persistence.EntityManagerProxy.persi

There is a lot more to the error. Maybe they are working on it right now.

Yes they are working on it. There are issues with connecting to the database right now.

CDOL is back up now.

I'm not the only one having this problem.

https://tech.lds.org/forum/showthread.p ... -match-MLs

He gives a "try this" suggestion in the thread. But this is something that can't be WAD. There is something going on between CDOL and the data going to LDS.org and LDSTools. It may warrant a closer look by whoever is providing or creating the data sets.

ammonihah wrote:Does CDOL store all callings, not just leadership? Most of the callings not updating seem to be things like ward missionary, relief society board member, and other callings that are not presidencies.

I know you were affected by the temporary server outage for CDOL. But I haven't heard yet whether you are seeing sync problems between MLS and CDOL, or between CDOL and LDS Tools. So far the only specific I've read from you is in your original post that says that MLS and LDS Tools aren't in sync.

What about CDOL? Does it match MLS or LDS Tools or neither?

ammonihah wrote:I'm not the only one having this problem.

https://tech.lds.org/forum/showthread.p ... -match-MLs

He gives a "try this" suggestion in the thread. But this is something that can't be WAD. There is something going on between CDOL and the data going to LDS.org and LDSTools. It may warrant a closer look by whoever is providing or creating the data sets.

From what I understand, the data in the Directory app on lds.org and the data going to LDSTools comes directly from CDOL with no intermediate data set so there is very little chance the problem is there. Have you verified that CDOL is correct?

I expect that the problem in the thread you referenced is also a problem getting information from MLS to CDOL. That's usually where these things go wrong.

MLS at our clerks office does not match CDOL. LDSTools does not match CDOL. Our MLS is up to day and we transmitted and received last Sunday. Must be a problem between MLS and CDOL, but it is trickling through to LDSTools.

ammonihah wrote:MLS at our clerks office does not match CDOL.

Since you did not say how they do not match I am assuming there are some missing callings in CDOL based on post #1. You may want to synchronize MLS and CDOL. To do this follow the procedure in the Correcting duplicate or missing callings section of the Callingswiki article.

I can understand the ward directory on LDS.org and MLS mis-matching, but my father-in-law's LDS Tools and LDS.org directory are very much out of sync (LDS Tools is missing a lot of callings). If both his LDS Tools and LDS.org directory both pull directly from the CDOL, then shouldn't LDS Tools and LDS.org match?

I believe that you have to tell LDS Tools to synchronize its list with the website.

randoogle wrote:LDS Tools is missing a lot of callings

LDS Tools (at least on the Android) doesn't support custom callings. Only standardized ones.