Patch failed to apply 7648
Product version:
iVend 6.6
Problem statement:
Customer is trying to apply Patch 7648, in the HO server, all patches deployed successfully. When replicating to a store and MC starts, the system showing an error message Database 2021_7825 Failed'.
Proposed Solution/Workaround:
We follow the below step:
1.We suggest to restart the SQL services and try again.
2.HO Management Console has been applied successfully for Management console patch.
3.It try to load the Database patch but it again fail.
4.We apply the patch manually.
Related Articles
6.6 iVend Retail - Patch Deployment Process
Query: How to plan iVend 6.6 upgrade and Patch update? Solution: Please follow the attached "iVend 6.6 Patch deployment Process" document. Additional Information: Patch deployment process document is available in Download section of iVend retail. In ...
Microsoft Azure is available in ivend if yes in which patch level or version
Product version: iVend 6.6 Problem statement: Kindly update us about single sign on for Microsoft Azure is available in ivend if yes in which patch level or version ?? Proposed solution/workaround: SSO is not feasible through custom development in ...
Error After Applying Patch
Problem Statement Customer is trying to apply PATCH 7648, in the HO server, all patches deployed successfully. When replicating to a store and MC starts, the system showing an error message 'Patch1 Database 2020 7648 Failed'. Environment iVend ...
iVend Patch not getting updated at POS
Environment: iVend 6.6 Patch 7915 Problem Description: Patches in HO and the POS indicates that it has already been updated but in POS it stays in a cycle asking for an update and does not allow it to be done. Scenario: None Solution: 1) At POS the ...
While applying the patch then getting an error "Patch 1 database_2021_7747 Failed."
Environment: iVend 6.6 Problem Statement: While applying the patch then getting an error "Patch 1 database_2021_7747 Failed." The below is the screenshot for the same: Solution: It was found that customer was using Windows Server 2019, which is not ...