After the successful installation of SQL Server 2016 Developer Edition (which is now free), you are more than likely going to want to install SSMS to manage the recently installed instance. You can get the latest build of SSMS here.
So looking forward to seeing what was new and to get some “hands on” with SQL 2016 I attempted to install SSMS, only to be presented with absolutely nothing, not even an application crash message dialog. For this, I blame Microsoft since I had to go digging to find the appcrash log as nothing was presented to me. However, the resolution to my install issue actually was because of VirtualBox’s 3D acceleration feature.
To give you some background, this is what I’m running:
VirtualBox version 4.3.30 r101610
Guest OS: Windows 10 Pro version 10.0.10586
To figure out why this application would not run, I attempted to search for files modified on my system in the past 24 hours, looking for files on or near the time of the attempted install of SSMS. This presented a hodge-podge of crap, but in the mix I noticed a folder titled “AppCrash_SSMS-Setup-ENU (…” with a long GUID appended to the folder name. Going into this folder yielded a file named “Report.wer”
Opening this file in notepad, revealed why the SSMS install had crashed:
Sig.Name=Fault Module Name
Sig.Name=Fault Module Version
Sig.Name=Fault Module Timestamp
Searching Google for “VBoxD3D9wddm-x86” led me to the resolution, 3D support within VirtualBox. The actual ticket which has been closed and fixed can be found here.
To resolve my issue, I shutdown my virtual machine and opened the display settings, turned off the “Enable 3D Acceleration” extended feature, powered on the VM and I was able to start the install process for SSMS 2016 without a hitch.
Another lesson learned with this experience…keep your software up-to-date! From what I’ve researched, version 5 of VirtualBox along with the updated Guest Additions should not experience this issue.
Now I’m off to update VirtualBox!