Skip to main content
Participant
January 1, 2013
Question

License expir message in frameaker 10

  • January 1, 2013
  • 11 replies
  • 14270 views

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

    This topic has been closed for replies.

    11 replies

    January 3, 2013

    I used the patch for version 10 (not version 10.0.1 or whatever it was), and it worked for me. However, another forum user seems to think that the version should have changed to 10.0.3...my version still says 10.0.2.419. I'm not too concerned about this since I am able to use the tool, but I just want to make sure I am not missing something...

    Thanks,

    Smitty

    January 3, 2013

    Nevermind....just read the page Kapil linked to...this screen will NOT change, but when checking the version in the Control Panel (Windows), my version is 10.0.3.419 - whew

    Participating Frequently
    January 4, 2013

    Hello All,

    Thanks again for your patience as we worked through the issue and provided the patch to fix this problem.

    Just to summarize for everyone, there is a FM10 patch out that you should download and apply, which would fix this issue. The webpage which has the links to the patch describes in detail which of the 2 patches you should apply depending on your product/version. Please refer to the patch page here URL http://helpx.adobe.com/framemaker/kb/cant-launch-framemaker-10.html

    Also, the link to the original blog post (summarizing the issue, our response and the various updates made) is here http://blogs.adobe.com/techcomm/2013/01/update-on-the-issue-of-framemaker-10-not-launching.html

    Hope this summary information is helpful.  Wishing you all a great weekend!

    Regards,

    Kapil Verma

    Sr. Product Manager - FrameMaker line of products

    Participating Frequently
    January 2, 2013

    Dear All,

    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.

    http://blogs.adobe.com/techcomm/2013/01/update-on-the-issue-of-framemaker-10-not-launching.html

    We hope that this will solve the issue for all of our users who were impacted.

    Regards,

    Kapil Verma

    Sr. Product Manager - FrameMaker line of products

    Tekscribe
    Participating Frequently
    January 2, 2013

    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.

    January 3, 2013

    Hi,

    Pls. refer the link

    http://helpx.adobe.com/framemaker/kb/cant-launch-framemaker-10.html for the

    details on the updater which is applicable

    on your FrameMaker 10 installation. If you are still getting an issue,

    pls. do the following :

    In order to understand the issue of your machine, can you do the following :

    1. Create a blank text file with name “ribs3debug” (without extension) and

    place it in the %temp% directory.

    2. Apply the patch again.

    3. Pls. send the installation logs generated at C

    :\\Common Files\Adobe\Installers\ with the name Adobe

    FrameMaker 10 (time stamp).gz to megha@adobe.com

    Regards,

    Megha

    Adobe FrameMaker

    Participant
    January 2, 2013

    Hi All!

    Adobe has posted an update here, which includes an executable that fixes the license file,

    --=Thanks!
    --==Trey

    http://blogs.adobe.com/techcomm/2013/01/update-on-the-issue-of-framema ker-10-not-launching.html

    Participating Frequently
    January 2, 2013

    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.

    Bob_Niland
    Community Expert
    Community Expert
    January 2, 2013

    > 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.

    Known Participant
    January 2, 2013

    Running  FM10_LicenseUpdater.exe corrects the problem for me to. FM10 UK.

    Thanks

    Participating Frequently
    January 2, 2013

    Hello Everyone,

    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

    Regards,

    Kapil Verma

    Sr. Product Manager, FrameMaker and FrameMaker Publishing Server

    Participant
    January 2, 2013

    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.

    Participant
    January 2, 2013

    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.

    Participant
    January 2, 2013

    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. 

    kevin.dillon wrote:

    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'

    Kevin

    Known Participant
    January 2, 2013

    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?

    Regards

    Ian

    Participant
    January 1, 2013

    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.

    January 1, 2013

    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.

    JairajMike
    Participating Frequently
    January 1, 2013

    Hi all,

    Follow the steps mentioned in this below document:

    http://helpx.adobe.com/creative-suite/kb/error-licensing-product-expired-cs4.html

    Regards,

    Jairaj

    Participant
    January 1, 2013

    Hi,

    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!

    Regards

    Mick

    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!

    kmacdowe+brdcom
    Inspiring
    January 1, 2013

    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.

    Participating Frequently
    January 1, 2013

    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.

    HTH

    Regards,

    Peter

    _______________________

    Peter Gold

    KnowHow ProServices

    Dekel07 wrote:

    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

    Bob_Niland
    Community Expert
    Community Expert
    January 1, 2013

    > ... 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.

    Participant
    January 1, 2013

    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.