Failed to initiate the upgrade sequence. An exception of type System.IO.IOException was thrown.

"Failed to upgrade SharePoint Products."

I have installed the office web app patch & re-run the configuration wizard when I encountered this exception 

Please Note the GUID is vital for clearing cache.



1. Stop the Timer service. To do this, follow these steps:
   
   1. Click Start, point to Administrative Tools, and then click Services.
   2. Right-click SharePoint 2010 Timer, and then click Stop.
   3. Close the Services console.
2. On the computer that is running Microsoft SharePoint Server 2010 and on which the Central Administration site is hosted, click Start, click Run, type explorer, and then press ENTER.
3. In Windows Explorer, locate and then double-click the following folder:
4. %SystemDrive%\ProgramData\Microsoft\SharePoint\Config\GUID
5. Notes
1. The %SystemDrive% system variable specifies the letter of the drive on which Windows is installed. By default, Windows is installed on drive C.
2. The GUID placeholder specifies the GUID folder. There may be more than one of these.
3. The ProgramData folder may be hidden. To view the hidden folder, follow these steps:
1. On the Tools menu, click Folder Options.
2. Click the View tab.
3. In the Advanced settings list, click Show hidden files and folders under Hidden files and folders, and then click OK.
4. You can also simply type this directly in the path if you do not want to show hidden files and folders.
6. Back up the Cache.ini file. (Make a copy of it. DO NOT DELETE THIS FILE, Only the XML files in the next step)
7. Delete all the XML configuration files in the GUID folder (DO NOTE DELETE THE FOLDER). Do this so that you can verify that the GUID folders content is replaced by new XML configuration files when the cache is rebuilt.
   Note When you empty the configuration cache in the GUID folder, make sure that you do NOTdelete the GUID folder and the Cache.ini file that is located in the GUID folder.
8. Double-click the Cache.ini file.
9. On the Edit menu, click Select All.
10. On the Edit menu, click Delete.
11. Type 1, and then click Save on the File menu. (Basically when you are done, the only text in the config.ini file should be the number 1)
12. On the File menu, click Exit.
13. Start the Timer service. To do this, follow these steps:
    1. Click Start, point to Administrative Tools, and then click Services.
    2. Right-click SharePoint 2010 Timer, and then click Start.
    3. Close the Services console.
14. Note The file system cache is re-created after you perform this procedure. Make sure that you perform this procedure on all servers in the server farm.
15. Make sure that the Cache.ini file in the GUID folder now contains its previous value. For example, make sure that the value of the Cache.ini file is not 1.
16. Check in the GUID folder to make sure that the xml files are repopulating. This may take a bit of time.

--------------------------------------------------------------

SharePoint People-picker Slowness

Recently my SharePoint portal seems to slowing from end user information entering. The User entry box people-picker was really taking forever to resolve name. The slowness was recorded across whole site collection and there was no customization involved which might have affected this issue.

In order to resolve this slowness following steps needs to be performed.
1. Execute following command on the WFE server.

 Stsadm–o setapppassword –password 

Please note - the password here is not the server.

2. Now execute following command on APP server.

Stsadm –o setproperty –pn peoplepicker -searchadforests –pv "forests:i.domain.com, Domain:i.domain.com" -url "http://Sharepointsite/"


This will do the trick. repeat same for Sub-site as well.

SharePoint 2010 -SVC service Exception :'System.Data.Services.Providers.IDataServiceUpdateProvider'

SharePoint 2010 has List data web service However many users trying to access get following exception :   http://yoursite/_vti_bin/ListData.svc

Could not load type 'System.Data.Services.Providers.IDataServiceUpdateProvider' from assembly 'System.Data.Services, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'.

Remedy:

Installation needed on SharePoint web front end servers: ADO.NET Data Services Update for .NET Framework 3.5 SP1 for Windows 7 and Windows Server 2008 R2

Click to Download -- ADO.NET Data Services Update for .NET Framework.

SharePoint 2010 -MS LYNC Integration.

SharePoint - a collaborative platform to have mash up functional is always fun. Recently I found can across well drafted article published by J.D. Wade on Sharepoint and Microsoft Lync.

Lync and SharePoint Integration

Special thanks : J.D Wade.

Hide the extension .aspx in the url of page ...

Now a days customers are more concerned with site URL and its relative path displayed on the browser address.
Many Suggest having interceptor/handler or use the existing global.asax (Application_Begin Request handler) for modifying the URL shown in the browser window, Web Routing is the concept (4.0 framework)

However you can get solution for .Net /sharepoint application there are following ways:

1. MVC
2. HttpModule rewrite URL
3. ISAPIRewrite to enable Extension-less URL Rewriting for IIS5 and IIS6
4. IIS level extension parsing

Step by step approaches refer below links:
URL Rewriting in ASP.NET
URL Rewriting in Asp.net
URL rewrite/Routing (4.0 framework concept) *
IIS Forum for Extension parsing

 Let me know your comments /feedback for the same

ASP .Net Page Life cycle

There are many post related to page life cycle. but the mentioned is really the best provided
Graphical View for Page Life Cycle

Sandbox Solution: Overview

What is sandbox solution

Sandbox is a restricted environment where programs are deployed with restrictions. It plays valuable role for developers to test their application by using sandbox solution. Once this is tested it can be later deployed to full use in the farm.

Solution that are deployed into sandbox are called sandbox solutions.

 

Advantages

If farm is load balanced.

Release code which is fully not tested for production release.

Less bottleneck for farm administrator as this can be managed at site collection by administrator to it.

Disadvantages

First decide whether you want this solution? as using this solution does has impact on performance of the servers. As the farm using sandbox does have more process load than a farm without this.

Code Access Security (CAS) limits the operations that the code can perform

How to use

Activate SharePoint 2010 User Code Host service(SPUCHostService.exe,)  on server you want this solution. Should be done by farm administrator

Sandbox Code Services

Sandbox can be applied at the root of site collection level.

Members of the site collection administrators group can deploy sandboxed solutions

Governance for sandbox

Before deploying think of below

When should the solution be blocked or unblocked?

When to release the solution to production?

Who should be given access, deployment rights etc?

Adding / Blocking /Load Balancing for Sandbox

This can be done via CA – System settings

Source - http://technet.microsoft.com/hi-in/library/ee704543(en-us).aspx

Special Thanks :Amarprit Jaspal

Warning: Super user account!

When Working on a farm environment couple of time we come across some warning stating:
"The super user account utilized by the cache is not configured...."

Temporary Solution :: execute- 'stsadm -o setproperty -propertyname portalsuperuseraccount -propertyvalue account -url webappurl'.

Furthermore, there is the caveat:
The account should be any account that has Full Control access to the SharePoint databases but is not an application pool account. What have people done - create a special account?

After doing an extensive research i found solution as stated by Mirjam van Olst

http://sharepointchick.com/archive/2010/10/06/resolving-the-super-user-account-utilized-by-the-cache-is.aspx

SharePoint Installation steps

For installing Sharepoint on your local system please refer this blog

Over view on Installing Sharepoint 2007by dataSprings

Over view on Installing Sharepoint 2010by SharePoint Knowledge

Create WebPart Properties with Drop Down Items.

 
Dealare field

protected WeekDays _daysWeek = WeekDays.Sun;

/// Days of the Week to be appended in the Dropdown List

public enum WeekDays
{
Mon,
Tue, Web, Thur, Fri, Sat, Sun
};
/// Properties
[Personalizable(PersonalizationScope.Shared)]

[WebBrowsable(true)] [System.ComponentModel.Category("My Zone")]
[WebDisplayName("My DropDown Property")] [WebDescription("Get webpart properties
with DropDown")]
public WeekDays SelectedDay
{
get 
{ return _daysWeek; }

set 

{ _daysWeek = value; }
}

Comparison between Visual Studio & SharePoint Designer Workflows

Here i'm added Key differences between Custom Visual Studio and SharePoint Designer workflow.
----

Authoring:

Visual Studio: >>Full development environment with a graphical designer that produces a template which can be associated with multiple sites, lists, and content types

Designer:>> Wizard-driven interface that utilizes conditions and actions to produce a template that contains a set of declarative rules and is bound to a specific list

Custom .NET code :

Visual Studio: >>Yes

Designer:>> No

Types:

Visual Studio: >>Sequential, State Machine

Designer:>> Sequential only

Completed Workflow:

Visual Studio: >>Workflow markup file and code-behind files are compiled into workflow assembly.

Designer:>> Workflow markup, workflow rules, and supporting files are stored uncompiled in a hidden document library on the site and compiled on demand.

Debugging:

Visual Studio: >>Yes. Visual Studio 2005 debugging except for JIT exceptions.

Designer:>> No step-by-step debugging available

Deployment:

Visual Studio: >>Packaged as a SharePoint feature and deployed to the server by an administrator

Designer:>> Deployed automatically when workflow is completed

Association:

Visual Studio: >>Template must be associated with each and every list before it will be available

Designer:>> Association occurs at design time only

Workflow Forms

Visual Studio: >> Can use any forms technology, such as InfoPath 2007 or ASP.NET 2.0 forms

Designer:>> Automatically generates ASP.NET 2.0 forms, which can then be customized

Create Custom Activities and Conditions

Visual Studio: >>Yes

Designer:>> No. Must use a predefined set of activities and conditions.

Workflow Modification

Visual Studio: >>Executing workflows can be modified.

Designer:>> No modification is possible.

-------

click here For more details..


Special Thanks :Amit Pasalkar.

Form Based Authentication in SharePoint

(A Step Wise Implementation of FBA in SharePoint)
Here I’m adding this article to implement and extend the existing portal and have accessibility using Form Based Authentication. The article below has step wise implementation from scratch.
--
1. Create SQL Database: using Visual Studio 2005 command Prompt.

2. Use command : ASPNET_REGSQL

3. Please Select “ Configure SQL Server for Application Services”
4. Enter the Server Name Authentication and the Database Name

(Please Add the Database Name of our choice :ex-newFBADatabase)

5. Continue till > finish.
6. Check Newly Created Database containing necessary tables and store procedures


7. Extend your web application in any of the prescribed zone (Internet, intranet, extranet, Custom)

a. The original web application is at port 333 (in this case).
b. We have extended to port 332 as shown and selected the zone as extranet.


8. Now In visual Studio (VS) create a web site and add following entries in web.config file.

<!--SQL CONNECTION STRING-->

<connectionStrings>
<add name="FBAConnectionString" connectionString="Data Source=MYDATABASE;Initial Catalog=FBAUSERS; Integrated Security=True"/>

</connectionStrings>
<system.web>

<!-- Membership Provider For FBA -->

<membership defaultProvider="FBADemoMember">

<providers>

<add connectionStringName="FBAConnectionString" enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="true" applicationName="/" requiresUniqueEmail="false" passwordFormat="Hashed"
maxInvalidPasswordAttempts="5" minRequiredPasswordLength="1" minRequiredNonalphanumericCharacters="0" passwordAttemptWindow="10" passwordStrengthRegularExpression="" name="FBADemoMember"
type="System.Web.Security.SqlMembershipProvider,System.Web,Version=2.0.0.0,Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a" />

</providers>

</membership>

<!-- role provider For FBA -->

<roleManager enabled="true" defaultProvider="FBADemoRole" >

<providers>
<add connectionStringName="FBAConnectionString" applicationName="/" name="FBADemoRole"
type="System.Web.Security.SqlRoleProvider,System.Web,Version=2.0.0.0,Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a" />

</providers>

</roleManager >

9. Select website > ASP.NET configuration in VS

10. Select Security hyperlink



11. Create Roles as needed.






12. Create Roles (Inside Create or Manage Roles)



13. Create Users
14. Create Users(Inside Create Users)




(~) From Central Administration
15. Select Authentication Provider in Application Security in central admin



16. Select the Web Application and select the extended Zone for FBA.


17. Select Authentication Type :
a. FORMS,
b. Membership Provider Name : same membership defaultProvider as in web.Config
c. similarly for Role Manager Name: roleManager defaultProviderd.

Enable Anonymous Access optional (depends on requirement)

18.Now Update the Extended Web Application Web.Config Place beneath <>tag in both (original and extended web application) web.config file. Also place & beneath in conjunction with connection string as shown below.



19. Add the FBA User in the original portal/Web Application through People and Groups.


20. Add user in the Defined Role/Groups As you can observe here the user will be present as FBADemoMember:

21. Now Login in the extended Site.
22. Bingo- Welcome the FBA users.


Thanks…..

Active Directory & Sharepoint Users

Including User from Active Directory in sharpeoint internally had few process, However you need to be clear about the difference between SharePoint users used for security and Profiles. These are related.
First Profiles.
1. Moss is setup to import all the users in your AD domain as profiles into the SSP that you create. However, this action is not scheduled. Profiles will not be imported until you either do a manual import or setup the schedule for Full and incremental imports. This imparts no security rights to the user at all.
2. After the profiles have been imported. If a user is deleted in AD then after 3 successive full profile imports there profile will be deleted also. If deactivated their MySite will be cleaned up, but not their profile.

---

Authentication/Authorization (Assuming you are not using any kind of Forms Based Authentication)
1. SharePoint depends on Windows Authentication via IIS to establish the user's identity. (this happens completely external to SharePoint)
2. SharePoint checks the user's AD identity and group membership, as established in #1, to see what the user has the ability to do in SharePoint. You can successfully authenticate and still not gain access to SharePoint.
3. Security Access in SharePoint is dependent on the AD identity or an AD group of which the user is a member being added as a SharePoint user. Or the user or group may be added directly to a SharePoint group. This will allow the user to gain access to SharePoint resources.
4. If the access is through group membership then the user's identity will only be added to SharePoint when the user logs in and submits something to a document library or list. This adds their identity as a user, but doesn't directly re-associate them with specific rights. The rights are still gained through group membership. But they would now show up in the People and Groups list.
5. If the user's account is deactivated or deleted in AD their account in SharePoint is NOT deleted, but they won't be able to use it to access SharePoint anymore because AD won't be able to authenticate them so they'll never get to Authorization. If deactivated, you will still be able to click on their name attached to documents or list items and see their profile. If deleted clicking on these items will normally lead to an error page because the profile isn't there anymore.
6. Removing SharePoint users can be done programmatically, but it is a fairly involved process requiring walking each object in the FARM and looking for the user entries. There are 3rd party products that do this, but I don't normally recommend using them since you are destroying the history of the user in the system.
----

Special Thanks: Paul Stork.

.