I, too, have recently experienced this problem. Quicken's support Web site says this regarding OL-221 errors: "These errors are caused by invalid information being transmitted by the financial institution's servers. Quicken Support does not have access to these servers or the information being transmitted by them and cannot resolve this issue. You can try the steps below to resolve it, but it may ultimately require action by the financial institution." I beg to differ. I'm a software engineer. I design, build and maintain eCommerce system for a large multi-national corporation. I performed a trace of network activity that occurs from Quicken when downloading transactions from PayPal. The following are my findings. Quicken does not connect directly to financial institutions from your computer. Rather, Quicken connects indirectly to financial institutions from your computer via various Web pages at services.quicken.com and financialdataaggregation.api.intuit.com. Transactions from your financial institution are obtained by Quicken via financialdataaggregation.api.intuit.com/soap/api using a sequence of six transactions. For each of the following six transactions, a status code of "ok" and a status string of "call successful" is returned. So all six transactions complete successfully with no errors. Transaction #1 CCLogonRequest - Your Quicken user Id and password are sent. CCLogonResponse - Your Quicken customer Id is returned. Transcation #2 CCGetInstitutionRequest - A "presence Id" is sent. I suspect the presence Id identifies the financial institution. CCGetInstitutionResponse - Lots of information about the financial institution, PayPal in this instance, is returned. Transaction #3 CCCompareAccountKeyValRequest - Your account Id and a key Id is sent to the financial institution. CCCompareAccountKeyValResponse - A value named "match" is returned. In this instance, that value is the letter T, which probably means "True". Transaction #4 CCGetAccountsRequest - You account Id is sent. CCGetAccountsResponse - Lots of information is returned about your account. Your account nickname, account number (which for PayPal is apparently your PayPal login), account type (checking, savings, etc.) and lots of additional data. Transaction #5 CCGetAccountTransactionsRequest - You account Id is sent along with a transaction start date. All transaction occuring on or after the transaction start date are returned. CCGetAccountTransactionsResponse - A list of transactions is returned. Each transaction contains lots of information. An Id, transaction date, posted date, amount, description, etc. Transaction #6 CCLogoutRequest - No data is sent. CCLogoutResponse - No data is returned. Your transaction download is now complete. As I mentioned above, for all six transactions, a status code of "ok" and a status string of "call successful" is returned. There were no errors. I went one step further and validated all XML data sent to and returned from the server. There were no errors. Whatever is going wrong here is happening in Quicken. The OL-221-A error does not appear in any of the six transaction requests or reponses. I suspect Quicken is somehow misunderstanding something in one of the transaction responses. When Quicken Support says, "These errors are caused by invalid information being transmitted by the financial institution's servers.", they appear to be mistaken. Every transaction response indicates success. No errors are reported. When Quicken Support says, "Quicken Support does not have access to these servers or the information being transmitted by them and cannot resolve this issue.", they are mistaken. All of the information coming from the financial institution's servers transits Quicken servers. Thus, they do have access to all of the data. When Quicken Support says, "You can try the steps below to resolve it, but it may ultimately require action by the financial institution.", they appear to be mistaken. The financial institution appears to be returning completely valid data. Again, no errors are reporeted in any of the transaction responses. They all indicate success. You can de-activate and re-activate online access to your PayPal account as many times as you want, but that will never fix this problem. Quicken needs to investigate this problem to the extent I have and identify and fix the root cause of this problem.
... View more
