Thanks for your response. I was able to delete the reg. file and that did get rid of the 'error loading extension', however I am still getting the other java error 'an unexpected error...' which is preventing MD from opening still. I'm guessing this is not necessarily a Foresight issue but Java? I did download and update Java just now but still no luck. Any ideas about that (Windows 10)? Also, I have not made any other changes to my computer for some time.
Thanks for your help. Well this just goes from bad to worse. The last auto backup I have is from almost a year ago, I remember now that I turned it off because it was so disruptive and took so long to backup I got frustrated with it.
There was another option to open a synced file from the Getting Started screen, since I have been using sync with Dropbox all along I thought that should work. Went through the process and all it could find was the same file from the old auto backup. I checked in my Dropbox folder and the moneydancesync folder is there with my most recent usage that worked, why won't MD locate that? Is it not possible to restore a synced file?
OK, so on your secondary computer do a FILE – EXPORT BACKUP.
Make sure Moneydance is closed on both computers.
Sign into your Dropbox account online and make a copy of your “.moneydancesync” folder under another name as a backup.
If the secondary computer is not already upgraded to 2020 upgrade it.
Open Moneydance on your primary computer. If Moneydance opens in the Welcome to Moneydance window click CREATE A NEW ACCOUNT SET or if Moneydance is open in a data set click FILE – NEW.
Then click OPEN SYNCED FILE. Use the dropdown to set the same sync method as you were using. Click NEXT and highlight your good data set from the list. Click NEXT and enter the same encryption password (passphrase) for syncing as before and click FINISH. If your data set is synced back into your computer it will be as a second computer data set, you can’t change the sync method and need converting into a primary computer data set as below. Also, you may find a lot of old, maybe closed accounts or other accounts you have removed from the side bar reappearing in the side bar. Use the “+” sign at bottom of side bar then ADVANCED to tidy up the side bar.
Procedure for converting a secondary data set into a primary data set.
Do a FILE – EXPORT BACKUP in case something goes wrong.
To convert a secondary data set to a primary data set you need to run the attached script md_convert_secondary_to_primary_data_set.py in Moneydance 2020.
With your data set open click WINDOW - SHOW MONEYBOT CONSOLE use OPEN SCRIPT to select the script and click OPEN then RUN. Wait until the script has run, this may take some time. Close and reopen Moneydance. You should now be able to change the syncing method, leave it at the current syncing method.
You should now find all your devices are syncing again with your primary data set recovered.
I had to go off script because when I got to the Welcome to MD (this is on the original primary computer that was botched up) and tried to Open Synced File I ended up back at my post #13 where I said that the only available file showing was from Dec. of 2019, so that was a dead end again. Instead, after I returned to Welcome I chose to import the file I had backed up from the secondary that you told me to do at the beginning.
At this point I had a good working file again but as predicted syncing was not available, so I ran the python script which did restore it to being primary syncing pc. But, the secondary was now apparently disconnected from syncing with my new primary and it was not possible to change the syncing method on the secondary.
So what do I need to do now to re-connect the secondary to sync with my restored primary?
When you have to create a new primary system from a secondary it is not possible to reconnect to the existing syncing relationship. You now effectively have a new standalone Moneydance system so you need to build a new syncing relationship from the ground up.
This means following the standard instructions for building a fresh syncing setup, the instructions can be found in the knowledge base.
Wait, that isn't what I thought it was because the new problem I have is that I can't change the syncing method on the secondary, I'm locked out of doing anything with it. I seem to recall some convoluted method of deleting syncing information from the secondary in order to be able to get back to being able to choose the method of syncing.
The syncing method was only every capable of being set on the primary system. With a secondary system when you are setting it up you use the Open synced file command and set the syncing method to be compatible with how the primary created the syncing relationship. Syncing type cannot be changed on the secondary and can only be changed on the primary if you either have the original data set there or a backup of the original data set. If you restore from a secondary backup you have to go back to having a standalone data set which has no relationship to the syncing relationship that was present.