Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[FustratedTech]

Hi,

First, I'd like to say, I'm very disappointed with the level of customer service and support from your organization. The last time I called, for "technical support" I got the sales woman who sounded like a secretary who had less knowledge about your product than I did.

My problem is simple. We had a machine in the environment (Vista 32 SP1). It was the only machine that we could get the "License Admin" program to run on. It crashed.

I'm now responsible for doling out this licenses, however, I cannot get the "License Admin" program to run. I've installed and run it from the original CD on several different OSes (Windows 2kSP3, 2kSP4, XPSP2-3, Vista XP1, event Windows NT Server). Each time, the program errors out with "Out of Mememy" and I'm unable to add additional licenses.

Please help!!!!!!!!

[Bob]

What version? (do help->version info) on one of the PC's in TelnetPro.

[FustratedTech]

Yes. Its version 5.1. Is there an updated version of License Admin that is not an MFC. It will not run on any OS that I've installed it on. And please, an upgrade is not an option.

[Bob]

5.1.what?
More information please, it's all there! Are you mixing versions? (a old CD and an installed upgrade for example).

Any version of licenseadmin from the last 5 years will run fine on any version of windows from 2k up through XP. To run on Vista you need a recent version.

[FustratedTech]

Sorry, Its 5.1.26

[FustratedTech]

Sorry the version in production is 5.0.76. Do you have to have telnet pro user installed in order to run the License Admin? If so, the License Admin that I'm using is 5.1.26, while the version of Telnet Pro in production is 5.0.76. 

I'm told that the original way it was setup was that the app was install on an NT server. Users would browse to the network share to install telnet pro (runing config wizard to get an Seq #).  The license files were stored on that same NT server everyone has read/write access to the folder. When we wanted to add/delete a license we would browse to that network share and run the "LicenseAdmin.exe" MFC application. To my knowledge, the only system we could get it to run on was the Vista SP1 system (which crashed). The configuration is still in place: the app is installed on the server, the license files are in share, the license admin app is still on the network share. However, at this point, we can't run the "license admn" app without getting an "out of memory error".

To troublshoot, I've 1) run the app on server different OSes, with varying service packs including the NT server its actually installed on. 2) I've Installed both telnet pro and license admin from the 5.1 CD on various OSes on various machines. 3) I've run memory test on all machines that its been installed on.

There is nothing wrong with the hardware these are P4 1.7+ Machines with 1GB+ memory. I even had a machine with 3GB memory. It seems that the app leaks memory as you can see the process scales up to 500MB memory and chews up more that 80% CPU before finally hitting "out of memory"

To be clear. We are having a problem creating licenses using the License Admin in the given configuration.

[Bob]

Ok, a few things I noticed from your very complete description (thanks).

Versions older than 5.0.81 are not compatible with any NT based OS's (2k and newer). This is because the versions older than 5.0.81 are not aware of the real multiple users introduced in 2k and this causes registry problems. There are several messages about this in the forum. The following two are related to your situation.
http://yabb.jriver.com/ice/index.php/topic,210.0.html
http://yabb.jriver.com/ice/index.php/topic,30.0.html

Also, Licenseadmin/configwizard and TelnetPro MUST be either both pre 5.0.81 or post 5.0.80. This is because things ICE stores in the registry changed locations to reflect the real multiple user accounts in 2k and onward. If you mix versions the licensing will not work.

Finally, I suspect that your license folder may be corrupted. That would explain the memory usage. licenseadmin is a REAL simple program. It doesn't do anything tricky. The licenses are all static, that is why the existing installs of the old 5.0.76 still work even though you can't get licenseadmin to run.

[Bob]

One last thing, if you are installing a fresh copy of licenseadmin, you need the license key NOT the serial number.

You can email
deanna (at) jriver.com

to get your license key(s) from your serial number if you have lost the key(s).

[FustratedTech]

Bob,

Thanks for your help. You've really help me to troubleshoot this thing in depth and I appreciate your incite. We have one last trick to check which is trying to manage the licenses uing the license admin from 5.0.76, which I suspect will not work because it is already install on the NT server that has the license folder. Nothing has changed on this server -- not even patches.

To anyone who has read this post our solution is as follows to rebuild the license folder, Bob, tell me what you think:

* Enumerate a list of computer names by reading the license files in the license folder (Think: Linux strings comand.
* Take the list of machines and compare it agains Active Directory (or whatever directory you use to manage your machines). Find the machines that are no longer active, and delete there license files.
* Next, enumerate the list of machines again, this will be the list of machines that are likely to need J.River in the first place, this is the list of machines you'll need to push a registry fix to.
* Install license admin with to a fresh folder, create your needed licenses
* Enumerate the list of licenses in your new folder, this time taking note of the file names (these are the sequence numbers
* Push a script to all the machines that changes the sequence number in the registry.