tag:infinitekind.tenderapp.com,2009-01-14:/discussions/problems/58048-disappearing-securitiesInfinite Kind: Discussion 2019-12-20T10:15:56Ztag:infinitekind.tenderapp.com,2009-01-14:Comment/479250832019-12-16T20:51:11Z2019-12-16T20:51:11ZDisappearing Securities<div><p>I'm fellow user.</p>
<p>It certainly sounds like odd behaviour.</p>
<p>Over the last few years there has been a common identified cause of some general odd behaviour with transactions so as a first step I would look to eliminate that as a possibility.</p>
<p>The data sets for Moneydance 2017 and newer should never be kept in your dropbox folder, or folders for any like service. Doing this seems to cause some very strange issues. So as a first step I would ensure that the Moneydance data is on a local disk.</p></div>dwgtag:infinitekind.tenderapp.com,2009-01-14:Comment/479250832019-12-17T02:11:45Z2019-12-17T02:11:45ZDisappearing Securities<div><p>I haven't seen this, but what version of MD and OS are you running. Please post the first dozen lines or so of Help->Console log or if you are comfortable after looking at it, the entire error log. Try a simple<br>
1. open MD<br>
2. Show Portfolio view and let the error show<br>
3. quit MD and post errlog.txt</p>
<p>(Mac OS) Library/Containers/com.infinitekind.MoneydanceOSX/Data/Library/Application Support/Moneydance/errlog.txt<br>
Press the option key and use the "Go" menu in the finder to access the Library folder.<br>
Or open a finder window, press Shift-Option-G and paste in this path<br>
~/Library/Containers/com.infinitekind.MoneydanceOSX/Data/Library/Application Support/Moneydance (Windows) C:\Users(yourusername).moneydance\errlog.txt</p></div>sthtag:infinitekind.tenderapp.com,2009-01-14:Comment/479250832019-12-17T02:59:24Z2019-12-17T02:59:26ZDisappearing Securities<div><p>Thanks both for the reply. My main files are stored on my local computer. but I do use drop box sync for the mobile app. And there is something curious there, there are .mdtxn files in my drop box folder dating to 2017. Is that normal? If that is the problem, what is the recommended work around to sync to the mobile app?</p>
<p>Macos 10.13.6<br>
MD 2019.3 1880<br>
Java version???? (I can't find the updater app, but many years ago I did have to deal with Java version conflicts between Moneydance and some other app I was using at the time)<br>
Attached is the errlog.txt file. The one thing I find curious is there is a common credit card transaction (not securities related)I made back in September 2019 from a trip to Alaska that has generated multiple errors. This is about the time the problems began (so maybe it's because of this transaction and not the 2019 upgrade?) . However, whatever is the reason for the error, my credit card transactions for this era have long since reconciled, so whatever is currently in Moneydance is likely correct. Is it safe to just delete all of the old .mdtxn files in my drop box folder?</p></div>dshafertag:infinitekind.tenderapp.com,2009-01-14:Comment/479250832019-12-17T03:11:10Z2019-12-17T03:11:12ZDisappearing Securities<div><p>My apologies. This is the errlog.txt file you want to look at, the one above was uploaded in error</p></div>dshafertag:infinitekind.tenderapp.com,2009-01-14:Comment/479250832019-12-17T16:49:11Z2019-12-17T16:49:11ZDisappearing Securities<div><p>That is some old files! They should be cleaned out with the 2019 version. One thing you can do to clean up is to disable Sync. Remove the Dropbox/.moneydancesync folder entirely and then reenable Sync. You might have to reset the remote devices as new files to the sync but this should reset everything. Older versions of MD seemed to keep very very old transaction files and you could end up with 20,000 files or more. MD 2019 fixed that and cleans up old transactions but maybe not in the sync directory?</p>
<p>In looking at the error log I have the following comments:<br>
MD includes it's own version of Java and you are running version:<br>
Java: 11.0.1 (Oracle Corporation)</p>
<p>You might want to remove the "Payoff Extension" and "Handybank" since it seems to be missing:<br>
file not found for Payoff extension<br>
I suggest removing and reinstalling all your extensions. There may have been some confusion during an update or a computer change.</p>
<p>You also have a bunch of bad transactions to be synced which may be the main source of your problem:<br>
Error reading synced transactions: java.lang.Exception: Unsupported action:4%260.desc%3DGifts%</p>
<p>I highly suggest turning off the sync and restarting it as mentioned above.</p></div>sthtag:infinitekind.tenderapp.com,2009-01-14:Comment/479250832019-12-17T20:01:00Z2019-12-17T20:01:00ZDisappearing Securities<div><p>I'm a fellow user.</p>
<p>There is certainly some crud in your error log. Some of it is legacy stuff from changes that have been made in the software.</p>
<p>I agree with sth that I would take it back to being a standalone system then build the syncing back up, after also doing some cleaning up.</p>
<p>You may find that through the Moneydance interface you can not remove the out of date extensions, this is unfortunately a hole in Extension management, you can try to edit your config.dict file to remove them (careful here as the file structure is important and do take a backup of the file before attempting this) or start with renaming the existing one and building another, alas the last approach does mean doing some re-creation of your preferences and setup.</p>
<p>The theme error is a result of some fields being removed, again you can try to edit the file to remove them.</p>
<p>After taking the system back to being a standalone solution I would delete all Moneydance data from Dropbox.</p>
<p>Once this is done I would have another look at the error log to ensure everything is clean before commencing on the syncing setup, if there appears to be any problems these should be looked at before going any further.</p></div>dwgtag:infinitekind.tenderapp.com,2009-01-14:Comment/479250832019-12-18T03:55:49Z2019-12-18T04:17:53ZDisappearing Securities<div><p>dwg and sth, thank you both for your input.<br>
I first found the offending credit card transaction, changed it's value to a new number, then changed back. I was hoping that would re-write the transaction in the database and fix the corruption. That didn't appear to do anything.<br>
I did both your suggestions at the same time, i.e. deleted all synch files and cleaned up the config.dict file. Not only did that fix the problem at hand, but the program seems more responsive in general.</p>
<p>The two plug-ins brought back memories, those two plug-ins were pre-MoneyDance 2015 plug-ins that that caused Moneydance to crash on launch as I upgraded to 2015. The program wouldn't launch until i deleted the files for those plug-ins from the fmodules directory, that's why they were still in the dict.conf file. Sad, I missed those two extensions and would even be willing to donate a few bucks for some developer to re-write them.</p>
<p>Thanks again</p></div>dshafer