Page 1 of 1

License Not Found

Posted: Mon 20 Aug 2007 17:39
by tim.heller
I have been using this product in a client/server environment with Pro on the client and had your temporary version running on a server... everything worked on the client machine and I could deploy my package to the server just fine until the servers temp expired. Everything was removed from the server and I purchased this site license and re-installed... but still get a "License not found" trying to validate my package on the server.

Posted: Tue 21 Aug 2007 08:14
by Alexey
Do you write class library (dll), executable application (exe), web project,
web project with dynamically compiled sources?
Do you compile your project in Visual Studio environment or using command line?
When exactly do you receive the error?

Posted: Tue 21 Aug 2007 15:33
by tim.heller
This is an SQL Server Integrated Services Package (SSIS). I recieve the error once I deploy this package to the server. Again, nothing has changed in the code or the client machine. Only the server had changed... it had been running your temporary version... it expired, was uninstalled and replaced with Professional Site License.

Posted: Wed 22 Aug 2007 06:39
by Alexey
How do you deploy it? Please describe in detail so that I could reproduce the problem.

Posted: Wed 22 Aug 2007 15:02
by tim.heller
This is configured by simply settin the CreatDeploymentUtility to yes under the Projects Property Page.. After you build (or rebuild) the project it places a file like Programname.SSISDeploymentManifest in the DeploymentOutputPath is typically (bin\Deployment)... double clicking on this walks you through a wizard for targeting the server you wish to deploy to... and also allows you to validate the package... if you select this option and attempt to deploy, it goes through all the steps and attempts to 'validate' each... it's here that I get an error saying the license is not found.

Posted: Thu 23 Aug 2007 13:18
by Alexey
Thanks for your step-by-step guidance. I could reproduce the problem.
It is a known one. Same thing happens if trying to run the package from the SQL Server Management Studio.
Unfortunately, we cannot support the licensing scheme needed
for this to work properly. You have to write a wrapper library for
MySqlConnection class and add licenses.licx, licenses.config files to it.
In the licenses.config file insert the name of the tool which perform the
deployment (dtsinstall.exe). Such scheme should work without any problem.
P.S. What I can't understand is that how it could work earlier with the trial version...