Missing DLL
- Thread starter vefatica
- Start date
- Jun
- 10
- 0
same problem here, jpworkszip16.dll and jpworksssh16.dll (Take command x64)
- Jun
- 7
- 0
same problem here, Take Command x64
- Jun
- 10
- 0
I have renamed jpworkszip9.dll to jpworkszip16.dll and jpworksssh9.dll to jpworksssh16.dll. TCMD starts now.
- Oct
- 43
- 1
That took care of it! Thanks Rex
- Jun
- 10
- 0
I had to uninstall all older versions of tcmd in Control-Panel (verion 15 to 20), then i could install the newest version! Error-Message was: there is an older version installed....
- May
- 13,117
- 180
That's odd. I have versions 11 - 20 installed and I'm never asked to uninstall older ones.
- Jun
- 10
- 0
I also had never problems with the older versions in Programs and Features, but with the current tcmd.exe from rconn, downloaded from the download-page, 20.11 Build 39, I've got this error
- May
- 13,117
- 180
I got mine the same way (download page) and had no such problem (on Win 7).
- Jun
- 10
- 0
I work on Windows 10, newest build. I don't know, why I got the error, but, after unstall of all TCMD's in Controlplanel, I could install the latest build of TCMD and the settings were still there. All's OK for me now.
- May
- 13,117
- 180
I had to uninstall a previous build of v20, but not older major versions (19, 18, .... Is it possible that you misunderstood the message?
- Jun
- 10
- 0
The message said 'older version'. For that reason, I uninstalled all older version. Maybe, the uninstall of version 20 were enough..
- Jun
- 10
- 0
Another version seems not to be the same as older, I misinterpreted the message.This is the message I got. Uninstalling v20 was enough.
This experience with the missing dll displayed a rather useless installer.
Doing a Repair was a rather bad idea as it installed Everything even though it weren't installed to begin with.
I assume Repair also registered all available file extensions rather than the previously selected .btm
Later I found that uninstalling TCMD didn't uninstall Everything installed by Repair.
I also tried to install .38 on top of .39, which made it say that a newer version already had been installed,
(even though said newer version were useless.)
Having an option in the installer to force a downgrade would be nice in situations like the above.
In the end I had to uninstall TCMD, manually remove the Everything service (SC delete), then reinstall TCMD.
However, now I've gotten .40, and it works.
Doing a Repair was a rather bad idea as it installed Everything even though it weren't installed to begin with.
I assume Repair also registered all available file extensions rather than the previously selected .btm
Later I found that uninstalling TCMD didn't uninstall Everything installed by Repair.
I also tried to install .38 on top of .39, which made it say that a newer version already had been installed,
(even though said newer version were useless.)
Having an option in the installer to force a downgrade would be nice in situations like the above.
In the end I had to uninstall TCMD, manually remove the Everything service (SC delete), then reinstall TCMD.
However, now I've gotten .40, and it works.