"Margaret" wrote
The only log files I have in my Quicken data directory are qfilenameOFXLOG.DAT and qfilenameOFXOLD.DAT. (Should I be looking elsewhere for CONNLOG?) I opened each with a text editor, but they look like HEX files. Consequently I see nothing like the "QFX_enabled='T'" (or any other text strings) you mention. Regardless, I've since run OSU several times, so the log files that most likely contain info related to the phantom transaction have been long overwritten. I didn't even *think* about saving the log files! :-(
I did just try a regular Web Connect download, and the spurious transaction was not there. Also, after I deleted the phantom transaction from the OSU download (without accepting it), Quicken successfully balanced my account *without* the phantom transaction. Strangely enough the transaction looked authentic.
Unfortunately it didn't occur to me the error might be the fault of Quicken, so I didn't save any evidence of the anomaly because I'd spoken with ACU.
------------------------------------------------------
To read the log files, use Quicken Help > Log Files. Choose OFXlog or Connlog.
[You can also Save the OFXlog to a TXT file from there; often (for some financial institutions) you can use Word (or similar) to help make the OFXlog more readable. And the Connlog file is already a TXT file, so it can be read with Notepad, as well as from Quicken Help.]
The OFXlog, as you now know, is in the folder where the Quicken data resides. The Connlog (for Win 7) is in:
C:\Users\YourWindowsUserName\Application Data\Intuit\Quicken\Log
Normally I would say: To capture appropriate log files, you should be able to create a New test Quicken file (in a separate folder), and do an EWC for the one account in that new file, then save the log files. You could rename the Connlog file just before starting the download, then it should only contain data from the one download ... though this probably isn't necessary for Intuit's purposes.
But there is some reason to believe that this may confuse the issue. As I understand it, when you setup the download in a new Quicken file; Intuit creates a new user-profile for that account/file on its EWC server. Under some conditions, it seems, this interferes with Intuit's ability to analyze the problem and construct a solution. I have not had the problem so I can't speak from experience, and my memory may not be completely accurate here. This is more in the way of a heads-up, in case you get some response from Intuit that your log files were not valid.
I believe the fact that you don't see the problem with a plain Web Connect download tends to confirm the fi's claim that it's not their problem, and to indicate an Intuit screen scrape problem.