Virsa Access Enforcer Upgrading from 5.1 to 5.2

Question

Hi,
we are upgrading Virsa Access Enforcer from 5.1 to 5.2 GRC acording to the Access Control 52 Product Migration Guide.
All required steps were finished successfully.
After this not a single request in AE can be displayed (Error:Request Approval Screen is not displayed because Request Status has changed),
One example of the error from the AE log:
2007-11-08 10:24:32,160 [SAPEngine_Application_Thread[impl:3]_12] ERROR SQL Exception in insert : [NWMss][SQLServer JDBC Driver][SQLServer]Violation of PRIMARY KEY constraint 'PK__VIRSA_AE_WF_STGF__149DFBA3'. Cannot insert duplicate key in object 'dbo.VIRSA_AE_WF_STGFLD'. ==> VIRSA_AE_WF_STGFLD : {FLD_NAME=Request Role, WFTYPE=AE, FLD_DESCRIPTION=Request Role}
neither the audit trail can be displayed (Erro:No audit trail found for given range or invalid range specified).
In AE52 there are four new tables where has new column REQPATHID added:
VIRSA_AE_RQD_WPCLD
VIRSA_AE_RQD_WPFWD
VIRSA_AE_RQD_WPHST
VIRSA_AE_RQD_WPTRN
Entries to this tables were copied during upgrade from tables:
VIRSA_AE_RQD_WFCLD
VIRSA_AE_RQD_WFFWD
VIRSA_AE_RQD_WFHST
VIRSA_AE_RQD_WFTRN,
but REQPATHID entries was not properly created.
Btw. when did AE52 installation from scratch, not upgrade, on PROD system, i was copying table entries manualy and also had to insert REQPATHID values manually in above mentioned tables.
What I am expecting, when upgrading, this should be done by the system automatically.
Has anyone similar experience with upgrading and how you handle with this.
Thank you.
Regards,
Robert Bilicic

Answer 1

Hi Christof,
The VB codes used in the excel sheets are only excel dependent. I don't think Microsoft has any backward compatability issue with 2003 to 2007. Similarly the VB commands from 5.1 is maintained in 7 so you should not face any major issues there too.
Badrish