OL-220-A Error on only Fidelity accounts after transfer from Mac to Windows

jdsebo15

Everything appeared to be peachy after a transfer from mac to windows. However, i am getting a OL-220-A error on my 4 fidelity accounts. What i have tried:

1. These are connected via fidelity investment. not fidelity investment and retirement accounts.
2. My 2 fidelity net benefits accounts work perfectly.
3. My 4 fidelity retirement accounts work perfectly in Mac.
4. My fidelity accounts work perfectly in a fresh quicken windows file.
5. I used the online services tab of account details to deactivate and reconnect all fidelity accounts.
   1. this appears to provide temporary relief. It normally error's out after coming back to the file in 30 minutes or longer.
   2. I did this multiple times.
6. I have a fidelity cash management account with the option to "show cash in a checking account" selected.
   1. i set this setting to no and allowed the checking account to unlink and dissappear moving all of those transactions back to the investment account.
   2. I then tried disconnecting all fidelity accounts and reconnecting, with the same results as the above.
7. Reviewed the online OL-220 support article. My connection method is direct connect. I called fidelity and they had generally no idea what i was talking about. They had a support article that recommended creating a test account which is what led me to number 4 above. This was enough for me and the tech to conclude that the issue was on quickens end.

What i am thinking about trying is disconnecting all accounts and exporting each as a .qif. Deleting the accounts from Quicken and then readding them brand new. Then trying to recover my past transaction history with the .qif file. I'm not sure this will work though so i haven't tried it yet.

I have called support twice and chatted twice.

1. first call led to an unposted service alert with fidelity.
2. second chat led to an unposted service alert with fidelity.
   1. i found these weird because it works as expected 100% of the time in my test file and mac file. just not in my windows file.
   2. Additionally, they would provide 0 details, mentioned that it wasn't posted on the community yet and they have no timeline or workaround. SO exactly zero details to share with me…
   3. lastly, i see no complaints on the forum at all. so i'm here posting this now looking for guidance.
3. second call led to a gentleman telling me that you can't transfer files from mac to windows like this and that i need to delete all of my fidelity accounts and restart from fresh.
   1. this was weird because i'm 99% sure it's not true. I assume we had a misunderstanding at some point.
4. first chat led to a productive conversation that got cut short by a disconnection…

Anyway, i wanted to provide as much detail as i could in hopes of getting the highest quality reply, so i apologize for the long wall of text.

Thanks to all in advance who are willing to help and happy new year!

Edit: i have reverted to my 12/16 backup and i might have it working again. This will result in a good bit of loss of data for me but probably won't be an issue. i still wonder what has happened to my other data file.

Quicken Kristina

Hello @jdsebo15,

Based on your description of the issue, the issue is most likely file-specific. When converting from Mac to Windows (or vice versa), there is always a small risk that some items won't convert correctly. I suspect that is the most likely cause of the OL-220-A error you saw after converting your file.

I'm glad to hear that the 12/16 backup seems to be working so far. If you haven't already tried it, were you able to find success with a more recent backup? Have you tried re-converting the original file (if you still have the Quicken for Mac version of it)? See this article for instructions on converting your file:

https://www.quicken.com/support/converting-your-data-quicken-mac-0/

When I look up your Support interactions, it seems like the agent who told you there was an unposted alert may have misunderstood the issue. The alert they linked in the ticket was for a $0 balance problem rather than an OL-220 error.

I hope this helps!