SharePointSupport

I have got this error while trying to install SharePoint 2013 What is Max Degree of Parallelism ? When an instance of SQL Server runs on a computer that has more than one microprocessor or CPU, it detects the best degree of parallelism, that is, the number of processors employed to run a single statement, for each parallel plan execution. You can use the  max degree of parallelism  option to limit the number of processors to use in parallel plan execution. SQL Server considers parallel execution plans for queries, index data definition language (DDL) operations, and static and keyset-driven cursor population. Read this for more details http://technet.microsoft.com/en-us/library/ms189094.aspx How to fix it ? Open Microsoft SQL Server Management Studio Login with sysadmin user Right Click on instance name and select properties >> Advanced Change  Max Degree of Parallelism  to 1 Restart the SQL Service

It goes without saying that every part of an enterprise relies on technology. With more and more technology providers coming to the fore, it is not uncommon to find a variety of technology platforms across the units of an enterprise. To keep the pieces of the enterprise moving together there is often a need for integrating the platforms, which are built by different providers. This blog provides a brief overview of ServiceNow, and what is involved in integrating ServiceNow and SharePoint 2013. What is ServiceNow? ServiceNow is a software platform that supports IT Service Management and automates common business processes. It’s a software as a service (SaaS) platform that offers targeted solutions for various units of an enterprise like IT, HR, Operations and IT Business Management. More than two thousand enterprises around the world use the ServiceNow platform extensively for their daily operations. ServiceNow brings the following key benefits for an enterprise: • Improves service

Scenario : We were working for a client, they had many groups and we had to build a collaboration portal for all the groups. Key thing was few sites of some groups were already present in SharePoint 2010 in different standalone servers. Migration was a key thing here as the existing sites has huge data, and huge user base. The Requirement was to build a portal /web application which will have migrated sites and new set of sites as per agreed site structure. According to the agreed architecture and design we created a new web application and started building the site hierarchy. As part of this we followed the regular approach database detach –attach method and migrated the existing SharePoint 2010 site .Migration was successful and we were able to access the site  with the system account. Later we tried with couple of site admin accounts, to our surprise we were getting “ACCESS DENIED” with any other user id. Background: By default when we create a web application in SharePo

I had a task to create a proof of concept environment for SharePoint 2013 for a presentation to a top level exec. Installed and Configured a SharePoint 2013 farm on couple of VM's with dedicated WFE/APP and SQL Server boxes, as this will be used as a POF and the reqcuirements were not clear how long the boxes will be used. MS has released the deployment guide for 2013 must read before thinking of creating a new farm. Created a new web application on the new farm and a root level Site Collection based on Team Site Template. Till this moment everything was looking good. On accessing the Site got the following error : SharePoint returned the following error: Invalid URI: The URI is empty. Contact your system administrator for help in resolving this problem. My first encounter with an issue on 2013 on a vanilla environment, thought it would be good to have this as a reference. To resolve this, I had to create and configure my site i.e. Created a new web app for my site C

Error : "Cannot add the specified assembly to the GAC in SharePoint 2010" We had a solution deployed numerous times as it houses a line of business process in SharePoint 2010. On performing Upgrade Solution via  stsadm  or  Update-Solution  via Power Shell , encountered the error: cannot add the specified assembly to the GAC. We started by created a test solution package and deployed it on the environment which worked fine to identify whether the issue was with the Package or environment. On updating the LOB Solution , it couldn’t add the assembly to the GAC for LOB WSP, on one of the WFE servers. Performed an IISRESET and restarted the timer service on the failing WFE, deployed the WSP package again, it did work but when we tried updating it again at the later stage, got the same error. Solution  : I had to rely on  Process Explorer  to figure out what process was using the  DLL  and from where. The beauty of this tool is, it displays the list of processes ru

* 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