Appleworks Failure to Launch

Help. I can't open Appleworks. I'm getting a red stop sign with an exclamation point that says "The application 'AppleWorks" could not be launched because of a shared library error:"- <AppleWorks> <MW_MSL.PPC.Shlb> <InterfaceLib> ". what do I do?

As far as I know, no one has figured out how or why it happens.
Hi Peggy
I recall a person who experienced this problem saying that they had recently copied AppleWorks to their Mac. It might have been 'cause they were restoring it from a backup, but I'm not sure now. I wonder if this might be the 'cause?
When this problem pops up we could ask people whether they had done anything unusual with AppleWorks recently to see if this provides any clues.
Cheers.
Dale

Similar Messages

Failure to Launch since Leopard install

Since installing leopard 10.5.2 I can't launch idvd (version4). I am constantly given the error message "failure to launch" Any suggestions? Are there any downloads that may be able to fix it?

Hi
NO - there is no solution.
You need a version more modern than iDVD 5 to be able to run under Mac OS X.5 !
No there are no download-fixes.
alt. Partioning the hard disk or use another FW external one with an older Mac OS
and start (boot) from this when doing DVDs.
Yours Bengt W

Failure to launch GoLive 5

Hey,
I have a "failure to launch" message that appears when I try to launch Adobe GoLive 5.0, a message that wasn't there yesterday (..wha?). It reads "Failure to launch GoLive 5 because SCL 2.0 could not be found". I've re-installed GL 5 but am still getting the message. This is an app that I've been running in Classic without a hitch, up til now. Can anyone help me understand what "SCL 2.0" is ?

Welcome to Apple Discussions!
Do you have a backup to compare your machine to from when it did work? Perhaps you disabled an extensions necessary for it to work.

Adobe X Failure to launch

I downloaded Adobe X, but it refuses to launch. I see the Akamai installer is a 32 bit program, and I guess Acrobat X is too. Can this failure to launch be a conflict with my 64 bit Wndows 7 os?

There is no conflict of Acrobat X with Windows 7 64 bit , we would like to know what exactly is the error message and when did you get it.?

Appleworks won't launch in Tiger

I just upgraded to Tiger and downloaded the update to 10.4.3. Now I can't even launch AppleWorks 6.2.9 at all. All I get is the spinning lollipop and the "not responding" message in the Force Quit dialog. I've tried repairing permissions, but that makes no difference. Any suggestions?

Welcome to Apple Discussions Ken
Although it would appear that Suitcase was the cause of you not being able to launch AppleWorks, I think that may only be a small part. As OS X is upgraded & updated, AppleWorks seems more & more sensitive to a couple of long-standing issues. The first is the "Recent Items bug" that can cause tremendous slow-downs to the point that AppleWorks won't launch. Take a look at the top post in this forum, especially my post, Peggy, "always waiting for spinning lolipop" #1, 03:59pm Sep 13, 2004 CDT, with links to three user tips about recent items. The second is the need to trash the AppleWorks preferences after applying a system update. My user tip, AppleWorks has stopped working correctly, has more on preferences.
Peggy

Visual Studio cannot remote debug Azure cloud service: There was a failure to launch the remote debugger

I am trying to invoke remote debugger on an Azure worker role cloud service, following the example of
http://msdn.microsoft.com/en-us/library/azure/ff683670.aspx
But on attaching the remote debugger for the cloud service instance
Microsoft Visual Studio
There was a failure to launch the remote debugger.
OK
According to somebody else's extra coverage on the topic, there are extra ports 4016/4017 that need to be taken care of (but do they have to be exposed externally)?
http://developers.de/blogs/damir_dobric/archive/2014/02/04/behind-windows-azure-remote-debugger.aspx
So servicedefinition.csdef gets
    <Endpoints>
      <InputEndpoint name="Endpoint1" protocol="http" port="80" />
      <InputEndpoint name="RemoteDebugger" protocol="tcp" port="4016" localPort="4016" />
      <InputEndpoint name="RemoteDebugger2" protocol="tcp" port="4017" localPort="4017" />
      <InstanceInputEndpoint name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Connector" protocol="tcp" localPort="30398">
        <AllocatePublicPortFrom>
          <FixedPortRange min="30400" max="30424" />
        </AllocatePublicPortFrom>
      </InstanceInputEndpoint>
      <InstanceInputEndpoint name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Forwarder" protocol="tcp" localPort="31398">
        <AllocatePublicPortFrom>
          <FixedPortRange min="31400" max="31424" />
        </AllocatePublicPortFrom>
      </InstanceInputEndpoint>
    </Endpoints>
Serviceconfiguration.cscfg gets
      <Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Connector.Enabled" value="true" />
      <Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Connector.Version" value="2.3" />
      <Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.ClientThumbprint" value="THUMBNAIL" />
      <Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.ServerThumbprint" value="THUMBNAIL" />
    </ConfigurationSettings>
    <Certificates>
      <Certificate name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.TransportValidation" thumbprint="THUMBNAIL" thumbprintAlgorithm="sha1"
/>
    </Certificates>
But all these are to no avail; the same error still pops for Visual Studio 2013 Update 4; Azure SDK 2.3
Anybody regularly perform remote debugging for Azure cloud services?
The melody of logic will always play out the truth. ~ Narumi Ayumu, Spiral

And, how do I control that in Visual Studio?
All I get is the Attach Debugger... context menu option in the Azure cloud service nodes in Server Explorer. That is where it is failing. There are no customisable options.
Because of that, the Attach to Process dialog box is unable to retrieve the list of processes (to debug) in the remote worker role instance server.
I tested a blank-template worker role project and published to a new cloud project, and this simplistic copy had no problems with the Remote debugger.
Now the question is, what is it about this real-world project/cloud service that is different from blank sample? From what I compare between what I think are the relevant settings, there are none.
ServiceDefinition.csdef
<Imports>
<Import moduleName="Diagnostics" />
<Import moduleName="RemoteAccess" />
<Import moduleName="RemoteForwarder" />
<Import moduleName="RemoteDebuggerConnector" />
</Imports>
<Contents>
<Content destination=".\">
<SourceDirectory path="D:\Projects\experiments\workerrole1\workerrole1\rcf\Debug\RemoteDebuggerContent\" />
</Content>
</Contents>
<Endpoints>
<InstanceInputEndpoint name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Connector" protocol="tcp" localPort="30398">
<AllocatePublicPortFrom>
<FixedPortRange min="30400" max="30424" />
</AllocatePublicPortFrom>
</InstanceInputEndpoint>
<InstanceInputEndpoint name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Forwarder" protocol="tcp" localPort="31398">
<AllocatePublicPortFrom>
<FixedPortRange min="31400" max="31424" />
</AllocatePublicPortFrom>
</InstanceInputEndpoint>
</Endpoints>
ServiceConfiguration.cscfg
<ConfigurationSettings>
<Setting name="Microsoft.WindowsAzure.Plugins.Diagnostics.ConnectionString" value="DefaultEndpointsProtocol=https;AccountName=storage;AccountKey=" />
<Setting name="Microsoft.WindowsAzure.Plugins.RemoteAccess.Enabled" value="true" />
<Setting name="Microsoft.WindowsAzure.Plugins.RemoteAccess.AccountUsername" value="" />
<Setting name="Microsoft.WindowsAzure.Plugins.RemoteAccess.AccountEncryptedPassword" value="" />
<Setting name="Microsoft.WindowsAzure.Plugins.RemoteAccess.AccountExpiration" value="2015-12-31T23:59:59.0000000+08:00" />
<Setting name="Microsoft.WindowsAzure.Plugins.RemoteForwarder.Enabled" value="true" />
<Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Connector.Enabled" value="true" />
<Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Connector.Version" value="2.4" />
<Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.ClientThumbprint" value="" />
<Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.ServerThumbprint" value="" />
</ConfigurationSettings>
<Certificates>
<Certificate name="Microsoft.WindowsAzure.Plugins.RemoteAccess.PasswordEncryption" thumbprint="" thumbprintAlgorithm="sha1" />
<Certificate name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.TransportValidation" thumbprint="" thumbprintAlgorithm="sha1" />
</Certificates>
The melody of logic will always play out the truth. ~ Narumi Ayumu, Spiral

Appleworks no longer launches after 10.4.6 update

Could use some advice if someone has solved this one. Running 6.2.9 version of Appleworks on my Intel iMac, (mainly for keeping the daughters homework in sync with her 466mhz/Lime-iBook). And it was always running just fine under 10.4.5. Did the 10.4.6 update and now it repeatedly "unexpectedly quits". Choosing "Get Info" reveals that there is not a box to check to launch in Rosetta, as with some old apps, but checking the report log, it is crashing after launching in Rosetta.
Exception: EXCBADACCESS (0x0001)
Codes: KERNPROTECTIONFAILURE (0x0002) at 0x00000129

Yes, yes and yes, on all three of those suggestions. No luck. Here is more from the log report, preceeded by the same two lines mentioned in my first post.
Thread 0 Crashed:
0 LaunchCFMApp 0xb80808f3 0xb8000000 + 526579
1 LaunchCFMApp 0xb807b116 0xb8000000 + 504086
2 LaunchCFMApp 0xb808f47a 0xb8000000 + 586874
3 LaunchCFMApp 0xb80e3e1d spinlockwrapper + 2799
Thread 1:
0 LaunchCFMApp 0xb81f2deb strchr + 72
1 LaunchCFMApp 0xb818e52a pthreadcondwait + 3114
2 LaunchCFMApp 0xb812a9b0 catchexception_raise_stateidentity + 320
3 LaunchCFMApp 0xb8129eda CallPPCFunctionAtAddressInt + 174780
4 LaunchCFMApp 0xb8129dd1 CallPPCFunctionAtAddressInt + 174515
5 LaunchCFMApp 0xb812aaae catchexception_raise_stateidentity + 574
6 LaunchCFMApp 0xb81c3f0c pthread_create + 1124
Thread 2:
0 LaunchCFMApp 0xb80f7f63 spinlockwrapper + 85045
1 LaunchCFMApp 0xb8122db4 CallPPCFunctionAtAddressInt + 145814
2 LaunchCFMApp 0xb8125865 CallPPCFunctionAtAddressInt + 156743
3 LaunchCFMApp 0xb809a35e 0xb8000000 + 631646
Thread 3:
0 LaunchCFMApp 0xb80f7f63 spinlockwrapper + 85045
1 LaunchCFMApp 0xb8122db4 CallPPCFunctionAtAddressInt + 145814
2 LaunchCFMApp 0xb8125865 CallPPCFunctionAtAddressInt + 156743
3 LaunchCFMApp 0xb809a35e 0xb8000000 + 631646
Thread 4:
0 LaunchCFMApp 0xb80f7e12 spinlockwrapper + 84708
1 LaunchCFMApp 0xb8110e74 CallPPCFunctionAtAddressInt + 72278
2 LaunchCFMApp 0xb808192e 0xb8000000 + 530734
3 LaunchCFMApp 0xb807b116 0xb8000000 + 504086
4 LaunchCFMApp 0xb808f47a 0xb8000000 + 586874
5 LaunchCFMApp 0xb80e4742 spinlockwrapper + 5140
Thread 5:
0 LaunchCFMApp 0xb80f7f63 spinlockwrapper + 85045
1 LaunchCFMApp 0xb8122db4 CallPPCFunctionAtAddressInt + 145814
2 LaunchCFMApp 0xb8125865 CallPPCFunctionAtAddressInt + 156743
3 LaunchCFMApp 0xb809a35e 0xb8000000 + 631646
Thread 0 crashed with i386 Thread State:
eax: 0x00000005 ebx: 0xb807ae88 ecx:0x00000129 edx: 0x00000000
edi: 0x8200dd80 esi: 0x00000129 ebp:0xb7fffa08 esp: 0xb7fffa00
ss: 0x0000002f efl: 0x00010246 eip:0xb80808f3 cs: 0x00000027
ds: 0x0000002f es: 0x0000002f fs:0x00000000 gs: 0x00000037

Appleworks fails to launch under Leopard

Appleworks 6.2.9 fails as soon as it begins to display recent documents. Has anyone else experienced this problem?

Welcome to Apple Discussions
Whenever you do an update of the system software &/or AppleWorks, it's a good idea to do two maintenance tasks, one for the system (Repair Permissions) and one for AppleWorks (delete preferences).
To Repair permissions in 10.4.x, launch Disk Utility, found in the Utilities folder in your Applications folder, click on First Aid, then on Repair Permissions.
To delete AppleWorks' preference files, go to HD > Users > Library > Preferences & delete the file com.apple.appleworks.plist. Then, in this same Preferences folder, find and open the folder AppleWorks Preferences, then delete all of the enclosed files (except the Button Bar Preferences if you have customized the Button Bars). AppleWorks will recreate the preference files as it needs them.
Also, recent items are a problem all by themselves. It can make it appear that AppleWorks has frozen or failed to launch. The user tip by Dale Gillard, AppleWorks slow? Spinning ball appears?, explains a lot.

Appleworks won't launch

getting prompt, "appleworks could not be launched because of a shared library error"
I have an eMac 10.411 and appleworks 6.2 I believe. Happened once before and Mac store
did something to make Appleworks load at start up and that has worked fine for about 6 months until
yesterday.. Help !

See this user tip.

Appleworks won't launch anymore

I click on the icon and it just bounces and then stops.
1) I emptied my recent items folder
2) dragged the applworks icon from the dock to the desktop and then reinstalled it from the finder/applications section onto the dock
To no avail and I can't figure out why it won't work now. My eMac is pretty full- is there a minimum amount of memory needed to run it? (663.5 MB available)

Try a couple of maintenance tasks, one for the system (Repair Permissions) and one for AppleWorks (delete preferences). (Thanks to Barry for this way to format this very common answer.)
To Repair permissions, launch Disk Utility, found in the Utilities folder in your Applications folder, click on First Aid, then on Repair Permissions.
To delete AppleWorks’ preference files, go to HD > Users > (your account) > Library > Preferences. Find and delete the file com.apple.appleworks.plist. Find and open the folder AppleWorks in this Preferences folder, then delete all of the enclosed files (with the exception of the Button Bar Preferences if you have customized the Button Bars). AppleWorks will recreate the preference files as it needs them.
AppleWorks cannot handle Unicode, so you must not have an "extended" keyboard layout selected in System Preferences > International > Input Menu.

Adobe Bridge Failure to Launch

I have CS4 Design Premium for Mac. As of this morning, as soon as I launch Adobe Bridge, it immediately shuts down. I have restarted my computer twice, checked for software updates and am out of ideas. Any ideas? Bridge has always been a little glitchy on my system (some viewer modes cause the software to shut down on occasion). Help?

1}I would say uninstall it, clean out any trace of it, reboot, check for any updates reboot, and reinstall, leave defualt location where it installs itself!
2} look for maybe an older version, you can find one anywhere like www.kat.com try that working it from the bottom on up! even if you have to start at 1.0, let mwe know how that goes!

Failure to launch on an iBook G3

Hello folks,
I've got an iBook, 600 MHz PowerPC G3, 640 MB memory, running Mac OS 10.2.8
I'm currently trying to specifically get it to run GarageBand, so I have a copy of iLife 04 I've installed on it. I can successfully run iMovie and iPhoto, iDVD is incompatible, plus redundant as it doesn't have a built in DVD drive (had to plug in an external just to read the install DVD for iLife 04), and even though it should have iTunes didn't install, doesn't show in finder. No matter, again all I really wanted out of the bundle at the moment was GarageBand, which was shown as entirely compatible with my system specs via its readme and displays on my applications list in finder after I've run the iLife 04 bundle installer.
However when I attempt to launch it, I get it jumping on the dock as it initializes, for a brief moment I get the title "GarageBand" and it's other sub-menus on the menu bar at the top of the screen, but then nothing actually launches, it stops jumping, and the menu bar reverts to Finder as it aborts running the application. No error dialogue bubble is displayed.
Is there a known reason why this happens?

It looks like GarageBand 3 came out with iLife '06:
http://www.apple.com/support/manuals/garageband/
It's probably too new to work with a G3 processor, and, if I remember correctly, even with earlier versions of GarageBand, it took a G4 processor to use GarageBand Musical Instruments with it.

Failure to Launch - unknown error (-50)

As the subject says I can no longer launch itunes and when I try I get an unknown error (-50). I uninstalled and reinstalled itunes and quick time. Any suggestions.

Ok, so I created a whole new user called Test.
I hooked up the nano, and it asked if i want to erase and sync, or transfer purchases.
I transferred purchases, so then I had a couple hundred songs in my itunes library.
Then I synced the nano, and got the usual "this nano syncs with another library to you want to erase everything and sync with this one" and i said yes.
It worked.
Then I went and turned on photo syncing (even though I have no photos in this new user account).
It worked.
Then I copied a few folders of pix from my regular user account into the test account's Pictures folder. Then opened iphoto and said 'import to library'. So it added all the pix in the pictures folder into iphoto.
I tried to sync the ipod again- it asked if I wanted to replace all pix with the new ones (the same as the music warning)- I said yes.
And hit sync- and it worked.
Soo... I guess that means the problem is either somewhere in my thousands of photos, or maybe in a pref file for my user?
Maybe the next step is to import ALL my pix from the old account. Then if THEY sync, it must be something in the user account itself?! Not sure if that logic works.
But I don't think my 4gb nano can hold all my pix, and I don't really want to erase my whole 80gb video...
Anyone have any other ideas? Where are the Apple helper people? The only people responding are people saying 'i have the same problem'. Can we get some help around here?
Please?

Failure to launch Camera Raw 5.2 correctly on a Mac with Elements 6?

I downloaded and installed the Adobe Camera Raw application, and I read the readme and followed the instructions (although I'm not positive that I did it correctly). When I open Elements and then Camera Raw, the loading window for Camera Raw pops up - but that's it. Nothing happens. The program doesn't load, but elements does not freeze either. Is there something I'm just not undertanding? Do I have to plug my camera in (Nikon D60) or do something else to get this plug-in to work? Please help - I really want to start working with RAW files! Thanks.

Here are the instructions for installing the ACR update:
To install with Adobe Photoshop Elements: NOTE: You must follow all of the new instructions in order to successfully install the Camera Raw plug-in for Photoshop Elements.
1. Exit Photoshop Elements and Adobe Bridge.
2. Open the download file, double-click CameraProfiles.dmg, and follow the onscreen instructions.
3. Navigate to the root of the local disk (not the user's home folder).
4. Navigate to: (Please read directory carefully)
Library/Application Support/Adobe/Plug-Ins/CS3/File Formats
5. Move the existing plug-in to another location (for example, a new folder on your desktop). Ensure that you keep this version in case you need to revert back.
6. Copy the Camera Raw plug-in, Camera Raw, from the download into the same folder as in Step 4.
7. Launch Photoshop Elements or Adobe Bridge.

Failure to launch in Vista

Users CD fails to start in Vista. I have a medical CD that
launches with autostart. It points to my launching Authorware7
Title.exe file. I have received no other errors from users. Any
ideas what might cause this? Is there a Vista compatability
problem? Here is what the user said:
"I have your RCIS cd and I am getting the following error
message when I try to run it in Windows Vista. I have not had a
problem running it on Windows XP. The error message says:
"Title.exe - Bad Image" this is at the top of my tab. And the error
message box says: "JS32.dll is either not designed to run on
Windows ir it contains an error. Try installing the program again
using the original installation media or contact my software vendor
for support." I am not trying to install the program I an just
trying to run it from the CD on this laptop."

There is not an inherent incompatibility between AW and
Vista. I've
developed and tested Authorware content on Vista almost daily
for 2 years
with no insurmountable problems.
Certainly I have never encountered an issue with the
JavaScsrpt dll.
As a first test, ask your customer to try running your
Authorware exe in XP
compatability mode.
Steve
http://twitter.com/Stevehoward999
Adobe Community Expert: eLearning, Mobile and Devices
European eLearning Summit - EeLS
Adobe-sponsored eLearning conference.
http://www.elearningsummit.eu

Appleworks Failure to Launch

Similar Messages

Maybe you are looking for