Setting Up the Development Environment for SharePoint 2010

MSDN has published an article about Setting Up the Development Environment for SharePoint Server. This article describes how to install a development environment with Microsoft SharePoint 2010 and Microsoft Visual Studio 2010. These instructions will enable us to get started with an environment that is specifically suited to developing SharePoint custom solutions.

SharePoint 2010 Beta Release Known Issues

You can find SharePoint 2010 Beta Release Known Issues and workarounds for them from here.

http://blogs.msdn.com/sharepointdeveloperdocs/archive/2009/11/20/sharepoint-2010-beta-release-known-issues.aspx

Topologies for SharePoint Server 2010

Microsoft releases a document which describes common ways to build and scale farm topologies, including planning which servers to start services on.

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=fd686cbb-8401-4f25-b65e-3ce7aa7dbeab

Manually Uninstalling MOSS 2007

I tried to install MOSS SP2 on top of MOSS SP1 on my development machine. Unfortunately I encountered so many errors while running the Sharepoint Product and technologies. So I decided to uninstall the exisiting installation and re-install a SP2 Slipstreamed version of MOSS 2007. When I go to add/remove programs and run the uninstaller it exited without prompting any error. After trying several steps I had to manually uninstall the existing MOSS 2007 installation.

Following are the steps I followed to uninstall MOSS 2007 Manually

Note: Before performing these operations make sure you backup all Share Point databases and create a backup of the registry.

a) Disable and Stop the following services

-Microsoft Single Sign-on Service
-Office SharePoint Server Search
-Windows SharePoint Services Administration
-Windows SharePoint Services Search
-Windows SharePoint Services Timer
-Windows SharePoint Services Tracing
-Windows SharePoint Services VSS Writer

b) Note the following registry keys:

From HKLM\Software\Microsoft\Office Server\12.0
-Install Path (default is C:\Program Files\Microsoft Office Servers\12)

From HKLM\Software\Microsoft\Shared Tools\
Web Server Extensions\12.0
-Location (default is C:\Program Files\Common Files\Microsoft Shared
\Web Server Extensions\12)

c) Delete the following registry hives:

HKLM\Software\Microsoft\Office Server\12.0
HKLM\Software\Microsoft\Shared Tools
\Web Server Extensions\12.0

[x32] – HKLM\Software\Microsoft\Windows
\CurrentVersion\Uninstall\OSERVER
[x64] – HKLM\SOFTWARE\Wow6432Node\Microsoft
\Windows\CurrentVersion\Uninstall\OSERVER

d) Delete the following folders:
The value of the InstallPath key
The value of the Location key
C:\%CommonProgramFiles%\Microsoft Shared\SERVER12
Restart the server and perform an installation as normal.
Before running the configuration wizard, follow the steps as follows
You need to restore the Server Language registry value by
creating the following .reg file (open notepad and paste the following):

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft
\Shared Tools\Web Server Extensions\12.0 \ServerLanguage]
“1033″=”"

-Save this as fixlanguage.reg and upload it to your server.
Double click the file and say yes to the prompts.

Earn money with Sharepoint Blogs

You can earn money for fulfill your hosting costs by signing up for SharePointAds.com . once the management committee review your blog you will be able to publish ads from sharepointAds.com.

Sharepoint In Plain english

Very simple and understandable introduction for Sharepoint 2007

http://www.microsoft.com/video/en/us/details/76e8d3af-c2bd-42a6-bb12-befcbd041bf1

MOSS 2007 SP2 Troubleshooting

I was trying to install MOSS SP2 on a server which has MOSS 2007 SP1 installation.

After install SP2 MOSS cannot complete configuration wizard step 8 out of 9,
and this message shows up:

Failed to upgrade SharePoint Products and Technologies. An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown.

After googling i found a great article which has been published by Lior for MOSS SP1 troubleshooting.

That was really helped me to overcome the solution. Thanks!!! Lior for that.

I have stated the steps below, which I followed to overcome this problem.

Workaround Steps:

1. Stop the services on the server
You can find these in Central Admin/Operations/Services on Server.
You should make a note of the settings for each as you may want them when you restart the services.
This is one place I would have, given the time, determine which of these needed to be stopped.

2. Stop the World Wide Web Publishing service on the server
WWWP is in Windows Services. If you have multiple web front ends I would stop it on all of them
and pay close attention to the instructions for installing SP1 in a farm.

3. Run the upgrade using PSCONFIG
Open a command prompt to the Office Server BIN
(typically 'C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN')

Execute: psconfig -cmd upgrade -inplace b2b -force
NOTE: It did not restart, start the World Wide Web publishing service

4. Restart services in the farm
Go to Central Admin/Operation/Services on Server and restart the services.
It’s recommended to delete the offending database and had Central Admin recreate it.

5. Open the SSP Admin and click on Search Settings under Search
You'll get an error – An Indexer is not assigned to the Shared Services Provider 'YourSSPName'

6. Click on Configure an indexer and a search database for this SSP.
Assign an Index Server, and click OK.