Happy new year ..... !
I have exactly the same problem since this morning: i have two German Licenses for Framemaker 10.
Last Saturday, all was warking still correct.
This morning, I get the message "Your license is not more available" (in German)
All my licenses are legal and from Adobe.
Did you find now a solution? ..... I have to deliver a job tomorrow .... !!!!!
It may the ghost of the Y2K problem! Since the problem occurs with the new year, try resetting your computer's time to a date in 2012. On some networks, the network clock and the individual workstation's clock may disagree about what year it is. You may need to change your workstation setting that synchronizes its clock with an Internet clock. If this permits FrameMaker to start, you might be able to reset the clock to the current date while working with files. Try to save a file to verify this. If it works, don't turn FrameMaker off until your IT support team returns to work.
From today i start to get 'licensing for this product has expired' messgae in frameMacker 10
i got this messgae in two computer 1 have windows 7 and the other has windows xp pro
i tried to reinstall but got the same message.
i have vaild licenses
> ... try resetting your computer's time ...
Why would an open-ended license have code that checks the date? I'm guessing that it might be some logic in a trial version, that's trying to discover if you're gaming the 30 days by rolling the clock back.
Meanwhile, until affected users can get Adobe to fix this, download a trial version of FM11 on a machine without FM. You'll have 30 days to get work done.
FM7.0 is running fine on my home machine.
We're not supposed to have our next Y2K until 2038-01-19, when the Unix clock rolls over.
Thank you very much, Peter!
With the date 1. december 2012 can I work. As soon as I rechange the date to 2013, FM start no more - but this is not really important: I can work today with the "wrong" day and hope to have help from Adobe tomorrow by phone.
Thanks again - you have saved my day
Framemaker 7.1, 7.2 and 9 are working fine.
The problem seems to be only with Framemaker 10 (and perhaps 11?)
The answer from Peter is perfect: change the date of your computer to 2012 back and Framemaker 10 is working fine.
I'm also experiencing the problem with FrameMaker 10. Sheesh!
Tried the recommended procedure by setting date back to 1st jan 2006. Deactivate process would not talk to Adobe, all other internet access OK.
Turned off firewall and tried again, still the same.
Set date to 1st November 2012, this time the deactivate worked.
Set the clock to correct date & time (i.e. 1st Jan 2013), started FrameMaker, and "Number of activated machines exceeded"
Could not through to anyone at Adobe.
What a mess and a waste of everyone's time.
Thanks for the link BTW!
p.s. Luckily I have another computer with an activated copy. It also told me the license had expired but (for now) I've set the date back to 1st November 2012.
I suspect we will all have to get Adobe support to reset things individually.
If anyone figures out a quicker solution please post, thanks!
I and several members of my group are also having this problem. I think Adobe should respond to this problem. Legitimate users should not have to jump through hoops just to get things they way they should be.
We are also having this issue. Turning back the clock is not an option for us. We need a legitimate fix soon!.
We are also having the same issue on multiple machine. Some machines are Windows 7 and some are XP and all are experiencing the issue.
Don't waste your time with Adobe chat since they referred me to tech support (which is closed today). The unbelievable thing is that when I asked the person why it was taking so long to reply to my chat answers, he admited that he was holding a chat with multiple customers at the same time.
It seems like Adobe should have known about the problem and had prepared their chat support staff.
Same issue, FM10, Win7. I will email support after this and hope for the best tomorrow. I found the following advice (mentioned above) which was only partially successful.
* Turn the system clock back, start your application, and erase the stored expiring serial number.
1. Set the computer clock back to January 1 2006.
(One month did it for me.)
2. Launch the affected application, or any application within the affected Creative Suite package.
3. Choose Help > Deactivate, and select the option Erase This Serial Number (CS4) or Deactivate Permanently (CS5).
(Not exactly the same interface in FM10, but I got this far.)
4. Quit the application.
5. Set the computer clock back to the current date.
6. Start the application. When prompted for the serial number, enter the number from your purchased product.
(I entered the valid serial #, then FM10 failed again, "Licensing for this product has expired."
I am left with running the back dated system which is very uncool for a full gash purchase price FrameMaker. Bad news.
I am having the same problem - FM10, Win7. Manually setting the clock back to Dec. 31 allows me to open FrameMaker but doing so is a temporary workaround at best. Frame will stay running if I set the computer back to Jan. 1, but it will not reopen again unless I change the date back to Dec. 31. Thanks for all the good information posted here.
We also have this problem, we are a multi user site. Adjusting dates is not a solution. We are running Win7 64 bit.
Jairaj I tried all the solutions suggested on the abobe line but end back at square one.
Has anyone been able to get anything out of Adobe re this issue.
An update, I have heard back from FM support,
'this issue is being faced by customers who are using the Adobe FrameMaker version 10 and is also replicated at our end.
We have the temporary fix for this issue right now with setting the date prior to January '13 which is mentioned on our forum link :- http://forums.adobe.com/message/4960865#4960865
You can view the same, however the issue has already been reported to the senior level of support and we are awaiting their response as of now.
Once we receive their reply, we would revert back with the information as soon as possible, however it might also take 24-48 hours' time'
I filed a bug report this morning and received a note back that Adobe
is aware of the issue and working hard to resolve it.
Yesterday we tried to work on FM10 that got license expire message, no matter what I did I got the same message.
So I found workaround to use FM10 until adobe will fix the problem please change the date on the machineS to before 1/1/2013.
Same problem this morning: FM10 and Windows 7, french version: "the license of this product has expired"
I cannot change the date because I am on a secure computer with reduced rights !
What I have to do ??
If you change the system date to last year you can start Frame 10. If you (or the system) then resets the date to 2013, Frame will carry on working (files can be edited, saved, etc.). So the problem seems to be confined to starting Frame. Once it's running, changing the date has no effect.
Not ideal. And not a solution for everyone. I hope the permanent solution does not involved relicensing, as my copy of Frame was installed by my IT guys, and I do not have the license information.
Is there a way to get your Frame license number?
I am the product manager of FrameMaker. Thanks for bringing this issue to our attention. We have already isolated the cause of this issue and are now working aggressively to provide a solution to our users. That being said, we do realize that many of you are blocked on your daily work due to this issue. We sincerely apologize for this and completely understand the difficult situation you are in.
While we work on a solution, we want you to be able to continue doing your work and be productive. For this, I have posted more details and a workaround to this issue on my blog post http://blogs.adobe.com/techcomm/2013/01/update-on-the-issue-of-framemaker-10-not-launching .html. This workaround will enable you to continue working with FM10 in the interim. I will be posting regular updates as and when they become available on this blog post. So, please do keep checking the blog post for more details.
Our hope is to provide a complete solution within the next 24 hours. Thanks for your patience and understanding.
* Note that this issue affects only FrameMaker 10 users and not those users using other versions of the product
Sr. Product Manager, FrameMaker and FrameMaker Publishing Server
Before manipulating the system time on a Windows network PC please contact your IT administrator if this affects the overall network operation. It may lead to more serious network problems. E.g. locking of the Windows user account.
a quick update. there is an additional workaround that has been posted. We have posted a utility which will do the suitable modification to make FM10 launch successfully. you can download the utility and how to run it, from the original blog post http://blogs.adobe.com/techcomm/2013/01/update-on-the-issue-of-framemaker-10-not-launching .html. Please refer to this workaround on the blog post.
Please stay tuned for more updates
Running the "FM10_LicenseUpdater.exe" corrects the problem !!! Thanks !
FM10 + Windows7 64-bit french
thanks. One question bugs me, though. Can you describe a situation in which FM10 is supposed to be "expired"? Is there a built-in "self destruction" mechanism, which automatically will disable FM at any point in time? Or is that an early implementation (or code leftover) of a (planned) subscription functionality?
I'm a little bit worried about what's happening here…
The patch corrected the problem for me as well. FM10 + Windows 7; US English.
This is a fantastically-rapid rsponse and fix! There's no doubt that the affected customers have benefied greatly from your quick involvement and action.
The updater works for me. I think the FM community affected by this calamity deserve an explanation! The problem really sheds a bad light on Adobe.
I have posted elsewhere in this Forum about chronic FM10 crashes (which have persisted for 7 months). Adobe Engineering (India) worked with me but could not find the problem. This issue is something to do with conditions, x-refs, and text insets.
The combination of this licensing issue and clear FM legacy bugs you think would ring alarm bells at the top with Adobe. No sign anyone in charge there has the courage to light a fire under FrameMaker Development.
Wow! Running the Patch which is mentioned in the blog resolved the issue!
Thank you, Kapil..:)
I find it encouraging that this sort of thing doesn't happen more often. It appears that some iOS users were also just hit by a year-end bug (Do Not Disturb feature). There was a leap second problem in the recent past, but I don't recall any swarm of date-related time bombs since Y2K, and most of those were quickly (and quietly) fixed because everyone had SWAT teams on standby for that.
This is a reminder to keep an eye on your run-time licensed applications, and have a plan B when the vendor moves your version to EOL, or the vendor gets acquired, or simply folds. We're still running some ancient RTL apps, vendor kaput, that will be completely irrecoverable if they ever hit a clock bug. It probably won't happen until 2038, but we might not even be able to use a clock-rollback trick, due to the network file system dependencies.
Lighting fires under people has been banned for many years here in the UK!
I think this is something that happens due to malcious code or some programmer prank.
The (possibly disgruntled) programmer probably left the company years ago. There is no way Adobe could detect this, there are too many lines of code in the product to test, probably hundreds of thousands. They can only react when such an event occurs.
Understandably, Adobe will probably never divulge the cause, but I'm sure thay'll work hard to come up with a fix.
Having worked for computer manufacturers for many years, I've seen similar events happen before. They keep their fingers crossed when any significant date arrives, such as New Year, Leap days and (here in the UK) April Fool's day!
Although it is very annoying, at least there is a workaround for most of us who can set the clock back temporarily.
Good luck to Adobe, I've always had good customer service in the past, and they could not have forseen this.
Running FM10_LicenseUpdater.exe corrects the problem for me to. FM10 UK.
Adobe has posted an update here, which includes an executable that fixes the license file,
It doesn't work in all instances. I have a private license on my home desktop, Win7 64-bit, English OS. That reset.
My work laptop, Win 7 32-bit, English OS, did not reset. The only work around available is to set your computer date to 2012.
> My work laptop, Win 7 32-bit, English OS, did not reset.
Is that also a local machine license, or is it relying on a network license server?
People aren't reporting their license environment (and may not even know), so I'm wondering if the bug behaviour/fix is different for local vs. network.
Thank you!! The utility fixed the issue for me and my group of writers.
Thanks for the quick response.
Update #2: We have released an update on FM10 and this should address the problem for all users. Please download and install this important update. For details, please visit my original blog post (link below) and look at the Update # 2 section for instructions on how to install this update.
We hope that this will solve the issue for all of our users who were impacted.
Sr. Product Manager - FrameMaker line of products
Your instructions say to install this latest update even if the utility-fix provided earlier was installed. I downloaded and extracted the zip but it would not install, complaining that "Update Failed" and further instructing that a new Adobe Application Installer be downloaded and installed. I did this, but the update still fails.
Thanks, that worked for me and my team (four have confirmed it worked, zero have complaimed).