04 August, 2012

An unexpected error has occurred.

You have a file that has a long file name. When you try to upload this file to a picture library in Microsoft SharePoint Server 2010, you receive the following error message:

An unexpected error has occurred.

Cause:
This problem occurs because the file name exceeds the limit of 125 characters.

Resolution:
To work around this problem, reduce the file name to less than 125 characters, and then re-upload the file.

Please let me know in case of any queries/questions, Thank you.

This document was checked out to your local drafts folder, but the local copy could not be checked in to the site, close any application that is editing the document and try to check in again, or discard the checkout


Problem Description:
Unable to check in large excel file ( 80 mb ) in document library http://amol.sharepoint.com/sites/. The operation fails with the following error:

"This document was checked out to your local drafts folder, but the local copy could not be checked in to the site, close any application that is editing the document and try to check in again, or discard the checkout."

The same behavior is observed on other site collections as well.

Probable cause:
Missing Office Filter packs 

Resolution:
Install the Office Filter Pack 2.0 which can be downloaded from:

Microsoft Office 2010 Filter Packs

The Microsoft Filter Pack is a single point-of-distribution for Office IFilters. IFilters are components that allow search services to index content of specific file types, letting you search for content in those files. They are intended for use with Microsoft Search Services (Sharepoint, SQL, Exchange, Windows Search).

Install this product if you want to search for content in the file types listed below.

The Filter Pack includes:

Legacy Office Filter (97-2003; .doc, .ppt, .xls)
Metro Office Filter (2007; .docx, .pptx, .xlsx)
Zip Filter
OneNote filter
Visio Filter
Publisher Filter
Open Document Format Filter

Please let me know in case of any queries/questions.
I would be more than happy to help you as well as resolves your issues, Thank you

02 August, 2012

Manage Access Requests in SharePoint 2010

Guys- we are already aware that manage access request means when a person gets access denied while accessing any SharePoint site then there is one link on the access denied page called as “request access” by which we can request the administrator to grant the access for the mentioned site.
Here is the screenshot that I am talking about:

This is pretty much similar in SharePoint 2007 also and same feature is continued in SharePoint 2010 also.
What we do in SharePoint 2007 for such issues? Where exactly we need to change request access ownership?
Here are the detailed steps:
·         Open the SharePoint site
·         Site actions
·         Site settings
·         Advanced permissions
·         Settings
·         Access requests

Note: same is applicable in SharePoint 2010 also but I am giving you the detail screenshot to avoid the confusion.

Please let me know in case of any queries/questions so that we can discuss and proceed further towards the resolution. Thank you

01 August, 2012

SharePoint 2010: 'Send-to' option to Record center from a source site collection does not work on a Claims-based web application

After setting up a Send-To connections (via central administration) to route records from a site collection to a record center on a web application that only supports claims based authentication, the send-to functionality does not work and fails with an 'access denied' error.

Possible Cause:
do not know the root cause at this time but i am suspecting that this is desired behavior and we can straight way say that-> 'Send-To' connections do not support Forms-based Claims Authentication.

Resolution:
There are two possible ways to resolve this issue:

1. Configure a zone that does not use Claims Authentication for the 'Send-To' destination Web Application. This zone needs Windows authentication enabled because service accounts, which are Windows accounts, perform the sending.

2. Use multi-mode authentication for the destination Web Application.

If you have any different views then please let me know so that we can share with SharePoint Communities and come to a final point. Thank you.