Recovered: SharePoint V3 on Virtual Servers
Out of DB Hell and on to SharePoint v3
So everyrobot that's anyrobot in the SharePoint crowd, already has the Office 12 SharePoint server up and running. And just to prove I'm a noRobot, I'm only doing it just now, and, just as you've come to expect, I expect it will be alot like getting my teeth drilled.
So, let's give it a go, shall we?
First you've got to have a suitable host. I'm using a virtual machine with Windows Server 2003 Enterprise Edition with Service Pack 1. It's got a Gb of RAM and they let me add it to our domain. So that's cool.
Next, you'll need the bits. I went here:
http://www.microsoft.com/office/preview/beta/download/en/default.mspx
Where I had to select my country and log-in and tell Microsoft all about me and then I had to pay $6 for WSSv3, MOSSv3, SharePoint designer and then I got the SharePoint Search. So I'm left with the following files:
-
SharePoint_Setup.exe – I think this is WSSv3.
-
OSS-EN.img – I think this is MOSS 2007.
-
SPS32-EN.img – I think this is SharePoint Search.
-
SPD-EN.EXE – I think this is the SharePoint Designer.
I got the WSSv3 Beta 2 Technical Refresh bits here:
I got the Beta2 Technical Refresh bits for the Office Server here:
I went here and got the documentation for the WSS Beta 2:
That should get me started.
So I run the SharePoint_Setup.exe.
I click RUN at the Execute File dialog box (duh) and then I get this funny little dialog box that says Do you wish to proceed with the installation?
So I click yes and the WSS install splash comes up (Yeah!) but then I get this message:
Setup is unable to process because of the following errors:
This product requires ASP.Net web server extensions to be enabled in Internet Information Services(IIS). Enable this setting and re-run setup.
Please refer to the readme file for instructions on how to obtain these pre-requisites. Correct the Issues(s) listed above and re-run setup.
Now, I have to admit, on a previous try, I also got a Windows Workflow Foundation 3.0 error but, based on the advice of a coworker, I installed the MS Web Service Enhancements 3.0 and that error went away. I got the WSE 3.0 install here:
That was not quite as bad a a drilled tooth but close.
The ASP.Net thing is alot like a drilled tooth.
So, I guess there's a readme, somewhere. The WSS Doc download above is a file called WSSBeta2docs.exe. I ran it and it unloaded a bunch of files, none of which are called ReadMe. There is one is called WSSDeploy.Doc. About halfway down the first page there's Software Requirements.
I ran through the Part about the .Net framework but all of that was right. So, I thought it might do to re-ininstall it.
So I uninstalled the .Net Framework 3.0 and that made the WWF error reappear. Not only that put it wiped out all my web service extension from IIS. So I uninstalled the .Net 2.0 Framework and then reinstalled it.
Then, rerunning the SharePoint_Setup.exe, I'm left with ony the WWF error:
Setup is unable to process because of the following errors:
This product requires Windows Workflow Foundation Beta 2 (build 3.0.3807 or later).
Please refer to the readme file for instructions on how to obtain these pre-requisites. Correct the Issues(s) listed above and re-run setup.
So, referring back to the WSSDeploy.doc, I'm directed to download and install the WWF Beta 2 and the Visual Studio extensions from here:
So, not that my teeth look like swiss cheese, I run SharePoint_setup.exe for the unteenth time and, Woohoo!
I get the license agreement and then the Basic or Advanced install option.
I recall that in WSS 2003, if you chose Basic, it would drop your DB into SQLExpress. So I'll choose advanced.
Then I get the Web Front-End or Stand-Alone option. The stand-alone option says Desktop Engine so, I'll choose web front end. I'm guessing what I am doing is something like building a farm where all components live on one box. My objective is to have the SharePoint database NOT live in SQLExpress.
I end up with the option to run the configuration wizard.
I tell it to create a new server farm.
As I suspected, then it asks me for a database server and gives me the default database name. I change the database name to RobotsRule and I give it a local admin username and password. I might have to change that later.
I click next through the rest of the wizard and I'm on to tasks 1 through 9.
Which would be good, except for step 2, Create Configuration Database.
I get this error: This access control list is not in canonical form and therefore cannot be modified.
Which I google and find this from my new best friend Bill:
http://blogs.interknowlogy.com/billsheldon/archive/2006/05/22/2705.aspx
Apparently, my problem is the Virtual Image I started with and the NewSID program I ran on it to give the VM a new ID.
Tags: