SharePoint 2010 SP1 Installation Issues

The following are issues that you may experience when you install these service packs:

  • Before you install the SP1 packages, make sure that you have sufficient disk space. For caching, the packages may require up to four times their file size in remaining disk space during installation.
  • You must restart the computer at the end of the installation process.
  • If Office Web Apps will be used in a mixed version environment, where Office Web Apps has SP1-or-later applied while SharePoint Server 2010 remains on the RTM version, you must install the following two updates before you install SP1 for Office Web Apps:
  • Install the service packs in the following order on every server in the farm:
    1. Service Pack 1 for SharePoint Foundation 2010
    2. Service Pack 1 for SharePoint Foundation 2010 Language Pack (if applicable)
    3. Service Pack 1 for SharePoint Server 2010
    4. Service Pack 1 for SharePoint Server 2010 Language Pack (if applicable)
  • After you install Service Pack 1 you must run the SharePoint 2010 Products Configuration Wizard or the psconfig –cmd upgrade –inplace b2b -wait command one time on every server in the farm. This step updates the farm to the latest version and is required in order to have full SharePoint functionality. If you do not run the wizard, the farm will run with reduced capacity. For example, Search will not be able to index content.
  • You must restart the User Profile Synchronization service after installing Service Pack 1. For more information about how to start the service, see the “Start the User Profile Synchronization service” section of the following Microsoft website:

    Configure profile synchronization (http://technet.microsoft.com/en-gb/library/ee721049.aspx#StartUPSSProc)

 

  • After SharePoint Server 2010 SP1 is installed, the Workflow feature is disabled when a new site collection is created. To use the Workflow feature in a new site collection, enable it in the Site Collection Settings page.
  • After you install SharePoint Foundation 2010 SP1 and SharePoint Server 2010 SP1, we strongly recommend that you install the install the June 2011 Cumulative Update refresh package. The June Cumulative Update includes several important security and bug fixes that are not included Service Pack 1. For more information about these updates, click the following article numbers to view the articles in the Microsoft Knowledge Base:

    2536601 (http://support.microsoft.com/kb/2536601/ ) Description of the SharePoint Foundation 2010 cumulative update package (SharePoint Foundation server-package): June 30, 2011
    2536599 (http://support.microsoft.com/kb/2536599/ ) Description of the SharePoint Server 2010 cumulative update package (SharePoint server-package): June 30, 2011

 

Resolution – Walk Through

  • Launch an elevated (Run as Administrator) SharePoint 2010 Management shell from start, All Programs, Microsoft SharePoint 2010 Products, SharePoint 2010 Management Shell.
  • Once the shell opens, type the following command and press enter:
                  (get-spserver $env:computername).NeedsUpgrade

4162.image_5D7A9422.png

Example: Running above command with true value

If the output is false

No further action is needed.

If the output is true

To complete the SharePoint service pack process you need to follow the same steps to complete PSCONFIG after a SharePoint update.

In order to update the SharePoint databases, you must manually run the PSconfig utility as follows:

      1. Open an Administrative command prompt.
      2. Change directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
      3. Run PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures


Please Note

  • The SharePoint site will be inaccessible while the command is running. It is best to run the command after business hours during a scheduled maintenance period.
  • The amount of time the command takes to run will vary on the size of the database and the speed of the machine.
  • On a reference machine with 8 logical processors, 32GB of RAM and a 2GB content database, the command took approximately 5 minutes to execute.
Advertisements

Send Document As An Email Attachment SharePoint 2010

 

This feature is particularly useful when you store document in SharePoint and you need to send them to people outside of your organisation that do not have permission to access your SharePoint sites…

Download the feature (WSP) file from CodePlex: http://sendemailsp2010.codeplex.com/

After deploying this solution, a new button “Send Document” will appear in the ribbon interface. Just select the document (one at a time) by clicking the check box before the document title and click on Send Document button. As soon as you click this button an email form will pop up which allows you to provide values for “To”, “Cc”, “Subject” and “Email body”. Just fill in the details and click send email. You document will be attached to this email and will be sent to the appropriate user.

Also note that as a part of this installation, a send document configuration list will also get deployed on the root site which allows you to add users to whom you want to give rights to send document as an attachment.

System requirements
SharePoint 2010 must be installed. There are no special requirements on the edition of SharePoint

On The client

Following requirements must be fulfilled on the Client in order to use the feature:
1. Outlook is installed on the computer and the computer is located in the same domain as the server.
2. This feature is to be used only with Internet Explorer, as the ActiveX-Technology is not supported by other web browsers.
3. In the security settings of Internet Explorer must be activated following settings: “Initialize and script ActiveX controls not marked as safe for scripting” and “Automatic logon with current user name and password”.
For the activation of settings, following steps must be carried out:
3.1. Click on Tools in the task menu at the upper border of the Internet Explorer
3.2. Click on “Internet Options” from dropdown-menu
3.3. In the internet options click tab ”Security”
3.4. Choose the zone ”Trusted sites”
3.5. Click the button “Sites” and insert your SharePoint-Site to “Trusted sites”.
3.6. Click the button “Custom level”
3.6.1. Activate the setting “Initialize and script ActiveX controls not marked as safe for scripting”
3.6.2. Activate the setting “Automatic logon with current user name and password”

Installation
The installation can be divided in to the following steps:
1. Adding “Communardo.SendSharePointDocumentsAsEmailAttachment.wsp” solution to the SharePoint Farm solutions. There is no possibility to do it by means of user interface. Thus, prompt-tool “stsadm” must be used. Following command should be run under administrative rights on the server (before that save the file “Communardo.SendSharePointDocumentsAsEmailAttachment.wsp” in any directory, e.g. under C:/Communardo).
image

2. Open SharePoint 2010 Central Administration and click the link “System Settings” and then the link “Manage farm solutions”

image

3. In the list of all SharePoint solutions click “Communardo.SendSharePointDocumentsAsEmailAttachment.wsp” and then on “Deploy Solution“

image

Activation
If the feature is not active, you can activate it by doing the following:
Open Internet Explorer and open your SharePoint Root-site. Log in as administrator. Click on “Site Actions” and in the context menu on “Site Settings”. On the page “Site Actions” click on the link “Site collection features. On the then following page search for the feature “Communardo Send documents as attachments” and click on the button “Activate”. The feature is now activated and can be used.

Application
Sending documents via Ribbon Bar
When the feature “Communardo Send documents as attachments” is active, there will be added a button “Send documents as e-mail” to the section “Share & Track” in the ribbon of document libraries.(Figure 4) This button will be active only if at least one document is selected. After clicking on “Send documents as email” the dialogue “New Mail-Dialog” of the Outlook will be opened and the selected documents will be automatically added as an attachment.

image

Sending separate documents as e-mail via context menu
There is a possibility to send separate documents as an e-mail. For this purpose, there is an entry in the context menu “As e-mail attachment”.

image

Remove button from the Ribbon in SharePoint 2010

 

In SharePoint 2007, I have quite a few requests from different client to remove button from the document list view, such as the “Edit in Datasheet” and “Open with Windows Explorer” button. I was able to solve the problem by writing a Javascript to hide the button.

Ribbon is introduced in SharePoint 2010. We can easily make customization it by using the Feature Infrastructure. For example, we can create a new button, delete an existing button, as well as replacing an existing button. Hence I can easily get around with the problem that I had in SharePoint 2007.

In order to hide a button, say the “Open with Explorer”, we will need to create a feature. We start by creating a new folder called “DisableRibbonButton”. Create a new file called “feature.xml” in the new folder and insert the following XML into the file


<Feature Id="33057CD9-6D14-45c9-83ED-5E1FE066AC92"
Title=”DisableRibbonButton”
Description=”DisableRibbonButton”
Version=”1.0.0.0″
Scope=”Web”
xmlns=”http://schemas.microsoft.com/sharepoint/”&gt;

Then create another file called “Manifest.xml” and insert the following XML:

<CustomAction
Id=”RemoveExplorerButton”
Location=”CommandUI.Ribbon”
RegistrationType=”List”
RegistrationId=”101″>

<CommandUIDefinition
Location=”Ribbon.Library.Actions.OpenWithExplorer” />

The above XML is to remove the “Open with Explorer” button from the Ribbon for all list with type ID 101, hence all the Document Library type. The location “Ribbon.Library.Actions.OpenWithExplorer” is the ID that is registered in the default Ribbon button XML, which can be found in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\GLOBAL\XML\CMDUI.XML”

Once you have created the above xml files…you will need to copy them to a folder called DisableRibbonButton in the Features folder in the 14 hive.

Now we will execute the following Cmdlet using the “SharePoint 2010 Management Shell” to install and active the feature:

Install-SPFeature DisableRibbonButton

Enable-SPFeature DisableRibbonButton –url http://

After that, go to any document library in your site, click the “Library” tab at the top and you should see the “Open with Explorer” button is now disappeared from the Ribbon.

image

Enable Anonymous Access in SharePoint 2010

Here are 8 simple steps on how to set up anonymous access in SharePoint 2010 It is not much different then SharePoint 2007 set up, the only difference is the GUI or the Ribbon.

1. Starting in Central Administration, under Application Management, click on the Manage web applications.

Anonymous Access Set Up Step 1

2. Make sure you select the site you want to enable anonymous access and click on the Authentication Providers icon.
Anonymous Access Set Up Step 2

3. On the Authentication Providers pop-up window click on the Default zone.
Anonymous Access Set Up Step 3

4. Under Edit Authentication, check Enable anonymous access and click Save.
Anonymous Access Set Up Step 4

5. Going back to Web Application Management click on the Anonymous Policy icon.
Anonymous Access Set Up Step 5

6. Under Anonymous Access Restrictions select your Zone and set the Permissions to None – No policy and click Save.
Anonymous Access Set Up Step 6

7. Now, web application will allow anonymous access to be set. So, navigate to your top level site collection for the web application. Click the Site Actions > Site Settings. Under Users and Permissions click Site permissions.
Anonymous Access Set Up Step 7

8. Under Permission Tools, click Anonymous Access icon and set the permissions to Entire Web site and click OK.
Anonymous Access Set Up Step 8
Anonymous Access Set Up Step 8

Anonymous Access Set Up

That’s all, folks! If you followed these steps properly you should have now Anonymous Access enabled.