SharePointSupport

* Navigated to master page gallery http://appweburl/_catalogs/masterpage . * In master page gallery I have seen all master pages related to SharePoint 2013 (app.master, seattle.master, oslo.master..etc.). By default app web use app.master page. * Download app.master to your local and add CSS/JavaScript code to the master page. * Upload it to masterpage gallery again. * Added #DeltaSuiteLinks{display:none} style in the master page. It worked for me.  * But make sure check this before in Dev/Stage before updating the production.

This part demonstrate how to configure windows cluster for two server, to be used as SQL Cluster. Before you start · You need to have two network adapters on each node, one Public and one Private(for heartbeat communication). · Shared storage (like SAN storage) should be present and connected to both cluster nodes  with at least: Quorum Disk (5GB) DTC Disk (1GB) SQL data files and log file disk(s) · domain user account (SPSadmin): add SPSadmin user as administrator on both servers · Prepare a preserved static IP and Cluster Name to be used. · Prepare a preserved static IP and DTC Name to be used. Windows Cluster Configuration 1. Install latest windows updates on all server nodes. 2. Install Application role and IIS role on both SQL DB server nodes 3. Install Fail over clustering feature on both SQL DB server nodes. 4. Provide a Cluster Name and Cluster IP for the dat

1. Install Network Load Balancing Feature on each Web Front End On each front end in the farm, within Server Manager , add the NLB feature : Click Install and wait a bit 2.Add a New Cluster Through the start menu, Administrator Tools , click Network Load Balancing Manager : Right click Network Load Balancing Clusters , and choose New Cluster Type the IP address of one of the web fronts in the farm to serve as the first host in the cluster Click Connect . Click next . Leave the defaults and click next again: 3.Set Cluster IP Address This IP Address is the dedicated IP address for the cluster and is what DNS will point to, to get load balanced between the front ends. On the Cluster IP Addresses box, click Add and type an available dedicated IP address and subn

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

Managed metadata is a hierarchical collection of centrally managed terms that you can define, and then use as attributes for items in Microsoft SharePoint Server 2010. This topic introduces the core concepts about managed metadata, and then describes ways to use managed metadata. The final section presents several benefits of incorporating managed metadata into your SharePoint Server 2010 solution. This topic includes: Understanding Managed Metadata Working with Managed Metadata Benefits of Using Managed Metadata Understanding Managed Metadata This section introduces several key concepts that are used in managed metadata, and that are the basis of objects that developers create and manage when creating custom managed metadata solutions. Terms and Term sets A term is a word or a phrase that can be associated with an item in SharePoint Server 2010. A term set is a collection of related terms. You can specify that a SharePoint Server 2010 column must contain a term from a s

A strange error occurred in one of my projects. In my SharePoint 2013 environment, I’ve a web application running on port 80. When I need another web app, I gave it port 89. After giving a CNAME , I setup AAM and IIS bindings so that users can access my web app by writing http://xxx.com.tr instead of http://sharepoint:89 . So everything worked fine except InfoPath. I have some InfoPath forms deployed on this new web app running on 89. When I tried to open any of this forms it gave me the following error.

Resolution : IIS  Reset

_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