SharePointSupport

Error : SERVER1: Windows 2008 R2 (x64) SharePoint 2010 SERVER2: Windows 2008 R2 (x64) SQL 2008 Services running on SERVER1 : (none as localsystem, localservice, networkservice) SharePoint 2010 Administration (started/auto) SharePoint 2010 Timer (started/auto) SharePoint 2010 Tracing (started/auto) SharePoint 2010 User Code Host (stopped/disabled) SharePoint 2010 VSS Writer (stopped/manual) SharePoint Foundation Search V4 (started/manual) SharePoint Server Search 14 (started/manual) The RELATED ISSUE(s): Search/indexing is not working, and in return, backups are failing claiming: Failure Message Object Query-0 (D: on SERVER1) failed in event On Backu p Search Service Application reports: Index Partition - 0 - SERVER2\Search_Service_Application_PropertyStoreDB_9a482efd99954748a062952a3d2617d7 Query Component 0 SERVER1 Not Responding System Event Log on SERVER1 reports: Event ID 2587 The following conditions are currently affecting index propagation to

Symptoms When users perform a search in a Microsoft SharePoint environment, they receive the following error message: Internal server error exception: Troubleshoot issues with Microsoft SharePoint Foundation Additionally, the following critical exception may be written to the ULS log of the SharePoint Web front-end server:  Process : OWSTIMER.EXE (0x1CE0) Product : SharePoint Foundation Category : Topology EvendID : 8031 Message : An exception occurred while updating addresses for connected app {eaf6c00c-cc3f-460e-8bf2-ad9b991ea6ea_aa16845d-045a-46bc-bbc6-d701ff13950d}. The uri endpoint information may be stale. System.InvalidOperationException: The requested application could not be found at Microsoft.SharePoint.SPTopologyWebServiceApplicationProxy.ProcessCommonExceptions(Uri endpointAddress, String operationName, Exception ex, SPServiceLoadBalancerContext context) at Microsoft.SharePoint.SPTopologyWebServiceApplicationProxy.ExecuteOnChannel(String operationName, CodeBlock

This topic describes how to configure a Windows firewall for Database Engine access in SQL Server 2016 by using SQL Server Configuration Manager. Firewall systems help prevent unauthorized access to computer resources. To access an instance of the SQL Server Database Engine through a firewall, you must configure the firewall on the computer running SQL Server to allow access. For more information about the default Windows firewall settings, and a description of the TCP ports that affect the Database Engine, Analysis Services, Reporting Services, and Integration Services, see  Configure the Windows Firewall to Allow SQL Server Access . There are many firewall systems available. For information specific to your system, see the firewall documentation. The principal steps to allow access are: Configure the Database Engine to use a specific TCP/IP port. The default instance of the Database Engine uses port 1433, but that can be changed. The port used by the Database Engine is liste

Error : Failed to get the server time zone id. Exception: Microsoft.SharePoint.SPEndpointAddressNotFoundException: There are no addresses available for this application.  When I check the View Web Analytics Reports from Central Admin on Production, it throws the above error though it works on Test environment. To resolve this, I have performed the following steps by looking at the ULS Logs. Navigate to  Central Administration   System Settings  and click on  Manage Services on Server Stopped  the following two services though it was already started Web Analytics Data Processing Service Web Analytics Web Service Started  the above two services but when I check View Web Analytics Report, doesn’t seem to work. On Further checks found the  Manage Metadata Service App  wasn’t able to retrieve the metadata Stopped and Started  the  Managed Metadata Web Service This resolved the issue for me now able to view the Web Analytics Reports from Central Admin If it doesn’t

To prevent Enterprise keyword fields from offering suggestions from a team set then unckeck this setting  Office 2010/2013 can integrate with Managed Metadata site column If you want to use Content type hubs then you need to activate this site collection feature :Content Type Hub Syndication feature.

Farm Information: Web Application published internally and externally (so make sure both URLs added to  Alternate Access Mapping ) Office Web Apps 2013 (Published externally via  TMG 2010  and internally) I have a farm which connected to Office Web Apps 2013 and It's working fine internally so then we decided to enable it to open Office Web Apps externally by the following steps : 1- In Office Web Apps Server , Open Power Shell and run this command to add the External URL to existing Farm: Set-OfficeWebAppsFarm -ExternalURL  http://test.com/  2-In SharePoint Server , Open SharePoint 2013 Management Shell and run the following commands:  Remove-SPWOPIBinding –All:$true New-SPWOPIBinding -ServerName OfficeWebAppServer.com -AllowHTTP Set-SPWopiZone internal-http $c = Get-SPSecurityTokenServiceConfig $c.AllowOAuthOverHttp = $true $c.Update()  then when I tried to access the Office documents from External URL I got the following error : "Sorry,we can't o

Image Renditions Good Ref : http://blog.mastykarz.nl/image-renditions-sharepoint-2013/ http://msdn.microsoft.com/en-us/library/jj720398.aspx http://msdn.microsoft.com/en-us/library/jj720392.aspx http://sp2013.blogspot.com/2012/07/image-renditions.html Required to enable Blob Cache IFrame Support Good Ref : http://www.learningsharepoint.com/2012/11/24/how-to-use-iframes-in-sharepoint-2013/ SEO ,Friendly URLs and SiteMap Good Ref : http://blog.mastykarz.nl/search-engine-optimization-sharepoint-2013/ http://www.informedconsulting.nl/blog/?p=283 Managed Navigation Good Ref : http://blog.robgarrett.com/2012/09/23/sharepoint-2013-managed-navigation / Cross Site Publishing Good Ref : http://sharepoint.microsoft.com/blog/Pages/BlogPost.aspx?pID=1038 http://blogs.msdn.com/b/justinvoels/archive/2012/09/24/sharepoint-2013-search-driven-publishing-and-cross_2d00_site-collection-publishing-overview.aspx http://blog.mastykarz.nl/easier-working-assets-cross-si

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