Skip to main content

SQL Server 2008 Installation Fails to Start

Recently I have been installing a new SQL Server 2008 instance on Vmware vSphere based  virtual server, the OS was Windows 2008 R2. I have done this several times before and I don't recall ever getting this issue. Seeing as it took me a short while to figure out what was going on I decided to make some notes about it here.

I attached the SQL Server 2008 iso to the VM, auto-run failed to kick in so off I went to the CD/DVD drive to start the setup manually. First up, it warned me that I needed to update Windows installer and the .Net framework to 3.5. I clicked OK to do this and it ran successfully and then the server prompted me to reboot.

When the server had restarted I ran the setup again but this time nothing happened, no error, no start screen, nothing. I did this a few times again, I rebooted again, not sure why I rebooted, more out of habit than necessity and just to make sure.

I tried setup again, same thing.

Off I went to the event viewer and I found an Error in the log that  looked something like this:

"The Windows update  could not be installed because of an error: 2149842974 "" (Command line: ""C:\Windows\system32\wusa.exe" "D:\x64\redist\Windows Installer\x64\INSTMSI45.MSU" /norestart")"

A quick google search did not return anything obvious to my situation. I even posted a question on a couple of forums.

Anyway I decided to try and get a more meaningful error and I ran the above command from a command prompt. I did in fact get a new error that said there was not enough space available on the drive, or something similar. This was a strange error because the only drive without space available was the d:\ drive...The CD/DVD drive.

Anyway I copied the contents of the DVD drive, the SQL Server 2008 setup files to a local drive on the server, with plenty of space. I then ran the setup again using the files on the local drive. This time I got the setup screen and was able to perform my installation.


Popular posts from this blog

SQL Server 2012 and Virtual Service Accounts

This post is written by David Postlethwaite
If you are using SQL Server 2012 you will probably have noticed that the default account for the SQL services has changed from that used in previous versions. With SQL 2005 and 2008 the default account for SQL service and SQL Agent service was “NT Authority\System”. This is one the built in accounts on a Windows machine, managed by the machine and selectable from a dedicated dropdown list

The Network Service account was introduced in Windows 2003 as an alternative to using the LocalSystem account, which has full local system privileges on the local machine, a major security concern.
The Network Service has limited local privileges easing these security concerns but when many services on a machine use the Network Service account it becomes harder to track which service is actually accessing resources and performing actions, because all the services are using the one Network Service account.
Also, this account, by default, has sysadmin per…

Always Encrypted

By David Postlethwaite

Always Encrypted is new features in SQL Server 2016 and it is also available in Azure SQL Database. Here you can encrypt columns in a table with a master key and a certificate so that they will appear as encrypted strings to those who don’t have the required certificate installed on their pc.
Once the certificate is installed on the computer then the unencrypted data can then be seen as normal.

The data passes from database to your application as the encrypted value, only the application with the correct certificate can unencrypt the data so it is secure across the wire. This will go some way to resolving the concern of people worried about putting their sensitive data on a shared server in the cloud such as Microsoft Azure and accessing the data across the Internet.

At the time of writing Always Encrypted is only supported with ADO.NET 4.6, JDBC 6.0 and ODBC 13.1 but expect other driver to become available.

The calling application (including SSMS) must also hav…

New in SQL Server 2017: Graph Databases

David has recorded and published a video of his presentation on SQL Server Graph Database. In his video which you can watch below, David provides an excellent introduction into SQL Server 2017 Graph Databases. In his presentation he looks at Tennis results at tournaments for  his favourite player "The Fed"  Rodger Federer.

David  shows how to set up graph database and work with them in SQL Server 2017.

Graph Database is not new. Other vendors have had graph database capabilities for some time so Microsoft are quite late to the market. In David presentation it appears that Microsoft have done a reasonable job of implementing some of the graph database features but he does point some of the limitations of the Microsoft product too and suggests that it is not ready for production yet but Microsoft seem serious about this feature.

Please watch the video and feel free to leave a comment or feedback - David is delivering a version of this talk on Graph databases in SQL Saturday Ka…