30 August 2012

How do I? – How I built this blog (Part 1 of 3)... Install SQL Server Express 2005

I've been asked before just how I went about putting this blog together. I've committed to doing a series on building a blog on WSS 3.0 and have finally been able to scrape the time together to get this done.
I'm filing this under my "How do I?" series so as usual there will be *LOTS* of screen prints and step by step guidance to ensure you can recreate the process on your own server. So that said, here are the steps to start the process of building a blog on Windows SharePoint Services 3.0:
  1. The first and most important component to this whole process is the server itself. You will need a Windows Server 2003 machine to start with. I was fortunate enough to win a copy of Microsoft Windows Server 2003 Enterprise Edition with 25 CALs at my local SharePoint user's group initial launch meeting. That set me up to be able to setup my server for production level usage. I have an MSDN subscription, but that only covers servers in a DEV environment so the new license was a very welcome addition.
  2. After a fresh install of Windows Server 2003, your server won't have any specific roles assigned to it. When you login to your server as an administrator, you should be greeted by the "Manage Your Server" page.
  3. The first thing we need to do is update our server to ensure we have all the latest security patches applied. Through the Start menu, click "All Programs/Windows Update".
  4. Select and install all critical updates.
  5. Once all updates have been applied, you will need to ensure that the .NET Framework 2.0 is installed on your server. It will be required by SQL Server 2005 Express. Through the Start menu, click "Control Panel/Add or Remove Programs".
  6. You should find the Microsoft .NET Framework 2.0 listed. In our example, the SP1 is also listed.
  7. If you do not have the .NET Framework 2.0 installed, you can download and install it from <<>>
  8. Once you're sure the framework is installed, return to the "Manage Your Server" page.
  9. Click the "Add or remove a role" link toward the top right of the page.
  10. The "Configure Your Server Wizard" springs into action. Click the "Next" button.
  11. Windows will go through the process of detecting your settings and roles. Once complete, a list of available roles will be presented. Select the "Application server (IIS, ASP.NET)" role and click the "Next" button.
  12. The "Application Server Options" page will open. Ensure that:
    1. FrontPage Server Extensions is NOT selected.
    2. Enable ASP.NET option IS select.
    Click the "Next" button to continue.
  13. The "Summary of Selections" page will load and list your selected options. Click the "Next" button to proceed.
  14. Windows will proceed with the application of your selected options.
  15. Depending on your installation, you might be prompted for the location of the Windows Server 2003 installation media. Insert the disk into the CD/DVD drive and click "OK".
  16. Upon successful configuration of your server, you should be presented with a summary page stating that your server is now configured as an application server. Click the "Finish" button to complete the process.
  17. Windows will return to the "Manage Your Server" page, but this time, "Application Server" should be listed as one of the roles of the server.
  18. Close the "Manage Your Server" window.
  19. Download the SQL Server 2005 Express installation package, saving it to a local drive location. In our case, we had created a "Setup" folder on the root of the C:\ drive where we saved our installation files. You could just install WSS 3.0 and elect to have it install SQL Server 2005 Express for you, but the problem with that is that you may experience issues when trying to manage the databases. Additionally, any uninstall of WSS 3.0 could also remove the database component and its data. That may not be a desired effect so we're going to flip flop the process by installing the stand alone, FREE database components first and then simply point WSS to it during its install process thus separating the logical connection between WSS and the database component.
  20. Open Windows Explorer and navigate to the location of the "SQLEXPR_ADV.EXE" file.
  21. Double click the "SQLEXPR_ADV.EXE" file. The self-extracting file will begin to unpack its contents.
  22. After unpacking its contents, the package will automatically launch Setup. You'll be presented with the EULA (End User License Agreement) screen.
  23. Read the contents of the EULA and ensure that you understand it and agree with it.
  24. Check the "I accept the license terms and conditions" check box.
  25. Once checked, the "Next" button should become active. Click it to continue.
  26. Setup will begin by checking your server for the prerequisites. Click the "Install" button to install the needed prerequisite files.
  27. You'll be presented with some visual feedback related to installation status.
  28. Once all prerequisites are installed, click the "Next" button to proceed to the next step.
  29. At this point, Setup will load the SQL Server Installation Wizard. Click the "Next" button on the opening screen to continue.
  30. Setup will conduct a System Configuration Check to ensure that your system is capable of running SQL Server. Click the "Next" button if no errors are identified. If you do encounter errors, you will need to abort the installation and address those errors first before continuing.
  31. Next you'll be prompted for the customary Name and Company information. Supply your desired values and click the "Next" button to continue.
  32. On the Feature Selection screen, you will need to select which features are to be installed, and how. Personally, I prefer to install everything locally. It takes up more space in the short term, but in the long term, it saves me from having to dig around for installation media if I suddenly decide to leverage some functionality that wasn't used before. If you've ever had to dig for your installation media, you KNOW how annoying this can be. Besides, disk space is cheap right? J
  33. Select the installation location for your files through the use of the "Browse" button. Some administrators like to change these settings to further obscure their server. In our case, we're accepting the default settings.
  34. After selecting your feature settings, click the "Next" button to continue.
  35. On the Authentication Mode screen, you will need to select if you wish to allow SQL Server authentication. The best option to use it Windows Authentication, but if you have some burning desire to also use SQL Server accounts, change your selection accordingly and click the "Next" button to continue.
  36. On the Report Server Installation Options screen, select if you wish the report server to be configured. We're just going to use the default configuration, but if you do not wish to configure the report server at this time, change your selection here. Click the "Next" button to continue.
  37. On the Error and Usage Report Settings screen, select the level of contribution you wish to make. These settings cause privacy concerns which is why you have the option to turn them off here, but sending error and usage information to Microsoft automatically, helps make the product better for everyone so we just checked both and clicked the "Next" button to continue.
  38. Finally, you'll reach the Ready to Install screen. Click the "Install" button to commence your installation.
  39. Setup will provide you with visual progress information as the installation continues. You'll notice that components are not necessarily installed in the sequence they are listed, but it doesn't matter.
  40. Once all components are installed, the "Cancel" button will be disabled and the "Next" button will become enabled. Click the "Next" button to continue.
  41. On the completion screen, you'll be presented with a summary log file as well as some other residual information. Click the "Finish" button to complete the installation.
Your database server components are now installed and you are ready to install WSS, but that we will cover in Part II.




there's no doubt a good reason that I'm missing ...

but why are you installing SQL Server 2005 Express with its 4GB limit rather than using the built-in "Windows Internal Database" with none ?

Or is this going to be a MOSS 2007 rather than a WSS 3.0 installation ?

 on 3/19/2007 7:00 AM


I had to weigh the 4 GB limit with the ability to access and manage the database.  If you install just the internal database, which is basically Express without the 4 GB limit, you cannot manage it from Management Studio.  Additionally, if you remove WSS 3.0 from the server, it automatically removes the database as well...
Weighing all these factors, I had to decide which was more important in this case... I chose near term accessibility.

I will probably upgrade to SQL Standard at some point, but for the purpose of a blog, if someone is going to be putting together 4 GB worth of content, they probably don't need me to be telling them how to blog on SharePoint. :)

Thanks for pointing that out though.  I appreciate the candid feedback.

Cornelius J. van DykNo presence information on 3/19/2007 11:44 AM

DC Install

Hi Cornelius,

Would there be issues on using a Domain Controller for this? Can the server be both a DC and App server?


 on 3/23/2007 12:33 AM


Hey C,
Mike of course had a good point but overall this was a fantastic post.   Good work bud

 on 3/24/2007 6:10 AM


Though I've not personally done it, I believe there are some things to be aware of.  Fellow SharePoint MVP Steve Smith posted a workaround on his site based on Beta 2 which should point you in the right direction.  You can find it here:


Cornelius J. van DykNo presence information on 3/26/2007 7:00 AM


Hey Bob,

Thanks for staying tuned in.  I always try to ensure that my content is good and relevant. :)

Cornelius J. van DykNo presence information on 3/26/2007 7:04 AM


How about surface area and collation configuration?

Microsoft specifies, that you should configure surface area to:

- Select Local and Remote Connections, select Using both TCP/IP and named pipes.

and configure collation to:

- The SQL Server database collation must be configured for case-insensitive, accent-sensitive, Kana-sensitive, and width-sensitive. This is to ensure file name uniqueness consistent with the Windows operating system.

This is taken directly from:


In a demo environment this probably doesn't matter that much, but shouldn't that be done in production environment?

/Robert Knudsen
 on 4/10/2007 4:01 AM


Hey Robert,

As you noted, there are some configuration options that can be set when installing SQL Server.  In this case though, in Step 36, we simply installed the default settings which already takes care of all these for us so we didn't need to delve into these.
If you feel adventurous, feel free to play with these settings though...


SharePoint Remote Event Receivers are DEAD!!!

 Well, the time has finally come.  It was evident when Microsoft started pushing everyone to WebHooks, but this FAQ and related announcement...