We’ve been doing more and more work on SharePoint these days. It’s not as nice as Domino. It requires more effort to develop applications. The simple things that we take for granted in Domino require some work. But, once you get started working with it you can see why companies like it. A lot of our client base has started to develop applications in Sharepoint or they are moving their Mission Critical Domino Applications over.
The nice thing about the Domino development environment is that it is easy enough to setup a server instance or instances on a local workstation and you can develop to your hearts content. Sharepoint requires more effort. Both from a licensing standpoint and required development tools.
Recently I decided to setup SharePoint Foundations on my workstation. Foundations is the “no Cost” solution requiring only licensing on the base operating system. Now, Microsoft does not officially support running SharePoint on a Workstation but does provide instructions on how to do it. However, the instructions seem to have a number of incorrect or missing steps. So my instance didn’t work.
Here are some of the things you need to do to get it working properly.
1. Read the instructions. Domino installs are easier and you can get a server running in minutes.
2. Do not use your favorite unarchiving tool and don’t do what the instructions say. I know I told you to follow the instructions but this one was wrong. If you use an unarchiving tool the files won’t get extracted properly. You need to run the following from the command line.
c:\<SharePointFiles Directory>\SharePointFoundationFiles /extract:c:\<SharePointFiles Directory>
The instructions that I’ve seen tell you to use
c:\<SharePointFiles Directory>\SharePoint /extract:c:\<SharePointFiles Directory>
Sharepoint.exe for foundations doesn’t exist at this point.
3. Edit the files\setup\config.xml to allow for installation on a workstation. If you try to run the setup program now you’ll find that it won’t work. It will come back saying that the base OS is not supported. You need to edit the config.xml file and add the following tag line inside the <configuration> tag:
<Setting Id=”AllowWindowsClientInstall” Value=”True”/>
4. If you get the following message - ”The language of this installation package is not supported by your system” – than you didn’t extract the files properly. Go back and do it right the first time.
5. Error during installation – As the installation is about to finish you get an error. When you check the logs it states
SharePoint installation error: dbwrap.exe failed with error code: -2068643839. Type: 8::CommandFailed
To fix this I had too do a number of things
a. Uninstall SQL Server 2008
Uninstall SQL Server 2008 because there can be problems if standalone installation finds some existing database.
b. Make sure you don’t have pending file operations
Start regedit and then go to HKEY_LOCAL_MACHINE>SYSTEM>CurrentControlSet>Control>Session Manager . Find the key “PendingFileRenameOperations” registry. Delete the key.
c. Install SharePoint 2010 as single instance again
I ran setup again and let it repair the last installation.
6. Startup the Sharepoint 2010 Central Administration and you get a blank page. Okay were almost there. You start the administration to start working and you get a blank screen. To fix this you need to go to the IIS administration. Lookup the sharepoint website and change the authentication. Make sure that Anonymous is disabled and Basic authentication is enabled.
After I did all that my SharePoint development instance was up and running. Definitely not as easy as Domino but well worth the work.