I'm creating a bugzilla account to report this - but I still get the same error. When I do the install I get an "upgrade" message - which makes me wonder if some old stuff is lingering around.
How do I completely uninstall the previous version? Do I need to uninstall all the installed components and then reinstall everything? If so, some hints about getting rid of the old stuff would be of help to a Mac-novice. Thomas D. Uram wrote: > > This problem has been fixed in a new build of the Intel Mac package, > available from the AG3 OSX webpage: > > http://www.mcs.anl.gov/fl/research/accessgrid/software/releases/3.0.1/macosx.html > > > > Note that Intel Mac support is still relatively new; please report any > problems you > find to the AG bugzilla server at: > > http://bugzilla.mcs.anl.gov/accessgrid > > Tom > > > > Bob Riddle wrote: >> this is the same error I shared with Suzanne during the AG Retreat. >> Tom Uram thought he'd have a "fixed" version out by in the next week. >> >> Tom? >> >> John Dalton wrote: >>> Hi All, >>> >>> I'm trying to get AG 3.0.1 running on a MacBook Pro. >>> >>> If I click on the icon, nothing happens. If I run the script >>> directly I get an error: >>> >>> casper:~ jrdalton$ >>> /Applications/AccessGridToolkit3.app/Contents/MacOS/runag.sh >>> Traceback (most recent call last): >>> File >>> "/Applications/AccessGridToolkit3.app/Contents/Resources/bin/AGLauncher.py", >>> >>> line 8, in ? >>> from AccessGrid.Toolkit import WXGUIApplication >>> File >>> "/Applications/AccessGridToolkit3.app/Contents/Resources/lib/python2.3/site-packages/AccessGrid3/AccessGrid/Toolkit.py", >>> >>> line 22, in ? >>> from AccessGrid.Preferences import Preferences >>> File >>> "/Applications/AccessGridToolkit3.app/Contents/Resources/lib/python2.3/site-packages/AccessGrid3/AccessGrid/Preferences.py", >>> >>> line 12, in ? >>> from AccessGrid.interfaces.AGNodeService_client import >>> AGNodeServiceIW >>> ImportError: No module named AGNodeService_client >>> >>> I have MacPython 2.4.3 installed on this box, which may be a >>> problem? I've tried re-exporting my PATH without MacPython in it >>> before running the script, but the result is the same. >>> >>> Any ideas what I've done wrong? >>> >>> Yours, >>> >>> John Dalton >>> >>> --John Dalton >>> Senior Systems Administrator >>> IT Resources - University of Tasmania >>> >>> >>> >> >> > >
