RSS

Category Archives: SharePoint

Error occurred in deployment step ‘Add Solution’: The solution cannot be deployed.


Issue: Got following error message when deploy solution in visual studio:

Directory “X” associated with feature ‘GUID1’ in the solution is used by feature ‘GUID2’ installed in the farm. All features must have unique directories to avoid overwriting files.”

Resolution for this issue.

– Run Manager Shell as Administrator:

stsadm -o uninstallfeature -id “GUID2” -force

– Deploy solution again.

Advertisements
 
Leave a comment

Posted by on 23/02/2013 in SharePoint

 

Yêu cầu hệ thống khi cài đặt Sharepoint Foundation 2010


Hardware requirements

Component Minimum requirement
Processor 64-bit, 4 cores
RAM
  • 4 GB for developer or evaluation use
  • 8 GB for production use in a single server or multiple server farm
Hard disk 80 GB for system drive

Software requirements

Environment Minimum requirement
Database server in a farm One of the following:

  • The 64-bit edition of Microsoft SQL Server 2008 R2.
  • The 64-bit edition of Microsoft SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2. From the Cumulative update package 2 for SQL Server 2008 Service Pack 1 (http://go.microsoft.com/fwlink/p/?LinkId=165962) page, click the View and request hotfix downloads link and follow the instructions. On the Hotfix Request page, download the SQL_Server_2008_SP1_Cumulative_Update_2 file. When you install Microsoft SQL Server 2008 SP1 on Windows Server 2008 R2, you might receive a compatibility warning. You can disregard this warning and continue with your installation.
Note:
We do not recommend that you use CU3 or CU4, but instead CU2, CU5, or a later CU than CU5. For more information, see Cumulative update package 5 for SQL Server 2008 (http://go.microsoft.com/fwlink/p/?LinkId=196928). Download the SQL_Server_2008_RTM_CU5_SNAC file.

For more information about choosing a version of SQL Server, see SQL Server 2008 R2 and SharePoint 2010 Products: Better Together (white paper) (SharePoint Server 2010).

Single server with built-in database
  • The 64-bit edition of Windows Server 2008 Standard, Enterprise, Data Center, or Web Server with SP2; the 64-bit edition of Windows Server 2008 R2 Standard, Enterprise, Data Center, or Web Server; or the 64-bit edition of Windows Server 2008 R2 Service Pack 1 (SP1) Standard, Enterprise, Data Center, or Web Server. If you are running Windows Server 2008 without SP2, the Microsoft SharePoint Products Preparation Tool installs Windows Server 2008 SP2 automatically.
Note:
You must download an update for Windows Server 2008 and Windows Server 2008 R2 before you run Setup. The update is a hotfix for the .NET Framework 3.5 SP1 that is installed by the Preparation tool. It provides a method to support token authentication without transport security or message encryption in WCF. For more information and links, see the “Access to Applicable Software” section later in this article.

For information, see the related KB article Two issues occur when you deploy an ASP.NET 2.0-based application on a server that is running IIS 7.0 or IIS 7.5 in Integrated mode (http://go.microsoft.com/fwlink/p/?LinkId=192578).

The preparation tool installs the following prerequisites:

  • Web Server (IIS) role
  • Application Server role
  • Microsoft .NET Framework version 3.5 SP1
  • SQL Server 2008 Express with SP1
  • Microsoft Sync Framework Runtime v1.0 (x64)
  • Microsoft Filter Pack 2.0
  • Microsoft Chart Controls for the Microsoft .NET Framework 3.5
  • Windows PowerShell 2.0
  • SQL Server 2008 Native Client
  • Microsoft SQL Server 2008 Analysis Services ADOMD.NET
  • ADO.NET Data Services Update for .NET Framework 3.5 SP1
  • A hotfix for the .NET Framework 3.5 SP1 that provides a method to support token authentication without transport security or message encryption in WCF.
  • Windows Identity Foundation (WIF)
Note:
If you have Microsoft “Geneva” Framework installed, you must uninstall it before you install the Windows Identity Foundation (WIF).
Front-end Web servers and application servers in a farm
  • The 64-bit edition of Windows Server 2008 Standard, Enterprise, Data Center, or Web Server with SP2; the 64-bit edition of Windows Server 2008 R2 Standard, Enterprise, Data Center, or Web Server; or the 64-bit edition of Windows Server 2008 R2 Service Pack 1 (SP1) Standard, Enterprise, Data Center, or Web Server. If you are running Windows Server 2008 with SP1, the Microsoft SharePoint Products Preparation Tool installs Windows Server 2008 SP2 automatically.
Note:
You must download an update for Windows Server 2008 and Windows Server 2008 R2 before you run Setup. The update is a hotfix for the .NET Framework 3.5 SP1 that is installed by the Preparation tool. It provides a method to support token authentication without transport security or message encryption in WCF. For more information and links, see the “Access to Applicable Software” section.

For information, see the related KB article Two issues occur when you deploy an ASP.NET 2.0-based application on a server that is running IIS 7.0 or IIS 7.5 in Integrated mode (http://go.microsoft.com/fwlink/p/?LinkId=192578).

The preparation tool installs the following prerequisites:

  • Web Server (IIS) role
  • Application Server role
  • Microsoft .NET Framework version 3.5 SP1
  • Microsoft Sync Framework Runtime v1.0 (x64)
  • Microsoft Filter Pack 2.0
  • Microsoft Chart Controls for the Microsoft .NET Framework 3.5
  • Windows PowerShell 2.0
  • SQL Server 2008 Native Client
  • Microsoft SQL Server 2008 Analysis Services ADOMD.NET
  • ADO.NET Data Services Update for .NET Framework 3.5 SP1
  • A hotfix for the .NET Framework 3.5 SP1 that provides a method to support token authentication without transport security or message encryption in WCF.
  • Windows Identity Foundation (WIF)
Note:
If you have Microsoft “Geneva” Framework installed, you must uninstall it before you install the Windows Identity Foundation (WIF).
Client computer

Optional software

Environment Optional software
Single server with built-in database and front-end Web servers and application servers in a farm

The preparation tool installs the following optional software:

  • Microsoft SQL Server 2008 R2 Reporting Services Add-in for Microsoft SharePoint Technologies 2010 (SSRS) to use Access Services for SharePoint Server 2010. For the download, go to the Download Center(http://go.microsoft.com/fwlink/p/?LinkID=192588).
  • Microsoft Server Speech Platform to make phonetic name matching work correctly for SharePoint Search 2010.
Client computer
 
Leave a comment

Posted by on 25/11/2012 in SharePoint

 

Tags: , ,

Sửa lỗi khi không có quyền upload file .swf vào library hoặc list trong Sharepoint 2010


Người dùng với quyền truy cập Contribute tải file .swf  hoặc các định dạng file bị chặn vào sharepoint library hoặc sharepoint list attachment thì gặp thông báo lỗi

Các định dạng file bị chặn (WebFileExtension) bao gồm:

  • ASPX
  • Master
  • XAP
  • SWF
  • JAR
  • ASMX
  • Ascx
  • XSN
  • XSF

Cách sửa như sau:

Mở SharePoint 2010 Management Shell.

Chạy các dòng script tương ứng như sau:

$WebApp = Get-SPWebApplication http://YourSiteCollectionURL/
$Extensions = $WebApp.WebFileExtensions
$Ext = $Extensions.Remove(“swf”)
$WebApp.Update()

Để xem danh sách WebFileExtensions dùng đoạn script sau:

$WebApp = Get-SPWebApplication https://YourSiteCollectionURL/
$Extensions = $WebApp.WebFileExtensions
$Extensions | ForEach-Object {Write-Host $_}

Nếu muốn thêm vào danh sách WebFileExtensions thì dùng lệnh .Add() thay lệnh .Remove()

 
Leave a comment

Posted by on 03/10/2012 in SharePoint

 

Tags: ,

SharePoint 2010 Powershell Feature Cmdlets


In this installment its time to look at the various cmdlets that have to do with Features. Of course you can look at the UI to do this but its much, much easier to do this powershell and dare I say more fun.

Now keep in mind that this only related to FARM level features, I will cover Sandbox solutions and features next!

Listing features on Farm, Site Collection and Site

The main cmdlet used within powershell to list features is the Get-SPFeature cmdlets. To show all the features on the farm listed by display name and sorted use this:

1 Get-SPFeature | Sort -Property DisplayName

To show all the features on the Farm grouped by scope in a table use:

1 Get-SPFeature | Sort -Property DisplayName, Scope | FT -GroupBy Scope DisplayName

To see all features for a Web Application:

1 Get-SPFeature -WebApplication http://webapplication

To see all features for a Site Collection:

1 Get-SPFeature -Site http://sitecollection

To see all features for a Site:

1 Get-SPFeature -Web http://siteurl

Remember for some more information relating to the features you can use:

1 Get-SPFeature -Web http://siteurl | Format-List

To see all the members that a feature definition has use:

1 Get-SPFeature -Web http://siteurl | Get-Member

Enabling and Disabling Features

To disable and enable features is all pretty easy once again using the Disable-SPFeature and Enable-SPFeature cmdlets but there is a trick. You need the name of the feature folder that contains the actual feature not what is displayed in the UI so be careful:

1 Enable-SPFeature -Identity "Hold" -URL http://url

You can apply this to any Site and Site Collection scoped features.
Obviously to disable a feature just use the same syntax but with the Disable-Feature cmdlet

1 Disable-SPFeature -Identity "Hold" -URL http://url

Remember though that the -Identity is the DisplayName property of the feature, not the text displayed on the UI which is actually retrieved from a resources file.
For example the Document Sets feature looks like below in the SharePoint interface:
But to actually enable it you have to use the following cmdlet:

1 Enable-SPFeature -Identity DocumentSet -URL http://url

Installing and Uninstalling Features

Once again this is pretty straight forward and is really made up of only two cmdlets: Install-SPFeature and Uninstall-SPFeature
To install a feature you need to specify the name of the folder that your feature contains:
1 Install-SPFeature "FeatureFolderName"

To uninstall simply use the same Uninstall-Feature command with the same parameters:

1 UnInstall-SPFeature "FeatureFolderName"
 
Leave a comment

Posted by on 03/05/2012 in SharePoint

 

Parser Error: Direct Dependencies and The Limit Has Been Exceeded


Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: The page ‘/sites/blah/_catalogs/masterpage/blah.master’ allows a limit of 11 direct dependencies, and that limit has been exceeded.

During deploying user control on the master page, in one of our project I used to get the above error. Generally such kind of exception is thrown will rendering a page. The reason behind this is the number of controls allowed on the page to render exceeds the limit specified in the web.config file

The solution of this problem can be fixed in two different ways.
Solution 1: Modify the control dependencies in the web.config file.
Solution 2: Optimize the usage of controls on the master page; this can be done either by deleting the duplicates, or integrating 2 or more control in one control.
The solution 2 is a complex one, where as the solution 1 is a simple modification as show below

Search for the following tag in the web config file and chage the DirectFileDependecies

<- SafeMode MaxControls=”200″ CallStack=”true” DirectFileDependencies=”20″ TotalFileDependencies=”50″ AllowPageLevelTrace=”false”>
By default the DirectFileDependecies will be set to 10, you can change to any limit u require.

 
Leave a comment

Posted by on 12/04/2012 in SharePoint

 

The referenced file ‘[User Control path]’ is not allowed on this page


After deploy UserControl for SharePoint 2010 for the first time, added a UserControl to one of my existing sites and I was presented with the following error message:

“The referenced file ‘/_layouts/PowerPivot/ReportGalleryView.ascx’ is not allowed on this page.”

After doing some research, I found this blog post. For whatever reason, Microsoft missed a step for the feature activation of the PowerPivot controls that adds the controls to the Safe Controls in the Web.Config file of your web application. You have to do this manually. For each Web.Config file on each server for each web application, you have to add the following Safe Control:
SafeControl Src="~/_layouts/powerpivot/*" IncludeSubFolders="True" Safe="True" AllowRemoteDesigner="True" SafeAgainstScript="True"
After adding that to your Safe Controls in each web.config, do an IISRESET and you are all set.

Source: http://www.sharepointjohn.com/sharepoint-2010-powerpivot-the-referenced-file-is-not-allowed-on-this-page/

 
Leave a comment

Posted by on 22/03/2012 in SharePoint

 

Enable Anonymous Access in SharePoint 2010


Here are 8 simple steps on how to set up anonymous access in MS 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.

2. Make sure you select the site you want to enable anonymous access and click on the Authentication Providers icon.

3. On the Authentication Providers pop-up window click on the Default zone.

4. Under Edit Authentication, check Enable anonymous access and click Save.

5. Going back to Web Application Management click on the Anonymous Policy icon.

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

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.

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

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

Source: http://www.topsharepoint.com/enable-anonymous-access-in-sharepoint-2010

 
Leave a comment

Posted by on 22/03/2012 in SharePoint