This Document is not yet Rated

Rate this Document

Why Do I Receive an Error when Accepting Permissions from Network Installers?

Primary Software: Other NI Software>>NI Volume License Manager
Primary Software Version: 2.0
Primary Software Fixed Version: N/A
Secondary Software: N/A

Problem:
I have recently installed a new license file for NI VLM. New end users have recently run the network installer for an NI product, and their permissions are now in the queue. When I attempt to accept the permissions, I see the following error:

Why am I receiving this error, and how can I solve the issue?

Solution:
This error occurs when the PACKAGE name of the NI Software changes in the license file. This can occur when the type of license changes (such as switching from Named-User to Computer-Based licenses), when changes to the package are made (changing Developer Suite options, for example), or when NI changes the package name to prevent other errors.

To fix this issue, you can take the following steps:

1. Create a new network installer for the software which is causing the error. For more information on creating network installers, see step 5 in KnowledgeBase 3KPEI86E: Getting Started with NI Volume License Manager.
2. Distribute the network installer to any end users which currently have permissions requests in the queue that cause the error.
3. Ask the end user's to run the file vlmclient.exe, which is found in the 'Client' folder in the network installer root directory. This executable will take them through the process of setting up communication and permissions with the VLM server without having to reinstall the software.
• NOTE  In earlier versions of VLM (pre 2.1) you need to run mslsetup.exe located in network installer root directory, not vlmclient.exe.
  
4. Once the permission request is found in the VLM queue, you can reject the old permission request which causes the error and accept the new permissions request.
   

The following is a solution if you do not wish to create new network installers. (Note: This solution is more complex. It involves manually modifying XML files as well as reading and understanding information in the volume license file. If you are not able to follow these instructions, or follow these instructions but the error remains, please use the first solution).

1. Open the volume license file received from NI in a text editor (such as WordPad).
   
2. Look for the PACKAGE line in the file which contains the software that relates to the permission request. For example, if the user was requesting permission for LabVIEW Full Development System (Computer-Based), then the package line in the license file may be "PACKAGE LabVIEW_FDSM_PKG"
3. Navigate to the network installer location. In the network installer root directory, open the file vlmclient.xml in a text/xml editor. (again, if pre-VLM 2.1, you will open mslsetup.xml)
4. You will notice the following tags near the bottom of the file:
   
     <features>
    <feature>
      <fullName>LabVIEW_FDS_PKG</fullName>
      <version>8.0000</version>
    </feature>
  </features> 
   
   Replace the fullname value with the PACKAGE name found in the license file. Using the above example, the fixed xml should look like this:
   
   <features>
    <feature>
      <fullName>LabVIEW_FDSM_PKG</fullName>
      <version>8.0000</version>
    </feature>
  </features>
   
   
5. Ask the end user's to run the file vlmclient.exe, which is found in the network installer root directory (again, if pre-VLM 2.1, run mslsetup.exe). This executable will take them through the process of setting up communication and permissions with the VLM server without having to reinstall the software.
6. Once the permission request is found in the VLM queue, you can reject the old permission request which causes the error and accept the new permissions request.

Related Links:
KnowledgeBase 3KPEI86E: Getting Started with NI Volume License Manager
KnowledgeBase 4IAG99NM: VLM Network Installer Causes Error -12 When Building Distribution in Application Builder
KnowledgeBase 4IDD6SH0: Sending Permission Requests Without Directly Using a Network Installer
KnowledgeBase 47IAHTQA: Creating a Network Installer in VLM

Attachments:


- vlmPermissionError.JPG



Report Date: 09/28/2006
Last Updated: 04/04/2008
Document ID: 41R9QE8M

Your Feedback!	Poor  |  Excellent							Yes	No
Document Quality?							Answered Your Question?
	1	2	3	4	5
Document needs work? Please tell us why.
Please Contact NI for all product and support inquiries.