Registration issue after deployment

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   I wrote an app in vb.net and then published it to see if it would install and run on another machine.  When it runs on the other machine, QP.UnlockKey(LicenseKey) returns 0.  Is this just because it is the 30 day trial or am I doing something else wrong?

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
dptulk Members Profile Find Members Posts Beginner Joined: 24 Feb 12 Location: Ohio Status: Offline Points: 12	Post Options Post Reply Quote dptulk Report Post Thanks(0) Quote Reply Topic: Registration issue after deployment Posted: 28 Feb 12 at 5:11PM
	I wrote an app in vb.net and then published it to see if it would install and run on another machine. When it runs on the other machine, QP.UnlockKey(LicenseKey) returns 0. Is this just because it is the 30 day trial or am I doing something else wrong?

edvoigt Members Profile Find Members Posts Senior Member Joined: 26 Mar 11 Location: Berlin, Germany Status: Offline Points: 111	Post Options Post Reply Quote edvoigt Report Post Thanks(0) Quote Reply Posted: 28 Feb 12 at 6:29PM
	Hi, with a compiled Delphi-App I had no trouble during trial. There is a copy enough. I guess, you have on the other machine to do the same registration stuff as on which you develop and there is anything gone wrong. So look for this. I can't say more. Werner

AndrewC Members Profile Find Members Posts Moderator Group Joined: 08 Dec 10 Location: Geelong, Aust Status: Offline Points: 841	Post Options Post Reply Quote AndrewC Report Post Thanks(0) Quote Reply Posted: 29 Feb 12 at 8:42AM
	Are you using the ActiveX version ? If so you need to register the ActiveX DLL file on each new PC. The DLL is automatically registered when you install Quick PDF Library using the install program. Start a DOS Command Prompt using 'Run As Administrator' regsvr32 QuickPDFAX0813.DLL If not the ActiveX then you need to make sure the DLL is in the same directory as the EXE file. Check the value of QP in your Debugger to make sure it is valid. Is your .NET exe set to x86 only and not CPU Any - ie. make sure it is not trying to use a 64Bit exe. Andrew Andrew