Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

PGP Commandline won't run on a schedule.

Created: 01 Jul 2013 • Updated: 24 Oct 2013 | 6 comments
This issue has been solved. See solution.

Hello,

we're moving our PGP commandline installation to a new workstation, running Windows7.

Version info : PGP Command Line 9.9 build 110

Problem : when running a batchfile for decrypting files everything works OK.
When running the same batchfile, with the same user, through the Task Scheduler, the job fails.
Upon investigation, it seems PGP gives the following error : pgp:decrypt (2713:no license has been entered)

PGP_HOME_DIR is defined as a system variable.
As stated : PGP works in command prompt, licensing was done correctly.
The user running the task has access to all resources needed for the batchfile.
All Windows security on the PGP directory and the directory with the batchfile and source/destination files have been verified and are explicitely set to Full Control for the user running the batchfile.

Does anybody have an idea how we can resolve this ?

Thank you !

Laurens.

Operating Systems:

Comments 6 CommentsJump to latest comment

Tom Mc's picture

Please note that the 9.9 Command Line Release Notes indicates that the only supported Windows are:

Windows Vista (32- and 64-bit) SP1, Windows Server 2003 SP2, Windows XP (32- and 64-bit) SP3,
Windows 2000 SP4

When you consider your issue resolved, please click Mark As Solution on the most helpful response.

Search the Knowledge Base &

ldmeyere's picture

Hi Tom,

thanks for the tip.

I installed a version 10 of the PGP Command Line, but unfortunately the problem persists...

dfinkelstein's picture

For your task scheduler job, you could try capturing the output of running

pgp --version --verbose

and look at the "File Information" section.  I suspect there is some issue getting the license information from PGPprefs.xml (either a path or permissions issue, or perhaps the HOME_DIR is not being properly set).

 

--------

David Finkelstein

Symantec R&D

ldmeyere's picture

Hi David,

thanks for the tip.

The File Information section looks correct, or at least shows the same information as when I run the command myself in a command prompt.

BUT : License information shows State: Not licensed

Now, I thought the issue was maybe related to the fact that I was using a domain account to run the task. So I created a local user on the system, logged in as that local user, re-licensed the software as this user.
Unfortunately this shows the same : when I run the version info myself in command prompt it shows as licensed, when I run it in a scheduled task, again state : not licensed...

 

dfinkelstein's picture

The license information is stored in the PGPprefs.xml file that is in the home directory.  The only thing I can think of is that the scheduled task has some permission or other issue that prevents it from properly reading this file.

There are other things that can cause these older versions of PGP Command Line to think they isn't properly licensed (running in virtual environments, crashes of the PGPServ process) but this feels more like a permissions issue.

Have you tried having the scheduled task run "--license-authorize"?

 

--------

David Finkelstein

Symantec R&D

SOLUTION
ldmeyere's picture

Hi David,

so the issue seems to be related to UAC and that sort of Win7 stuff.

What I did was remove the PGPprefs.xml from the PGP Homedir, and try a new licensing. This also didn't work (PGPprefs.xml didn't reappear).

I then did a search for PGPprefs.xml on the C:-drive, which showed me some PGPprefs.xml files in the C:\Users directory structure, in subfolders named VirtualStore. It appears that the system stores files there that it can't store due to missing administrator rights (even though I had already put explicit admin rights for the user on the system).

Next I relicensed the product using a command prompt where I explicitely took Administrator rights (right-click, run as Administrator) > PGPprefs.xml appears in the PGP Homedir.

Lastly, we needed to add 'run with Highest Priviliges' in the properties of the Scheuled task.

I hope this is clear for you?

Anyway, thanks for your assitance in this, and I hope our thread can help some other users with similar issues.

 

Kind regards,

Laurens.