In an effort to squeeze at least another year’s use out of my Dell Vostro 3750, I purchased an SSD to replace my existing hard drive. Of course, installing a new drive means you get to spend a good deal of time reinstalling operating systems, applications, etc. Fun, right? Well, the SSD is smoking fast, so that has made the entire process slightly less tedious, and since I needed to start from scratch, I decided I might as well upgrade Windows and Office, thus adding to the fun. Turns out I like Windows 8 more than I thought I would during the first five minutes of using it, and I really like the minimalist color scheme in Office 2013, even though it’s likely I’m in the minority opinion here.
But, I digress . . .
All my installs were going along swimmingly until I got to SQL Server. I kept getting this weird error that made me think I was having permissions issues with the account I set up to run the SQL Services. I ended up spending my day Googling what I thought was the issue and trying several different things all to no avail. Long story short, I finally Googled the *exact* error message I was getting: [Configuration error description: '' is not a valid login or you do not have permission.]
Turns out, my complete lack of creativity when choosing a name for my computer during Windows setup came back to haunt me. By naming my computer Christina and also setting up my user account as Christina, it caused the SQL install to blow up when I tried to add myself as a SQL Administrator. DOH!
- Do yourself a favor, and don’t give your computer the same name as your user account if you expect to be able to add that user as a system administrator when you install SQL Server.
- Search for the exact error message text. I’d have solved my problem three installs earlier had I followed troubleshooting 101.
Now, go play with Windows 8 and Office 2013!