SaaS CMS has officially launched! Learn more now.

Shahid nawaz
Dec 13, 2010
  6649
(1 votes)

Load Balancing License Issues when upgrading to CMS-6

Every now and then we are being asked different license issues after upgrading to CMS-6 enterprise and load balancing. As I wrote in my previous post about the working of new license model in CMS-5 & 6 but it seems that there are some confusion still out there.

Let's take couple of them with examples. :)

"This slave site has no master license information"
or
"This slave site failed when validating master license information".
If you come across one of the above errors than first thing you need to do is to follow the FAQ. If the error remains than make sure that you have right licenses uploaded through admin mode. Open up your master license from master site and slave license from slave site.  Check the MetaData in both configs as below: 

Master License.config:

<LicenseNumber>1234756</LicenseNumber>
<Enterprise>True</Enterprise>
<
Master>True</Master>

Slave License.config:

<LicenseNumber>789102</LicenseNumber>
<Enterprise>True</Enterprise>
<
SlaveTo>1234756</SlaveTo>

Make sure that SlaveTo points to correct master license ID. Also make sure that the account which you used to connect to database(s) has "DBOwner" access.

If you have upgraded your license from CMS-5 Old enterprise and have received multiple config files than there are chances that you have uploaded incorrect license in your site(s).

If you require to change master license bindings in any of your existing license then send a request to license admin or "sales at episerver dot com" and supply correct license numbers.

 

 

"License violation - license in use at another site"
wait a sec ... yes yes we do have couple of FAQs (one & two) available already but when it comes to CMS-6, you need to make sure that you have uploaded a new license file for every additional enterprise site since one license only supports one site to run with. 

Dec 13, 2010

Comments

Please login to comment.
Latest blogs
Getting Started with Optimizely SaaS using Next.js Starter App - Extend a component - Part 3

This is the final part of our Optimizely SaaS CMS proof-of-concept (POC) blog series. In this post, we'll dive into extending a component within th...

Raghavendra Murthy | Jul 23, 2024 | Syndicated blog

Optimizely Graph – Faceting with Geta Categories

Overview As Optimizely Graph (and Content Cloud SaaS) makes its global debut, it is known that there are going to be some bugs and quirks. One of t...

Eric Markson | Jul 22, 2024 | Syndicated blog

Integration Bynder (DAM) with Optimizely

Bynder is a comprehensive digital asset management (DAM) platform that enables businesses to efficiently manage, store, organize, and share their...

Sanjay Kumar | Jul 22, 2024

Frontend Hosting for SaaS CMS Solutions

Introduction Now that CMS SaaS Core has gone into general availability, it is a good time to start discussing where to host the head. SaaS Core is...

Minesh Shah (Netcel) | Jul 20, 2024