|Products Purchase Articles Support Company Contact|
support > Product FAQ > Desaware Licensing System
Event Log Toolkit
NT Service Toolkit
Desaware Licensing System Support
Frequently Asked Questions (version 1.0 - 1.6)
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. To help, we invite you to download our new server configuration guide. Also, check out our VPS Installation instructions - these instructions will work on most clean Windows 2003/2008 servers.
In order to run your licensed application under the Visual Studio .NET debugger, you must copy your dls10client.dlsc file to the same folder as your compiled assembly file. The dls10client.dlsc file is installed to the LicenseManager sub folder (on Vista/Windows 7, look on your system drive in the ProgramData directory - you'll find a folder whose name ends with LicenseManager... This folder will contain the dls10client.dlsc file. You may need to configure your folder view options to display hidden files and directories in order to see the ProgramData directory).
Effective version 1.6, a copy of the dls10client.dlsc file for your system can also be found in the Program Files\Desaware license System directory.
In other words - the machine license component is itself licensed. So you need to place the dls10client.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.
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 machine that hosts the licensing web service to validate the Applications install codes. You would only need additional Server licenses if you want to run the licensing web service on multiple machines - for example, if you wanted to divide the licensing of different applications onto different machines.
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.
Please visit our downloads page or contact Desaware support if you need updates.
Aside from corrupted/missing certificates or attempts to hack/modify the certificate, this error may indicate one of the following:
To avoid versioning problems we recommend you specify a required runtime version in your application configuration file. There are a number of breaking changes between .NET 1.1 and 2.0, and you should never allow an application to run under a later version of .NET until you have thoroughly tested it in that environment.
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 and .NET 2.0 applications cannot run in the same application pool. Be sure all your .NET 1.1. and .NET 2.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:
Please download the 1.6 version of the licensing system from our downloads page.
There are two steps to diagnosing server data problems. First, you must make sure your ProvideServerData function is being called. Turn on server diagnostics (see the documentation and server configuration guide). Cycle the server application (easily done by just modifying the web.config file or through IIS Manager), and examine the log generated when an activation is attempted. The log will show whether or not your server data function 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 ProvideServerData code.
You can debug your ProvideServerData function 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. Client and server components for the .NET 2.0 framework are included with the package.
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).
|Products Purchase Articles Support Company Contact