All posts by James Hall

CRM Utilities for Visual Studio updated to VS2019

I have just updated the CRM Utilities for Visual Studio package to work with Visual Studio 2019 as well. The version is now at 3.6.2 and is ready to download from the Marketplace.

Just search for James Hall on the extensions window of Visual Studio or visit the marketplace.

It can also be downloaded directly from here :

Adxstudio 7 solutions do not import into Dynamics 365 V9

Here is a bit of useless information for you!

I setup a trial of a V9 instance of Microsoft Dynamics 365 for some testing, and I found that the Adxstudio 7 solutions would not import.  The installer goes in, but installing the base portals solution fails.

To get round this, I converted the instance to a sandbox, reset it to V8.2, installed the solutions, and I intend to upgrade it to V9, although I will have to wait a week for the scheduled update to work.

So there you have it.  You cannot set up a new V9 instance to run old portal code on.

Solution export error, check SLA’s

Recently I had an issue where all of a sudden, a solution would not export from the development environment, even though it was previously fine, and as far as I knew, it had not changed.  Dynamics would throw a very unhelpful error, with no details of what went wrong.

I tried creating a new solution, and adding the exact same components and that one also failed, so I knew it was not the solution itself, but its contents.

After a bit of trial and error, I discovered that it was the SLA’s that were causing the issue.  Turns out that it was because one of the SLA’s had not been activated.  Never thought it needed to be, but in this case, it was causing an issue.

So, if it ever happens to you, make that one of the first things you check, it might save you some time.

This was a version 8.2 on premise install, but I didn’t have access to the actual server.

DevOps Home Server – Part two – Software

For the purposes of my own home DevOps server, I decided to use the range of Atlassian software.

Source Code Control Atlassian Bitbucket
Project and Issues tracking Atlassian JIRA
Documentation Atlassian Confluence
Build and Deploy server Atlassian Bamboo
Code Analysis SonarQube

The main reasons for this are :

  • I have used these applications in a previous job
  • They all integrate really nicely with each other
  • They are affordable (even though there are free open source equivalents)

Once they are all set up, and connected together, you can quickly change between them when browsing the web interfaces.

In terms of price, each one of these applications (apart from SonarQube which is free) costs $10 for a permanent license for 10 users.  If you wish to get software maintenance, then you can pay that price every year (actually, its half that for extending the maintenance after the initial purchase), but in my case, the initial purchase is going to be fine, costing not much more than a decent takeaway.

The Virtual Machines

Both VM’s are running on my original Intel NUC Server (i7, 16GB RAM), set-up with Microsoft Windows Server 2012.  I decided to create a separate SQL Server machine for a couple of reasons, one to reduce risk of failure (so one VM is not hosting everything), but also in case I ever need a general purpose SQL Server, it can be used for that as well.

SQL Server

I have installed Microsoft SQL Server 2016 on the VM, opened up appropriate ports, firewall rules etc., and that was about it.  It now sits there chugging away nicely.  I have still yet to sort out any form of backup system.  I will probably set up some automated database backups, but I will also aim to have the actual VM backed up as well.

DevOps Server

The DevOps Server is another VM, although I have given it a big more power than the SQL one purely as it will be hosting a number of applications at the same time, and it will need a fair amount of oomph to keep it all running smoothly.

Installing the software

NOTE: this is not a guide on how to install everything, just an overview of the experience.

The first step was to install Java as most of the Atlassian products are built on Java, after which I also installed Visual Studio as I knew that was a requirement for the Bamboo Build and Deploy server.  I then one by one installed and configured the following applications :

  • Atlassian JIRA
  • Atlassian Confluence
  • Atlassian Bitbucket
  • Atlassian Bamboo
  • SonarQube

Each piece of software required me to choose a program location, and a data directory.  Most software also added a Windows Service as well (although some had to be manually installed by running some command scripts).  Each application would start, and allow me to perform the first time configuration.  This involved the usual initial settings, database connection etc.  Most Databases had to be created prior to running the first time config, and also had to adhere to the softwares requirements in terms of collation settings.  Each Database was given its own specific user for the application to use (a standard sql user).

As I was wanting them all to have the same user database, I elected to use Active Directory, although this had to be set up after the initial install.  Most of the applications required the same AD config, and once I had figured it out for the first one, the others were straight forward.

Once everything was up and running, I was able to connect all of the Atlassian applications together so they show up on each applications hamburger menu, and as they are all configured with the same set of AD users, I am able to switch seamlessly between the applications.

External access

Obviously, as this is all just running on my home network, if I ever have to go anywhere, I don’t want to not be able to access it all, so I wanted to expose it to the outside world.  I am not worried about security, or about having my home broadband thrashed by outside users as its only going to be me using it.

To expose them online, all I had to do was configure up some port redirects on my router, so that any traffic hitting it on the relevant applications ports where forwarded to the correct port on the virtual server.  I configured my router to use a dynamic DNS service (Netgear’s own service) so that my home network could be reached on on all of the configured ports.

I then configured an appropriate domain so that the various sub domains would also redirect to the → → → → →

Unfortunately, this means that everything is still reliant on ports, so when accessing one of the sites, I would still need to use something like, but I am not too bothered about that.

Internal DNS

Now, one issue that I discovered with this plan was that each application, when trying to internally communicate with the other applications, because all URL’s (on the server itself) where full domains, and not just IP addresses, they would actually do the round trip to the internet and back.  This was not good as it would of caused delays etc.  What I did to fix this was to go on to my Active Directory VM, and set up DNS so that forward lookup DNS settings meant that any machine on the internal network, using AD, would not need to go outside the network for these URL’s.


In terms of performance, it all seems to work well.  There are times (such as if there is a build job running), that things seem to slow down somewhat, but I would say its no worse than I have seen in a real production environment.  It all works rather well, and it feels like I have my own professional business environment right at home.  The only issue is that the actual server makes a bit of noise. The fan seems to be working pretty hard, but I can just shut the door on my office and forget about it.

In the next blog post, I am going to describe the workflow of using it all.

DevOps home server – part one – the equipment


Ah, DevOps, such a buzz word now.  It seems that everyone wants to bring Operations and Development together, in a harmonious gathering of intellectual minds.  To get in on the action, I wanted to do some hands on development, with a little saucy operation to go with it, and so wanted to experiment with some home server shenanigans.

Why bother, I hear you say, why not just use the existing cloud services I hear you cry.  Well, I really don’t have an explanation, other than to say, why not.  Sometimes, a workplace environment may not be in a position to use the various cloud services, and may have to host everything themselves, so its worth having a bit of experience with such a situation.  So, I bring to you my experience of setting it all up, using Windows Hyper-V.

Firstly, a little bit of background as to what I already had, before I get in to the most recent information with regards to my little home development environment.


The existing Hyper-V server


I have always had the drive to have my own little server at home, primarily to run my own instance of Microsoft Dynamics, simply because for development purposes, it was too expensive to have an online instance for general experimentation.  As a result, quite a while ago, I purchased a small Intel NUC small form factor PC to run Hyper-V on, and host my development environments.  This was an Intel i7 PC, 16GB of RAM, a 512GB SSD, and a 1TB Hard Disk. It was a small machine, took very little power, and since Windows 10 Pro also provided Hyper-V Virtualisation, there was no need for it to run Windows Server.  On this PC, I set up a Virtual Machine to host Active Directory, and then a second Virtual Machine where I was able to install Microsoft SQL Server, and Microsoft Dynamics.  This provided me with a nice little CRM test environment.  Overtime, I hit a little snag when my requirements overstretched the little machine, as I needed other Virtual Machines to host other bits and bobs, and the initial CRM VM also became bogged down with the amount of different CRM organisations I was running.  It was time for an upgrade.

Hyper-V server, the second coming


So, keeping with the excellent experience I had with the intel NUC, I decided to get a new one, but the latest version.  This little baby was the latest i7, it had a maximum of 32GB of RAM, but otherwise was pretty similar to the original one.

Coupled with 32GB of RAM, a 512GB SSD for the operating system, and a 2 TB 2.5 inch Drive, it was ready to receive Windows 10 Professional.

Installing Windows 10 was easy, then adding Hyper-V, and then moving my VM’s across to it.  With the 32GB of memory, I was able to increase the memory of the Dynamics Virtual Machine to give it space to grow, and I still had memory left over.

Enabling the server for remote desktop access enabled me to unplug it from the screen and keyboard, and position it out of the way, simply connected to power and ethernet.  And there it sits, chugging away.



Servers in action

And this is what they look like.

Microsoft.Crm.Entities.PluginType and PluginTypeNode: System.Xml.XmlElement caused an exception

I was getting this error when trying to import a solution into an On Premise Dynamics 365 environment.

This was a solution that I knew had previously imported into other environments, so I was very confused why it would not import.  Turns out, the Sandbox Processing Service on the server was not actually running.

Restarting the Service allowed the solution import to proceed.

I believe this must have happened as we had experienced a power cut, and I have certainly seen Dynamics services not restart properly when a server is not safely switched off correctly.  Also, it may have had something to do with the fact that this one little Virtual Machine server was running about 20 different CRM Organisations at once.

Anyway, never assume that its an issue with your solution.  Nine times out of ten, it is, but always remember to check your environment as well.


Dynamics Solution Dashboard

I have decided to release a small utility that I have been working on to assist me in my day to day work with Dynamics CRM.  A common requirement in the standard Development, Test, Train and Production environment setup is the moving of solutions between organisations, and version numbering.  One thing I often need to do is to check the version numbers of a solution across different CRM instances, to see if there are any discrepancies.

I needed a tool that could just do it for me with a click of a button and highlight any differences.

And so, here it is.

The application can simply be configured to connect to any number of CRM environments (within reason) and it will detect all of the solutions installed, and their version numbers, and show them in a grid.  Any instances where an environment does not have the same version number, the solution is highlighted.

To configure it, simply click the Settings button, and then the Connections button to add your connections. On the settings screen, you can enable and disable the connections you wish to view.  It should be fairly straight forward.

I shall probably be adding more features to it as I go, but for the first version, its already proving very useful to me, so thought I would share it.

If you wish to Download it, you can download the Zip file, extract it and run it.

Downloadable version of Dynamics Solution Dashboard


Portals Support added to CRM Utilities for Visual Studio

Get it on the Marketplace

I have updated my extension to support publishing of files from Visual Studio to Microsoft Dynamics Portals.

The tool now supports publishing files to Web Templates and Web Files, allowing you to use Visual Studio to edit and track changes of your portal related files, and quickly update Dynamics with the appropriate Portal files.

Web Files and Web Templates are simply listed within the Web Resource linker dialog for you to select.  You can then publish the appropriate files within your Visual Studio solution to Dynamics.

If you have installed the extension from the Marketplace, then it should prompt you to update, but if not, you can get it from the below link.

CRM Utilities for Visual Studio

Discord channel (update)

I have decided to remove the Discord links from this site, although, its still an open channel.

I wanted to set up a global group chat for people within the Microsoft Dynamics Development space.  I use Slack at work, but the problem with that is the closed invite system.  It is difficult setting up Slack to allow people from different teams/companies if they have different email addresses.

Discord is traditionally a gaming chat system that works very similar to Slack, but is free, and with an appropriate Link, allows anyone to join specific channels.

So, I thought I would give it ago.  If you are reading this blog, then feel free to use the link below and join Microsoft Dynamics Discord channel and introduce yourself.

Microsoft Dynamics Discord Channel