Skip to main content
Question

What decides the CRC-code for node-locked licenses?

  • June 1, 2018
  • 4 replies
  • 81 views
havmoejbv
Contributor
Forum|alt.badge.img+16

I didn't use to have any issues with this, but after switching to a new PC and upgrading to Win10 I'm having problems with the FME licence failing due to CRC-check errors. For some reason, my PC now has a different registration key (2-014-702-034) than it had a month ago (2-992-327-444) when I got my last license file.

There are no hardware changes to the PC (a HP Zbook with docking station). So what is it that can affect my reg. key this way?

    This post is closed to further activity.
    It may be an old question, an answered question, an implemented idea, or a notification-only post.
    Please check post dates before relying on any information in a question or answer.
    For follow-up or related questions, please post a new question or idea.
    If there is a genuine update to be made, please contact us and request that the post is reopened.

    4 replies

    havmoejbv
    Contributor
    Forum|alt.badge.img+16
    • havmoejbvContributor
    • Author
    • Contributor
    • 38 replies
    • June 1, 2018
    @sigtill > Worked a few days ago, not anymore...
    sigtill
    Supporter
    Forum|alt.badge.img+25
    • sigtillSupporter
    • Supporter
    • 956 replies
    • June 1, 2018
    @sigtill > Worked a few days ago, not anymore...
    @havmoejbv / usually a windows update, hardware change (docking/undocking) or expired license file.

     

    The real SigTill
    sigtill
    Supporter
    Forum|alt.badge.img+25
    • sigtillSupporter
    • Supporter
    • 956 replies
    • June 1, 2018
    @sigtill > Worked a few days ago, not anymore...
    More info here - and in the comment section: https://knowledge.safe.com/articles/688/fixed-license-troubleshooting.html

     

     

    The real SigTill
    havmoejbv
    Contributor
    Forum|alt.badge.img+16
    • havmoejbvContributor
    • Author
    • Contributor
    • 38 replies
    • June 1, 2018
    @havmoejbv / usually a windows update, hardware change (docking/undocking) or expired license file.

     

     

    I've testet with docking/undocking before and gotten the same key. The main issue is that I have no control over windows updates; when they happen or what is installed. Add in that most updates does not affect the key, and it becomes a rather frustrating task to try and predict this... Luckily I get great support from our local dealer ;)

    Community Stats

    32,060
    Posts
    121,724
    Replies
    39,688
    Members

    Latest FME

    Terms & ConditionsCookie settingsAccessibility statement
    A product of
    Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.