SharePoint 2010: Site Collection Administrator does not receive storage quota alerts

To help manage site and server resources, an administrator of the local server computer can specify quotas that are used to limit the amount of storage available on a site and the number of users that are added to a site collection. These quotas help to ensure that one site cannot deplete so many resources that other sites can no longer function.

The server administrator can use locks to stop sites from exceeding the storage quota limits, and to block all users from accessing a site if necessary.

A user is a SharePoint Site Collection Administrator. The Site Collection reaches its quota, and has passed the warning limit. However, the user does not receive a warning email message. 

Probable causes:

This issue occurs because the warning email message only goes to the Site Owner.

Resolution:

To resolve this issue, validate that the user is not the Site Owner. To do this, follow these steps: 

1)      Log on to any server of the farm. 

2)      Open Central Administration. 

3)      Application Management, and then

4)      Click View All Site Collections.  

5)      Find the site in question.  

6)   Notice the "Primary administrator." 

The primary site collection administrator will be the user who receives quota alerts. If the customer has to change this, we can run the following cmdlet:

stsadm -o siteOwner -url <Site Collection> -ownerLogin <Domain\Alias>

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

People Picker control gets spell checked on a custom layout page: SharePoint 2010

Happy Friday to all of you :)

People Picker is configured at the zone level for a farm by using the Stsadm setproperty operation. By configuring the settings for the control, you can filter and restrict the results that are displayed when a user searches for a user, group, or claim. Those settings will apply to every site within the site collection.

Problem Description:

While editing a custom layout page that contains a people picker control, you spell check the page. The spell check returns a large number of errors on the people picker control.

Probable Causes:

During the page editing process, SharePoint looks for text that are spell checking candidates. The text is included unless the control is explicitly marked for exclusion by a non-public attribute or by having its class set to 'ms-spellcheck-false'.

The people picker control fails both tests and its text, in xml format, is included in the spelling chunks.

Resolution:

Add a small custom code to override the above behavior and exclude the control from the spell checking. Follow the steps listed below:

1.   Launch SharePoint Designer and from the File Menu, choose Sites.

2.   Open your site and from the site objects menu on the left, select Page Layouts.

3.   From the list of page layouts on the right panel, right click on the page with the issue (the one containing the people picker control) and select “Edit File in Advanced Mode”.  

Note: If the page is not checked-out, you will get a prompt for it. Click ‘Yes' for it.

-  For the next steps, refer to the following code example:
  
Step 1

On the HTML that defines the control, add an ID property if one does not exist already. You will need this ID for the next step. Your page should resemble something like this:

<table>
    <tr>
        <td>
            Contact:<SharePointWebControls:UserField FieldName="Publishing Contact" runat="server" ID="PeoplePicker1">
        </td>
    </tr>
</table>

Step 2

before the last statement on the page (the </asp: Content> tag), add the following script:

 <script type="text/javascript">
_spBodyOnLoadFunctionNames.push("OverrideSpelling");

function OverrideSpelling(){ 
   var $fld_in = document.getElementsByTagName('input'); 
   var $fld_tx = document.getElementsByTagName('textarea'); 

   for( $i = 0; $i < $fld_in.length; $i ++ ) {
      var $inputName = $fld_in[$i].getAttribute('name');   
      if($inputName.indexOf('PeoplePicker1') != -1) {
         $fld_in[$i].className = 'ms-spellcheck-false';   
      }
   }

   for( $i = 0; $i < $fld_tx.length; $i ++ ) {
      var $inputName = $fld_tx[$i].getAttribute('name');   
      if($inputName.indexOf('PeoplePicker1') != -1) {
         $fld_tx[$i].setAttribute("excludeFromSpellCheck","true");   
      }
   }
}
</script>

1.   Note the bold value on the function argument. You will need to use the same ID that was used on the control declaration.

2.  
Save the page and try the spell check now.

3.   The page should now exclude the people picker control from the spell check.

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 :) Happy SharePoint to all of you :)

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

http://www.microsoft.com/en-us/download/details.aspx?id=17062

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

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