Ramblings of a Dynamics GP Consultant
I restarted the virtual machine running the Microsoft Dynamics GP 2013 Web Client and tried to login but got the beow error message;
An unexpected error has occurred. Press the Sign-in button to reconnect to the application. Correlation ID: 99259225-b352-b163-b7c1a166e06cOver the last few posts, I’ve covered the installation of the Web Client Runtime, added the IIS role, created a self-signed certificate, installed the Web Client, ran the Configuration Wizard, and installed the GP Resource Web Cache. Now it is time to run the Web Client for the first time to ensure required components are installed on a client; I’m installing a new demo machine so I know one component won’t be installed.
Navigate to the address if the site hosting the Web Client. In the case when you have a self-signed security certificate (which I would only advise for demo or test systems) you will be presented with a warning that the site may not be safe; this is the one time I will recommend to someone that they go against the browser’s advice and click Continue to this website (like my credit card company, MBNA, who have a site with an invalid certificate, going on for six years now, and have the security team advise people to accept the invalid certificate and proceed);
With the Microsoft Dynamics GP Web Client installed and configured the Web Client is now available for use. However, there is one final additional product which can be installed from the Microsoft Dynamics GP 2013 setup utility and that is the GP Web Resource Cache which improves performance by enabling web client caching.
On a multi-machine deployment the GP Web Resource Cache should be installed on each Session Host machine.
Launch the Microsoft Dynamics GP 2013 setup utility and under Additional products select GP Web Resource Cache;
In the last post, I showed how to install the Microsoft Dynamics GP Web Client; the next step is to run the Microsoft Dynamics GP Web Client Configuration Wizard from the Windows Start menu;
In this series of posts, I’m taking a look at the steps needed to install the Microsoft Dynamics GP 2013 Web Client. In the previous posts I took a look at installing the Web Client Runtime, adding the IIS Role and a self-signed certificate created. With those steps completed, we can now install the Web Client itself.
This is done from the Microsoft Dynamics GP 2013 setup utility by selecting Web Client under the Additional Products section;
Earlier in this series of posts, I took a look at installing the Web Client Runtime and adding the IIS server role. In this post I’ll take a look at installing a self-signed certificate (self-signed is really only a valid option for a demo or test system; on a live system you should really use a real certificate.
To create a self-signed one, open Internet Information Services (IIS) Manager and click on Server Certificates;
In this series of posts, I’m taking a look at installing the Microsoft Dynamics GP 2013 Web Client as a single machine deployment. To be able to install the Web Client, we need to have ISS installed. The server I am installing this on is a Windows Server 2012 so this is done via the Server Manager.
To add the ISS Role, click on Add Roles and Features;
I’ve been working my way through a number of different products which ship alongside Microsoft Dynamics GP 2013, such as Business Analyzer and Integration Manager, and thought I’d also cover one of the additional products which is brand new: the Web Client.
In this series of posts, I’m going to take a look at a Single Machine deployment (I will look at a Multi-Machine deployment another time). The first step in the deployment of the Web Client is to install the Web Client Runtime on a machine which already has Microsoft Dynamics GP 2013 desktop client installed.
This can be done either via Programs and Features in the Control Panel or, as I am doing in this example, via the Microsoft Dynamics GP 2013 setup utility. In the setup utility, select Microsoft Dynamics GP;
In the last post, I took a look at installing the Web Services Runtime; in this one I’ll step through the initial configuration of the web services.
This is done using the GP Web Services Configuration Wizard (). Once launched click Next on the Welcome screen;
After what felt like a really long wait, but in reality was to the announced timeline, 19th December 2012 saw Microsoft announce the general availability of Microsoft Dynamics GP 2013 on the Inside Microsoft Dynamics GP blog.
As Errol Schoenfish, Director Product Management at Microsoft, said in the announcement, this version of Microsoft Dynamics GP allows customers to access it either via the traditional desktop client or, at no extra license cost, through an innovative new Web Client presented via Silverlight in Microsoft Internet Explorer. I think the web client is a really good addition to GP with the interface looking very clean and modern and means whether the user is in the office, at home or on the road, they can access information when they need it and in a web client which has the same structure as the familiar desktop client.
In addition to the Web Client, Microsoft Dynamics GP 2013 has seen the addition of more than 120 new features and capability enhancements to the already rich and comprehensive business management functionality; a sample of the new features can be seen in the Microsoft announced Feature of the Day.
