Ticket Options

Question Details

TICKET ARCHIVE -> Shared Library Error

Faramarz - Nov 22, 2005 - 8:24 pm

Hi,

I have just gotten my first Shared Library Error. I tried to run Nikon's Picture Project, which has run before with no problem. I get-- The application "PictureProject" could not be launched because of a shared library error: ",<>".

I have a G4 Powerbook running 10.3.9

I tried reinstalling the Picture Project software and restarting.


Thanks,

Fred

BjarneDM - Nov 23, 2005 - 10:06 am

Is there no information about !which! shared library that's missing ?

--------
Bjarne D Mathiesen ; København ; Danmark
Mac OS X 10.4.2 ; 2xTiBook + 15" iMac + MacMini

Faramarz - Nov 23, 2005 - 9:03 pm

Hi Bjarne,

The entire text of the error message is as follows:

The application "PictureProject" could not be launched because of a shared library error: ",<>"

Thanks for your help.

Fred

BjarneDM - Nov 24, 2005 - 5:34 am

Well, we really need to find out !which! shared library that's missing. That error-message is giving almost no useful feedback.

Now, in /Applications/Utilities there's a program called 'Console'. Start that. Then try starting 'Picture Project' again. You'll have to look a little around in 'Console' for appropriate logs, but the System console log, your own user log and the crash logs are the ones primarily to look for.

Report whatever you find.

--------
Bjarne D Mathiesen ; København ; Danmark
Mac OS X 10.4.2 ; 2xTiBook + 15" iMac + MacMini

Faramarz - Nov 24, 2005 - 4:29 pm

Hi again,

Console listed error message:

Launch failed with error code -2804

The shared library error is <>

I sure hope I don't have to reinstall my system! I tried reinstalling Picture project with no improvement.

Thanks,

Fred

BjarneDM - Nov 25, 2005 - 5:37 pm

There's no help at all in the error messages you've posted on what's causing the underlying problem, so I can neither offer any further help nor a solution.

Sorry.

philippe99 - Nov 26, 2005 - 3:11 pm

Faramaz,
(A) could you first perform the following maintenance tips
First level
--------
Close all the running applications (except the Finder)
(1) Could you try to repair permissions
(must be admin)
Launch Applications/Utilities/DiskUtility
On the left pane, select the drive
On the right, select the First Aid (or SOS) tab
Then click on repair permissions and let run; don not worry about messages like " new permissions...."
Quit DiskUtility
Shutdown and reboot

(2) could also download Macjanitor
http://personalpages.tds.net/~brian_...acjanitor.html
and use it to run the maintenance scripts
The maintenance scripts are Unix scripts which are automatically ran on your
Mac between 02Am and 04 am..if your Mac is on at this moment.
I can advice you to run, through Macjanitor, the daily script each day, the week script each week, ..and so on

Second level
----------
(3) Could you also download Onyx
http://www.titanium.free.fr/pgs/english.html
Go into the cleaning tab and use it to clean the caches. use the defauts Onyx offers, do not
clean at this stage the system caches.
!!! Please download the release corresponding to your OS !!!

Third level
---------
Running fsck
To run fsck, you first need to start up your Mac in single-user mode. Here's how:
1. Restart your Mac.
2. Immediately press and hold the Command and "S" keys.
You'll see a bunch of text begin scrolling on your screen. In a few more seconds, you'll see the Unix command line prompt (#).
You're now in single-user mode.

Now that you're at the # prompt, here's how to run fsck:
1. Type: "fsck -y" (that's fsck-space-minus-y).
If the 1st pass says that nothing has to be repaired, try "fsck -fy"
Option "-y" forces a "yes" response to every question of the system, which is very important because answering "no" to a fsck question will stop the process !
Option "-f" forces fsck to chack a system that this command seems to have find "clean"
2. Press Return.
The fsck utility will blast some text onto your screen. If there's damage to your disk, you'll see a message that says:

***** FILE SYSTEM WAS MODIFIED *****

If you see this message--and this is extremely important-- repeat running fsck. It is normal to have to run fsck more than once -- the first run's repairs often uncover additional problems..

When fsck finally reports that no problems were found, and the # prompt reappears:
3. Type: "reboot" to restart,
or type "exit" to start up without rebooting.
4. Press Return.

Your Mac should proceed to start up normally to the login window or the Finder.


(2) could you also download the 10.3.9 combo
http://www.apple.com/support/downloa...pdate1039.html
and re-apply it over your existing OS

(3) beside Nikkon's application, do other applications show the same issue ?

Regards
Philippe