Archive

Archive for the ‘administration and configuartion’ Category

ListingSummary webparts don’t work after upgrading to SharePoint 2010

April 5, 2012 2 comments

If you upgrade your portal from  SharePoint Point 2003 to SharePoint Server 2010.you will face many issues , especially if you are using Listing Summary web parts in SharePoint Portal 2003, because when you upgrade from SharePoint 2003 to Microsoft SharePoint Server 2007 , you find that the listing summery web part is obsolete now in MOSS 2007 and it’s replaced by Content Query Webpart

This following article shows the listingsummary class as obsolete in 2007.

http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.portal.webcontrols(office.12).aspx

also, if you upgrade to SharePoint Server 2010 and your content Database still have references to this web parts type. You will get an exception as the following

“Web Part Error: A Web Part or Web Form Control on this Page cannot be displayed or imported. The type could not be found or it is not registered as safe.”

You can solve this issue as the following :-

1-      In MOSS 2007 Environment, export this type of webparts

2-      Edit exported file, you will find a reference as below

Microsoft.SharePoint.Portal.WebControls.ListingSummary, Microsoft.SharePoint.Portal, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c

3-      Delete above reference , and add the following reference

Microsoft.SharePoint.Publishing.WebControls.ContentByQueryWebPart, Microsoft.SharePoint.Publishing, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c

And import it in the same place in SharePoint Server 2010

Apply  above steps to all webpart of this type, then you will find that your portal woring fine

SharePoint Server 2010 Cannot Load Homepage After upgradeing from MOSS 2007

April 5, 2012 9 comments

We have faced an issue while upgrading SharePoint Portal 2003 to SharePoint Server 2010 .

In this case  we have 2 pahse of upgrade , 1st  phase is upgrading from SharePoint Portal 2003 to Microsoft Office SharePoint Server 2007, then 2nd phase in upgrading from Microsoft Office SharePoint Server 2007 to SharePoint Server 2010 .

As we know, there were a huge  differences between Microsoft Office SharePoint Server 2007  version and SharePoint Portal 2003 version in Architecture Information level such as master pages , page layouts , Shared Service Provider ,..  plus there many features added to MOSS 2007 Version such as InfoPath Forms, BCD,..

So when we upgrade from SharePoint Portal 2003 to MOSS 2007 , many  classes and web parts were replaced with a new classes in MOSS 2007 such  as HomePage this class was used in SharePoint Portal 2003 and it’s deprecated in MOSS 2007 ( a reference to this  class in home page  was the reason  in Loading Home Page Exception after upgrading to SharePoint Server 2010)

In our case , we upgrade 1st Phase successfully without any issue except some adjustment in home page UI , the portal after is working fine and all sites and inner page  also.

Moving to SharePoint Server 2010 was a problem , because as I mentioned above many classes come from SharePoint Portal 2003  is deprecated in Moss 2007 and  there are no references to them in SharePoint 2010 Dlls. As we doing an upgrade , the references to these classes are still exist in content DB, so an exception has occurred in loading home Page and inner pages.

So , in 2nd phase of Upgrade ( Upgrade Moss 2007 to SP 2010 ) , below Exception appear in loading Portal home Page

Could not load type ‘Microsoft.SharePoint.Portal.WebControls.HomePage’ from assembly ‘Microsoft.SharePoint.Portal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c’ “

This issue was ‘Microsoft.SharePoint.Portal.WebControls.HomePage’ is obsolete, and it is no longer existing in the ‘Microsoft.SharePoint.Portal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c’, however, it is existing in ‘Microsoft.SharePoint.Portal, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c’.
In this case, it seems you are using the ‘Microsoft.SharePoint.Portal.WebControls.HomePage’ control in the SharePoint 2007(I mean Microsoft Office SharePoint Server(MOSS) 2007). After upgrading, the SharePoint 2010 tries to load the ‘Microsoft.SharePoint.Portal.WebControls.HomePage’ from the assembly with version 14.0.0.0. However, it is not existing. That is what the error means.

So to fix the issue, you need to remove the ‘Microsoft.SharePoint.Portal.WebControls.HomePage’ from SharePoint 2007, and then upgrade the site again.

SharePoint 2010 Calendar features

April 5, 2012 2 comments

SharePoint 2010 introduce group of enhanced features in Calendar , here I’m trying to cover all these features.

One of the most popular feature is the Ribbon interface , where you can access most of calendar functionality easier than the need to drill down to the list.

 

Let us display list of feature with some screen shots

1-     Scope

This feature give us the ability of displaying the calendar in Month, Week, or Day View.

 

2-     Expand

If you have multiple appointment or events in specific day , and you want to display all these events instead of summery view, just you use ExpandAll or CollapseAll

3-     Calendars Overlay

The Calendars Overlay feature in SharePoint 2010 allows you to display items from one or more calendars in the same calendar view.

 

 Let us display an example for this feature, say you want to display exchange calendar events  here in SharePoint Calendar .

a-      Open the SharePoint calendar  –> Calendar Tools –> Calendar Overlay –>New Calendar,

 

b-     Fill in the :

  • Name: Give a name to this calendar
  • Type: Select Exchange
  • Outlook Web Access URL: the OWA url of your organization.
  • Exchange Web Service URL: which can be determined as follows:

If your OWA URL is https://exch.contoso.com/owa, then the Exchange web Service URL would be https://exch.contoso.com/ews/exchange.asmx

(in other words, from the OWA URL , remove the trailing “owa” and add “ews/exchange.asmx”)

          

c-      The result view will be as the following

4-     Manage views

You can create or update views for the calendar , also you can create new column

 

5-     Share & Track

Here , users can subscribe in this calendar to get notifications if any events added also, they can setup RSS feature also from the same tab

 

6-     Connect & Export

If you want to synchronize SharePoint calendar with outlook  calendar , just click on ” connect to Outlook”, also we can export to Excel, and to synchronize SharePoint calendar with Access

7-     Customize List

You can customize list or list forms page using SharePoint designer or InfoPath.

 

8-     Settings: List Settings, Permissions, and Workflow Settings

 

How to block search engines from indexing your SharePoint Site

March 15, 2012 4 comments

If you want to block search engines from indexing your site you need to create a robots.txt file and place it in the root of your root site.

What is a Robots.txt

Robots.txt is a text (not html) file placed in the root of your site to tell search robots which pages should and should not be visited/indexed. It is not mandatory for search engines to adhere to the instructions found in the robots.txt but generally search engines obey what they are asked not to do.

It is important to note that a robots.txt does not completely prevent search engines from crawling your site (i.e. it is not a firewall) and the fact that you may have a robots.txt file on your site is something like putting a note “Please, do not enter” on your unlocked front door. Put simply, it will not prevent thieves from coming in but the good guys will not open to door and enter.

It goes without saying therefore, if you have sensitive data, you cannot rely 100% on a robots.txt to protect it from being indexed and displayed in search results.

The location of robots.txt is very important. It must be in the main directory because otherwise user agents (search engines) will not be able to find it. They do not search the whole site for a file named robots.txt. Instead, they look first in the main directory (i.e. http://www.sitename.com/robots.txt) and if they don’t find it there, they simply assume that this site does not have a robots.txt file and therefore they index everything they find along the way. So, if you don’t put robots.txt in the right place, don’t be surprised that search engines index your whole site.

Creating a Robots.txt

  1. Launch Notepad
  2. Put the following in your robots.txt file:

User-agent: *
Disallow: /

  1. Save the file as: robots.txt

Adding a robots.txt file to the root of your public anonymous SharePoint site.

  1. Open up your root site in SharePoint Designer.
  2. Double Click the folder All Files
  3. Drag and drop the newly created robots.txt to the All Files folder.
  4. Exit SharePoint Designer.

Alternatively you can create the robots.txt from within SharePoint Designer itself.

To ensure the file is accessible to search engines go to your site URL adding “/robots.txt” at the end.

Example: http://www.sitename.com/robots.txt

You should see the contents of your robots.txt file displayed in the browser.

refernces:-

http://www.agileit.com/Blog/Lists/Posts/Post.aspx?Id=5

http://sharepointingitout.blogspot.com/2011/06/sharepoint-2010-adding-robotstxt.html

http://blog.drisgill.com/2009/01/adding-robotstxt-to-sharepoint.html

SharePoint 2010 Services

March 14, 2012 Leave a comment

Visio Services and SharePoint 2010

March 13, 2012 1 comment

In SharePoint 2010, Microsoft has taken the Visio Services to the next level by allowing rendering of Visio diagrams and charts within the browser. Users can now use the out of the box Visio web parts to render the Visio diagrams and bring in the seamless integration of business intelligence between Visio, SharePoint and back end data.

Let me show you an example:

Lets create a simple Visio diagram which fetches values from external data:

 

This diagram is using the SupplyChain SQL database and the Suppliers table:

I can now save this as a Visio Web Diagram (.vdw) and upload to a document library in my Business Intelligence site.

Now, I can go to my dashboard and insert the Visio web diagram using the Visio Web Access web part.

This will add the Visio Web Access web part to the dashboard page where you can specify the Visio file to render:

Below is the rendered Visio web diagram in the web part:

 

You can see that the external data is also fetched in the diagram!

Notice there is also an option to enable refresh!

You can pan and also zoom into the diagram using the zooming controls (its very interactive!):

You can configure some of the default behaviour of the web part from its web part options pane:

The Real Deal

Lets go to SQL and change the Assembly Time value for the Bevel Assembly from 45 to 55

Lets go back to our dashboard page and refresh the Visio web diagram:

We now have the updated value!

Configuring Visio Services

The Visio Services is managed by the Visio Graphics Service service application (Central Administration | Application Management | Manage Service Applications)

references :

http://blogs.msdn.com/b/visio/archive/2009/10/20/announcing-sharepoint-2010-and-visio-services.aspx

http://www.chakkaradeep.com/post/SharePoint-2010-Visio-Services.aspx

http://www.wictorwilen.se/Post/Creating-SharePoint-2010-workflows-with-Visio-2010.aspx

SharePoint 2010: Ten points to pay attention for a good infrastructure

March 13, 2012 2 comments

#1 Limit your SQL

When you install SharePoint 2010 on a complete mode with a SQL SERVER 2008R2, there is an option on the properties of the server, that you can limit the RAM usage. If you don’t limit the usage, it will use 2.1 petabytes.

The default value for SQL Server 2008R2 Maximum Server Memory setting is 2,147,483,647 MB. Therefore, SQL Server will use all available memory for its own use.

1

 

 

#2 Use different users for your environment

When you will configure Web Applications, Service Applications … Do not forget to create for each of these Applications a user.

The main raison is that when this service or user will get an error it will be easy for us to know with service has failed. (EVENT VIEWER)

Second raison is that on IIS7, the application pool names are getting GUID. So we can have more information just on regarding the username:

1

 

If we had the same user for each service, we could never know which GUID was for witch Service.

(1 first) The e6266ed1faa2406cbae0bbbf33f6e4ba is my Access Service..

#3 Use a Warm up Script

Yes, everybody knows SharePoint is slow, and in many cases it’s extremely slow. But there are many solutions therefore. The best solution is to use a WARM UP script.

It will compile everything, and your SharePoint will be very faster.

Download link: http://www.gokanozcifci.be/subsite/warm-up-script-for-sharepoint-2010.html 1

Download link: http://spwakeup.codeplex.com/ 1

 

 

#4 Disable unused warnings on SharePoint

The SharePoint Health Analyzer detected a condition requiring your attention. Drives are at risk of running out of free space.

This is an example of a BETA warning on SharePoint; it can be disabled on Review Job Definitions. Do the same of each job that you think that’s unusual for you.

1

 

 

#5 SQL BROWSER

Start your SQL BROWSER service on services.msc on your SQL Server. It is a very useful tool that helps you to see each warning, error … on the SQL Server

It will show you more information about the login failure’s with an explicit SQL ID.

 

1

 

#6 Service Connections

When you will create a new WEB APPLICATION SharePoint will attach each service on your WEB APPLICATION. Even the one that you don’t need, so in place of using de “default” value use the custom value on Central Administration

1

 

#7 Made a SHORTCUT 14/

Made a Shortcut to the desktop of you 14 document and it will be easier to check your logs and many other things.

1

 

 

#8 DisableloopbackCheck

When you use the fully qualified domain name (FQDN) or a custom host header to browse a local Web site that is hosted on a computer that is running Microsoft Internet Information Services (IIS) 5.1 or a later version, you may receive an error message that resembles the following:

HTTP 401.1 – Unauthorized: Logon Failed

This issue occurs when the Web site uses Integrated Authentication and has a name that is mapped to the local loopback address.

Download Link: http://www.gokanozcifci.be/subsite/DisableLoopbackCheck.html 1

 

 

#9 Use a PowerShell Script for downloading prerequisites.

SharePoint prerequisites installer will install “everything” that he thinks that it will be ever used. But in many of cases it’s not true. Take this script modify it and download the applications that “you” need..

Download Link: http://www.gokanozcifci.be/subsite/download-prerequirements-sharepoint-2010-powershell.html 1

1

 

#10 don’t use port 80 for Central Administration

When you will install SharePoint Server/Foundation, it will ask to give a Port number for Central Administration; give everything but don’t give 80 (http protocol). So you can hide your Central administration from possible attacks. It will give a standard IIS page.

1

reference : http://www.gokanozcifci.be/subsite/points-to-pay-attention-for-sharepoint-2010.html