New Learning Roadmaps for SharePoint 2013

A learning roadmap is a way of organizing content (articles, white papers, videos, blog posts, etc.) to provide a customized and optimized learning path for a technology, feature, product, or solution. Starting with prerequisites and then moving on to introductory, intermediate, and advanced learning goals, learning roadmaps enables a novice to ramp up quickly and an experienced technology person to build more expertise in a particular area.

My colleagues on the SharePoint IT pro writing team have been very busy publishing the following additional learning roadmaps:

·    Upgrade for SharePoint 2013

·    Virtualize SharePoint 2013

·    Windows PowerShell for SharePoint 2013

If you need to technically ramp up in any of these areas, take a look at these articles to understand the prerequisite knowledge and then dive in.

See Learning roadmaps for SharePoint 2013 for the complete list for SharePoint 2013.

See Learning Roadmaps Portal for the complete list across Microsoft products. To create your own learning roadmap, see the Learning Roadmap Template.

Reference: http://blogs.technet.com/b/tothesharepoint/archive/2013/02/25/new-learning-roadmaps-for-sharepoint-2013.aspx

Missing server side dependencies

We have done the migration from SharePoint Server 2007 to SharePoint 2010. After the successful migration, when we checked the HEALTH ANALYZER reports then we have seen the following errors:

Exception#1:

[MissingFeature] Database [WSS_Content_101] has reference(s) to a missing feature: Id = [fc5e2840-0b48-42eb-9ad7-076f5add58ad]. The feature with Id fc5e2840-0b48-42eb-9ad7-076f5add58ad is referenced in the database [WSS_Content], but is not installed on the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.

Exception#2:

[MissingWebPart] WebPart class [8d6034c4-a416-e535-281a-6b714894e1aa] is referenced [20] times in the database [SharePoint_AdminContent_8c793f3b-123c-4965-81b3-b7bbed64d8ae], but is not installed on the current farm. Please install any feature/solution which contains this web part. One or more web parts are referenced in the database [SharePoint_AdminContent_8c793f3b-123c-4965-81b3-b7bbed64d8ae], but are not installed on the current farm. Please install any feature or solution which contains these web parts.

Exception#3:

[MissingSetupFile] File [themes\THEME\alldaydefault_granite.gif] is referenced [4] times in the database [WSS_Content], but is not installed on the current farm. Please install any feature/solution which contains this file. One or more setup files are referenced in the database [WSS_Content], but are not installed on the current farm. Please install any feature or solution which contains these files.

Exception#4:

Assembly [Nintex.Workflow.Features, Version=1.0.0.0, Culture=neutral, PublicKeyToken=913f6bae0ca5ae12] is referenced in the database [WSS_Content], but is not installed on the current farm. Please install any feature/solution which contains this assembly. Remedy: One or more assemblies are referenced in the database [WSS_Content], but are not installed on the current farm. Please install any feature or solution which contains these assemblies.

Long series of messages, it’s very difficult to troubleshoot this all messages/exceptions in a single shot so I have targeted one exception: [Missing Feature]

As per the error message, we have the following details as follows:

Name of the database: WSS_Content_101

Feature ID: fc5e2840-0b48-42eb-9ad7-076f5add58ad

Site Collection Link: No Info

Site collection ID: No Info

Hmm...Really difficult to delete this feature if we don’t have a site collection links.

I think if we have a site ID/Link then it’s very simple to delete this feature but the problem is there are so many features which are throwing exceptions against the same database name so there might be so many site collections.

Resolution:

Million Thanks to Codeplex Team

These types of errors can be cleaned up using the SharePoint Feature Administration and Clean Up Tool on Codeplex: http://featureadmin.codeplex.com

Product Applies To:

SharePoint Server 2010

SharePoint Server 2013

SharePoint Foundation 2010

Important Note:

My Troubleshooting is still going on to find out the resolution for further exceptions. Will keep you posted regarding each and every exception. Thank you.

If you have any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues…

Thank you.

Feature enhancements in SharePoint 2013 than SharePoint 2010.

SharePoint 2013 general model remain same as SharePoint 2010 but has few platform level improvements and new capabilities like
• Shredded Storage
• SQL Improvements
• Cache Service
• Request Management
• Themes
• Sharing

In terms of Service Applications:
• New service applications available and improvements on existing ones
• Office Web Apps is no longer a service application
• Web Analytics is no longer service application, it’s part of search

Enterprise content Management
• Policies:
• Site-level retention policies compliance levels has been extended to sites
• Policies include Retention policy for sites and Team Mailbox associated with site
• Project closure and expiration policy
• Designed for managing discovery cases and holds
• Establishes a portal through which you can access discovery cases to conduct searches, place content on hold, and export content
• eDiscovery capabilities
• Support for searching and exporting content from file shares
• Export discovered content from Exchange and SharePoint
• Team folders
• Seamless integration of Exchange and SharePoint to provide best of both world and end user flexibility

Web Content Management
• Support the tools and workflows designers usage
• Variations & Content Translation
• Search Engine Optimization
• Cross Site Publishing
• Video & Embedding
• Image renditions
• Clean Urls
• Metadata navigation

Social
• Microblogging
• "Share content, links, and media"
• Follow people, sites, content, and conversations"
• Activity Feeds
• Provides a view into recent activity related to content, links, media, and people"
• Communities
• Community sites with self-service administration and moderation
• Modern community features such as achievements and reputation
• Discussions
• Modern discussion boards
• Blogs
• Client application integration
• "Categories, comments, and moderation "

Search
• New Search architecture with one unified search
• Personalized search results based on search history
• Rich contextual previews

Outlook 2007/2010: What is the character limit for a link to open?

As I just shared the Character limitation of URL in Sharepoint .

Outlook Hyperlink also has its own limitation

One of my user was copying a shortcut as a hyperlink in Outlook and it opened the site with a empty Document Library .

I Compared the shortcut url with the one sent as hyperlink in the outlook and found that the one sent to the users is not a complete url/link . so thought their might be some limitation to that too .   

Based on my research, this is what i found

Outlook 2013 – Seems no limitation.

Outlook 2010 – 1033 characters

Outlook 2007 – 1033 characters

Outlook 2003 – 256 characters

Readers - if you find any descripancies in the numbers (limitations ) please comment so that we can keep this post updated . 

URL path length restrictions (SharePoint Server 2010)

I have come across so many users who are not able to create or upload files after certain stage and it says

"The specified file or folder name is too long"

This is Limitation is in Sharepoint 2007 and continues in 2010.

The total length of a SharePoint URL equals the length of the folder or file path, including the protocol and server name and the folder or file name, plus any parameters that are included as part of the URL. The formula is as follows:

• URL = protocol + server name + folder or file path + folder or file name+ parameters

For example, the following is a typical URL path to a file stored in Microsoft SharePoint Server 2010:
http://www.contoso.com/sites/marketing/documents/Shared%20Documents/Promotion/Some%20File.xlsx

When you go to the site and open the file with Microsoft Office

http://www.contoso.com/sites/marketing/documents/_layouts/xlviewer.aspx?id=/sites/marketing/documents/Shared%20Documents/Promotion/Some%20File.xlsx&Source=http%3A%2F%2Fwww%2Econtoso%2Ecom%2Fsites%2Fmarketing%2Fdocuments%2FShared%2520Documents%2FForms%2FAllItems%2Easpx%3FRootFolder%3D%252Fsites%252Fmarketing%252Fdocuments%252FShared%2520Documents%252FPromotion%26FolderCTID%3D0x012000F2A09653197F4F4F919923797C42ADEC&DefaultItemOpen=1

The limitations In this section apply to the total length of the URL path to a folder or a file in SharePoint Server 2010 but not to the length of any parameters. Also, these limitations apply only to un-encoded URLs, not to encoded URLs. There is no limit to encoded URLs in SharePoint Server 2010. The limitations are the following:

• 260 Unicode (UTF-16) code units – the characters in a full file path, not including a domain/server name.
  
• 256 Unicode (UTF-16) code units – the characters in a full folder path, not including the file name and the domain/server name.
  
• 128 Unicode (UTF-16) code units - characters in a path component, that is, a file or folder name.
  
• 260 Unicode (UTF-16) code units – the characters in a full path, including a domain/server name for use with Office clients.
  
• 256 Unicode (UTF-16) code units – the characters in a full path including the domain/server name, for use with Active X controls.

Reference :

http://technet.microsoft.com/en-us/library/ff919564(v=office.14).aspx#about

You receive a "The specified file or folder name is too long" error message