Posts

Showing posts with the label Service Application

Query-0 Server Not Responding - Event ID 2587

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

Failed to get the server time zone id. Exception: Microsoft.SharePoint.SPEndpointAddressNotFoundException: There are no addresses available for this application

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

Managed metadata

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

Unable to open any Excel Services spreadsheet "We're sorry. We ran into a problem completing your request. Please try again in a few minutes."

Resolution : IIS  Reset

"We’re sorry. We ran into a problem completing your request. Please try that again in few minutes." Excel Service SharePoint

Image
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

Share service applications across farms in SharePoint 2013

Image
In SharePoint 2013, some service applications can be shared across server farms. By publishing a service application, you can optimize resources, avoid redundancy, and provide enterprise-wide services without installing a dedicated enterprise services farm. You can publish the following service applications in a SharePoint 2013 farm: Business Data Connectivity Machine Translation Managed Metadata User Profile Search Secure Store Additionally, a SharePoint 2010 farm can consume services from a SharePoint 2013 Server farm. This allows for upgrade of multi-farm environments in which a farm hosting service applications is upgraded first. In this scenario, the service applications and features that the SharePoint 2010 farm experiences are limited to those that are available in SharePoint 2010. For example, a SharePoint 2010 farm cannot consume the Machine Translation service application from a SharePoint Server 2013 farm and does not benefit from the new features of the User Prof

Managed Metadata, Taxonomy

Image
One of the most talked about capabilities since the launch of SharePoint 2010 is the Managed Metadata Service .  For those of you who aren’t already familiar with this service and the support it provides for modelling and deploying a rich corporate taxonomy.   For those who need get to the basics, configuration & related features for it, we would recommend going thru the links available at " Managed Metadata and Taxonomy in SharePoint Server 2010 " We would use this blog post  to bring about some additional information on situations which you might face in day to day work . The Taxonomy Field is lookup field. The taxonomy field is a lookup field. The lookup list associated with this field is called the Taxonomy Hidden List. This list is located at http://siteURL/lists/taxonomyhiddenlist . It exists only on the root web of the site collection, and is used as lookup by all the site/list taxonomy fields within that site collection. Every time a term is used

Administer search in SharePoint Server 2013

Manage the search schema in SharePoint Server 2013 Learn how to view, add, edit, map, and delete crawled properties, crawled property categories and managed properties in the search schema. Manage the Search Center Learn about pages that are created in a Search Center site in SharePoint 2013, and see articles about how to configure Web Parts. Manage search relevance in SharePoint Server 2013 Learn how you can configure settings to provide the most relevant search results. Manage crawling in SharePoint Server 2013   Learn how to crawl content that you want users to be able to search for in SharePoint 2013. Manage the search topology in SharePoint Server 2013 Learn how to manage search components to scale out the search topology in SharePoint 2013. View search diagnostics in SharePoint Server 2013 Learn about search and usage reports, query health

Create a Search Topology in SharePoint 2013

As you may remember in SharePoint 2010 you had a specific user interface to create and reconfigure your enterprise Search topology, in the Search Service applications management.  There you can create, edit and remove the following components: Admin component Crawl components Crawl databases Query components Partitions And it was very easy by the administrator to use any server in their farm to configure the best enterprise Search topology for their business requirements. One thing than many people said to me was that the configuration was very easy with the UI, but if you put something wrong or your farm have any issue, when you finished to reconfigure your enterprise search topology, and you click in the button to apply all the changes, it takes a while and gives you an error and also you lose the majority of the changes that you made before. The above problem was a good reason to configure your enterprise search topology with Power Shell, because you have t