Moneydance fails to load after Java update OS X 10.5 Update 4
Following the Java Update to Mac OS X 10.5 (Update 4) Moneydance fails to load.
-
Picture_2.png
21.8 KB
Picture_2.png
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by cbtengr on 16 Jun, 2009 12:00 PM
I ran the update last night (OS X 10.5.7) & MD runs. Are you using 10.5.7?
Check Java version being used. It's easy to do from the Terminal, instructions here:
https://wiki.csuchico.edu/confluence/display/usrvkb/How+to+Check+Your+Java+Version+(MAC)
My result was: java version "1.5.0_19"
2 Posted by neil.patton on 16 Jun, 2009 12:45 PM
Hi,
I am using OS X 10.5.7
The Java version is as follows:
NP:~ NP$ java -version
java version "1.6.0_13"
Java(TM) SE Runtime Environment (build 1.6.0_13-b03-211)
Java HotSpot(TM) 64-Bit Server VM (build 11.3-b02-83, mixed mode)
I've tried the following:
I downloaded a "fresh" copy of Moneydance to see if it was the Add-ons that were causing the problem (Budget-Bars, Find/Replace). The problem still occurred.
I tried playing around with the Java settings/preferences to use previous versions of Java - same problem.
Right now I'm locked out of Moneydance. I look forward to someone telling me where I went wrong.
3 Posted by Brian Adler on 16 Jun, 2009 01:53 PM
Blade,
Open the Java Preferences application (in /Applications/Utilities) and drag the "Java 1.6" (or Java 6) item above the Java 1.5 (or Java 5) item in the list of java versions for applications.
4 Posted by neil.patton on 16 Jun, 2009 02:28 PM
Firstly, thanks for looking into this...
My Java preferences are shown in the attached pic. They appear to satisfy your recommendation.
5 Posted by John Selden on 16 Jun, 2009 02:50 PM
In my Java preferences, Java 5 32-bit is listed before Java 6 64-bit. Again, I have not run the update yet. Maybe if you switch the order of those two, that would be a temporary solution for you until you get this worked out?
6 Posted by neil.patton on 16 Jun, 2009 02:56 PM
Thanks for the suggestion John. I did try that and it did not solve the problem.
7 Posted by cbtengr on 16 Jun, 2009 03:07 PM
Another possibility is to delete the Java plist files
Library/Preferences/com.apple.java
There are three files.
8 Posted by Brian Adler on 16 Jun, 2009 03:17 PM
Blade,
You should remove your extensions and start MD again. To remove your extensions go to the Finder and type Command-Shift-G (or Go->GoToFolder... and then type "~/.moneydance/fmodules" and move those extension files to another location. Then start Moneydance and you won't have any extensions but also will not see the error.
Once you've opened Moneydance, you can select the Moneydance - About Moneydance menu to make sure that MD is using the 1.6 version of Java.
From there you can re-add your extensions one-by-one to see which one is causing the problem.
9 Posted by Florence on 16 Jun, 2009 04:32 PM
I had the same problem as Blade.
Your last suggestion (removing the extensions) solved the problem. Thank you! Florence
10 Posted by Florence on 16 Jun, 2009 04:47 PM
In my case, it was the extension "findandreplace.mxt" which caused the problem. All the others (that I have) work fine. Maybe Blade could try removing just that extension and see if it is enough.
Florence
11 Posted by Brian Adler on 16 Jun, 2009 05:16 PM
That seems like a good suggestion Florence!
12 Posted by neil.patton on 16 Jun, 2009 08:34 PM
Problem solved.. as per Brian's procedure. "Findandreplace.mxt" was the culprit.
Moneydance (build 639) reports using Java Version: 1.5.0_19
That's a bit odd as the Terminal "java -version" command reports version 1.6.0_13 as described in the 2nd post of this thread. A minor technicality as everything is back working again.
Thanks to all.
13 Posted by alannies on 17 Jun, 2009 01:00 AM
I had the same problem and the same result. However, although MD is working fine, I can no longer use the findandreplace extension which I found very very useful. I tried reinstalling the extension and I get the Java error even though my java preferences are set correctly for that extension. I have emailed Kevin, the developer of this extension and have yet to hear from him. But has anyone gotten both MD and the findandreplace extension working after the java update? Alan
14 Posted by Richard on 17 Jun, 2009 01:28 PM
I am wondering about the post by Blade (#12).
Why is Moneydance reporting it is using 1.5.0_19 (under OSX 10.5.7) when the "java -version" reports 1.6.0_13?
I looked in the info.plist and it has JVMVersion set to 1.3+ which should use the most recent version as set by Java Preferences and indicated by the "java -version" command.
Does anyone get version 1.6 reported by Moneydance in the "About Moneydance" dialogue? Is this just an OSX thing, is it only certain systems or what?
Richard
15 Posted by Florence on 17 Jun, 2009 02:09 PM
Same here. Moneydance shows 1.5.0_19 and Java Preference has Java SE 6 as top choice.
16 Posted by alannies on 19 Jun, 2009 03:01 PM
The problem appears to be in the JavaApplicationStub that is part of the Moneydance application. To fix this, go to Applications/Moneydance and right click to show package contents. Then go to Contents/MacOS and rename the JavaApplicationStub to JavaApplicationStub.bak Then go to the Macintosh HD/System/Library/Frameworks/JavaVM.Framework/Versons/Current/Resources/MacOS and copy the JavaApplicationStub to the folder where you had created the backup above. Moneydance will now show the updated Java and will work with the find and replace extension. Alan
17 Posted by Florence on 19 Jun, 2009 03:14 PM
Works for me. Thanks to all for their help, especially Brian Adler and alannies. Florence
18 Posted by Vger on 20 Jun, 2009 11:45 PM
Alannies' solution above worked for me as well!
I recommend you post a not about this to the FAQ on the support home page, because a lot of Mac users are probably going to hit this in the coming days!
Thanks for the quick respond; I was dead-in-the-water also!
Vince
19 Posted by Brian Adler on 21 Jun, 2009 12:41 AM
Soon we will be releasing a new MD version (640) which will resolve this issue.
Raimund Buchholz closed this discussion on 17 Dec, 2009 01:21 AM.