SharePointSupport

Error : I have a Sharepoint 2013 running on a Windows Server 2012. Following issue appeared: I made a new Site-Collection as wiki. Everything (links,...) works fine on the server but when I want to access the wiki from outside (not localhost) the server runs in a 404 Not found error. http://localhost/sites/wiki/Pages/Home.aspx - works fine(localhost) http://10.38.0.15/sites/wiki/Pages/Home.aspx - doesn't work. I checked the IIS settings, all servers are up and running. The log file has no errors in it. Resolution : The most common cause for this is that you don't have the IIS host header configured correctly . The 404 will appear because you are hitting a different IIS web site and not the one you intended to. If you go into IIS Manager and click on " Sites " in the right hand pane there will be a column called bindings and a column called ID . IIS will check in the order of ID for the first site that matches. Make sure the default site is stopped

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()

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

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

Intro to Host Name Site Collections (HNSC) * Host Name Site Collections are the answer to simplifying and consolidating SharePoint Farm/s.   Let’s assume a SharePoint Farm has 5 web applications each mapped to a unique application pool.   While this gives you a nice separation for security purposes, it adds unnecessary strain on each WFE.   E ach time an application pool is spun up, it must load all of the assemblies from memory.  * So in this case, each WFE is consuming 5x memory right off the bat.   The costs increase by having to procure beefy machines with lots of memory to support this requirement. * For many of our customers, this led to many multifarm environments due to hitting a cap in physical memory.   Also as you’ve experienced, the sheer # of web applications can lead to long patching cycles with PSConfig . * By consolidating web applications, your essentially cutting operations costs (faster patching times) and reducing infrastructure costs (additiona

I was about to give up on one of my labb SharePoint 2013 Environments because it was so extremely slow all the time. Warmup scripts, reloads, more memory, more CPU, stopping services, stopping search …nothing helped. I had a constant loadtime of all aspx pages of 6+ seconds, 6.10-6.20 something. Even when the page was just loaded and I pressed F5 to reload, it still took 6.10 seconds. This was an environment that gave you sensitive nerves… So, after looking for any solution or more like looking for the little issue that caused this all day, I gave up more or less. – CPU was at a maximum 40% on SQL, SharePoint cranked it up to 18%… – Memory consumtion was at 25% of the 12GB SharePoint had… – SQL was Lightning fast to all other SharePoint farms… – Network utilization showed about 100Kbps at the most… I scavenged the internet as usual and found nothing but the standard: add more memeory, add more CPU, stop services, stop search… None of that helped and I had tried it al

I have created a new site. When I open the site uing the URL the browser gives this. HTTP/1.1 404 Connection: close Date: Tue, 01 Feb 2011 15:44:05 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET MicrosoftSharePointTeamServices: 12.0.0.4518 Solution : * The most probably reason is you haven’t create the Top-Level site collection . * SPS will not create the Top-Level site collection for you by default. To create the Top-Level site collection, goto Central Administration > Application Management > Create Site Collection.

Very slow SharePoint, what can you do against it without upgrading your hardware : what you can do if your SharePoint is sometimes very slow. E.g.: on the first start of a Site Sometimes during the day a search query will take about a minute until you get results..... Just look on that article: http://support.microsoft.com/kb/2625048 it will improve your "feeled" performance (site response times) massive, if you're going to implement both solutions. Disabling CRL Check is just necessary if the SP Server does not have internet connectivity! -> that means proxy settings must be configured for the server itself http://technet.microsoft.com/de-de/library/bb430772(v=exchg.141).aspx , and your proxy must allow traffic from the server of course.