Restore from Backup isn't Correct/Complete Datafile
Last week my MD file apparently became corrupted because when I attempted to open it again I got a "Bad Padding Exception" error. So, I attempted to restore from my backup, but the resulting new file was incorrect.... most obvious issue was tons of money showing in 2 accounts that have been closed for 2yrs. I dug around a little in the "folders" within the original file and came across the tiksync/out folder containing 438 little txn files. Do these need to somehow be re-imported? I am still using MD 2021.1 (3069) just haven't gotten around to upgrading to 2022. I do NOT use sync, only use MD on my 1 PC - although I do keep the file in a different location than the default.
Trying to figure out how to get my file back to its complete state from last week. Appreciate any tips!
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by jkosa on Jun 13, 2022 @ 11:47 PM
Forgot to attach the errlog.txt in case it helps. I do notice in here that there are numerous warnings "transaction is assigned to root account" Wondering if this is part of my issue.
2 Posted by Stuart Beesley ... on Jun 14, 2022 @ 09:38 AM
'warning: transaction is assigned to root account:' is a big problem.... I would NOT use this dataset..
I would humbly suggest that you keep going backwards looking for a backup that is clean of errors/problems...
As for the 'tiksync/out folder containing 438 little txn files'... Depends in what dataset they came from... In theory, these could be reapplied to a good restored dataset to roll forward to current day.... However, you would have to be an expert to make this work and you would have to be very sure of the start and end points... Personally, I've not seen this done (in this forum)... I expect you would need a screen-sharing session with Sean (developer) if this were to be attempted...
Perhaps support can jump in and help you further here?
(not support, just a fellow user)
3 Posted by jkosa on Jun 14, 2022 @ 02:25 PM
Thanks for your reply Stuart. I have now restored from a week prior backup and the numbers all look good. I think I can remember a week's worth of xans - most are likely just downloads from my bank.
But, in my errlog.txt I still have many warnings about xan assigned to root account. I will search the forum for that issue now. The log doesn't show enough specifics for me to go look at the xan in MD, but they are all SplitTxn possibly in my investment accts. Hmm.
4 Posted by Stuart Beesley ... on Jun 14, 2022 @ 06:05 PM
OK, so what's happened is that somehow you lost/deleted an account/category that was being used by these Investment txns.. They all seem to be Xfr which are cash transfers to/from an account/expense.. I suspect therefore that your 'missing' data is not missing, but it's hiding under the root account...
I have written a script/fix that will create a new/fake expense category, and then reassign the new fake category to these txns with the warning.. This does NOT delete them... It means they will still be valid. HOWEVER.... You will need to assign the right account/category.. I cannot help unless you say that they should all be the same..
BACKUP FIRST..
Download and save this script file.
Window > Show Moneybot Console.
Click Open Script. Select this file. Then click RUN (not run snippet)... Watch the console output...
As I say, I have tested it with my own simulation test data.... But BACKUP FIRST...
Let me know how it goes?
5 Posted by jkosa on Jun 14, 2022 @ 09:05 PM
Wow - incredible thanks to you Stuart.
Fixes applied to 802 parent txns.. Please check your txns and the expense category: **FIX-FOR-ROOT-TXNS**
Finished running normally at Tue Jun 14 16:46:18 EDT 2022
I then closed and reopened and Exported another backup etc. My errlog.txt is now free of the warnings : )
You were right that all of these xans are from a contribution to my 401k up until 2019. When I converted from Q to MD 2yrs ago, all of those came in with the category "Auto" if I recall. I had to do a bunch of work to get the 401k acct setup correctly for MD going forward, setup my payroll split to work correctly, and left those old xans as is. I think it had to do with not being allowed to record a transaction into the same acct that Q used to permit.
Apparently then, sometime in the past 6mo, I'll just guess it was in January!, I was cleaning up that "Auto" category to be "Automobile" with sub expenses for Service, Fuel etc. Don't remember exactly how I cleaned things up for the car expenses, but I'm sure I didn't remember all the old 401k contribs. Seems likely that messed things up.
Again thank you for your help with this! Jaimi
6 Posted by Stuart Beesley ... on Jun 14, 2022 @ 09:15 PM
So now you really could do with reassigning these txns from the fake category to the right category/account. OR you could just rename the category to something more meaningful (like quicken_401k_contribution) if in fact they are all the same thing…. Anyway up to you.
👍 +1 😃
System closed this discussion on Sep 13, 2022 @ 09:20 PM.