GP 2015 Web Client Uninstall – Issue & Resolution

In my earlier post, I discussed about an issue that I came across while installing web client. This one’s while uninstalling the web client.

My VM is added to my work domain and when I installed web client, my VM was connected to my work network. Back at home, in my holidays, I was experimenting with various stuff. Got my VM web client corrupted and decided to uninstall it.

Running the web client uninstall started off properly but threw the following error soon after:

Screen Shot 2015-01-02 at 6.45.37 PM

Screen Shot 2015-01-02 at 6.45.48 PM

You may see the point in time at which the uninstall process stopped: ConfigureUsers.

Tried various things, as usual, but could not fix it. Every time I tried to uninstall, it stopped exactly at ConfigureUsers.

My instinct was telling me that it was something to do with domain network issue. As I was trying this at home, it could probably be something related to that.

I connected to my work VPN and then restarted the uninstall process. This time around, the process went on smoothly and completed.

Screen Shot 2015-01-02 at 6.49.15 PM

Remember. If your machine (or a VM) is affiliated to your work domain when you installed the web client, make sure that your machine (or a VM) is connected to your work domain when you try to uninstall.

This makes a world of difference. You do know what that difference is, by now.


GP 2015 Web Client Installation – Port Conflict Issue & Resolution

I have been doing some R&D with GP2015 (Desktop & Web Client) on my virtual machine for almost a week now. On that note, let me share with you one particular issue, that’s a bit silly, yet possible to be faced by many of you out there.

I had a working instance of GP 2015 Web Client on my VM (that’s connected to my work domain). I uninstalled it due to an SSL conflict with local web site. Uninstall went on smoothly.

I worked on that local web site stuff and decided to install web client back. When I began the installation, following error message happened:

Screen Shot 2015-01-02 at 3.49.01 PM

Screen Shot 2015-01-02 at 3.50.47 PM

I had no idea about this port, as this port number was never used while setting up the web client installation. I am not an expert in networking either. So googled this error and got this link on Microsoft Support KB: How to determine which program uses or blocks specific transmission control protocol ports in Windows.

I used the command netstat -ano to figure out which process is using the port 48665. Below is the list that I got:

Screen Shot 2015-01-02 at 3.50.25 PM

Highlighted on RED box is the one that was using the port 48665. This process was System Process, as found through Task Manager:

Screen Shot 2015-01-02 at 4.15.35 PM

Well, only to that extent could I proceed. My instinct asked me to restart the VM once and see if that clears this port. And it did.

Screen Shot 2015-01-02 at 3.55.00 PM

And my web client installation went on well and completed without any issues.

Reason: After uninstalling my Web Client earlier, I did not restart my machine. I continued with the local web site task and tried to install Web Client again. Previous installation would have held that port (just my assumption) and did not release it till I restarted my VM.

Resolution: If you are going to install Web Client, just make sure that you restart the server.

On my next post, I shall discuss about an issue that I faced while uninstalling my web client and the resolution to the same.


GP Web Client: Rendering Issue – Some Facts

Almost a month back, I had posted my GP web client test drive results on how the client is rendered on Mac based browsers and possible issue with Silverlight plugin. I am probably wrong.

Everything works other than pictures; that’s what I had found. Upon drilling down further, what I realised is that it sounds obvious that it doesn’t work on Mac based browsers. Reason: Native Pictures.

Definition of Native Picture says following:


Consider, for instance, the following snapshot of GP login window on a web client rendered on Mac Safari:


It’s not shown. Initially I thought it was something to do with Silverlight rendering. But not exactly. It’s because, this picture is a Native Picture. And by definition, it’s specific to Windows OS. Look at this picture definition below:


Apparently, by nature, it’s NOT supposed to show up on any OS other than Windows.

It’s not just this picture. Lookup Button icons, Note icons are all Native Picture types. And due to that, they are not going to render on any other OS. And if I am not mistaken, this will remain as it is at least till next major version of GP.

Those who implement GP web client MUST be aware of this.


GP 2013 Web Client – Cross Domain Error

This probably would be a common error faced by many of us across the GP world, while trying to access GP 2013 Web Client.

Upon launching GP web client on my browser, it asked me to enter my domain credentials and once I did that, I was greeted with following error:



Complete error message is as follows:

Severity: Critical
Summary: An error occurred while initializing communication with the server.
Details: [CrossDomainError]
Arguments: https://<machine name>.<domain name>:48652/RuntimeService/5652
Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See

Reason is quite trivial; I had entered the url on my browser as follows:

https://<machine name>/GP

Instead, I should have entered the url on my browser as follows:

https://<machine name>.<domain name>/GP

For instance, if my GP web client server name is GPDEV and my domain name is GPDOMAIN.COM, then I should enter my url as follows:

There could be several other reasons for this CrossDomainError issue, but above solution fixed mine.


GP2013 Web Client – Test Drive #MSDYNGP

It’s been an awkwardly long time since I had written anything on this blog. Now is the time probably to break that jinx.

I have been working on testing GP2013 Web Client on our environment. I have been constantly keeping myself updated with GP Web Client by reading our community blogs and forums, but never had seen it on my own machine till today.

Below is the snapshot of GP2013 Web on my MacBook Pro; on Mac OS X Safari browser.


All you need to do is to install Silverlight for Safari on Mac. If it’s not there, you would be prompted to download and install.

I am now excited to get my customisations work with it. Will post anything that’s interesting and worth to be shared in coming days.


Microsoft Dynamics GP 2013 SP2 – Release Schedule Announced

Over at Microsoft Dynamics GP official blog, Errol sheds light on Microsoft Dynamics GP 2013 SP2 release schedule.

Along with that, he also lists on new features this release would have. Pretty interesting, especially on Web Client front.

I’m excited.


Caps Lock Reminder – For Microsoft Dynamics GP 2013

I had developed a small customisation module which would alert users while logging on to Dynamics GP with CapsLock key on. You can read more about it here: GP Login Form – Caps Lock Reminder Update.

That customisation was developed using Modifier with VBA. But with Dynamics GP 2013, much emphasis has been given to the new Web Client. Which means, all our VBA code logic won’t be supported by web client.

That said, I have now converted my code from VBA to VS Tools (using C#.Net as programming language). Those who are interested can download it FOR FREE from following link:


Instructions to use:

  1. Copy this DLL file and paste it on to GP AddIns folder (can be located inside GP 2013 application folder).
  2. Ask users to log out and log on back.
  3. If you do not need this tool anymore, just remove this DLL from AddIns folder, after all users log out.
  4. This can be used safely in production environment. This tool doesn’t interfere in any of your day-to-day transactional activities. The scope of this is restricted only to GP login form.

Your feedback is always welcome.