Website NOT in sync with MLS

[jonesrk]

I serve in a YSA ward which used to have 2 Elders Quorums; we have since deleted the second quorum, but cannot get 3 callings (and therefore the second quorum) to be removed from online.

I have used the 'Request Unit Refresh Data...' feature several times and did have some callings come through that we did not know we had, but the second Elders Quorum and the 3 phantom callings will not come back. They show up online, but not in our MLS.

Any ideas?

There is a bug in MLS that when you merge to quorums MLS doesn't send up releases for those in the quorum that was merged.

I don't know what you did but it looks like you only have one Elders Quorum presidency now in CDOL. If there are still some there that shouldn't be, let me know and I can clean them up for you.

[russellhltn]

They show up online, but not in our MLS.

Silly question, but where are you checking? If it's the classic LUWS, it doesn't sync with MLS. A website admin has to fix it.

If it's the CDOL or the new directory, it should sync, but it may take a day or two.

[pendletonkb]

Refreshing our unit data worked great and I was able to remove all of the duplicates and old callings from MLS (and now hopefully the website). Unfortunately, now our "Callings by Organization" link pops up "An Error Occurred" instead of the report. The error still occurs after a reboot.

In the log file I found this error:

[E] {Wed 2011-03-02 20:59:55} mls.shell.actions.CmdViewOrganizationDirectories: java.lang.NullPointerException
at mls.organizations.OrganizationDirectoriesTabPanel.init(Unknown Source)
at mls.organizations.OrganizationDirectoriesTabPanel.<init>(Unknown Source)
at mls.shell.actions.CmdViewOrganizationDirectories.doCmd(Unknown Source)
at mls.shell.CMDAction.actionPerformed(Unknown Source)
at org.lds.ics.jtg.tools.widgets.CSLink.fireLinkEvent(Unknown Source)
at org.lds.ics.jtg.tools.widgets.CSLink.mouseReleased(Unknown Source)
at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
at java.awt.Component.processMouseEvent(Unknown Source)
at javax.swing.JComponent.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
{Wed 2011-03-02 20:59:55} Log: 2.1: mls.util.Utils.showGenericErrorPopup(Unknown Source)
{Wed 2011-03-02 20:59:55} Log: 2.2: mls.shell.CMDAction.actionPerformed(Unknown Source)
{Wed 2011-03-02 20:59:55} Log: 2.3: org.lds.ics.jtg.tools.widgets.CSLink.fireLinkEvent(Unknown Source)
{Wed 2011-03-02 20:59:55} Log: 2.4: org.lds.ics.jtg.tools.widgets.CSLink.mouseReleased(Unknown Source)
{Wed 2011-03-02 20:59:55} Log: 2.5: java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
{Wed 2011-03-02 20:59:55} Log: 2.6: java.awt.Component.processMouseEvent(Unknown Source)
{Wed 2011-03-02 20:59:55} Log: 2.7: javax.swing.JComponent.processMouseEvent(Unknown Source)
{Wed 2011-03-02 20:59:55} Log: 2.8: java.awt.Component.processEvent(Unknown Source)
{Wed 2011-03-02 20:59:55} Log: 2.9: java.awt.Container.processEvent(Unknown Source)
{Wed 2011-03-02 20:59:55} Log: 2.10: java.awt.Component.dispatchEventImpl(Unknown Source)

[jdlessley]

Other units have reported the same issue in the thread "Callings by Organization" is no longer available. Help!. In that same thread post #18 says:

This problem is being caused by a corruption of the database.
Units that had custom organizational reports had the problem after MLS 3.3 was installed.
The solution is to call MLS Support (801) 240-3500 and advise them.
They will have you do a Send/Receive and then the programmers will send down a script file in a day or so that will correct the problem. Doing another install of the MLS program will not resolve this.

Even though you may be using a later version I think the solution is the same.

[mcallaghan]

This process didn't work at all for me. I requested a Unit Refresh Data. An hour later I did a send/receive, which said that data was refreshed. But nothing has changed. I don't see any duplicate callings in MLS, but there are still plenty on the web site. Any thoughts? Thanks!

[jonesrk]

This process didn't work at all for me. I requested a Unit Refresh Data. An hour later I did a send/receive, which said that data was refreshed. But nothing has changed. I don't see any duplicate callings in MLS, but there are still plenty on the web site. Any thoughts? Thanks!

I can see that the request for callings update came in for your Branch and that CDOL sent them back down. Those files aren't waiting so you must have gotten them. There is a large membership file waiting, so I wonder if this process only works correctly if it gets the membership update at the same time (I'm guessing here.) My other thought is if there is something that isn't working correctly for a branch. The other choice is to send feedback within CDOL and let them know which of the duplicates to delete. I am passing this along to the MLS QA staff to see if they know anything else.

[gammaxy]

My ward has incorrect/old information listed in the new online directory. Would the steps listed in reply #2 solve the problem or are they just for callings? There is a woman with an ex-spouse listed as her head of household, but the information in MLS seems current. Also, I suspect addresses are wrong as some of the automatically placed dots in the new map are at old addresses.

[RossEvans]

There is a woman with an ex-spouse listed as her head of household, but the information in MLS seems current.

That could be a case of this apparent bug if it involves a non-member spouse. The new online directory does not just report households as defined in MLS, but apparently harvests the name of non-member spouses from the confidential detail within the member's record. So non-member names that do not appear in MLS directories now appear on the website directories. They do not appear on the "classic" website.

That itself would be a serious bug. But the damage can be compounded if a couple is just separated, or if a divorce was never recorded on the member's record. (Such errors of omission are not uncommon, especially among less active members who don't report these facts to ward clerks.) Normally these erroneous details are confined to the confidential membership record and IOS. But because of the website bug, they are being published to the whole stake.

Also, I suspect addresses are wrong as some of the automatically placed dots in the new map are at old addresses.

That is a longstanding issue with the maps website. Apparently the geocoded locations do not get updated in a timely fashion when addresses change.

[ElliottCK]

I can see that the request for callings update came in for your Branch and that CDOL sent them back down. Those files aren't waiting so you must have gotten them. There is a large membership file waiting, so I wonder if this process only works correctly if it gets the membership update at the same time (I'm guessing here.) My other thought is if there is something that isn't working correctly for a branch. The other choice is to send feedback within CDOL and let them know which of the duplicates to delete. I am passing this along to the MLS QA staff to see if they know anything else.

Membership, Finance, Temple or any other files are processed independently of each other. There is no requirement or dependency between receiving or processing files. The data that is contained in the files are written to the MLS database. MLS enforces dependencies of the data once its written to the database.

I have replicated your scenario and do see the duplicates in MLS. I will send you a e-mail of the users I see duplicated so we can compare notes.

[kerryhaxton]

We have the issue that is addressed at the biginnning (Callings not in sync). I asked the unit to perform this, but the clerk said that in the past this caused Home teaching , and other things to get dropped... Is this still the case...