Back to list
Sep 09 2016

T61-2016: (Update 2) Recommended hiatus in making Production upgrades from Biological Registration 3.1 or Chemical Registration 3.2.x to Registration 2016 or 2017

Biological Registration

Products Impacted
Biological Registration 3.1
Chemical Registration 3.2 and 3.2 SP1
 
Description:
 
A defect that manifests itself as a “Memory Access Violation Error” has been reported during the upgrade process from Chemical Registration or Biological Registration 3.x to the 2016 or 2017 versions of these applications.
Resolution:

Resolution
 
Original Resolution Published on 11-Aug-2016

 

  • BIOVIA strongly recommends that Registration Customers DO NOT move to “UAT” or “Production” stages of your upgrade of Registration from 3.x to 2016 or 2017 until BIOVIA fully understands this defect and provides further guidance.
  • BIOVIA at this time is reviewing this defect and will provide our next update by 19-Aug-2016.
  • Other efforts to plan and start your upgrade can continue; especially performing your initial 3.x upgrades in “Sandbox” or “Dev” environments and creating or updating
    • Custom Entities
    • Custom rules
    • Custom protocols
    • Creation of search and browse forms
    • Etc…

Update 1 (18-Aug-2016)

 

 

  • BIOVIA has added REG-16988 to this investigation
  • BIOVIA is actively creating a Hotfix to address REG-16876 and REG-16988
  • BIOVIA Continues to recommend that Customers do not move into UAT or Production environments
  • Other efforts to plan and start your upgrade can continue; especially performing your initial 3.x upgrades in “Sandbox” or “Dev” environments and creating or updating
    • Custom Entities
    • Custom rules
    • Custom protocols
    • Creation of search and browse forms
    • Etc…
  • BIOVIA will provide our next update on this issue by 25-Aug-2016

 Update 2 (2-Sep-2016)

 

 

  • BIOVIA is actively creating two Hotfix to address REG-16876 and REG-16988 and expects to release this Hotfix by September 9th.  These Hotfixes will be released as:
    • ​Pipeline Pilot 2016 SP2 HF2
    • Pipeline Pilot 2017 HF2
  • Registration 3.x customers can use the following SQL to determine if they will need to have this Hotfix in place when upgrading from Chemical Registration 3.2.x or Biological Registration 3.1.  If the results of both of these SQL statements return 0 THEN you can safely continue with your upgrade without applying the Hotfixes under development.

 

 

select tran_id, entity_fk, count(tran_id) from ems_audit_lifecycle group by tran_id, entity_fk having count(tran_id) > 1;
select count(*) from ems_entity_attr where attr_type_fk in (select attr_type_pk from ems_attr_type where remote_attr_type_fk is not null and rship_fk is not null);

 

 

  • BIOVIA Continues to recommend that Customers do not move into UAT or Production environments if the results of the above SQL statements indicate that you will need the Hotfix under development.
  • For Customers who will need this Hotfix, other efforts to plan and start your upgrade can continue; especially performing your initial 3.x upgrades in “Sandbox” or “Dev” environments and creating or updating
    • Custom Entities
    • Custom rules
    • Custom protocols
    • Creation of search and browse forms
    • Etc…

If you require more information about this defect please contact BIOVIA Support or members of the BIOVIA Professional Services team who you might be working with.
 
Jira Defect Numbers:  REG-16876 and REG-16988