INACCESSIBLE_BOOT_DEVICE, courtesy of Intel Rapid Storage Technology drivers (14.5.0.1081)

Note to self: do not update Intel Rapid Storage Technology drivers on a HP Proliant ML10v2, unless I really, really need to.

I’ve become complacent when throwing drivers at devices and this is a reminder how easy it is to break things. I recently added a TPM to one of my servers and one of the fixed drives is classified as removable by Windows, which means I can’t use the TPM with it. There’s at least two ways to fix this, either install Intel RST drivers and configure it through the console, or change some registry keys to force them to fixed drives.

So – download Intel RST version 14.5.0.1081 (the latest one that I thought was compatible), install, and reboot.

Restarting takes ages with a server BIOS, and you’re unlikely to have it hooked up to a display, so I had to jump into the iLO console to work out why it hadn’t started. After a reboot, all I had was the Windows logo, the spinning wheel, and shortly after a:

INACCESSIBLE_BOOT_DEVICE (we must restart)

Restarts will yield the same result, even on safe mode, I didn’t have access to restore points, and the startup repair was also fruitless.

A fair while later I stumbled across this brilliant blog post which eventually provided success through:

  1. Restoring an earlier driver version as per the post
  2. Using the “Use last known good configuration (advanced)”, which managed to remove the BSOD.

All in all, much of an evening wasted by a single driver.

Installing a SSL certificate to Qlik Sense Enterprise on Windows Server 2012 R2

In this post I’m going to look at how quick and easy (and cheap) it is to procure and install a SSL certificate on your Qlik Sense deployment. This assumes you are starting with only the self signed certificates, and that you want to use a certificate generated by a signing authority for use on an externally facing site.

A couple of things to note:

  • I’m using Qlik Sense Enterprise 3.1 with a single-node deployment using the default settings
  • You have a choice of verification methods – I chose to use DNS by adding a CNAME (pointer) to my chosen domain, and managed this through a linux DNS host. You can also verify through email or http (placement of a file)
  • I’ve used a basic certificate from PositiveSSL that offers only domain validation (DV). Certificates offering greater levels of protection and assurance are also available
  • The server is running Windows Server 2012 R2 with IIS 8, which is up-to-date with the latest updates at time of writing (January 2017)

 

On a clean installation of Qlik Sense Enterprise, you’ll note that the domain fails SSL validation in most browsers. Why? Because the certificate is one that has been generated by your server, and not by a “trusted” certificate authority. Have a read of this page about Certificate Authorities if you’re after further detail.

Continue reading “Installing a SSL certificate to Qlik Sense Enterprise on Windows Server 2012 R2”

Qlik Sense and general port troubleshooting on Windows Server 2012 R2

One of the beauties of Qlik Sense Enterprise is that it can be installed on nearly any Windows machine, with very few pre-requisites.

One of the drawbacks is that you may then be tempted to load it onto a multi-purpose box, or at the very least, one with a number of core Windows roles installed (especially if you’re just testing).

Uh oh, it's a 404
Uh oh, it’s a 404

This post is going to offer some quick ways of resolving port clashes, and working out what’s binding where without changing the core Qlik Sense Enterprise installation.

Continue reading “Qlik Sense and general port troubleshooting on Windows Server 2012 R2”