This article aims to help with the installation and updating of Batch Posting Service Toolkit to the latest builds.

For the latest versions of Microsoft Dynamics GP, only supported releases (build 13 or later) can be registered, but it is recommended to be on the latest build (build 15).

Download the latest Batch Posting Service Toolkit build for your version of Microsoft Dynamics GP from here.

Updating all workstations to a new build can be a lot of work when there are many separate machines. This article explains the options available to assist you with the process.

You will need to install the update to all workstations in your system with the product already installed as you cannot mix builds of Batch Posting Service Toolkit. Once an update is installed on one workstation in the system, the other workstations will display a version warning on login and the product will be disabled until it is updated as well.

As there will likely be server components (tables, views, stored procedures, etc.) changes when installing the update, it is highly recommended to ensure all users are logged out until the update is completed. It is a requirement that no users can be running Dynamics GP (Dynamcis.exe) on the workstation or server currently being installed as the installer will display a message and stop.

After updating the code, you will be required to log in on any updated machine ONCE per system as an administrator user (‘sa’ or equivalent) to complete the updates to the server components in the system (usually DYNAMICS) database. Once the server components have been updated, any other machines running an older build of Batch Posting Service Toolkit will display a warning on login that they must also be updated.

When upgrading “in place” for a NEW version of Microsoft Dynamics GP, it is recommended to uninstall the workstation (not server) from inside Microsoft Dynamics GP and then from the control panel. Then reinstall the latest code downloaded for the appropriate version of Microsoft Dynamics GP. This includes installing a service pack, hot fix, or year end update that changes the GP version number. See Uninstall Information article below for more information.

When updating to a new build of Batch Posting Service Toolkit for the SAME version of Microsoft Dynamics GP, there is no requirement to uninstall an existing installation. Batch Positing Service Toolkit can be installed over the top of an existing build. Just select the option on the installer to update/reinstall an existing instance. Then click Next, Next, I Accept, Next, (Select Instance, Next), Next, Next, and Finish.

If you want to automate the installation process, you can use the command line options to perform a silent install for the default instance:

PostingServices_18.07.0015.exe /s INSTALL=TRUE TARGETDIR="C:\Program Files (x86)\Microsoft Dynamics\GP\"

Note: You can add an additional logging option if desired, add /l=<Path to Log File> to the end of the command line above.

To specify an instance such as GP 2018 R2, add DYNINSTDESC=”R2″. Check the Control Panel >> Programs and Features for the instance names. For example, using an instance of R2 with BPST Build 14 (last build for GP 18.0):

PostingServices_18.00.0014.exe /s INSTALL=TRUE TARGETDIR="C:\Program Files (x86)\Microsoft Dynamics\GP2018\" DYNINSTDESC="R2"

From build 11 onwards, if you want to automate the uninstallation process, you can use the command line options to perform a silent uninstall for the default instance (once the product is removed from the Dynamics.set launch file using the uninstall inside GP or manually):

PostingServices_18.07.0015.exe /s UNINSTALL=TRUE TARGETDIR="C:\Program Files (x86)\Microsoft Dynamics\GP\"

Note: You can add an additional logging option if desired, add /l=<Path to Log File> to the end of the command line above.

To specify an instance such as GP 2018 R2, add DYNINSTDESC=”R2″. Check the Control Panel >> Programs and Features for the instance names. For example, using an instance of R2 with BPST Build 14 (last build for GP 18.0):

PostingServices_18.00.0014.exe /s UNINSTALL=TRUE TARGETDIR="C:\Program Files (x86)\Microsoft Dynamics\GP2018\" DYNINSTDESC="R2"

While a full installation is the preferred approach, it is also possible to copy the updated files from one installation to the other workstations in a system.

Note: Using the method of copying files will not replace the installer files and so will not fix the Security Vulnerability discovered. Only running the latest installer files will replace the installer files.

The files that need to be copied are:

• Application.PostingServices.dll
• Application.PostingServices.xml
• Application.PostingServices.Metadata.dll (GP 2015 or later)
• Application.PostingServices.Metadata.xml (GP 2015 or later)
• PostServ.dic
• PostServ.pdf
• PostServ.txt
• PostServ_License.doc
• QlmLicenseLib.dll
• Addins\WinthropDC.BatchPostingServiceToolkit.dll

For a method of automating the copying of the above files, see my articles on the Developing for Dynamics GP blog:

• Automating Distribution of Customizations Part 1
• Automating Distribution of Customizations Part 2

Note: You will need to login once as a user with sysadmin SQL privileges (such as ‘sa’) to complete the table updates for the new build.

If you have already updated and still can’t get keys, then check with your partner or directly with Winthrop if your subscription is current.

For more details on the changes to the registration system see: Solution to Registration issues on Winthrop Development Consultants products. To see what the current release details are, check the portal: http://WinthropDC.com/BPST.

Terminal Server

When installing on a Terminal Server, it is recommended that the server is placed into Install Mode (change user /install) before installation and restored to Execute Mode afterwards (change user /execute).

These articles discuss install mode and the change user command and what it actually does:

• Microsoft Learn – Change User command
• How to Correctly Install Applications on a Remote Desktop Server

DPM.exe or DPS.exe is Running Issue

Please note that no processes with the following executable filenames can be running during the install: Dynamics.exe, DPM.exe and DPS.exe. See the articles below for more information:

• Installer Error: Microsoft Dynamics GP Process Monitor (DPM.exe)
• Installer Error: Microsoft Dynamics GP Process Server (DPS.exe)

Getting SBA Working

Getting Service Based Architecture (SBA) working so you can use Batch Posting Service Toolkit via web service calls is a little complex. The following article has information and steps to help guide you through the process:

• #BPST Getting Service Based Architecture (SBA) working

Uninstalling Information

the following article covers how to uninstall Winthrop Products and also how to remove previous versions showing in Programs and Features in the Control Panel.

• Uninstalling Winthrop Products and Removing previous versions from Programs and Features

Hope you find this information useful.

David

26-Jul-2018: Add direct link to downloads.
27-Aug-2018: Added more detail for install process.
11-Sep-2018: Added more detail about updating all workstations and logging users out.
12-Sep-2018: Added more information including link to Solution to Registration Issues article.
14-Mar-2019: Updated with command line logging option.
11-Aug-2020: Updated with uninstall feature added for build 11.
13-Aug-2022: Updated after release of Build 12.
02-Feb-2022: Added note that copying files will not fix Security Vulnerability discovered.
02-Mar-2023: Added example command lines including the instance description.
22-Aug-2022: Updated after release of Build 13.1.
14-Sep-2023: Added article with DPM.exe issue.
22-Dec-2023: Added more information as to why Install Mode is recommended on Terminal Server.
10-Jan-2024: Added information on installing when upgrading Microsoft Dynamics GP.
09-Apr-2024: Updated after release of Build 14.1 and added link to Getting SBA working article.
15-Apr-2025: Updated for clarity about when users can be logged in and updating server components.
20-Jun-2025: Added article with DPS.exe issue.
23-Jun-2025: Updated after the release of Build 15.1.

This article was originally posted on http://www.winthropdc.com/blog.