Install TC 17.00.37 x64 expires immediately & invalidates registered TCmd v16.03.55

Mar 10, 2012
12
0
I am a registered Take Command user. After seeing the newsletter, I decided to install the TC 17 Beta by clicking on the link in the newsletter. My current Take Command v16.03.55 is installed in C:\TC, and I backed up that folder to C:\TC16. I am running Windows 7 and I installed the 64 bit version of today's build.

When I ran the new tcmd from the start menu it refused to run giving a message box, "This trial version of Take Command 17.0 has expired!". So I visited the support forum in jpsoft.com and downloaded the very latest build and ran that. Same message box error.

Good thing I backed up my Take Command v16, I thought. So I ran C:\TC16\tcmd.exe dated 7/12/2014. The same message box occured, and I could not run tcmd.exe version 16 either. So I tried running C:\TC16\tcc.exe. This worked, opening a tcc.exe console window. From that window I tried to run C:\TC16\tcmd.exe and the same message box error occurred. I cannot run C:\TC\tcc.exe, which is version 17 without the message box and opening my browser to the JPSoft web store.

After installing TC v17 beta, I cannot run either tcmd v17 or tcc v17 or tcmd v16. I'm not completely stuck, since I have tcc v16.03.55 running. And I have it on a thumb drive too. But something is wrong with the registration system.

The text below is from the TC v16 console window. The message box error occurs after running tcmd.exe

C:\TC16
>ver /r

TCC 16.03.55 x64 Windows 7 [Version 6.1.7601]
TCC Build 55 Windows 7 Build 7601 Service Pack 1
Registered to Steven Kraus - 1 System License

C:\TC16
>dir c:\tc16\tcmd.exe

Volume in drive C is Windows7_OS Serial number is 968c:176e
Directory of C:\tc16\tcmd.exe

7/12/2014 10:33 5,934,696 tcmd.exe
5,934,696 bytes in 1 file and 0 dirs 5,935,104 bytes allocated
66,991,734,784 bytes free

C:\TC16
>c:\tc16\tcmd.exe
 

rconn

Administrator
Staff member
May 14, 2008
12,340
149
Take Command v17 and v16 do not share any registration info, and installing v17 will not overwrite or affect any of the v16 files. Did you install v17 into the same directory as v16 (i.,e., without deleting the v16 files)? That would not be a good idea, as the COM dll's will not register themselves correctly in that situation.

And you cannot "move" a TCMD installation from one directory to another (without a reinstall); again the COM dll's will not work (Windows will be looking in the original directory).

The only time I've seen something like what you're describing is when trying to run TCMD under a debugger, or with the wrong (or modified or corrupted or unregistered) IsLicense50.dll.

Try starting an elevated TCC or CMD session, and go to the TCMD17 installation directory. Run:

regsvr32 /u islicense50.dll
regsvr32 islicense50.dll

and see if that resolves your startup problem.
 
Last edited:
Mar 10, 2012
12
0
Take Command v17 and v16 do not share any registration info, and installing v17 will not overwrite or affect any of the v16 files. Did you install v17 into the same directory as v16 (i.,e., without deleting the v16 files)? That would not be a good idea, as the COM dll's will not register themselves correctly in that situation.

And you cannot "move" a TCMD installation from one directory to another (without a reinstall); again the COM dll's will not work (Windows will be looking in the original directory).

The only time I've seen something like what you're describing is when trying to run TCMD under a debugger, or with the wrong (or modified or corrupted or unregistered) IsLicense50.dll.

Try starting an elevated TCC or CMD session, and go to the TCMD17 installation directory. Run:

regsvr32 /u islicense50.dll
regsvr32 islicense50.dll

and see if that resolves your startup problem.

Why always install to C:\TC ?
My Take Command installation is always in the \TC folder off the boot drive.
On USB thumb drives, registered Take Command is always in the \TC folder, and I have version 15 and version 16 on a couple of thumb drives.
I have put all of my .btm files and associated data files they use in the \TC folder.
I have written several programs that start a tcc.exe process running a batch file from the \TC folder, and those programs check to see which drive they were loaded from, and append the "\TC\tcc.exe" and the batch file. I occasionally run TC from a thumb drive on a customer's computer, where Take Command is not installed and it is not in the path on their computer.

I type "\TC" quite a lot.

I tried running revsvr32 from an elevated CMD session and the messages indicated these two commands succeeded.
But this did not fix the TCmd 17 startup problem. The "expired" message appeared when I started Take Command version 17 and versipn 16.
So I deleted all the installed files from C:\TC (except my .btm and data files) and reinstalled the Take Command beta into C:\TC.

Reinstall works
After reinstalling Take Command 17, I was able to run the unregistered tcmd.exe.
And my registered tcc.exe version 16 continued to work from "C:\TC16\tcc.exe" where it was copied. ver /r shows it is registered version 16. This is good.
But C:\TC16\tcmd.exe apparently runs tcmd version 17

I can understand why copying Take Command without installing breaks the registration. Many shareware programs that use a key file or use the registry work if you install a new version right over top the old file. And they also work if copied to a new folder. But that registration method is not as secure.

I am a contractor and I usually have a separate thumb drive for each client. Take Command is one of my essential tools. So I make thumb drives with registered Take Command, and I write on tape on the thumb drive "TC v15" or whatever version.

Thanks, Rex, for your prompt response at 1 AM !
Steve
 
Similar threads
Thread starter Title Forum Replies Date
fishman@panix.com 27.00.17 x64 will not install for me!! Support 4
J How to? 20beta: How to install x86 on x64 Support 2
bwawsc2 Can't install updates to TCMD x64 Support 5
I Take Command 18 x64 Install Hang Support 2
samintz Can't install 15.01.54 on Win7 x64 Support 6
Joe Caverly Here-Document on new Install Support 21
S 32-bit Take Command v22 install for thumb drive Support 1
Roedy install fail Support 9
A Reinstalling TCC-RT 21.01.57 triggers a new install instead of update/reinstall Support 3
R Portable install with v21 - why did it not work? Support 3
G How to? Unable to install TCMD 21 under Win2012R2 Support 5
samintz Build 38 Install issue Support 5
N Cannot install Support 2
fishman@panix.com Version 21.23 fails to install Support 4
Seven Update / install issue with 20.0.20.10.32 take command Support 7
keithg1964 TCC RT Install Files Support 1
fishman@panix.com Once again the Can't Install bug bites... Support 2
Roedy missing English.dll, failed install Support 2
T Beta - duplicate install Support 7
fishman@panix.com 19.10.51 will not install for me Support 1
A Latest TCC/LE install broken Support 1
M How to? Take Command\TCC install problem... Support 2
H New Install; Everything setup issues Support 9
fishman@panix.com 19.02.37 Does Not Install For Me Support 2
D V19 fails to install on Win7-64bit, installer says: Support 2
Alpengreis [TC 19.0 Beta 22/23] Install/Update-"Problems" Support 4
fishman@panix.com 18.00.31 would not install for me Support 5
M How to? Run TCC from Windows Install DVD... Support 2
T Everything install forced (sometimes) Support 2
vefatica Build 28 install Support 8
S How to? Remote Install Support 1
vefatica Build 14 install Support 3
T Clean install - squeaky clean Support 14
Alpengreis [TC 17.x] Install with "option /u" failed Support 5
vefatica Update to current install dir? Support 8
CWBillow TCMD v16 won't install Support 6
C Build 34 install error Support 4
jbanaszczyk TCMD 16 Install - download folder Support 2
L 15.01.54 won't install on Windows 8.1 x86 Support 2
MickeyF gpf when trying to use tcc.exe on standalone install Support 0
S How to? Install TCMD for ALL users Support 5
noahcoad How to? Prevent web url from opening after silent install Support 0
D New 64-bit install goes to Program Files x86 Support 3
C Install Issue with 3rd Party Privelege Escalation Support 2
S How to? Install from same installer copy after cancelling previously Support 6
F How to install 64-bit after having installed 32-bit on Win7 Support 2
Peter Bratton Observations on v15 install Support 4
gschizas Is there any way to do a silent install? Support 15
vefatica Install two minor versions Support 4
Roedy WAD Minor long-standing install problems Support 6

Similar threads