So, I finally decided to purchase my very own copy of CS3 several months ago (about 6) after using CS2 at work for a number of years. I figured it would be a good time to get it since I am a college student right now so I qualified for the academic version (an old one, having gone back after many years out, but a college student none-the-less...LOL!) It has been nothing but problems since I got it! I never experienced anything like this with Adobe Product before and I have been using them for over 20 year (all the way back to Aldus Pagemaker even!)
It worked great for about 4 months, not a problem at all, then all of the sudden I started getting this stupid AMT failure message:
AMT Subsystem Failure
The licensing subsystem has failed catastrophically. You must reinstall or call customer support.
I tried calling support (outsourced support obviously, as they were VERY hard to understand on the phone and I talked to no less than three different people). Removed and reinstalled only to have it creep back up over and over again. I got sick of removing and reinstalling it and since Adobe was no help at all started troubleshooting and logging the problem.
Could this be a RAM issue? My dual core desktop iMac is maxed out, so if it is there is nothing more I can do. :(
Basically, when I start the machine I can open all my CS programs first, before any other programs (AI, ID, PS, DW, and Acrobat). I am pretty much good to go and can then open all my other programs and begin working for the day. But, if one of the CS3 programs stalls on me, which seems to happen daily, causing me to force quit it. It will not longer open and gives me the error message above.
Then I have to restart my blasted machine and start all over, with all programs opening fine after the restart. Anyone else got any theories or has Adobe even addressed this AMT failure which, judging from a Google Search, seems to be a widespread problem across both PC and Mac platforms?
My initial thought is it's a RAM issue because all works fine after a restart and only starts acting up as the day goes on, forcing another restart to begin any kind of work flow again.
whistlingturtle, Jun 25, 2010 8:39 AM
Recurring and unexplained problems with Adobe's license control software are causing unwarranted aggravation and inconvenience for customers. Dan Margulis, author of several books on Color Management, warned of this likelihood in his newsletter when Adobe first implemented the control in Windows PhotoShop. Since this control is designed and licensed to Adobe by a third party, what will be the implications if that party closes its doors someday?
I, too, have experienced FLEXnet / AMT errors on both personal and work equipment. One apparent handicap of CS3 is the inability to switch between Users on a single machine (fast user switching) and open the same Adobe app. It was possible before.
I'm miffed by Adobe's lax and unapologetic attitude to FLEXnet's buggy behavior. I'll wager that software pirates are still ripping Adobe' products at the same rate and that their "customers" aren't inconvenienced.
Its the same with me now. I suddenly started getting this errors on my office laptop.. ouch... Its irritating reinstalling application and still nothing seems to happen..
This is coupled with stupid javas script errors I am getting everytime I start and stop dreamweaver..
I find myself in the same circumstances as the first poster, even down to having returned to college as a mature student, for which I purchased a new Macbook and Adobe Creative Suite. This has now failed in exactly the way described above with the added irony that having followed the instructions given by Adobe to correct it the problem continues even after restarting! I'm in the middle of a design course for which the software is essential - "failed catastrophically" - at least they got that part right...
This message is to let everyone know in the thread that Adobe has been investigating this problem in detail and there are multiple reasons why it occurs.
There's a Technical Note on the support site (on Adobe.com) that explains some of the symptoms that some of you seem to describe here, and provide specific solutions for the problem. The article is available here: http://kb.adobe.com/selfservice/viewContent.do?externalId=kb402004&sl iceId=2
We do appreciate your patience and encourage all of you to continue providing feedback to Adobe so we can do a better job troubleshooting problems and providing solution for current and future versions of our products.
Amitoj suggested the first user (Nora) to get the error code recorded in the log files. Please try to obtain that code when getting the error as that would help us troubleshooting the issue (sorry in advance due to the techy nature of the log files...)
Mac OS Details
* Log files to obtain (2 files): amt.log and alm.log
* Location: ~/tmp/amt.log and ~/tmp/alm.log
To navigate to the log files do the following:
1) Open a terminal window
2) Type "cd /tmp"
3) Type "open ." in the terminal window
4) a finder window should open with the contents of /tmp
You should be able to locate the amt.log and alm.log with in the /tmp folder that opened in the Finder window. Open each log file and report the error codes included in the logs.
Here's what I did that just fixed this issue on a mac 10.5.2
After determining that the permissions on the FLEXnet folder were fine:
1. Moved the Trusted Storage File (TSF) out of the FLEXnet folder.
Library/Preferences/FLEXnet Publisher/FLEXnet folder (Mac OS).
2. Renamed the FLEXnet folder.
Tried launching, entered the sn and received activation error:
Error code 150:30. Re-executed the steps, then rebooted the machine, ran disk permissions repair and tried launching again.
Conclusion: After following the steps in kb401528 rebooted the machine and repaired disk permissions, was then able to activate successfully.
hope that helps,
I've just come across this problem for the first time and will try the above from Cindy - hope it works - can't work without this software!
Though I have been using the package on my Previous machine G5 Dual 2.7Gb for over a year! without a problem. but now I have changed to the latest iMac duo core, I'm wondering if it's related to the Intel system?
I'm assuming the CS3 package has been optimised for the Intel platform correctly?
I, too am experiencing this problem and it has brought my entire job to a complete stop until I can solve it as nearly everything I do is using CS3. First of all, in Juan-Carlos' message he refers to kb402004 which tell us (unlike the earlier mentioned by Cindy) that we must DEACTIVATE BEFORE UNINSTALLING everything, from WITHIN one of the apps. Well, a) how can I deactive from within an app if I can't open it, and b) too late now as I already followed the earlier instructions and went through the long, painful uninstall, did a complete reinstall (4 hours in all), repaired permissions twice (the FlexNet file folder was correct to begin with) and still nothing works. On top of that, when I follow the instructions for checking the logs, Terminal gives me a "no such file" message. Great.
Hi...im not sure where the Vista Posting goes...you seem to know your business though...I am getting the AMT Error as well....I do the Systems > Flex > Manual (Its already on manual) and nothing changes...i did the system restore and now NOTHING in my cs3 works
If you want help with widows stuff go to the Windows forum. I don't do Windows. neither does most everyone else in the Mac forum. I suppose one guy might stop by that has used vista before but if you want more than one Windows person to see your problem asking in the Windows forum is the thing to do.
If you go back to the top of the forums page and click the Creative
Suites link you should see a page that will allow you to choose the
I'm running Vista Ultimate 64 and XP SP3 here and haven't seen this issue.
As for Buko, he's generally helpful but also painfully blunt. Try not to
read too much into what anyone writes here. The written word leave much
to be desired when it comes to reading intent with the message.
I had this happen to me on a Mac (I posted a similar cry for HELP in the forum) and the answer, after hours online with a bored and somewhat rude customer service person in India was to spend HOURS uninstalling everything Adobe on my machine, then to download the MacCS3Clean utility script and go through a whole series of commands in Terminal to find and erase left-behind license files that came from previous versions of Adobe CS and were apparently tricking CS3 into thinking that I was trying to do something illegal. As I understand it, the issue has to do with the third-party licensing scheme Adobe uses, which has numerous issues. There is a similar script for PC. Since you're posting in the Macintosh forum I assume that you are running Vista on a Mac...
Here is a link to the Adobe page with the CS3Clean scripts : http://kb.adobe.com/selfservice/viewContent.do?externalId=kb402767
I had this same problem after I had to do a system restore. The only way to fix it was to reinstal/repair.
Frankly I think this licensing system is hurting Adobe... I just kill the FLEXnet process after my product loads because it causes slow downs and crashes. My firewall blocks all the other update features that cause the same problems. Adobe products are far worse than any virus that tries to take root.
I won't be buying another Adobe product until they resolve these issues. IT'S NOT WORKING ADOBE, YOU'RE ALIENATING AND FRUSTRATING YOUR PAYING CUSTOMERS!!! You're not a SaaS and we work with large files... we can't have resources being eating up with your leaky bloated licensing/updating code.