ActionRegenerator

(imported topic written by SystemAdmin)

Hi, I have been trying to get the ActionRegenerator to work.

I have download the latest version of the API, ActionGenerator, server & client, installed the API and put the actionregenerator on the server, which is running Windows 2003 Server.

I have created a actionregenerator BigFix account and I have connected to the console sucessfully.

I have configured the actionregenerator.config file as follows

######################################

  1. Action Regenerator Config File

######################################

  1. You need to change these config options:

databasedsn=bes_EnterpriseServer;

username=ActionRegenerator;

password=*******;

signingkeysfolder=D:\Program Files\BigFix Enterprise\ActionRegenerator;

  1. You probably don’t want to change these (although you can if you want)

preactiontitle=AUTOGENERATED: ;

sitename=BigFix AntiPest;

fixletid=4;

actionid=2;

targetrelevance=true;

daystillexpire=7;

temporaldistribution=60;

skipverification=1;

The output I get from the command line is as follows

ACTIONLOG: Tue Mar 11 16:42:34 2008: Running Script…

ACTIONLOG: Tue Mar 11 16:42:34 2008: WARNING! Could not find the BES Server inst

alled version key. The BES Server may not be installed correctly or at all.

ACTIONLOG: Tue Mar 11 16:42:37 2008: Action 0 found with sha1: 08fea08d3a62adb20

c0e12c46f516e26c06db954.

ACTIONLOG: Tue Mar 11 16:42:37 2008: LastRunSHA1 doesn’t exist (probably the fir

st time the script has been run). Propagating action 0 of Fixlet 4 of site "BigF

ix AntiPest"…

ACTIONLOG: Tue Mar 11 16:42:37 2008: ERROR: Signing keys are not valid. Error me

ssage is: These signing keys are not valid. They may be inconsistent with the da

tabase you

are connecting to, may be for a different operator, or may have been revoked.

Please verify that you have selected valid key and license files and try again.

Signing keys are not valid. Error message is: These signing keys are not valid.

They may be inconsistent with the database you

are connecting to, may be for a different operator, or may have been revoked.

Please verify that you have selected valid key and license files and try again.

Does anyone know what I’m not doing correctly

Many Thanks

(imported comment written by SystemAdmin)

I played around with my config file and created new user accounts. I get a different error message if I mess up the database location, username or password, or set the signingkeysfolder to an invalid path. I get the same error message if I set the signingkeysfolder to a path that contains some other users key files or if I use BES Admin to remove the user.

So, I believe that one of two things is happening:

  1. You removed the ActionRegenerator user

  2. The signingkeysfolder path contains some other users keys

If you can log into the console as the ActionRegenerator user, can you propagate actions? Are you sure that the signing keys used used for the BES Console are in the same path as in the actionregenerator script?