ICE
TCP/IP Products => TCP-PRO => Topic started by: bluebyte on October 09, 2007, 08:38:19 pm
-
When running FTP pro from within TCP pro I cannot make a connection to our server. I receive the following error message.
ftp control is not licensed correctly. new sessions can not be created telnet pro.
We are using ICE.TCP pro version 5.1.07
-
Also I have just found FTP only displays this error when Telnet pro is running. If I run ftp from the shortcut it works fine.
-
Sounds like you might have 2 copies of ftppro on your machine.
-
We have tried uninstalling anything on the pc to do with ice.tcp pro, deleting all directories and registry keys. All pc's are using the same version of ice.tcp, it's odd that the issue started randomly nothing appeared to have triggered it. The installation had been working fine until now.
-
After you deleted everything did you reinstall the current version?
Did you do a search for files on your machine for ftppro.exe?
-
I have just tested this on my own desktop as to avoid further user interference. Now when I connect to a telnet session the screen is completely black with a blue line across the bottom. This is not an SSH connection and I have tried importing the default tcp pro profile.
-
Are you saying you can't make a telnet pro connection??
Try doing: start->run
type in
telnet 1.2.3.4
where 1.2.3.4 is replaced with your server IP address. See if you get a login prompt...
-
I can open a telnet session fine via a command prompt (start / run / telnet 1.2.3.4) but when I attempt to make a telnet session using tcp pro the screen is black though it appears connection so the issue is with tcp pro. I though it may have been an issue with the profile but as I said previously I have tried importing the profile again and nothing has changed.
-
Try importing one of the profiles listed here:
ftp://ftp.jriver.com/pub/TECH.SUPPORT/profiles/
After importing, make sure the terminal type is correct, rerun TelnetPro and report the results.
-
I tried importing one of these profiles and it didn't help at all. I don't understand how the default profile we are using would suddenly not work?
-
I don't know what's going on based on what you are saying. I haven't seen this before. I'm going to take a couple of stabs in the dark.
1) Using regedit, remove the J.River folder in HKEY_CURRENT_USER->Software (highlight J.River and choose delete). You will lose your profile and host settings but it will be created fresh when next time you bring up telnetpro. Then import the profile I told you about again and add your host.
if that doesn't work...
2) Try changing your display color depth just to see if that changes anything (right click on the desktop, properties, settings).
3) Install the classic client and see what that does..
-
Hi,
I am having the same issue with a clients machine at the moment. The company I work for has a large volume license for 100 users and this 1 user in particular has all of a sudden developed this exact same issue. I noticed you have not resolved this other fellows issue and I would appreciate it if you would offer some suggestions to support your product.
-
I am having the same issue with a clients machine at the moment. The company I work for has a large volume license for 100 users and this 1 user in particular has all of a sudden developed this exact same issue. I noticed you have not resolved this other fellows issue and I would appreciate it if you would offer some suggestions to support your product.
He was talking about at least 2 different issues. Are you having trouble with TelnetPro or FtpPro? What version? (in TelnetPro do help->version information).
-
Hi Bob,
Thanks for the quick reply, really appreciate it. We are running Telnet Pro and FTP Pro, its FTP Pro we are having the issues with at the moment, the version being 5.1.26.0 for FTP pro. The exact text of the issue is:
FTP Control is not licensed correctly.
New sessions cannot be created.
However this issue has never happened with any of the other machines throughout the company. I was thinking if purging the registry of any entries and removing all related .dll files. The only other thing I can think of is a conflicting license file but I have checked the LicenseAdmin utility and there are currently no conflicts.
-
What is the version of TelnetPro on that machine? Does it work properly? You could try browsing to the TCP5_USER share on your licenseadmin machine and re-running configwizard (de-selecting the "get configuration profile" option). Then try FtpPro again.
-
Hello Bob,
The version of Telnet Pro is the same version as the FTP pro. Its an all in 1 installation pretty much.
I have had Ramona, the lady in question, load up Telnet Pro and then attempt to export it to an excel format through FTP Pro, but when it opens FTP Pro, that error comes up again.
However when I changed the license, and loaded up FTP Pro from the standard .exe it worked. But when attempting to send information from Telnet pro -> ftp pro it comes up with the error, then whenever we try to open FTP Pro on its own again, it comes up with the error also.
Is there any way for you to be able to get in contact with us directly regarding this matter? We need this issue resolved as soon as possible as it is holding up a significant ammount of work at the moment.
-
Also please note,
The FTP error only comes up when Ramona is actually logged into Telnet Pro at the time.
-
FtpPro has to read the registry to look for a license.
TelnetPro reads and writes the registry.
First I'd look for duplicate copies of ftppro.exe, ftppro.ocx, ftpro_en.dll (perhaps you have mixed versions).
Second, check for viruses on the machine
Third, if you have a real-time virus checker make sure it allows writing of the registry by Ftppro and TelnetPro.
-
Is there any way for you to be able to get in contact with us directly regarding this matter? We need this issue resolved as soon as possible as it is holding up a significant ammount of work at the moment.
We have a support line you can call (see http://www.icetcp.com/support/support-options.html (http://www.icetcp.com/support/support-options.html)) however we are 5 hours west of UTC here so the time difference is going to be pretty difficult to deal with (when it's 5pm here it's 8am in Sydney).