Licensing....again

[Bas]

I'm using the VPEngine in a Visual Basic-program.
I'm deploying the follwing files with the setup of the program.
- DAV3_32.DLL
- LEON3_32.DLL
- BARVISD.DLL
- VPDF3236.DLL
- VZLIB32.DLL
- VPEX3236.DLL
- VPECTRL36.OCX

Only one of our customers is having trouble with the license.
He keeps getting the DEMO VERSION in the printout of our program.

I told him to re-install the program, what didn't work for him.
Then I told him to remove all of the above files, before installing, but that didn't work also.
I made him a new setup file with "Inno Setup", which replaces and re-registers the ocx/dll-files, but that didn't work either.

Could you tell me what the customer or me is doing wrong?

Thanks in advance,
Bas

[IDEAL Software Support]

Maybe he is executing VPE on a server? Citrix or Terminal Server are also servers.

Regards
Thorsten Radde
IDEAL Software GmbH

[Bas]

I informed with the customer...
He is starting the program from Novell Application Launcher.

So should he install the program locally on his machine?

[IDEAL Software Support]

We don't know the Novell Application Launcher.

The question is, whether VPE is executed on the CPU and in the memory of a server, or if it is executed directly on the client machine. In the latter case there is no problem. VPE may be loaded for example from a file server into the memory of a client machine without requiring a server license.

Regards
Thorsten Radde
IDEAL Software GmbH

[Bas]

Today I got a reply-mail from the customer.

The dll's/ocx's are installed locally.
And the program is also runned locally.

He now tells me the problem occured after the installation
of ServicePack 2 of Windows XP. Before that there were
no problems....

[IDEAL Software Support]

We tested the licensing with VB 6 SP6 on Win XP SP2 and had no problems.

For whatever reason, VPE seems to identify itself as a server process. And as you said, it only happens with this specific customer. An idea which comes to my mind is that, if the Novell Application Launcher is running as a service and launches VPE, this will make VPE a child process of a service, so VPE would identify itself as a server process.

Regards
Thorsten Radde
IDEAL Software GmbH

[Bas]

Thought you might wanted to know...

The sysadmin from my customers company managed to get it working.

Mail from the sysadmin, translated from Dutch:

We have tested with Service Pack 1 and 2 and with open and closed policy, in alle cases the program came with: "DEMO VERSION".
Starting the program from Start/Programs did start a fully functional version.
It looked like it had something to do with our version of Zfdagent (Zfd=Zenworks for desktops). Normally we use version 6.5.3.
NAL, from where we start the applications, is part of Zfdagent.
Replacing version 6.5.3 by an older version (4.0) gave us a good working program.
Upgrading to version 6.5.3 of ZfdAgent resulted in "DEMO VERSION" again.

From Novell Coolsolutions we got a tool (startup.exe). With this tool we got the program working with ZfdAgent 6.5.3.