Wednesday, May 26, 2010

I (x) Adobe

A couple of weeks ago I questioned whether Adobe really did (heart) Apple ... and noted that whilst I'd just installed Elements 8, I hadn't actually tried to run it. I just did. This is what greeted me:

201005262145.jpg

Followed by this after trying again ... the fabled 150:30 error ... see below for the Adobe-published solution for Mac and Windows:


201005262147.jpg

Now I know that they totally don't get Mac users. I don't have an IT administrator!

And then this when I tried to uninstall


201005262156.jpg

Why would firefox running stop an uninstall?

The web is full of tales of woe regarding the error 150:30. I am not alone.

For those who experience the same error, here's what Adobe say you need to do:

Solution 1: Apply the Licensing Service Update

  1. Close any Adobe applications.
  2. Download the Licensing Service Update.
  3. Run the License Service Update.
    1. Extract the LicenseRecovery109.zip.
      Important: A utility such as WinZip must be used to extract the contents on the zipped file.
    2. Double click LicenseRecover.exe.
  4. Follow the on-screen instructions.
  5. Start your Adobe application.

    Important: The patch applies to Creative Suite 3 or 4 products, Acrobat 8 or 9, Photoshop Elements 6, 7 or 8, Director, and Technical Communication Suite.  If your issue was not resolved on the first attempt, run the patch again and enter option 0, when prompted to do so. If the issue persists after you run the patch a second time, proceed to Solution 2: Set the FLEXnet Licensing Service to Manual and Start the service.

I like that last bit ... it's a bug that hasn't been fixed in the last 3 versions of software and sometimes takes 2 or even 3 goes to fix it using the licensing repair tool (which I'm downloading now and is 40MB). Almost entirely completely BAFFLING.
Just to reassure you ... you will be greeted by this
201005262221.jpg
Do not be alarmed. But do make sure you have closed any Adobe applications, including Acrobat and so on.

I've had to run it twice so far with a reboot inbetween.I haven't seen anything like this since I last saw a Unix prompt. 1987 I think that was.

And it still gives the same 150:30 error. Poor.

No comments:

Post a Comment