Apr 10, 2014
  4974
(1 votes)

License error: Current version is newer than required version

In EPiServer 7.5 if you upgrade to latest update through nuget (starting from update-6) you might get a license error something like :

Current version 7.6.0.0 is newer than required version 7.5.9999

Don’t worry, you don't need to "upgrade" your license as normally is the case when upgrading from EPiServer-5 to EPiServer-6 or 6 to 7. The reason for above error is probably your license file has max version set to :

<Restrictions>
        <Restriction>
          <VersionRestriction From="7.0" To="7.5.9999" ….

EPiServer 7 license works both for 7 & 7.5 release.

Solution:

Re-generate the license file from license center (required admin access). Login to license center, go under "Licenses" tab, open the license
and click "Send license file by email". When you re-send the license file, it will automatically update the maxversion of all grouped/bundled EPiServer 7 licenses as well. So you don’t need to re-regenerate each license file separately.

If you don’t have License Admin access to license center then send a request to LicenseAdmin at episerver dot com to regenerate the license file for you.

Apr 10, 2014

Comments

Daniel Badro
Daniel Badro Apr 11, 2014 11:07 AM

Thanx for the intel, I got this error and ended upp ordering a new developer licens.
/D

Please login to comment.
Latest blogs
OpenAI-Driven AI Assistant for TinyMCE in Optimizely CMS 12

The Tiny.AI add-on enhances Optimizely CMS 12 by seamlessly integrating OpenAI directly into the TinyMCE editor. It empowers editors to rewrite,...

Adnan Zameer | Mar 3, 2026 |

Your first SAAS Project -- Setup

Hey everyone, When I first started Remko's StarterKit, I honestly had no idea what I was doing. After spending a couple of months working through i...

PuneetGarg | Mar 3, 2026

Catalog Traversal with Hangfire. Part 3: Advanced Job Management

In Part 1, I showed how to build a memory-efficient catalog traversal service, and in Part 2, I demonstrated practical patterns using Optimizely’s...

Stanisław Szołkowski | Mar 3, 2026 |

Bypassing WAF Blocking in Optimizely CMS 11 with Custom Base64 Properties

Introduction As Optimizely developers, we frequently encounter requirements to allow editors to inject third-party scripts into the head or body of...

Amit Mittal | Mar 2, 2026

Inspect SaaS CMS Packages Without Losing Your Sanity (Package Explorer Update)

Optimizely export packages have quietly become more complex. Inline (nested) blocks in CMS 12 and PaaS solutions weren’t always displayed clearly,...

Allan Thraen | Mar 1, 2026 |

Unstoppable: Insights from Optimizely’s 2026 UK Partner day

Over 150 Optimizely partners met in Shoreditch for the 2026 London Partner Kick Off. The theme was very much Opal with a side order of Optimizely's...

Mark Welland | Feb 27, 2026