|Products Purchase Publishing Articles Support Company Contact|
support > Product FAQ > Desaware Licensing System
Event Log Toolkit
NT Service Toolkit
Desaware Licensing System Support
Frequently Asked Questions (version 2.0)
FAQ for version 1.0-1.6 of the licensing system can be found here.
Between the different operating systems, databases, IIS configurations, and other services that can be installed on a server, the possible permutations are nearly endless. It's no surprise that virtually every support question we get on this product relates to server configuration. Please refer to the Getting Started section of the licensing system documentation (available when you install your client software and here) for an in-depth guide to installing the server. Use the license manager application diagnostics to retrieve server logs that can identify most problems. Please include a copy of these diagnostics when contacting Desaware support.
In order to run your licensed application under the Visual Studio .NET debugger, you must copy your dls20client.dlsc file to the same folder as your compiled assembly file. A copy of the dls20client.dlsc file for your system can be found in the Program Files\Desaware license System directory (assuming that is where you installed the client software).
In other words - the machine license component is itself licensed. So you need to place the dls20client.dlsc file that was created during installation into the bin directory of your application in order to debug it. This is, of course, only required to debug your licensed application (during development).
This is also discussed in the licensing system readme file and documentation.
Note that the version 2.0 license file is dls20client.dlsc. The prior version dls10client.dlsc file will not work with verison 2 software.
See our Hosting Information page.
You would need a minimum of 1 server license and 1 client license. The Server License is for the Licensing System's web service that validates your applications and install codes, manages the database, and allows you to create new applications and install codes. The Client License is for the developer and those who are managing licenses.
Your initial client and server license allows you to use the Desaware.MachineLicense.dll component to add to your application project, test and run it in debug mode. It also includes the Desaware License Manager which allows you to communicate with the License Server to create new Applications and their corresponding RESX file, generate install codes, sign DLSC files, etc.
The License Server allows you to create as many unique Applications as you wish for one particular URL used to access the licensing web service. You would only need additional Server licenses if you want to access the licensing web service using multiple URLs - for example, if you wanted to divide the licensing of different applications onto different domains. If you use the installer application to install the license server, you will also be able to access the licensing web service from the local system.
The server licensing has changed from version 1 (where the server was also licensed per-machine). Read more about this here.
The License Client allows you to develop .NET projects that use the Licensing System or run the License Manager application. This is licensed per machine. You would need additional client licenses if you have more than one developer working on the licensing or installation code for a particular project (you do not need a license for each developer who is working on the project - only those who need to debug the licensing code).
You will also need additional client licenses for each system that runs the License Manager application - that allows creation and management of installation keys and applications.
Once you create your application, you can freely redistribute the Licensing System's required files without any additional fees.
We've worked hard to ensure that different versions of the licensing system remain compatible with each other, but changes in the .NET framework have not always made this possible. The following compatibility matrix will help you ensure that your existing applications continue to license correctly as you update both your applications and servers.
Our highest priority has been to ensure that older versions of the client component (MachineLicense) will work correctly with newer versions of the licensing server.
This table assumes all versions of the software are running under their target version of the framework. The 1.0 framework machinelicense component should not be run under .NET 2.0. The latest version of the 1.1 framework machinelicense component will run under .NET 2.0 but will only work with the latest server (1.1 or 2.0 framework). You can use your application configuration file to prevent applications from running under incorrect framework versions.
License version numbers are NOT synced to the .NET framework.
Server Error in '/LicenseServer' Application.
First, make sure you have configured IIS to use the correct .NET runtime for the version of the licensing system you installed (this is selected on the ASP .NET tab under the IIS Management properties for your web site).
You may also need to change the application pool for your web site. .NET 1.1, .NET 2.0 and .NET 4.0 applications cannot run in the same application pool. Be sure all your .NET 1.1, .NET 2.0 and .NET 4.0 web sites are in an application pool configured for the version of the runtime they need.
You may also need to add the following code to the <system.web> section in your web.config file:
<compilation> <assemblies> <add assembly="*" /> </assemblies> </compilation>
By default, .NET assemblies are supposed to preload all assemblies in their bin directory, however on some systems we've found that they do not. This change to the web.config file should solve the problem.
"Failed to Access IIS Metabase" or "The process account used to run ASP.NET must have read access to the IIS metabase (e.g. IIS://servername/W3SVC)"
To solve this problem (in most cases), you can do the following:
There are two steps to diagnosing server data problems. Turn on server diagnostics (see the documentation). Use the license manager application diagnostics tab to verify that your plug-in has been installed for the application you are testing. Cycle the server application (easily done by just modifying the web.config file or through IIS Manager), and examine the trace log available in the diagnostics tab of the license manager application after an activation is attempted. The log will show whether or not your plug-in has been found and any errors that occur. In many cases, an error in your desaware.licenseserverxx.dll.config file will be the issue. The most cases you'll find an unhandled exception occurred in your code.
Your plugin can embed diagnostic data into the system logs using the IManagement.Trace method.
You can debug your server plug-in functions by attaching a debugger. This is done using the System.Diagnostics.Debugger.Launch method to attach a debugger to your server, then call the System.Diagnostics.Debugger.Break method to actually break into the debugger.
The Desaware Licensing System currently requires .NET 3.5 to install (the 3.5 client installer installs .NET 2.0, .NET 3.5 and .NET 4.0 components).
Note that the .NET 2.0 client component does not support all of the new features of the licensing system.
Client and server components for the .NET 1.1 framework are available on request from Desaware support. These components are supported but are no longer under active development.
On a clean Windows 2008 web server install, you'll need to take the following steps:
The installer uses the IIS6 interface to set up the web application.
The Access oledb drivers are available in 32-bits only. IIS 7 application pools on 64 bit operating systems by default only allow 64 bit applications to run. To use an Access database, select the Application Pool that you are using for your license server. Choose the "Advanced Settings" option in the IIS manager. Then check to box to enable 32 bit applications in the application pool.
IIS 6 metabase compatibility (enabled via Windows features) is only required to run the license server installer. It is not a requirement for the license server to run, and is not required when deploying to a production environment (using the hosted install feature of the server).
With version 2.0, the license server has changed to be licensed by URL instead of by machine. For example: if you set up a server at licensing.yourcompany.com, then wish to also access it as licensing.secondcompany.com, you will need an additional license.
The reason for this change is because it dramatically simplifies the process of upgrading servers and supporting clusters and cloud scenarios. Each distinct URL (consisting of a complete requesting URL path including the domain and application path) is licensed separately and the corresponding license certificate is stored in the license database.
Now, when you upgrade to a new server, or deploy your server to a cloud or cluster of web servers, there will be no need to license each individual server as long as they are accessed using the original licensed URL.
The following is a brief overview of the process of migrating for a verison 2.0 server - A more in-depth discussion including recommendations for minimizing downtime can be found here.
Obviously there are variations - if the new machine is going to take over the same IP address as the old one, you don't have to do the DNS change - so you can skip straight from step 1 to 4.
Refer to the in-depth migration guide for additional details including instructions for minimizing downtime.
|Products Purchase Articles Support Company Contact