How To Install The GP Web Services – Installation

● Ian Grieve ●  ● 9 Comments   ● 

This is the second in a series of posts covering the installation and configuration of the Web Services for Microsoft Dynamics GP. The first post covered the prerequisites and, in this post, I’m going to cover the actual installation process.

The Web Services for Microsoft Dynamics GP are installed using the same Microsoft Dynamics GP setup utility.

To start the installation process, click the Web Services Runtime option;

Microsoft Dynamics GP 2010 Setup Utility

As with virtually any application, you need to accept the license agreement;

Web Services for Microsoft Dynamics GP Setup Utility - License Agreement

Supply the SQL Serer connection information. In this case I’m using the AZC-SQL1 server and supplied the sa username and password. I could have used Windows Trusted Authentication as I’m logged in as a Domain Administrator who is also a SQL Administrator but I prefer to use the sa account;

Web Services for Microsoft Dynamics GP Setup Utility - SQL Connection Information

The install location will be defaulted in but can be changed if you want to install somewhere other than the default installation folder;

Web Services for Microsoft Dynamics GP Setup Utility - Install Location

Next, select the Dynamics Security Data Store location. The default is to use SQL Server, and is the option I’ve selected, but you could also use ADAM or Active Directory;

Web Services for Microsoft Dynamics GP Setup Utility - Dynamics Security Data Store

Having selected SQL Server, the Server (which must be running at least Windows Server 2008) and Database names need to be supplied. If the supplied database doesn’t exist it will be created;

Web Services for Microsoft Dynamics GP Setup Utility - SQL Server Connection Store

The setup utility will check if the specified database doesn’t exist, then a warning will be displayed informing the user of this and that a data store will be created by the install process;

SQL Security Store: No security store currently exists at the specified location. One will be created during the installation.

The Application User name needs to be supplied including DOMAIN, User Name and Password. If the Web Services are being installed on the SQL Server then a local user account can be specified, otherwise a Domain User Account is needed. In this case I am using a Domain User Account on DOMAIN.azurecurve.co.uk which I have specially created for use called GPWebServices;

Web Services for Microsoft Dynamics GP Setup Utility - Application User Account

Confirm that the install should be run;

Web Services for Microsoft Dynamics GP Setup Utility - Install Program

Once everything has been installed, the setup utility will confirm this and ask if you want to run the Configuration Wizard;

Web Services for Microsoft Dynamics GP Setup Utility - Installation Complete

In the next post, I’ll give a run through of the Configuration Wizard, so stay tuned.

What should we write about next?

Please leave this field empty.

Your Name (required) -
Your Email (required) -
● Categories: Dynamics, GP, Microsoft, Web Services ● Tags: , , , , , , , ,  ● Permalink ● Shortlink ●

9 Responses

  1. Yasser Mahmoud 16th March 2013 / 03:45

    Hi Ian,

    i have a problem when install Web Service for GP 2010 SP3 running that window appear has message ‘cannot use the special principal ‘dbo” and installation Rollback. What this message mean and how can i solve this issue. My environment is VMware have Windows Server 2008 R2, SQL Server 2012 SP1, and GP 2010 sp3.

    Thanks

Leave a Reply

Your email address will not be published. Required fields are marked *