Access to bank when using Zone Alarm?

I was just wondering if reinstalling Quicken might solve the problem.

Notan

Frankly I hadn't considered that. Obviously I'd rather not do that, but at this point I'm getting desperate.

Before doing an uninstall and fresh reinstall, I think I'd just try reinstalling over your current installation.

Notan

oops. I guess I was getting a different error message. Sorry about that.

Where did you find this log? What's the filename? I'll check it against mine.

Laura, this is a Win2K machine with multiple users. The log is located at:

C:\Documents and Settings\Administrator\Application Data\Intuit\Quicken\Log\connlog.txt.

No, this started late on Friday, so I haven't had a chance to call the bank. That'll be my next step I think, before uninstalling anything. It just seems like an unreasonable coincidence that such a problem would start at almost the exact time I installed a firewall. I guess we'll find out tomorrow. I'll let everyone know what happens, and thanks very much for your help.

"Mike Fairleigh" wrote in news:T_Rhe.97$ snipped-for-privacy@newssvr11.news.prodigy.com:

This is part of my connlog.txt file this morning. It describes the error when the server isn't ready to communicate (being serviced in all likelyhood):

20050516 06:33:16: QFN: Beginning send to https://ofx-prod- brand.intuit.com/qw1400/fib.dll 20050516 06:33:17: QFN: End send to https://ofx-prod- brand.intuit.com/qw1400/fib.dll, netstatus 0 20050516 06:33:18: QFN: Beginning send to 06:33:18: QFN: End send to netstatus 020050516 06:33:18: QFN: Beginning send to 06:33:20: QFN: End send to netstatus 020050516 06:33:20: CPS Error : TSysHeader: Error: PSB SCHD ERROR - DIBSTAT=TJ(2 control characters)Start serv20050516 06:33:20:

Hope this helps

Sorry for not seeing this any sooner, but it looks like Laura and Han have you pointed in the right direction. Direct Connect does bring up a different set of troubleshooting conditions, which does not involve ZASS. I think Laura and Han are correct in thinking it is an issue with your FI and not ZA.

I hope this is sorted out soon. Take care.

Well, to close the book on this... I got set to call the bank this morning and tried an update once more first - and it worked fine! What are the odds that a service would be available without interruption for nearly 3 years (at least, if it was ever down I wasn't aware of it and I'm a frequent user), and then go down within an hour of me installing a firewall??? Well, apparently that's what happened.

Several of you folks hung in there and tried several different suggestions and helped with the troubleshooting, and I truly appreciate it. Thank you very much. Now, I'm off to buy a lottery ticket...

When you are dealing with computers, that can be the rule instead of the exception. Glad that it's working.

Your welcome. Now when you win don't forget us. :)

"Mike Fairleigh" wrote in news:%e4ie.267$ snipped-for-privacy@newssvr12.news.prodigy.com:

Probably, the FI "upgraded" their software, resulting in the bug you could get around. Thanks to your (and maybe others') complaining they fixed it. Congratulations! Nobody knows what would have happened without you saying something.