Seen many complaints, no fixes though, sorry.

@IntuitBettyJo  Im sure this is on someones radar over there, we just havent seen anything official about whats being done to rectify the issue...got any news?

Just saying my two cents here but of the ones I've seen the root cause has typically been unsupported bank. And aside from that have seen Banks that require an MFA secondary step that doesn't come thru with Fido. Note that the import feature is meant to save time and if that's an issue you've had for that long you may want to manually enter. 

You've sat on a return for two months rather than manually summarize & enter the info?  Wow.

My back would hurt if I sat on something for that long.  What does your client think?  He or she must wonder what is going on.  They might have even read the instructions in the meantime  and found that you can just enter totals.

Multiple returns with many, many details transactions. 

But you can enter totals.

When you say multiple returns, are you producing that error with all of them? And do all use the same bank? Also is this doing scan and importing or is this doing Fido?

Many people have asked about it, many different banks, its been at least a month now. That same Error Code 1.

Noted @Just-Lisa-Now- tax scan and importing isn't my forte but figured I'd ask just in case. If all imports do this then I would lean towards software or the specific os. So let me ask this... When was ProSeries last updated and do you have any pending Windows updates not downloaded and or installed? And lastly if on a network can other workstations successfully import?

Slight additional edit: I will look at this Monday too when I get in the office, see if I can locate anything specific. and will report back if i find something specific to this. Promise 🙂  In the mean time i would stick by my recommendation of updating both ProSeries (and/or running Repair/Refresh updates) and checking to see if any Windows updates are pending.

The error code occurs when importing Fido. After the error message appears, the next message is "import has been successful" but the data do not show in the returns.  

ProSeries and Windows are updated.

Did you find out anything?

Investigation completed. Update released today fixed the problem. Thanks.

The direct import function is on the blink again the same as last year. Don't know why Intuit can't get this fixed. Spent 2 hours on the phone with tech  support to no avail. May have to do a work around. What a bummer. 

The Import function is a problem again this cycle. On the phone with Tech Support for 2 hours, and didn't get a solution. Is this problem being investigated and when can we expect a fix?