Why does VLM v2.0 close after disconnecting a computer

[RobSevick]

After upgrading to Volume License Manager (VLM) v2.0, I'm trying to setup a "permanently" disconnected license for an existing computer license.  When I do this, I provide the file name and path, then I get an hour glass for a few moments, then the VLM closes. 

It creates the license file but does not indicate in VLM that the license is disconnected (with a red X). 

*Note this is the second update to VLM v2.0.  The first time, the Create Network Installer wouldn't work properly.  That is working now, but this is not. 

Please help... Thank you,

Rob Sevick

JHU/APL

[~jiggawax~]

Hey Rob,

Here is a link that will describe what to do with the Disconnected License File.  After I Create a Disconnected License from NI Volume License Manager, How do I Use It? I hope this is helpful.

[~jiggawax~]

Here's some more info as well: What is a Disconnected License File?

[RobSevick]

Thanks Sam,

But I know what to do with a disconnected license, I was intentionally setting up a disconnected license for a new computer.  My question was, why when I tried to disconnect this license, the VLM closed abruptly. 

Thanks, Rob Sevick

[~jiggawax~]

Hey Rob,

Sorry for the misunderstanding.  I'm curious exactly when your VLM closes?  Does it close right after you select "Disconnected license should never expire" and then click the OK button?  When you open it back up does it show the computer as disconnected with the red X?  Do you get the same behavior if you chose the "Disconnected license should expire on the date below"?  Can you consistently reproduce this issue?  This sounds like a glitch or something because it's not supposed to behave this way.  Did you install VLM from the CD?  I would suggest copying it to your harddrive and reinstalling it from there.  Other than that I've never heard of this issue.  I would be curious to know all the steps to reproduce it and exactly when it happens.

[~jiggawax~]

Message Edited by Sam R on 12-19-2005 04:23 PM

[RobSevick]

Here is the problem with creating a Disconnected license in the new VLM v2.0. I was speaking with someone in the forums but no solution yet has been found.

Here is what I do:

- If I right-click on a computer, then choose Disconnect…

- Choose Permanent, then click OK

- Provide a license file name and path, then click Save.

- When I click on Save, the VLM abruptly closes and takes me back to the desktop. There is an event log error message that indicate: "The NILM License Manager service terminated unexpectedly." Event ID: 7031.

- Oddly, it creates the disconnected license file, but does not indicate the computer is disconnected in VLM (with a Red X).

This is repeatable. Please help,

[~jiggawax~]

Hey Rob,

Try a reinstall and let me know if you get the same behavior.  Thanks!!  Check out this KB before you do it though.

Message Edited by Sam R on 12-20-2005 02:52 PM

[RobSevick]

Sam - I'm a little nervous about that.  I installed the first release of VLM 2.0 and the Create Network Installer would not work properly and it also removed all of my permissions from the Computer licenses I had.  I had to readd the permissions manually, which wasn't fun.  So I found a newer version of VLM v2.0 that was released to fix the Create Network Installer problem (I think there was a forum/discussion on it) and installed the newer version of VLM v2.0 over top of the existing version.  Now, the Create Network Installer works but for some reason this (Create a Disconnected license) doesn't work. 

So installing it again makes me a little nervous.  Is there a newer version out then the one I have? 

[~jiggawax~]

The latest version was updated on November 17th.  The reason I ask you to reinstall is because you may have gotten a glitch somewhere during you installation.  Maybe because you installed the newer version over the older version.  I know that is what you were told to do but this is fairly new software and we haven't tested it in every case.  It is useful to have feedback from users.  Either way we want you to be satisfied. If you do reinstall it and it fixes the issue I can pass that information along to R&D.  Thanks for the patience.