Monday, August 11, 2014

The feature: "windows SharePoint services integration" is not supported in this edition of Reporting Services



The feature: "windows SharePoint services integration" is not supported in this edition of Reporting Services

Environment: SharePoint 2013, SQL 2012 Reporting Services

Description: After setting up and configuring SSRS in SharePoint 2013; Once you navigate to Reporting Services Service Application and click on the Settings link you might see below error:

Error: The feature: "Windows SharePoint Services integration" is not supported in this edition of Reporting Services. ---> Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: The feature: "Windows SharePoint Services integration" is not supported in this edition of Reporting Services.

Solution: If this happens make sure you have the right SQL 2012 edition for the Reporting Services and Add-ins on the SharePoint server. 

For this navigate to Reporting Services log files location: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\WebServices\LogFiles\

Check for the following string in the log files:

"INFO: Reporting Services starting SKU: Express"
If you are able to find this line then it signifies that you have the wrong edition (i.e. SQL Express) on the server. SQL Express edition does not support Reporting Services integration and Power Pivot integration with SharePoint 2013.

To fix the issue:

Uninstall the existing SQL 2012 bits from the server. You can do that via control panel - add remove programs. Select SQL Server and then uninstall it.

Install SQL 2012 Enterprise/Standard now and follow the SSRS integration steps (running the PowerShell cmdlts and creating the Service Application).

How to configure the SSRS: http://expertsharepoint.blogspot.de/2014/03/sql-reporting-services-installation.html

MS article: http://technet.microsoft.com/en-us/library/ee384252%28v=sql.100%29.aspx

 

I hope the above information will help you to resolve the issue, in case of 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.

Friday, August 8, 2014

Script to add or remove a user as site collection administrator in many site collections



Script to add or remove a user as site collection administrator in many site collections

Description: many times as a SharePoint administrator we required to perform a task that to add a user as administrator in many site collections. This is very difficult if has 100’s of site collections. In this article I am providing the script how to achieve this with one click.

Instructions: Follow the Instructions below to run successfully.

1.   Copy the script in notepad and save as .PS1
2.   Do modifications as said below
3.   Open power shell as Admin,Ensure your in the same location where Script is copied.
4.   Run ./Script.ps1
5.   You see a below screen once its run successfully

Modifications: You need to do below modifications according to your requirements.

1.   $newSiteCollectionAdminLoginName = "Name of user"
2.   $newSiteCollectionAdminEmail = " user  mail ID"
3.   $newSiteCollectionAdminName = " Name of user "
4.   $siteURL = " siteURL " #URL to any site in the web application.
Script:

# This script will add named Site Collection Administrator
# to all Site Collections within a Web Application.
#
# Author: Anil Avula
######################## Start Variables ########################
$newSiteCollectionAdminLoginName = ""Name of user "
$newSiteCollectionAdminEmail = " user  mail ID "
$newSiteCollectionAdminName = " Name of user "
$newSiteCollectionAdminNotes = ""
$siteURL = " siteURL " #URL to any site in the web application.
$add = 1 # 1 for adding this user, 0 to remove this user
######################## End Variables ########################
Clear-Host
$siteCount = 0
[system.reflection.assembly]::loadwithpartialname("Microsoft.SharePoint")
$site = new-object microsoft.sharepoint.spsite($siteURL)
$webApp = $site.webapplication
$allSites = $webApp.sites
foreach ($site in $allSites)
{
   
    $web = $site.openweb()
    $web.allusers.add($newSiteCollectionAdminLoginName, $newSiteCollectionAdminEmail, $newSiteCollectionAdminName, $newSiteCollectionAdminNotes)
   
    $user = $web.allUsers[$newSiteCollectionAdminLoginName]
    $user.IsSiteAdmin = $add
    $user.Update()
    $web.Dispose()
    $siteCount++
}
$site.dispose()
write-host "Updated" $siteCount "Site Collections."

 

I hope the above information will help you to resolve the issue, in case of 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.

Thursday, August 7, 2014

“Open with Explorer” is disabled in for document library in SharePoint 2013



“Open with Explorer” is disabled in for document library in SharePoint 2013

Solution: Please find the below limitations on open with the explorer.

1.    Since SharePoint 2013 fully support IE 32-bit version above 7, there might be compatibility issue with other browsers. I’d recommend you use IE 8,9,10 32-bit for optimal Performance.
2.    Open the same document library in Internet Explorer as this functions does not work with Firefox or Chrome by default
3.    Make sure the IE (Internet Explorer) Version should be 32-bit and not a 64-bit
 

I hope the above information will help you to resolve the issue, in case of 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.

Tuesday, August 5, 2014

The file reached the maximum download limit. Check that the full text of the document can be meaningfully crawled” in the Crawling log Error



The file reached the maximum download limit. Check that the full text of the document can be meaningfully crawled” in the Crawling log Error.

Issue: The file reached the maximum download limit. Check that the full text of the document can be meaningfully crawled” in the Crawling log Error

Description: Since working with SharePoint 2013, I had lot of crawl warning saying the file was not fully indexed as it reached the maximum download limit: “The file reached the maximum download limit warnings. Check that the full text of the document can be meaningfully crawled”.

Cause: it was an ‘issue’ with the new search engine (now SharePoint 2013 is fully using Fast as search engine) as my content was properly crawled with SharePoint 2010.

Solution 1: The solution is (off course) to increase the download limit for the index process.
1)   Open the SharePoint Management Shell
2)   Run the following commands

a.   $searchapp = Get-SPEnterpriseSearchServiceApplication
b.   $searchapp.GetProperty(“MaxDownloadSize”) |this command is just to check the current value; default is 64
c.   $searchapp.SetProperty(“MaxDownloadSize”, <value>) where you replace <value> with the download limit; for example, 128
d.   $searchapp.Update()

3)   Restart the server
4)   Do a full crawl and the ‘download’ warnings will disappears

Solution 2: Please change the registry settings for search as below.

1.   Start Registry Editor (Regedit.exe).
2.   Locate the following key in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\15.0\Search\Global\Gathering Manager
3.   Open Edit – New – DWORD Value. Name it MaxDownloadSize. Double-click, change the value to Decimal, and type the maximum size (in MB) for files that the gatherer downloads.
4.   Restart the server.
5.   Start Full Crawl. 

Note: Increasing the file size may cause a timeout exception. How To increase timeout value check the Article below.

http://expertsharepoint.blogspot.de/2013/12/this-item-could-not-be-crawled-because.html

 

I hope the above information will help you to resolve the issue, in case of 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.

ShareThis

X