While applying the patch then getting an error "Patch 1 database_2021_7747 Failed."

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 tested yet hence can not determine the behavior.
So it is recommended to use the OS as per specified in Hardware and software specification guide.

    • Related Articles

    • 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 Retail 6.5 Update 6 Patch 1

      Recommendation(s) It is recommended that patch is applied in Test Environment first and then production environment. Preferable if replication and integration queue is all clear. Apply iVend Patch during business downtime Pre-Requisite(s) Back-up ERP ...

    • 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 ...

    • ISSUES WHEN INTIALIZING MASTER TABLES FROM SAP: "iVend 6.*.*.* add-on failed to update the database"

      Product version 6.5 Update 6 Problem statement Getting Error "iVend 6.*.*.* add-on failed to update the database" when initializing master tables from SAP Reason CXSINTEGRATION DATABASE IS DELETED SAP database, already initialized with iVend database ...

    • Cannot open database 'CXSIntegration' login failed

      Environment: iVend 6.6 Problem Statement: Cannot open database 'CXSIntegration' login failed Symptoms: Environment Specific Resolution/Work Around: It seems wrong SQL password is entered for user "sa". So need to check correct password for SQL login ...