Quicken 2008 and Vmware Workstation 6.5 B2

bsobel

Moderator Emeritus<br>Elite Member
Dec 9, 2001
13,346
0
0
Well, 2 hours of my day were spent realizing that Quicken 2008 (for reasons I'm sure someone will point out, but I cant come up with) sets a fricken windows hook which is dragging a bunch of their dll's into every process when it's running. Worse, they carry around a xmlparser.dll which gets pulled it to. Well, Vmware Workstation 6.5 carries around its own (and different) xmlparser.dll, so they two dont get along together.

And since its being pulled in via the hook, no path or other tricks are gonna work. Now I need to deal with Intuit support (yea me) long enough to get to someone who will actually understand this there.

Ugh (my rant is now done). Also, this is an FYI if your running into this (apparently Adobe Elements also fails thanks to quicken because of this same issue)..
 

BigPoppa

Golden Member
Oct 9, 1999
1,930
0
0
Sort of ties into your rant...

We (meaning computer users) run into these problems quite often. Poor coding practices lead to huge issues. This is, in my opinion, the cause of the vast majority of issues that people run into with Windows Vista. All the barebones Vista 32/64 + drivers only installs work absolutely flawlessly. It isn't until multiple applications are installed that issues crop up.

I wish you luck on getting someone from level 2/3 support for a fix.
 

mapte

Junior Member
Sep 26, 2008
2
0
0
I am having the same problem.

I had VMWare workstation 6.0.5 and Quicken 2008 and things were fine.
I upgraded to VMWare Workstation 6.5 and I started having the xmlparse.dll problem. I upgraded Quicken to 2009, but I still have the same problem.
 

bsobel

Moderator Emeritus<br>Elite Member
Dec 9, 2001
13,346
0
0
Yea, looks like they didnt fix it prior to release (damm it!)

 

Czar

Lifer
Oct 9, 1999
28,510
0
0
create a vm to run quicken or setup quicken with software like thinapp or softgrid, that way quicken can use its own dll in its own sandbox
 

mapte

Junior Member
Sep 26, 2008
2
0
0
Since I had both vmware 6.0.5 and quicken 2008 living together happily, I don't know who is the culprit, vmware 6.5 or quicken 2008/2009.

I started seeing the problem when I upgraded only the vmware to 6.5, quicken was still 2008.

I get the following error.

The procedure entry point XML_ParserCreate could not be located in the dynamic link library xmlparse.dll

The above dialog comes up if my quicken is running and I move my mouse over the vmware.exe's main window. As soon as I quit quicken the problem goes away.
I get this dialog continuously as long as quicken is running.