Windows 8 and the Microsoft Dynamics GP Web Client Series - Part 4

Windows 8 and the Microsoft Dynamics GP Web Client Series
Part 4

This series narrate my personal experiences of installing Microsoft Dynamics GP 2013 Beta and the Web Client in an unsupported environment. The following installation steps are for testing purposes only and were done on a test box. If you are to test, please make sure your machine is not a production box.

"While it's not supported, it doesn't mean it won't work. It only means we haven't tested it"...
                                                                                                      Microsoft Dynamics GP Support

Where were we?

In the previous installment I wrote about a number of errors that may happen and think I did a decent job at pointing out the most common ones - services down, you missed the web client runtime install, and so forth.

However, in my quest to get this thing working on Windows 8, I also found out the heartaches that can happen when your certificates go bad.

In my environment, I have self-signed certificate which was created specifically for SSL encryption on each of the ports used for listening purposes by the different web client component services - see part 2b of this series for more information on the different components.

The certificate has the following Thumbprint.

Certificate Thumbprint

If the installation process went well, the Certificate Hash assigned to each port used by Session Service (port 48650), Session Central Service (port 48651), and Runtime Service (port 48652) should match the thumbprint value of the certificate in IIS.

To verify the Certificate Hash value on each port, you can execute the network shell command, netsh, from the DOS command prompt:

netsh http show sslcert

Certificate hash on each listening port must match that of the certificate in IIS
If for some reason the values do not match, there are two ways (that I know of) to fix this:

1. You can try to uninstall the Web Client, which in turn ~should~ remove the SSL certificate bindings for each of the ports listed above. If the bindings are cleared, you can then proceed to remove and recreate the certificate in IIS, then reinstall the Web Client, selecting the correct certificate.

2. You can manually remove the SSL certificate bindings with the following command line:

netsh http delete sslcert ipport=0.0.0.0:48650
netsh http delete sslcert ipport=0.0.0.0:48651
netsh http delete sslcert ipport=0.0.0.0:48652

As a matter of fact, it is also wise to delete the URL reservation associated with the certificate binding as well,

netsh http delete urlacl url=https://+:48650/SessionCentralService/
netsh http delete urlacl url=https://+:48651/SessionService/
netsh http delete urlacl url=https://+:48652/RuntimeService/
netsh http delete urlacl url=https://+:48652/

Following this process, you can then uninstall the Web Client, recreate the certificate in IIS, and reinstall the Web Client, this time selecting the certificate.

For more information on the network shell command take a look at:

MSDN: Netsh commands for HTTP

Until next post!

MG.-
Mariano Gomez, MVP
IntellPartners, LLC
http://www.IntellPartners.com/

Comments

Post a Comment

Popular posts from this blog

DBMS: 12 Microsoft Dynamics GP: 0 error when updating to Microsoft Dynamics GP 2013 R2

Image
Hello all! It's been quite a while since I've actually written anything of remote interest to anyone who follows my blog, but at the same time, you will be pleased to know that I've been quite busy in the consulting front, with upgrades, server migrations, complex multi-instance postings involving 10's of thousands of transactions, wrapping up some Field Service Automation projects, and the list goes on and on. This time around I want to bring to the forefront, an issue I encountered updating  from Microsoft Dynamics GP 2013 SP2 to Microsoft Dynamics GP 2013 R2 plus the latest service pack. Background My client requested a server migration to a new environment where they wanted to deploy Dynamics GP 2013 R2 web client (plus the latest service pack) and upgrade their relational database management system to Microsoft SQL Server 2014. This is something I'm absolutely comfortable with (for the most part) given also that my client was sitting at Microsoft Dynamics...
Read more

Do I have to use those "Z-" currency IDs in GP?

Image
I know this seems like a trivia question, but recently I have come across a number of clients who have been using Microsoft Dynamics GP for a number of years and have been told by their former partners that they *must* use the predefined currency IDs created after adding the sample company, with no real explanation to support these claims. Case in point, my new client in Saudi Arabia, has been struggling for years to understand why they were told to prefix all currency IDs with the "Z-". So they went ahead and setup "Z-SR" for the Saudi Real. If you are familiar with Microsoft Dynamics GP and the sample company, Fabrikam, you may have noticed by now that after adding the sample company (which is not a requirement by any means), you will get a number of predefined currencies such as Z-US$ (US Dollars), Z-UK (British Pounds), Z-C$ (Canadian Dollars), Z-AUD (Australian Dollars), and so forth, accompanied by a number of exchange rate tables. If you are not familiar wi...
Read more

Microsoft Dynamics GP Scrolling Windows and Line Sequence Numbers

Image
I thought I would write about something meaningless that no one really thinks about. However, I realized that this is a compelling topic since it makes for some interesting discussion around the ability to insert line items withinin most transaction scrolling windows. Let’s take some time to understand where Line Sequence Numbers come from. A Line Sequence Number is auto generated by Dynamics GP and uses a seed value of 16,384 as a basis for the first line. Each subsequent line in the scrolling window is incremented by this number, so line number 2 would have a Line Sequence Number value of 32,768, line number 3 would have Line Sequence Number Value of 49,152, and so on. Since most GP transaction entry scrolling windows allow inserting rows in between line items, the newly inserted Line Sequence Number value is calculated as an average between the previous and the next line item sequences, i.e., if you were to insert an item in between row 1 and row 2 in the scrolling window -- keep in...
Read more