SharePointSupport

_layouts/15/user.aspx                                            -------   Site Permission _layouts/15/appprincipals.aspx?Scope=Web   -------  Site App Permissions _layouts/15/mngfield.aspx                                 -------   Site Columns _layouts/15/mngctype.aspx                                 -------  Site Content Types _catalogs/masterpage/Forms/AllItems.aspx     -----   Master Page Gallery _catalogs/design/AllItems.aspx                         -------  Composed Looks _layouts/15/ReportServer/ScheduleList.aspx   -----  Manage Shared Schedules _layouts/15/ManageFeatures.aspx                        ----  Manage Site Features _layouts/15/savetmpl.aspx                                     -----  Save As Template _layouts/15/mcontent.aspx                                     ----  Site Libraries and Lists

https://technet.microsoft.com/en-in/library/dn135237.aspx http://blogs.technet.com/b/office_resource_kit/archive/tags/office+web+apps/ https://technet.microsoft.com/library/8480064e-14a4-4b46-ad6b-0c836b192af2(Office.15).aspx http://blogs.technet.com/b/office_resource_kit/ https://technet.microsoft.com/en-in/library/ff433481.aspx https://technet.microsoft.com/en-in/library/jj219435.aspx

Once I was trying to send the attachments along with the email messages being sent to the SharePoint document library. All the configurations were proper and I had properly associated the document library with an email address. After the stage was properly setup for the document library to receive emails with the attachment, I tested the same and expected it to work just fine, but I did not get any success.  I did a quick research over the internet and found out the solution from the MSDN site. The reason mentioned was pretty straight forward. While associating a document library with an email address, the Directory Management Service might miss out adding the following two attributes: internet Encoding = 1310720 mAPIRecipient = false These two attributes must be added manually using the Active Directory Service Interfaces (ADSI). Note: On Windows Server 2008 or Windows Server 2008 R2, the Active Directory Service Interfaces (ADSI)   Edi

People have liked the Organization Browser web part so much that they want the web part to be added to their companies main Portal web application. I too recently came across this interesting situation, wherein we were supposed to show the My Site Organization Browser web part inside our publishing site. It was a task that according to me was very small. Just add the Organization Browser web part from the Social Collaboration group (as shown in the figure below) in the webpage and you are sorted. I started working on it. As mentioned, I just added the web part from the Social Collaboration group, and whoa!!!.. I was done. Wait......there was something wrong. The Silverlight web part did not show anything inside it. There was no rendering done. I tried to do a lot of tweaking, but to avail no success : ( I started searching for the solution over the internet, and noticed that I was not the only one facing the problem. Instead there were many with the same problem. Finally I got s

On a recent SharePoint 2013 deployment, I faced a strange issue, wherein the search index got corrupted and I was not able to reset the index. Although, I was able to get to the reset index screen and the reset index button was clickable, but each time it went into an infinite loop on clicking the reset index button, and the index was not reset. After much banging our heads and googling around, I found a small piece of information that really helped and did the trick. Below is a step-wise approach to resolve such an issue. Step-1 Stop the Windows SharePoint Services Timer service Step-2 Navigate to the cache folder in the following location: System Drive:\ProgramData\Microsoft\SharePoint\Config Step-3 Locate the folder that has the file “Cache.ini”. There may be multiple GUID folders with cache.ini file Step-4 Back up these folders with the Cache.ini file Step-5 Delete all the XML configuration files in the GUID folder Note: When you delete the xml

We all know that SharePoint doesn’t support saving publishing sites as a template . I don’t recommend doing that anyway as the produced template will have errors and isn’t reliable to be used in production to create new sites off of. However, sometimes as a developer you need to save a publishing site as a template to see how SharePoint packages things. This can help you build your own custom web template which is a neat thing and replaces the need to save a publishing site as template. Well, since the Save site as a template option is hidden from the publishing sites settings page we all used the following URL to go there directly: /_layouts/savetmpl.aspx Or /_layouts/15/savetmpl.aspx Well, that is not going to work anymore in SharePoint 2013 if your site is a publishing site or have the publishing features activated . You basically get that following error: The “Save site as template” action is not supported on this site.   In order to get around this i

$site = Get-SPSite "http://yoursite" foreach ($web in $site.AllWebs) { $web | Select-Object -Property Title,Url,WebTemplate } $site.Dispose()

This article explains about Excel related issue in our SharePoint 2013 Environment. Whenever user tries to open excel files uploaded in document library, it launches browser to open the file and then displays below error- " We’re sorry. We ran into a problem completing your request. Please try that again in few minutes." Also see below screenshot- As part of issue analysis, following checks were performed- 1.) Check if Excel Services is running. ( This was running in our case. ) Open Central Administration -> System Settings -> Manage Services on Server -> Excel Calculation Service -> Started 2.) Check if Excel Service Application is associated to Web Application in question. ( This was configured in our case. ) Open Central Administration -> Application Management -> Manage Web Applications -> Select Web Application -> Select Configure Service Associations 3.) Check if Trusted File Location is configured for Excel Service

This article is related to below post where user reported missing ribbon issue after migration from SharePoint 2007 to 2013 version. https://social.technet.microsoft.com/Forums/en-US/628b9f7b-b1e7-4bb1-b01d-fcb11b252862/ribbons-missing-after-migration Scenario: Ribbon not visible on SharePoint List/Library page load. Mostly reported after site migration from 2007 to 2010/2013 version. Also if you have added a content editor web part on this page. Cause: When content editor web part is added to standard list/library pages, classification of page changes from List View page to Application page. Solution: First of all, if you are experiencing this issue after migration, perform below checks- Check if this issue appears for existing/new list/library pages. Is it happening for all lists/libraries If item in a list/library is selected, ribbon appears? Any customization  like Content Editor Web Part or JavaScript  code added on that page. Now if you hav

Background: I wanted to see all users who have access to the SharePoint site and belongs to which SharePoint group. Solution: Below SharePoint powershell script helps me to get list of users group wise- $site = Get-SPSite <Provide Site Collection URL here> $web = $site.OpenWeb() $groups = $web.sitegroups foreach ($grp in $groups) {      "Group: " + $grp.name;      $groupName = $grp.name      write-host "Group: " $groupName   -foregroundcolor green      foreach ($user in $grp.users) {              "User: " + $user.name              write-host "User " $user.UserLogin   -foregroundcolor red      } } Usage: Navigate to Script location and type below command- GetUsers.ps1 This will show output on screen. Navigate to Script location and type below command- GetUsers.ps1 | Out-File C:\Output.csv This will generate output as csv file. " C:\Output.csv " is

You can control which mode (2010 or 2013, or both) can be used when a user creates a site collection. The CompatibilityRange property on a web application controls the site modes available for a web application. You can view or change the settings for CompatibilityRange by using Windows PowerShell. check the following and let me know if helpful http://technet.microsoft.com/en-us/library/jj219599(v=office.15).aspx http://technet.microsoft.com/en-us/library/ff191199(v=office.15).aspx http://technet.microsoft.com/en-us/library/jj219650(v=office.15).aspx If you upgrade from SharePoint Server 2010 to SharePoint Server 2013, there are special considerations for My Sites. (My Sites are not available in SharePoint Foundation 2013.) Make sure that you upgrade the My Site Host site collection before you allow users to access their individual My Sites in SharePoint Server 2013. This makes sure that the server software and database changes are complete so that users ca

SharePoint 2010 and 2013 is having software boundary that we can't upload file bigger than 2 GB, so what if we have bigger files? To handle large files that are bigger than 2 GB there are few options you have: Use software to split files and then upload them and when you download them you will use the software to merge them again, there are available software to do the following Use File Share servers and from SharePoint create view to point to those file share servers. Upload files to cloud and inside SharePoint just add links to refer to those sites.

Workflow Manager is an added value to the SharePoint 2013, in the previous versions workflow was part of the SharePoint on SharePoint 2013 there are 2 flavors you can use when developing workflows the first one is the SharePoint 2010 workflow and the second and new one is the new workflow manager which is now a separate component, when you install the new workflow manager it will allow to create SharePoint 2013 workflows. The Architecture of the Workflow Manager depends on several separate databases to save the workflows so now the workflows are stored on those separate databases and not on the content databases so important in any backup and restore to make sure that all those workflows are backed up in case restoration is needed and while restoring there are important steps and scripts that needs to run in certain order to restore the workflow farm correctly. I will be walking through the steps to restore the workflow farms and the scripts used can be found in this l

To Migrate SharePoint DBs from SQL Server to another either same version or to a new version (2008 to 2008 or 2008 to 2012) you can follow the following steps: Stop all SharePoint and IIS Related Services. Stop IIS. Detach all related SQL Server databases. Configuration database Central Administration content database Content databases Service application databases   Move all database files (.mdf, .ldf, and .ndf) to the new server. Set up same user permissions on the new SQL server. Attach your databases to the new SQL Server. Verify ports in your new SQL server. Go to your SharePoint server and create your SQL Server Alias. Start all your SharePoint services.

Microsoft has introduced new Workflow engine and concept with SharePoint 2013 called Workflow Manager. The SharePoint 2013 Workflow platform uses the new Workflow Manager service. Workflow Manager is built on top of Windows Workflow Foundation. Windows Workflow Foundation is part of the .NET Framework 4.5. Workflow Manager is a separate download and must be configured to communicate with the SharePoint Server 2013 farm. In several cases your environment is secured and not accessing the internet and you want to install the workflow manager so in the following steps I am going to explain how to do that so you can install Workflow Manager offline to server(s) not connected to the internet. Download the web platform installer  http://download.microsoft.com/download/C/F/F/CFF3A0B8-99D4-41A2-AE1A-496C08BEB904/WebPlatformInstaller_amd64_en-US.msi and install it on a machine with internet access Run the following commands as administrator from command prom

Introduction One of the feature updates of the   March 2013 Public Update   for SharePoint 2013 enables you to use multiple app domains in SharePoint 2013 environments with alternate access mapping or host-header web application configurations. Microsoft introduced a new concept with SharePoint 2013 and Office 365 to extend the out of the box functionality instead of the normal approach of farm solutions now you can add apps (add ins) through Java script code or using .net and hosting apps outside SharePoint environment without need to go and deploy code into SharePoint which increase the  re-usability , enhance the security and assure that SharePoint farm stability and code isolation. To have apps working you need to configure App Domain which is a corner stone to have apps working, at some cases you will need to have more than one app domain configured so I am going through this topic in the few lines. Why we need multiple App Domains? You could use app

Here we go, it’s been a long time I didn’t publish an article which consist of hardcore troubleshooting! Yes, you are correct. It took some time to resolve but finally the issue has been resolved. This time it’s regarding problem occurring while ‘save site as template’ and how we found the culprit.  Problem description:- User has raised the problem ticket by mentioning “facing problem while saving the site as template”, additionally the templates are getting saved in the solution gallery but not able to activate it also.   Error message:- An unexpected error has occurred. Troubleshoot issues with Microsoft SharePoint Foundation. Correlation ID: acd95f50-4049-4625-9682-aa93aded118f   Troubleshooting done:- Further debugging in the SP ULS logs and we found some strange facts which are based on event receivers- please refer below-   SPSolutionExporter: Microsoft.SharePoint.SPException: Feature definition with Id 77658379-50ff-4e1e-a431-5652bee07a87 failed

Project Server 2010 Error Codes Project Server 2013 error codes