Showing posts from 2009

Synchronization Issue in Sharepoint 2007 Servers


I got a small farm environment - 2 WFE's and 1 SQL Server. The Central Admin is configured on WFE-1, Every time I create a New Website it actually throws the error "Request Timed Out" in the end - and then we could see the application created on WFE-1 and not on WFE-2. I finally manage to find the error message from 12/LOGS (No error message in eventviewr) but not sure how to move on - Could anyone please help.
Error -
08/25/2009 16:32:16.42 w3wp.exe (0x09F8)0x16C0 Windows SharePoint ServicesGener al8nca Verbose Application error when access /_admin/extendvs.aspx, Error=Request timed out.

Here are my findings -
Analyzed Log files on Event Viewer

- App Logs - No Luck
- Sys Logs – No Luck
Analyzed Sharepoint Logs
- Timer Job Logs - No Logs
- Timer Job definition – Showed up Job failures Errors on WFE2 – (Bit relief some errors)
- 12 Logs started logging in errors after setting changes in CA
08/25/2009 16:32:16.42 w3wp.exe (0x09F8) 0x16C0 W…

Delete Error WSP Solution from Solution Store

Removing malfunctioning Windows SharePoint Services solutions
I got this fantastic article from i would share it for all.

It could happen that you (or whatever) accidentally break a deployed solution on a Windows SharePoint Services 3.0 (or MOSS 2007 for that matter) farm or site. If that happens, you can no longer retract and/or remove a solution by using the Operations part of the Central Administration website. It will show up as an error in the list of solutions under "Solution Management".
So how do you go about removing the solution entirely? You can use the command-line tool STSADM.exe which can be found under "C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN" for a normal installation of WSS 3.0. Let's assume that the malfunctioning solution is called HelloWorldWebPart.wsp.
To see a list of all solutions …

How to Enable anonymous access in SharePoint 2007

Even though Microsoft has done a great job on improving the user interface in SharePoint 2007, some things are still buried and require a little “black magic” to get done. In this entry I’ll show you how to enable anonymous access on your site.
First, you need to enable anonymous on the IIS web site (called a Web Application in SharePoint land). This can be done by:
+ Launching Internet Information Services Manager from the Start -> Administration Tools menu Select the web site, right click and select Properties Click on the Directory Security tab Click on Edit in the Authentication and access control sectionInstead we’ll do it SharePoint style using the Central Administration section:
+ Then get to your portal. Then under “My Links” look for “Central Administration” and select it. In the Central Administration site select “Application Management” either in the Quick Launch or across the top tabs Select “Authentication Providers” in the “Application Security” section Click on the “Def…

Error in sharepoint best practices analyzer

I was getting this error when i tried to run sharepoint best practices analyzer in our sharepoint Farm.

An error has occurred while establishing a connection to the server. When conne
cting to SQL Server 2005, this failure may be caused by the fact that under the
default settings SQL Server does not allow remote connections. (provider: Named
Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Completed Collecting Data phase.
Starting Postprocessing Rules phase.
Completed Postprocessing Rules phase.

The Webfarm was configured with SQLServer 2005 with a default instance, everything was fine until i decided to run the sbp in LIVE . It was working fine in my Dev machines and in other enviorments except LIVE, there it throws this stupid error.

Google search, tried all my might to make it work but nothing happend and got no much help from net. There were couple of guys saying they created the database alias and got it fixed but nothing was solid.

Spend 2 days on it and finally got …

Free WSS 3.0 BOOK

If you are looking for Free WSS 3.0 BOOK, you can download it here.

How to uninstall MOSS from a Farm

If you want to wipe out and create a new MOSS Farm here are the steps

+ Run the Configuration Wizard and, on the second page, select Disconnect from this server farm and click Yes on the warning dialog. This will delete the IIS web site and the application pool.

+ Then, run the uninstall from the Control Panel's Features and Programs application and click Yes on the warning dialog. This will take a reboot.

+ Then, if you really want to get rid of it all, go to the database server and delete the Config and Admin Content databases

Alternatively you can also disconnect the central admin from the 12 hive using cmd line if nothing works:

psconfig -cmd adminvs -unprovision

psconfig -cmd configdb -disconnect

Implement Form Based Authentication


The purpose of this document is to provide the step by step information about enabling the Form Based Authentication (FBA) for MOSS 2007 site. MOSS 2007 sites uses windows authentication by default. But some business needs form based authentication to fulfill the requirements.

Below section explains to enable Form Authentication for MOSS 2007 site.

Setting up ASP.Net 2.0 Forms Authentication User and Role Data Source

This section explains creation of database which is used to store user's information such as credentials and roles which is used for Form Authentication. This section also explains the configuration of Membership and Role providers in the web.config file and creation of users using ASP.Net configuration wizard. This article shows creating a user and which will be used for testing Form Authentication later.

Create Database

To create database, Microsoft has provided a tool/ utility called aspnet_regsql.exe that creates a database for us. This utility can be foun…