Skip to main content

Install or Configure MicrOpay Client Service

Setup and configure MCS when integrating with a third-party application or when moving MicrOpay to a new server

Updated over 2 weeks ago

If you are running a third-party application using the Web API Interface, you must also install MicrOpay Client Service (MCS).

You can download the latest version of MCS from the Access MicrOpay Product Downloads page. Once you have downloaded the file to the MicrOpay server:

  1. Right-click on the zip file and select Properties.

  2. Tick Unblock under Security.

  3. Unzip the file to the desktop.

  4. Double-click on the .mis file to install. (As it is an .msi file, ‘Run as Admin’ is not required)

  5. Follow the prompts to install.

  6. Once installed, open SQL Management Studio and define/create an account to use with the service. The account needs ‘db_owner’ to both the payroll and common databases. You can use SQL accounts over AD at this stage.

  7. Use the Start/Windows button and find/open Micropay Client Configuration (default: C:\Program Files (x86)\Micropay Client Service\Config).

  8. Click Stop Service, it automatically starts as part of the install.

  9. Select Add on the right-hand side and fill in the appropriate details:

    1. Left-hand is all based on the client-server configuration

      • Database Type: Meridian

      • Database Desc.: Payroll DB Name

      • ServerName x 2: Windows/SQL Server/Instance Name

      • Database Name: Payroll Database Name

      • Common DB Name: Common Database Name

      • Security x 2: Define security options used to connect to the server

    2. Click Test DB to confirm connectivity (there will be two pop-up messages)

    3. Right-hand selections are based on the connectivity back to the Web API

    4. Select Save.

      • image.png
  10. Select Start Service.

  11. After a while, check the logs via the Show Logs button.

    1. IT can access the new Event Log by going to Event Viewer, Applications and Services Logs, MicropayService.

    2. If there are any errors, raise a case via the Customer Portal.

Did this answer your question?