FAQs

The following is a list of frequently asked questions. Please consult this list before contacting support as you may very well find the answer you are looking for here.

Installation

The install for Version 4 runs to completeion, but the first time I attempt to open the Admin tool in a browser, the browser is blank, and the it appears that the page is continuously loading. 

You probably have the wrong Application Pool or the wrong version of the .Net framework assigned to the Admin web application and/or the BusinessService web application.  To correct this, open IIS Manager, view the properties for the InstallKey virtual folders and select an Application pool that is running the correct framework.  See the QuickStartGuide and the Developer Guide for or information.

When installing version 3.4, I get this error: You don't have sufficient privileges to complete this installtion for all users of the machine. Log on as administrator and then retry the installation.

The installer may fail if you try to install with elevated privledges. When installing on Vista, Windows 7 or Windows 2008, you must be logged in as an administrator AND windows User Account Control (UAC) must be disabled and turned off.

The install runs to completeion, but the first time I open any of the urls in a browser I see an error like this: br /> Unrecognized attribute 'type'.
Line 9: <sectionGroup name="applicationSettings" type="System.Configuration.ApplicationSettingsGroup, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
Source File: C:\inetpub\wwwroot\InstallKeyAdmin\web.config Line: 9
Version Information: Microsoft .NET Framework Version:1.1.4322.2407; ASP.NET Version:1.1.4322.2407

You probably have both the .Net Framework version 1.1 and version 2.0 installed and your web server is configured to use .Net 1.1 as the default for new web applciations.  To correct this, open IIS Manager, view the properties for the InstallKey virtual folders, select the ASP.Net tab, and select the 2.0 version of Asp.Net.

Integration with your application

I have some applications that are written against the .Net 2.0 framework and other applications that are written against the .Net 4.0 framework.  Do I need two versions of InstallKey on the server side? Do I have to purchase both version 3.4 and version 4.0 of InstallKey.

No. The InstallKey version 4.0 server is backwards compatible with the client side components of InstallKey versions 3.0 thru 3.4.  Your .Net 2.0/3.0/3.5 based applications that use the version 3.0 thru 3.4 client side dlls can validate against the InstallKey 4.0 server. Just purchase InstallKey version 4.0.

I don't want my customers to be able to read the contents of the surety file.

Set the CientLicense.EncryptLocalSurety property to true. The entire contents of the surety file will be encrypted the next time that the surety file is persisted.

Does the surety have to be stored as file in the current working folder?

No. The you can change the filename and the location where it is stored. In fact, the surety does not even have to be stored as a file. It can be stored anyplace that you can persist a string. See the chapter in the dev guide called 'Storing the Local Surety'

InstallKey Admin

Can I generate a key automatically or programatically? Do I have to use the InstallKey Admin website to create my keys?

Yes you can generate keys programatically. No, you do not have to use the provided Admin website to manage your keys.

The InstallKey Business Service website is a collection of ASP.Net web services which allow you to perform any action that you can do with the InstallKey Admin website. In fact, you do not even need to use the InstallKey Admin Website if you write your own utilites that consume the BusinessService web services.

I am using InstallKey 3.4 and am trying to enter a trial expires date into the text box in DD/MM/YYYY format.  Some dates, such as 18/8/2010 result in invalid date errors.  Other dates, such as 9/8/2010 result in the trial date being stored as the 8th of September.

This problem has been isolated to data entry field in the Admin UI, and does not effect the functioning of the trial date.  This issue has been fixed in version 4.0 of InstallKey.

To workaround this issue in version 3.4, the trial expires date field must always be entered in MM/DD/YYYY format.  Or just use the date picker popup next to the field to select the correct date.  The date picker popup will always format the text box value in the correct format.

I am using InstallKey 3.0 and I get an error code 500 when I create a new Keyset -or- I get an error every time I select Keysets from the menu.

This is a known bug that occurs when a Keyset has a name that is greater than 16 characters in length. This was fixed in release 3.1. If you are using version 3.0, do not create keysets with names that are more than 16 characters in length.

I am using InstallKey 3.1 and after I log in to the InstallKeyAdmin site, the dropdown menus do not work or are hidden.

This problem occurs only when viewing the InstallKeyAdmin web pages with IE8 or Google Chrome browser. (This problem should not occur with IE6, IE7 or FireFox) This was fixed in version 3.2 of InstallKey. 

The issue is a known bug in way that the ASP.Net menu control interacts with these newer browsers. Setting the IE8 browser to compaitiblity mode, will also fix this issue.