Symptoms

1) A user tries to login and receives the error message:

LICENSE WARNING: No valid license was found for your system. This system can only be accessed using the original System Admin member account. All other members cannot log in...

2) An admin attempts to add a new user to the system and encounters an error message:

LICENSE WARNING: The limit on active members for this license has been reached. This change was not saved...

In this case, only the original Admin account will be able to log in to the system.

Click the About link (in the login window for case 1 above or in the left nav for case 2)...

 

...then click on 'License Details'...

 

 

...and you can see the type of license you have and the current usage (in this case a Trial License and 11 licenses used). 

 

1: License Details window says 'Trial License'

If the License Details window says 'Trial License' and you are getting the license warnings above, it means that your trial has expired.

Resolution 1 - Expired Trial License

Please contact your VersionOne sales representative (use sales@versionone.com if you don't know the specific individual) to purchase a customer license or obtain a copy of your license if you are already a customer. Delete the trial license from the (ApplicationName)\bin directory on your webserver and replace it with your customer license file.

2: License Detail window says 'Agile Community'

If the License Details window says 'Agile Community' it means either no valid license could be found or the license that exists does not apply to the Release you are now running.

Check This Next

From the License Details window, right click on the window and elect to show the page source, which will contain a comment that shows more detail on the status of any license file(s) found.

Resolution 2A - Missing License File

If the source of the license details page contains 3 repeated entries of the following exception (varying by the directory checked), it means there is no license file.

No licenses found in (various directories listed).

You will need to place your valid license file in the (ApplicationName)\bin directory on your webserver. If you do not have a valid license file, please contact your VersionOne sales representative (use sales@versionone.com if you don't know the specific individual) to purchase a customer license or obtain a copy of your license if you are already a customer.

 

Resolution 2B - Upgraded to New Release Beyond License

If the source of the license details page contains something similar to the following exception, it means that the license file found is not valid for the release being run (though may be valid for earlier releases).

Assembly version 9.3.4862.0 is not between 6.0 and 8.65535.

This can occur after an upgrade to a new annual release level. In general, licenses apply to the Releases for the given calendar year, so you must obtain a new license if you upgrade from any 2008 release to a new 2009 release, for example. Please contact your VersionOne sales representative (use sales@versionone.com if you don't know the specific individual) to obtain your new customer license.

 

Resolution 2C - Permissions Issue

If the source of the license details page contains the following exception, it means that the license file found has a permissions issue. This can occur after manually copying files.

Unexpected error while loading c:\inetpub\wwwroot\nextrelease\bin\VersionOne.Development.Enterprise.lic: Could not load license pack: Access to the path 'c:\inetpub\wwwroot\nextrelease\bin\VersionOne.Development.Enterprise.lic' is denied.

The user account that the ASP.NET worker process runs under needs to have read access to the license file. To correct this, one can typically adjust the file to ensure it is inheriting the parent permission entries rather than storing its own unique settings.

1. Right-click on the license file in the \bin directory and select Properties

2. Select the Security tab (this example is done using Windows XP)

3. Click on the Advanced button as shown above to pop up the Advanced Security Settings

4. Click the Inherit checkbox as shown above

5. Click Apply and to save the change

6. Try accessing the application once again

 

Details by Operating System

On Win2K with IIS 5 this account is usually "ASPNET", and it is normally a member of "Users" local group. Security rights are usually assigned directly to "ASPNET" account under this configuration.

On Win2003 with IIS 6 the account is usually "Network Service" (configured under "Identity" settings of the AppPool the web app runs under), and it normally belongs to "IIS_WPG" local group. Security rights are usually assigned through "IIS_WPG" group under this configuration.

Either the ASP.NET worker process account or one of the groups it belongs to must be granted "Read" rights to both the application's "bin" directory and the license file itself. When a user copies the license file into "bin" or saves it directly into "bin" from an e-mail attachment, the file might end up having user-specific security rights applied to it, and might not be allowing security rights to be inherited from its parent directory. The user needs to verify that license file security rights are being inherited from "bin" directory, and that ASP.NET worker process account has "Read" rights granted to it.