| Author | Forum: Licensing Issues Topic: Contents of the Licenses.licx file |
| HRTIII From: Flora, MS USA Posts: 5 Member Since: 08/31/10 |
posted August 31, 2010 11:22 AM I have developed an application in VB .Net using the PowerTCP SSH and SFTP for .Net component and I am having a licensing issue when I try to deploy the application. I have created the licenses.licx file and rebuilt my project as instructed in the help file. But I noticed a discrepancy between the information in the help file and the information that appears on the licensing error message popup. The help file says that the licenses.licx file contents should read: Dart.PowerTCP.Ssh.Sftp, Dart.PowerTCP.Ssh But the error message popup says is should be: Dart.PowerTCP.Ssh.Ssh, Dart.PowerTCP.Ssh Which one is correct? Also, I have some machines that run the application without any licensing error message while others get the licensing error message when the application launches. All of the machine are running the same copy of the EXE from the same location. Any suggestions? Thanks! |
| Nick B (Admin) From: Utica, NY USA Posts: 619 Member Since: 05/25/10 Extra Support Options Custom Application Development |
posted August 31, 2010 1:38 PM Hello, You should use the one defined in the popup message (as long as you are using the component mentioned in the message in your application). |
| HRTIII From: Flora, MS USA Posts: 5 Member Since: 08/31/10 |
posted August 31, 2010 1:48 PM I don't see how the DLL could be registered on these machines since this is a new component that I just purchased and this is the first application that I have created using this component. I will inspect the registry of the machine that is not getting to license error message to see if I see any indication that the component is registered. |
| Jason Farrar (Admin) From: Oneida, NY USA Posts: 223 Member Since: 07/24/07 Extra Support Options Custom Application Development |
posted August 31, 2010 2:38 PM Our components are structured in such a way that you can use any licensed component in the licenses.licx, so in the case both Dart.PowerTCP.Sftp, Dart.PowerTCP.Ssh and Dart.PowerTCP.Ssh, Dart.PowerTCP.Ssh should work equally well in terms of licensing. You don't need to search through your registry to try and find if the component is registered. The SSH component is a .NET component and not an ActiveX one, as such it doesn't get COM registered. I think this was a miscommunication and misunderstanding on our part. If I understand correctly the problem you are seeing is that you have an executable compiled from a project containing a licenses.licx. When you run this executable on some mahcines it works fine on other machines you get the above licensing exception, is this correct? |
| HRTIII From: Flora, MS USA Posts: 5 Member Since: 08/31/10 |
posted August 31, 2010 2:49 PM Yes. That is correct and, thus far, I can't find any rhyme or reason as to why it works on one machine versus another. I have considered the OS version (2000 vs. XP) and the version of the .Net Framework that is installed, but I haven't identified any common element that accounts for the machines that work versus those that don't. |
| HRTIII From: Flora, MS USA Posts: 5 Member Since: 08/31/10 |
posted September 1, 2010 11:15 AM I have some new information. This appears to be a rights issue. When I log on to the machines that are generating the license errors as myself, I can launch the application without the license error. My userid is in the Admin group for the domain. The question is: what local rights are needed on a Windows 2000 platform to validate the license? If I know that, I can grant the needed rights to the users of the application. |
| Jason Farrar (Admin) From: Oneida, NY USA Posts: 223 Member Since: 07/24/07 Extra Support Options Custom Application Development |
posted September 1, 2010 1:13 PM OK. I'll give this a go on a 2000 VM to see if I can duplicate the issue. |
| HRTIII From: Flora, MS USA Posts: 5 Member Since: 08/31/10 |
posted September 7, 2010 2:10 PM I have identified the issue and it is not, strictly speaking, a rights issue after all. The executable resides in a shared folder on a server. I gave each user a copy of a shortcut that I created to the executable. When I created the shortcut, I specified the location of the executable as a UNC rather than using the available mapped drive to identify the shared folder. This worked fine on the XP clients but it generated the licensing error message on the Win 2000 clients. When I modified the shortcut to speicfy the path to the executable using the mapped drive, everything worked fine. |
| Reply | Licensing Issues Topics | Forums |
This site is powered by
PowerTCP WebServer for ActiveX
|