Patcher Troubleshooting

3 Weeks Ago
LauraG
HOW TO'S

Summary

During the installation of a new patch that follows the process described in this article, it is advisable to follow the considerations included below.

Applies to

Bizagi All versions

What you need to do: 

Possible issues you may encounter

 

Yellow exclamation icons

When you open the file GUI.Patcher.exe, the window might look like Figure 1. Notice the yellow exclamation icons next to the items in the Bizagi Applications list. This means that the program needs administration rights to apply the new patch but is running without them. To fix it, close the window and open it again by double clicking the file and selecting the option “Run as administrator.”

Figure 1. First view of the installation wizard after opening “GUI.Patcher.exe” when the wizard is running without needed administration rights.

Programs running while the patcher applier is executing

If one of the selected applications is running when opening the installation wizard, there will appear a message at the bottom of the window informing you that you will need to stop them before installing because the wizard will not close them, and something might go wrong (Figure 4).

Figure 2. Alert message about running applications that will be affected by the installation.

Unspecified path for one or many Bizagi Applications

The list of applications might look something like Figures 3 or 4:

Figure 3. Applications without path. Studio does not have any information associated.

Figure 4. Applications without path. None of the applications has information associated.

This happens when one or more applications are not installed in the default path the wizard looks for when executed. By default, the installation wizard will look for the applications in the path “C:\ProgramFiles\Bizagi\BizagiStudio\”. If the applications are installed somewhere else, the program will assume they are not installed.

If the scenario is like that in Figure 4 (where the patch applies to WebApp, but WebApp was not found on the machine), then you need to verify if the application is installed and edit the text field to indicate the wizard the location of the program.

All paths will be verified before moving on, and an error message will appear if a path is not valid (see Figure 5):

Figure 5. Error message that appears when the paths selected by the user are invalid.

Applications running in different machines

There are scenarios where the applications a patch will upgrade are in different machines (e.g. Studio and MC should always be running in different machines). In this case, it is normal that the wizard will not find one or the other even if the patch applies to them. Have in mind that you will have to go through the installation process in all the machines running the applications to be upgraded.

Additionally, review the information on the version and patch included in the list for each application. The version for the selected application must be the same as that of the patch, otherwise you will not be able to install it. Also, if the application has the information of a later patch installed, it will not install the one you are trying to apply. For example, if you are trying to install the patch number 007 to the WebApp application but it already has patch 010 installed, it will not install patch 007.

Adding a project to the updating process

Figure 6. Window form to add a new project to the upgrading process of the new patch.

In Figure 6 the textboxes for “WebApp Path” and “Scheduler Path” have a red exclamation icon. This happens when you click on the “Add” button without including the information for either one. This means that you need a name for your project and at least the path to one of the applications (the one you want to apply the patch to). For editing the paths, you can click on the “Browse” button for each of them, or you can copy and paste the path directly to the textbox. The paths you assign will be verified before moving on and there will appear an error message if the paths are invalid (as with the paths in the Bizagi Applications tab).

Other things to consider

The patch numbers for the applications are important and worth noticing. A patch number of 000 in an application means that no patches have ever been applied before.

Also, have in mind that patches are collective, this means that later patches will include the information of previous ones. For example, patch 007 will contain the changes made in patches 001-006 along with its own. If you have installed previous patches, the wizard will install those that are missing to upgrade to the latest version (i.e. if you have installed patch 004 before and receive patch 007, the wizard will only install the changes concerning patches 005-007).

Currently, it is not possible to roll-back the installation of a patch (in case you need to, please contact our Support team); however, the wizard will back the projects up before installing the new patch so that the previous versions may be recovered in case something goes wrong. Project backups will be stored in the following path: “AppData\Local\BizagiPatcher.”

Once the backup has been made and the patch installed, the wizard will show you a summary view such as the one on Figure 7. Click “Done” and the window will close.

Figure 7. Summary view.

Considerations

If you encounter any other trouble that is not included in this article, please feel free to contact our Support Team so we can assist you.

Rate this Article:

Details

Last Modified:3 Weeks Ago
Last Modified By: LauraG
Type: HOWTO
Level: Beginner
Article not rated yet.
Article has been viewed 72 times.

Options