I recently updated my personal sandbox to use SQL Server 2016. While the installation succeeded, one of the first few problems that I ran into were:

• The SQL Server 2016 instance failed to shutdown
• Error 17054 was logged every time a shutdown is attempted with the error: “The current event was not reported to the Windows Events log. Operating system error = (null). You may need to clear the Windows Events log if it is full.“
• Installation of KB3207512 (update for SQL Server 2016 SP1 Reporting Services) and latest CUs kept failing
• User databases would not be accessible with an error: “The operating system returned error 21(The device is not ready.)“

While I was trying to figure out what was wrong, I ran into the same problem with a few other instances.

The Solutions

After a lot of rounds of trial and error, the following changes finally did the trick. The items below collectively make up the solution and all items need to be performed in order to get the SQL server instance up-to speed again.

• Launch the SQL Server Configuration Manager
• Under “SQL Server Network Configuration” ensure that the TCP/IP protocol is enabled
• Under “SQL Server Services”, ensure that the following services are started:
  • SQL Server PolyBase Engine
  • SQL Server PolyBase Data Movement

Once the steps provided above are done, all the problems listed above should cease to exist.

Until we meet next time,

Be courteous. Drive responsibly.