SharePoint 2010 – SharePoint 2010 sp1 download is here.

יום רביעי, יוני 29, 2011

Many people lost patience for waiting when SharePoint 2010 SP1 will be released. Now I can shout for all people SharePoint 2010 SP1 is here. You can download it from those links. Service Pack 1 for SharePoint Foundation 2010 (KB2460058) and Service Pack 1 for Microsoft SharePoint Server 2010 (KB2460045) In this link you can find white paper for SharePoint 2010 SP1. Service Pack 1 (SP1) for Microsoft SharePoint Foundation 2010 and Microsoft SharePoint Server 2010 (white paper)  Install and Enjoy now.  
אין תגובות

SharePoint 2010 – Enable Session State in SharePoint 2010

יום שני, יוני 20, 2011

When you want to use Session object inside C# or VB.NET Code in SharePoint pages and Web Parts, you receive such error message: Session state can only be used when enableSessionState is set to true, either in a configuration file or in the Page directive. Many people wrote 3 steps, that you need to do for enabling Session State inside SharePoint: 1. Change enableSessionState in page section in system.web inside web.config for your Web Application. <pages enableSessionState="true" enableViewState="true" enableViewStateMac="true" validateRequest="false" pageParserFilterType="Microsoft.SharePoint.ApplicationRuntime.SPPageParserFilter, Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" asyncTimeout="7"> 2. Add Session Module in modules section in system.web inside web.config for your Web Application <modules runAllManagedModulesForAllRequests="true"> <remove name="Session" /> <add...
אין תגובות

SharePoint 2010 Upgrade Solution – Upgrading from SharePoint 2007 to SharePoint 2010 Part 4 – Handle Missing Features.

יום ראשון, יוני 12, 2011

This post is describe how to handle problem with "Missing Site Features". You received for example such message inside PreUpgrade Report. The following feature(s) are referenced by the content, but they are not installed on the web server Name = Unknown, Feature id = 0fa6a8ce-3f64-4d44-8419-69942b3e0471, Reference count = 3, Scope = Web, Status = Missing You need run stsadm.exe command  for locate where this site features is used. cd C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN stsadm -o enumallwebs -includefeatures > c:\migration\features.txt this command create text file that  contain all site references for site feature in your   Sharepoint Enviroment, but isn't enough from this file you can't handle missing feature.   For...

SharePoint 2010 Upgrade Solution – Upgrading from SharePoint 2007 to SharePoint 2010 Part 3 – Handle Missing Event Receivers

יום שני, יוני 6, 2011

This post is describe how to handle problem with "Missing Event Receivers". You received for example such message inside PreUpgrade Report. The following event receiver assembly(s) are referenced by the content, but they are not installed on the web server Assembly = ListEventReceiver.TravelPortal, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c033f84e3e5850b7, Count = 6, Status = Missing. You need run stsadm.exe command  for locate where this event receiver is used. cd C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN stsadm -o enumallwebs -includeeventreceivers > c:\migration\eventRec.txt this command create text file that  contain all site references for event receivers in your   Sharepoint Enviroment, but isn't enough for this file you can't know where specific event   receiver is...

SharePoint 2010 Upgrade Solution – Upgrading from SharePoint 2007 to SharePoint 2010 Part 1

In this series of posts I discuss about Upgrading from SharePoint 2007 to SharePoint 2010. The first step before starting upgrading to SharePoint 2007 is installing SP2 and October 2010 CU for SharePoint 2007. After installing this SP2 you receive possibility to run tool for determinate problems in current SharePoint 2007 installation. To run this tool, open command line prompt by Start->Run->cmd and press Enter. Navigate to SharePoint Root Installation Folder for example: cd C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN and press Enter. After this run this command line: stsadm -o preupgradecheck Pre-upgrade scanning tool create an XML log file and a text log file, these log...

SharePoint 2010 Upgrade Solution – Upgrading from SharePoint 2007 to SharePoint 2010 Part 2 – Handle Missing Web Parts

יום חמישי, יוני 2, 2011

Upgrade proccess from SharePoint 2007 to SharePoint 2010 include running preupgradecheck tool, this tool create report, that contain potential issues that can prevent upgrading from SharePoint 2007 to SharePoint 2010.  The one from those issues is missing Web Parts in you environment, those web part may be missing by many reason, for example: uncorrent uninstall some web parts solution, previous migration proccess from SharePoint 2003 and etc.. For example you can receive such report. Id = 8c21d9e7-b788-0a69-b08b-d97f59ab5b93, Type = Unknown, Reference = 28, Status = Missing Id = c9cc33de-c985-ef33-f124-ce539263d419, Type = Unknown, Reference = 1, Status = Missing Id = a7563a72-5661-4571-de0c-b2bc1de8718d, Type = Unknown, Reference...

SharePoint 2010 Upgrade Solution – Upgrading from SharePoint 2007: tools, tips and tricks

יום שלישי, מאי 31, 2011

Upgrading Process from SharePoint 2007 to SharePoint 2010 is depends on many factors and elements that are used in SharePoint 2007 environment, such as web parts, features, event receiver and site templates. In this article I try to describe and explain how to fixed unespected problems that you meet in upgrading process. The first step in upgrading process is checking you SharePoint 2007 environment. This page is describe this step:  Using preupgradecheck tool that create pre upgrading report, in this report you need handle some problematic issues. Next posts will describe how to solve them.  1. Handle Missing Web Parts 2. Handle Missing Event Receivers. 3. Handle Missing...

SharePoint 2010 – Content Query Web Part – Open Links in new window

יום שלישי, מאי 3, 2011

Content Query Web Part is very useful Web Part that allow show relevant data from defferent sources by definition special filter conditions.  But when relevant data is rendered all link are opened in the same window. You can change this behavior by changing ItemStyle.xsl that placed in "Style Library" library inside "XSL Style Sheets" folder. You can navigate to this library: http://servername/Style%20Library. For changing ItemStyle.xsl file, download it to local disk. For example if you use "Default" style inside Content Query Web Part, you can duplicate  xsl:template part with name "Default"  and change style name for example "DefaultNewWindows". Inside this template you can add new attribute"target"...

SharePoint 2010 – SharePoint Alerts don't work after upgrading from SharePoint 2007 – Fix This Problem by C# Code

יום שני, אפריל 11, 2011

After upgrading to SharePoint 2010 from SharePoint 2007 or moving SharePoint 2010 to another server, Old SharePoint Alerts stop working and only new created alerts are worked. I found microsoft support arcticle http://support.microsoft.com/default.aspx?scid=kb;en-us;936759 and one blog for SharePoint 2007 with explanation: http://blogs.msdn.com/b/skelley/archive/2007/06/18/alerts.aspx I combined two those arcticles in one and build console application based on 64bit Target inside VS2010. static void Main(string args)        {            string strNewSiteCollection = string.Empty;            string strOldSiteCollection = string.Empty;            // First (and only) argument is the URL to the Site Collection            if (args.Length > 1)            {                strNewSiteCollection = args;                strOldSiteCollection = args;                try                {                    using (SPSite spsitecol = new SPSite(strNewSiteCollection))                    {                        using...

SharePoint 2010 – Personal View for page is corrupted – Personal View for page returns error.

יום ראשון, אפריל 10, 2011

User can modify his Personal View for specific page if this personalization is defined for specific Web Part Zone. User can put new  Web Parts to his personal view, move existing Web Part to another Web Part Zone. If user put corrrupted Web Part to his pesonal view, this personal view becomes corrupted. User can not navigate to this pesonal view and this page too. To solve this problem this user need to navigate to special Web Part Maintenance page and remove corrupted Web Parts. For example: If your site url is http://portal/DepartmentSite and your corrupted page is ContentPage.aspx and this page is placed inside Pages...