I make a lot of use of virtual machines for both testing and demonstrating Microsoft Dynamics GP. As a company, when I joined, Perfect Image tended to use VMware (I’ll reserve comment, which I realise tells it’s own story), but more recently have started making more use of Microsoft Hyper-V, which is what I also use at home for testing and writing my blog and books.
After installing Hyper-V on my work laptop I created a virtual machine and clicked start. Unfortunately, I received the below error messages:
I did some digging around and found that although Hyper-V was installed, the hypervisor wasn’t running. Fortunately, the laptop I have does support Hyper-V and I only had to do one thing which was to enable the hypervisor by opening an elevated command prompt and type the following command:
bcdedit /set hypervisorlaunchtype auto
Once I had run the command I was able to start the virtual machine without further problem; at least with Hyper-V.
What I found was that with the hypervisor running, I wasn’t able to start a VMware virtual machine. So a second command can be used to disable the hypervisor for those times when I need to use a VMware virtual machine:
bcdedit /set hypervisorlaunchtype off
Hopefully, I’ll be able to complete the transition away from VMWare very soon and stop toggling from one to the other.
Taking a slight diversion from my usual subject matter with this post. I was trying to connect to a clients system via VPN a short while ago when I received error 778:
Error 778: It was not possible to verify the identity of the server
I did a little digging and found that this error actually relates to the username and password being incorrect. I checked our records and found that the password had been reset since the last time I logged on; after entering the new details I was able to log in successfully.
It would be nice if the error message had been a little more descriptive of the actual problem, but at least it was a simple solution.
The System Requirements for Microsoft Dynamics GP 2015 are now available from CustomerSource (login required).
The stand out items for me is that support has been dropped for several older versions of Windows, SQL Server and Office:
- Windows XP all editions
- Windows Vista all editions
- Windows Server 2003 all editions
- SQL Server:
- 2008 all editions (including R2)
The only surprise on the above list is that some of the software listed as no longer supported was also listed as no longer supported with Dynamics GP 2013; in fact only SQL Server 2008 is new to the list.
Apart from the above retired software, the recommendations look pretty much the same as Dynamics GP 2013; Windows 8.1 and SQL Server 2014 have been added as supported.