I don't believe there is any specific Money KB article on setting up a
firewall to work with Money, since there are several different firewall
sofware packages available. If the firewall software itself does not help,
the I've heard what works sometimes is to actually remove the firewall
software, install Money and make sure it works fine, then reinstall the
firewall (which will "hopefully" grandfather in the connections from already
installed software).
There may also be a way with the firewall software to set it to "Prompt"
instead of automatically blocking access, that way you can allow the
connections that Money attempts to make.

I don't have a BofA account, so I'm not sure that I can help too much with
that. It may be that specific set of banks at BofA (BofA has a variety of
connections, since they've gobbled up other banks).

-Mark

"Shawn" <Shawn[at]discussions.microsoft.com> wrote in message
news:67FE6E63-95D8-4F0B-9028-71536E33ADF9[at]microsoft.com...
- quote -

FWIW I am using ZoneAlarm Pro with Money 2005 and didn't have to do anything
to ZoneAlarm when I upgraded to M2005.

Check Program Control > Programs tab in ZA and make sure that there is an
entry for MSmoney. Highlight the entry and check in the panel at the bottom
of the screen that the path to Money2005 is correct.

--
Regards
Bob Peel,
Microsoft MVP - Money

For UK tips & fixes see
http://support.microsoft.com/default...d=fh;EN-GB;mny.
For wishes or suggestions see
http://register.microsoft.com/mswish/suggestion.asp
or for UK wishes http://www.microsoft.com/uk/support/money/feedback

I do not respond to any emails that I have not specifically asked for.


"Shawn" <Shawn[at]discussions.microsoft.com> wrote in message
news:67FE6E63-95D8-4F0B-9028-71536E33ADF9[at]microsoft.com...
- quote -

Yes, I did try disabling Zone Alarm but it didn't seem to make a difference
after restarting Money.

What seemed to finally work was running "salv.exe" again. It seemed to stop
the lockup (for now). I believe I did this while I had Zone Alarm disabled
(I don't know if it made a difference or not). The thing about it is, I
can't remember exactly if I used this utility on this file or not before. I
believe I said that I had in my original reply to this thread because I've
tried restoring my Money 2004 file and restarting the upgrade several times
and have run the "salv.exe" util many times in the process.

Some problems still persist:
1) I'm still not getting "current" transaction updates from Bank of America.
2) One of my Bank of America Savings accounts did not get created when
setting up online services the first time. My checking account and one of my
other savings accouts did get setup.

Do you have a similar setup to mine? I.e. are you using Zone Alarm, too?

Do you know if there is a Money KB article on how to setup a firewall to
work with Money 2005?

-Shawn

"Mark" wrote:

- quote -

Have you tried disabling Zone Alarm (or even uninstalling it) to see if that
is the source of the conflict?

-Mark
"Shawn" <Shawn[at]discussions.microsoft.com> wrote in message
news:3BDE6F1A-194B-4C97-BA7A-7C0AE0A44185[at]microsoft.com...
- quote -

I am also having lockup problems with 2005. Maybe we should all compare
notes and look for commonalities. I'm using:

* Windows XP SP2 with all latest updates
* I have ZoneAlarm Pro firewall installed and have the Windows Firewall
turned off. I have setup ZoneAlarm so that it will let the "msmoney.exe"
program access the internet.
* Money 2005 Deluxe and has automatically downloaded it's latest program
update (last one was in mid-November I think)
* I upgraded from 2004 Deluxe
* I use Bank of America
* I use MSN Bill Pay


I noticed the lockup problem after I did the following:
1) I restored my 2004 money file (the one that ends in .M12) - doing this in
2005 automatically converted my money file. I was informed that the Access
Money on the Web feature would be disabled so the upgrade could be performed.

2) I exited and restarted money 2005 after my file was upgraded. I made
sure the msmoney.exe process went away by itself (I watched through Task
Manager) and did not kill the process or anything.

3) I then re-enabled Money's access money data on the web and told Money to
use my Money accounts from my computer instead of the ones on the web (MSN
Money, I guess). This seemed to create a new MSN Bill Pay checking account
in my Account List named, "Bank of America Checking-#1". My checking account
in money is called "Bank of America Checking".

4) I went to Manage Online services and setup Bank of America online
services. After doing this, I could see 2 new Bank of America accounts in my
Account List. One for my checking and one for one of my savings accounts.
For some reason, my other savings account did NOT show up (I believe this is
a BUG with Yodlee or Money).

5) I then merged my 2 new Bank of America accounts with the ones I had in
money already.

6) I then merged my MSN Bill Pay account with my checking account. Doing
this threw my starting balance for my checking account (now called "Bank of
America Checking-#1"). It basically reset my starting balance back to zero.
So, I tried doing a quick repair which did NOT help. Luckily, I had recorded
the starting balance for my bank accounts and manually set the starting
balance for my checking account which seemed to fix the problem.

7) About 2 to 3 minutes later, Money locked up and my CPU utilization went
to 100%. The only way I could kill Money was to kill the msmoney.exe process
using the Task Manager.

8) I tried rebooting and restarting Money but the same thing happened
immediately after starting Money.

9) I tried the "salv.exe" utility but it did not help, either.

I believe this is some kind of deadlock problem or race condition
(programmer's speak) with the msmoney.exe process or one of the threads that
it spawns. I was able to watch the msmoney.exe process using programs from
SysInternal's called File Monitor and TCP Viewer. I can see that msmoney.exe
is still reading my money file over and over again and accessing a file in my
IE cache. It is accessing these files over and over again in a pattern which
makes me think that Money is stuck in some kind of loop.

Overall, I am very frustrated with this product. I really DO NOT want to
have to create a new Money 2005 file and start all over again if this is due
to some kind of file corruption issue!!! It seems that every problem I've
seen addressed by support is related to file corruption problems. If file
corruption problems are such a nuissance then Microsoft programmers should a
better job of preventing corruption problems in the first place (I wonder if
Quicken has corruption problems, too?). Or, at the very least they should
provide a mass export/import feature with on the fly corruption
checking/prevention so that all accounts, budgets, reports, etc. can be
imported into a new money file (that's probably what "salv.exe" is supposed
to do, though).

IMHO, I really feel like this product was not QAed heavily enough because it
was rushed out the door (just like it is every year to try to match Quicken's
yearly offering). But, I do understand that QA can only cover so many
different combinations of Money with different online banking services. I
think this will be my last time to buy the next version of Money so quickly
after it comes out. Next time I think I'll wait a good 6 months before
upgrading _IF_ I decide to stick with it after this.

"Mike" wrote:

- quote -

I have a similar problem. Mine locks up as soon as the file is opened.
I believe this is a conversion error in Money 2005. I even tried
converting a m10 file witch is a backup from Money 2002 with the
same results. I was able to export QIF files from money 2004 and
import them into Money 2005. Seems unlikely that if the corruption
occurred in Money 2002 I would have been able to upgrade to Money 2003
and then to money 2004.

Jonathan



On Mon, 22 Nov 2004 04:07:02 -0800, "wiredup"
<wiredup[at]discussions.microsoft.com> wrote:

- quote -

Mike,

Couple of things:
1. can you create a new file and logon? If so, then your .mny file may be
corrupt.
2. have you tried to run the salv.exe (located in money directory) utility
against your .mny file?

If (1) is true and (2) doesn't change anything, then go to your backups. If
you do not have backups, you are screwed.

I had Money Planner errors all over the place. Did above with MSFT
support--no result. Had to go to 2-day old backup (which is better than
nothing!)

Good luck.

"Mike" wrote:

- quote -

Hi all. First time here. Got frustrated with two hours of phone support
with no solution and figured I'd have more luck here!!

Have used Money with no probs for a long time, till I upgraded from 2004 to
2005.

After installation all went well for maybe five program "start ups". On
the sixth, Money freezes (as in "program not responding" in the Task
Manager...).

I've reinstalled maybe five times. Each time, it works fine for maybe four
or five "start ups", then I have the freezing/crashing problem.

The program starts fine - it's only after "sign in" that the lock up occurs.

I'm on Windows XP Home Edition and everything else seems to run fine.

Thoughts? Suggestions? Help?

Thanks all

Mike
Atlanta