&#60;p&#62;Seeking to update the hopex.core and hopex.dpx components the database went into a recovery situation.&#60;br&#62;I didn't understand the reasons and the evidence is in the associated images.&#60;br&#62;We are perplexed by what has happened. What procedure should I follow.&#60;br&#62;Regards&#60;/p&#62;
&#60;p&#62; &#60;/p&#62;
&#60;div class="mega-case-d-block mega-case-d-block-comment"&#62;
&#60;h3&#62;Case Comments&#60;/h3&#62;
&#60;/div&#62;
&#60;div class="mega-case-d-block mega-case-d-comment"&#62;
&#60;div class="mega-case-d-comment mega-case-d-item"&#62;
&#60;div class="mega-case-d-info-wrapper"&#62;
&#60;div class="mega-case-d-title"&#62;Author&#60;/div&#62;
&#60;div class="mega-case-d-value"&#62;Joseph CAMARA&#60;/div&#62;
&#60;/div&#62;
&#60;div class="mega-case-d-info-wrapper"&#62;
&#60;div class="mega-case-d-title"&#62;Date&#60;/div&#62;
&#60;div class="mega-case-d-value"&#62;2022/02/15 13:32:54 UTC&#60;/div&#62;
&#60;/div&#62;
&#60;div class="mega-case-d-info-wrapper"&#62;
&#60;div class="mega-case-d-title"&#62;Description&#60;/div&#62;
&#60;div class="mega-case-d-value mega-case-d-value-desc"&#62;From: JS Jimenez &#38;lt;jsjimenez@evolvebr.com&#38;gt;&#60;br&#62;Sent: Monday, February 14, 2022 10:22 PM&#60;br&#62;To: CAMARA Joseph &#38;lt;jcamara@mega.com&#38;gt;&#60;br&#62;Subject: RES: Case 00114564: Database went to recovery in the upgrade process - Additional information required [ ref:_00D20Mcmj._5002p2f9m3T:ref ]&#60;br&#62;Hi&#60;br&#62;&#60;br&#62;Please , closed this case.&#60;br&#62;&#60;br&#62;Regards&#60;/div&#62;
&#60;/div&#62;
&#60;/div&#62;
&#60;/div&#62;
&#60;div class="mega-case-d-block mega-case-d-comment"&#62;
&#60;div class="mega-case-d-comment mega-case-d-item"&#62;
&#60;div class="mega-case-d-info-wrapper"&#62;
&#60;div class="mega-case-d-title"&#62;Author&#60;/div&#62;
&#60;div class="mega-case-d-value"&#62;Joseph CAMARA&#60;/div&#62;
&#60;/div&#62;
&#60;div class="mega-case-d-info-wrapper"&#62;
&#60;div class="mega-case-d-title"&#62;Date&#60;/div&#62;
&#60;div class="mega-case-d-value"&#62;2022/02/02 17:35:34 UTC&#60;/div&#62;
&#60;/div&#62;
&#60;div class="mega-case-d-info-wrapper"&#62;
&#60;div class="mega-case-d-title"&#62;Description&#60;/div&#62;
&#60;div class="mega-case-d-value mega-case-d-value-desc"&#62;Hello,&#60;br&#62;From what I could gather from the lead developer, using the “Demo Starter” module and opting to upgrade other components (which can force the upgrade to the demo module), that component can/will start the process of overwriting/upgrading the “demo module”. This can take a fair amount of time (2 hours or more). Since you stopped the process, it put the environment in the “Recovery” state. There’s no way of reverting the state besides restoring the Sql databases and environment folder from a backup (assuming you had made one before you upgraded the modules). If you did not backup, then the environment is no longer accessible. This only occurs with the demo starter and Standard Starter modules since they are replacement environments at their core.&#60;br&#62;If you did not perform a backup of the original Databases/environment folder before attempting to upgrade, then I’d recommend you follow our Administration documentation on how to create a new environment:&#60;br&#62;&#60;br&#62;Or, you could remove the current “Hopex Database backup- Demo Starter Module”, stop the Hopex Core, delete the reference to the “broken” Environment through Administration, restart the core, re-add the “Hopex Database backup- Demo Starter Module” so Hopex could rebuild the latest Demo environment. Keep in mind the Latest Demo environment may not have been brought up to the latest core module version and may require an “Environment Automatic Update” once the module is done creating the new environment.&#60;br&#62;Please let me know if this reply provides you with the information necessary to proceed with resolving the “In Recovery” issue.&#60;br&#62;Kind Regards,&#60;br&#62;Joseph CAMARA&#60;/div&#62;
&#60;/div&#62;
&#60;/div&#62;
&#60;/div&#62;
&#60;div class="mega-case-d-block mega-case-d-comment"&#62;
&#60;div class="mega-case-d-comment mega-case-d-item"&#62;
&#60;div class="mega-case-d-info-wrapper"&#62;
&#60;div class="mega-case-d-title"&#62;Author&#60;/div&#62;
&#60;div class="mega-case-d-value"&#62;Joseph CAMARA&#60;/div&#62;
&#60;/div&#62;
&#60;div class="mega-case-d-info-wrapper"&#62;
&#60;div class="mega-case-d-title"&#62;Date&#60;/div&#62;
&#60;div class="mega-case-d-value"&#62;2022/01/25 01:19:47 UTC&#60;/div&#62;
&#60;/div&#62;
&#60;div class="mega-case-d-info-wrapper"&#62;
&#60;div class="mega-case-d-title"&#62;Description&#60;/div&#62;
&#60;div class="mega-case-d-value mega-case-d-value-desc"&#62;From: JS Jimenez &#38;lt;jsjimenez@evolvebr.com&#38;gt;&#60;br&#62;Sent: Saturday, January 22, 2022 9:12 AM&#60;br&#62;To: CAMARA Joseph &#38;lt;jcamara@mega.com&#38;gt;&#60;br&#62;Subject: RES: Case 00114564: Database went to recovery in the upgrade process - Additional information required [ ref:_00D20Mcmj._5002p2f9m3T:ref ]&#60;br&#62;Hi JOSEPH, thanks for your help, below you have your solicitation:&#60;br&#62;&#60;br&#62;. This is my company's work environment, where we make presentations and have several POC repositories used for HOPEX sales.&#60;br&#62;. We were facing some errors in the generation of Assessment and exposure of reports that work in Hopex Customizer and do not work in HOPEX ITBM, that's why the update.&#60;br&#62;. We verified the existence of HOPEX Core Back-End V5.0 CP1 (15.1.1.6050) replacing (15.1.0+6027).&#60;br&#62;. Likewise the HOPEX Questionnaire Builder 15.1.1.6050 replacing 15.1.0+6027. All this information is present in HOPEX Application Server - Console , Modules List option.&#60;br&#62;. When performing the update procedure, we received the information that the activity was running in back-ground, but we did not have the evolution information.&#60;br&#62;. After 2 hours, we performed, stopped the HOPEX Core Back-End, and tried to perform the automatic update via the HOPEX Administration Client.&#60;br&#62;. We only noticed what happened because none of the client, Administrator, Supervisor, License, etc applications did not open.&#60;br&#62;. Analyzing the Logs we arrived at SQL BD and saw that it was in recovery.&#60;br&#62;. I hope I explained.&#60;br&#62;&#60;br&#62;If possible you can send the right process do make this kind of update?&#60;br&#62;&#60;br&#62;Thanks in advanced.&#60;br&#62;JSJimenez&#60;/div&#62;
&#60;/div&#62;
&#60;/div&#62;
&#60;/div&#62;