Since its introduction, Workflow for Microsoft Dynamics GP has proven to be very popular and is a module I have spent a lot of time with. Workflow integrates with the Web Services for Microsoft Dynamics GP for the approval (or rejection) via email; there is a fair bit of complexity around this area, mainly in accessing the email actions from outside of the domain.
Dan Peltier of Microsoft has a good write up of what is required for DNS settings to allow for external access of approvals.
In the near future, I am going to be doing a small series on configuring web services to use https for approval/rejection, but will be written on the assumption you have working DNS records ready (DNS is very much not my specialist subject). Dan’s post is a good starting point if you need assistance in this area.
While installing the scale-out deployment of the Microsoft Dynamics GP 2013 Web Client, I encountered an error which took me a lot longer than I liked to resolve:
There was no endpoint listening at https://sc1.domain.azurecurve.co.uk:48650/SessioNCentralService that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---? Syste.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not propoerly respond after a period of time, or established connection failed because connected host has failed to respond: 22.214.171.1246:48650
Continue reading “Troubleshooting The Microsoft Dynamics GP 2013 SP2 Web Client: No Endpoint Listening”
The release of Management Reporter brought several advantages over FRx; x64 compatibility, replacement of the Access database with SQL Server and a modern client among them. However, one of the downsides is that Management Reporter requires a domain to be available for both the installation and running.
Where FRx could be run on any PC or laptop regardless of the operating system, Management Reporter can only be run on a server OS. This means that the Business Development Managers, and I, need either a laptop with Windows Server 2008, or better the R2 version, installed or we need a VM with the same. To make everyday life easier I opted for the latter as I can install it once and then copy the VM between machines.
I am a Microsoft Dynamics GP consultant by training, certification and experience but I don’t have a huge amount of experience with Active Directory. I am the most knowledgeable here about installing GP and Management Reporter though, so it falls to me to do the setup of the demo systems and I figured I might as well do the full monty rather than getting someone else to install the operating system and then passing it back to me.
To this end I needed to learn how to install and configure Active Directory Domain Services (ADDS) and I thought it best to document here for anyone else interested and also for my own future reference. Continue reading “How To Create A Domain Controller”
[One of the annoyances when migrating a client’s installation of Microsoft Dynamics GP to a new server is that, unless the new server has the same name as the old one, the password of every user needs to be reset as the server name is encrypted in with the password.
The is another alternative though and that is to create a DNS CNAME Alias and use this as the server name in the SQL Server ODBC instead of the servers actual name. When GP is migrated to a new box you only need to amend the DNS CNAME Alias and users can continue logging in with the same password. Continue reading “Transferring GP To A New Server Without Resetting All Passwords”