Print

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

[CDSmith]

When upgrading 2 Windows XP Pro computers from 5.0.80 to 5.1.19 on a remote network which has a DSL connection to the Internet and where Telnet Pro is used to connect to an SCO server at the main office location, I am having a problem with a conflict when Telnet Pro is run from both computers.  The workaround at the moment is to only run Telnet Pro on one computer.  I have created a Server install and have reserved 2 sequence numbers for these two machines.  Each reservation was exported to floppy and the LicenseKeys file for each of the 2 computers was copied up to the local hard drive on each computer and used when running Config Wizard.

When Telnet Pro is run from the second machine after it is already running on the first machine, the following errors occur on both computers:

Application Event IDs 1000, 1001, and 1002

Event ID 1000

Faulting application telnetpro.exe version 5.1.19.0 faulting module dejavu.ocx, version 5.1.19.0 fault address 0x0039c00

Event ID 1001

Fault Bucket 72306190

Event ID 1002

hanging application telnetpro.exe version 5.1.19.0 hanging module hungapp, version 0.0.0.0, hang address 0x00000000

Currently, only one computer is in use and I'm hoping someone will have an answer for me.

[Bob]

The must have the same sequence number.
In regedit check:

HKEY_LOCAL_MACHINE
  SOFTWARE
    J. River
       ICE.TCP
          5.0
            License

The key you want to check is TempUserID. This way you can tell which one is incorrect. You cannot change the value of the sequence number by changing TempUserID, it's only a reflection of the internal value. You will need to export the license you wanted and try running configwizard on the exported license again.

[CDSmith]

Ok, with this registry key to examine, I was able to figure out how to make the second machine get sequence number 2 as the problem indeed was that it had the same sequence number 1 as the other computer.  I didn't have an easy time getting to this however and I've apparently misunderstood when I've thought that the LicenseKeys file included the sequence number.

When reading the "Keeping Track of Users" section of the Help from the button on the LicenseAdmin utility, I started by first creating 6 reservations for 3 pairs of remote comptuers.  THEN, I exported each one in turn and copied the License folder from the floppy to a hard drive folder named for each of the 6 computers (taking a floppy to each computer is impractical due to distance and time required).  For the second computer at this first site, I had simply transferred the LicenseKeys file and put it into an empty License folder and then run ConfigWizard which resulted in getting another assignment of sequence number 1.  I did not use the same LicenseKeys file used on computer one.

Since viewing your reply, I've taken a different approach and I transferred the entire License folder up to the second computer and ran ConfigWizard again.   Included in the folder was the LicenseKeys file plus 6 reservation files named 1,2,3,4,5 and 6 (readonly, hidden).  In this case, after running ConfigWizard, the sequence number assigned in the registery TempUserID was 7.  It was then that I realized that the sequence number must not be included in the LicenseKeys file which I've thought for years.  So, since I wanted this particular second computer to have sequence number 3, I deleted the reservation files named 2,3,4,5 and 6 leaving only the reservation file named 1 and the LicenseKeys file.  Then, after running ConfigWizard again, the sequence number was now properly assigned as sequence number 2.

I believe that if I had created 6 floppies and taken them to each machine, I'd have ended up with sequence number 7 being assigned to all 6 computers.

Anyway, I found this process very frustrating but feel that I have a pattern to follow by including reservation files such that the next available sequence above the reservation files will be assigned.   If I've made this harder that it should be, please explain how I should have proceeded.  

Thanks,

Chris

[Bob]

Sorry that you have had a difficult time with this.

Another, perhaps easier, way to do this is to not reserve ANY computers in licenseadmin and take the license folder to each machine one at a time and run configwizard pointing to that license folder. Each machine will grab a new sequence number from the folder and update the appropriate files in that folder. When you are finished you can copy that folder back over the top of the one on the license server and now licenseadmin should reflect the current state of your licenses. Be sure to backup the previous license folder on the server before you do this.

[CDSmith]

Ok, much thanks, Bob.  I'm doing fine now with 4 of 6 remote workstations upgraded and I've got good control over the assigned sequence numbers.

Chris