The link you referenced is either invalid or more likely a private discussion. If you want help from other users post the version and build of Moneydance you have on both computers. Confirm you are only trying to sync between two computers. What are there operating systems and what Dropbox syncing method are you trying to use, Folder or Connection. Provide any other information you think would help support or others to help you.
on 17 Dec, 2018 04:16 PM
this particular problem is showing up on Windows 10, using Moneydaynce 2017.10 (1706) - on all computers.
I am trying to sync between three computers in fact: at least at first. I have a desktop
which has the master record and a laptop which is sync'd to it (via dropbox folder mechanism) and I am attempting to retire the laptop and replace it with a new laptop.
The issue that I am finding is that the new laptop does not show the moneydance file/folder/name I am expecting to see when I attempt to create a new file on the new laptop from a sync'd source.
The last time I tested adding a third computer to syncing the name I was presented with under FILE – NEW – OPEN SYNCED FILE was instead of my master data set name a long alpha numeric string. The folder name you find in the sync folder “.moneydancesync”. Selecting that should work. The only problem comes is if you have more than one alpha numeric folder in “.moneydancesync. Which one to select. In each of the alpha numeric folders you will find a text file mdsyncinfo.txt Opening this file should show the data set name its associated with.
If this does not help then you may need to reset syncing, if needed I can post a procedure.
Showing a long Alphanumeric name instead of the data set name you are familiar with is a known issue, no one seems to known why it happens.
Moneydance itself does not use the data set name that you known instead it generates the long alphanumeric name you see that should also be unique and uses this name internally in the syncing process. When you add a computer to the system it is supposed to look up the name you use and display this but it sometimes doesn't.
As Derek has suggested you need to identify which data set it is that you need to use and use the associated alphanumeric name. What will likely happen is that Moneydance will use this name for the data set on the new computer. To fix this simply close Moneydance, use Explorer to rename the data set, which is a folder on Window to what you want, restart Moneydance then you should see the data set under a more familiar name that you can open.
The bug in this case is more an annoyance than anything else.
on 17 Dec, 2018 10:19 PM
Hi Derek & DWG,
Thanks for your suggestion - it made a lot of sense and I started to work out what I thought was going on, however something isn't working as I thought:
When I go into the .moneydancesync folder on the new laptop, I can see a number of folders with checksum-style names - 1db3edb4-9ecc-<etc> and there is one that corresponds to the data that I'm trying to sync to.
But when I open moneydance and then try to create a new fsync'd file from a dropbox folder none of those checksum folders appear as options to sync to and instead I see four other folders which aren't present in the .moneydancesync folder at all.
Is this something that I can rescue or am I going to have to reset the syncing? (Which isn't the end of the world as the master computer is still working fine).
It's probably recoverable, but it sounds like you have had your share of system problems. Given this I think I would personally be inclined to take it back to single system operation, clean out all the crap from Dropbox and setup it up cleanly from scratch. now would seem to be a good time to do this.
on 18 Dec, 2018 10:01 AM
I think you make a good point - now is the time to do it. So I assume what this entails is going to the master version of moneydance, setting that to "Don't Sync", (make a backup in case), and then deleting the .moneydancesync folder from dropbox? .. and then set up the sync'ing as normal?
If you are using Dropbox folder, after deleting the moneydancesync folder from Dropbox make sure it gets deleted in you local dropbox folder, in other words make sure the deletion is replicated everywhere, you don't want any remnants.
If you are really paranoid you could restore your data from backup test it and use this to setup syncing, removing your original data set (backups actually removes some syncing information from the data set) Like I said it depends on how paranoid you are.
I agree with dwg. Resetting syncing may seem a big task but its safer and less trouble in the long run.
After setting don't sync on your primary computer and doing a backup and deleting Dropbox folder ".moneydancesync" I would also delete all the data sets on all your secondary computers before starting the syncing process again. Make sure the sync folder and all its contents are present on a secondary computer before you start secondary computer syncing.
Syncing is one of those things that has to be just right, there is no near enough option.
If I recall correctly your primary machine failed and you rebuilt a Moneydance data from the syncing data in drop box thus creating another secondary system. You then made this system into the primary machine.
This is not a standard practice it is rather what should be referred to as Disaster Recovery, you are one step away from completely losing the data but you were fortunate, it is only due to the way syncing works that make it viable, it is not the intent of this data.
After such an event I think it is time to take stock. Because of the process there is going to be orphan data set(s), your new master can not use the data that is already in drop box because that data belongs to another master - one that will never again be present so there needs to be a cleanup, dropping back to a non-synced system and cleaning out all old data is often the easiest and most straightforward approach to take, navigating though data sets to work out what is an is not active can be a little dangerous.
There is syncing information internal to the data set, I also think it can be advantages to clean this out as much as possible, I can envisage old data causing confusion - it would be nice if IK wrote a script that would complete wipe all syncing information from the data set, I do not think there is a process or a series of processes that do this!
on 19 Dec, 2018 08:26 AM
Hi Derek & DWG,
I took your advice and cleaned everything out - both on the master and the new sync'd machine (I basically took the recent backup which was known to be good - deleted EVERYTHING else and started from there).
For anyone else reading this in the future, it took two goes to get this right. The issue being that when you initiate the share via a dropbox folder you must make sure that everything is fully sync'd on both the machines before you start the secondary moneydance slave. Otherwise the slave just doesn't see the sync data .. still .. which was probably the real thing I did wrong in the first place.
Derek & DWG - many many thanks for your help on this. Invaluable.