There was a problem retrieving data for this field. Updating values in the field is disabled temporarily. You can still update values in other fields.

Issue: There was a problem retrieving data for this field. Updating values in the field is disabled temporarily. You can still update values in other fields.                                                                     

                              

                                                                                                                                                            Cause: Properties containing these fields are linked to the Managed Metadata Service Application. These particular properties require a healthy Managed Metadata Service Application\Service Connection as well as associated (service instance) to be started    (or)
 The Managed Metadata Service Connection is missing from the associated proxy group

      Solution: Please check the below steps.

1.    Ensure the Managed Metadata Web Service started in application management->service application->manage services on server.

                           

         

2.    Ensure the service application “managed meta data service” created and started in Application management->service application->manage service application.

       

                

3.    If the Managed meta data service application is working fine, then data in the field will get update.

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help!!!

This item could not be crawled because the repository did not respond within the specified time out period.

  This item could not be crawled because the repository did not respond within the specified time out period.

                                                                             

   Detailed issue: "This item could not be crawled because the repository did not respond within the specified timeout period. Try to crawl the repository at a later time, or increase the timeout value on the Proxy and Timeout page in search administration. You might also want to crawl this repository during off-peak usage times"

   Solution 1:  Increase the timeout value on the Proxy and Timeout page in            search administration. Follow the below steps

·        Go to central admin->Manage service Applications

·        Click on Search service application.

·        Go to farm search administration below central administration.

·        Click on Time out seconds and change.

                                                                                                        

                                                         

NOTE: Increasing time out value causes the performance issue. 

Solution 2 : similar cases caused by IE proxy settings also. You can try to edit the

Internet Options>Connections>LAN settings. Uncheck ‘Automatically detect settings’. And check the crawl again.

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

December 2013 Cumulative Update Packages

     December 2013 Cumulative Update Packages: 

                              

December 2013 Cumulative Update Packages for SharePoint Foundation 2010, SharePoint Server 2010 and Project Server 2010 have been released. 

Use the following links to download the update packages:

December 2013 CU for SharePoint Foundation 2010 - KB 2849990 http://support.microsoft.com/kb/2849990

December 2013 CU for SharePoint Server 2010 - KB 2849971 http://support.microsoft.com/kb/2849971

December 2013 CU for Project Server 2010 - KB 2849972 http://support.microsoft.com/kb/2849972

 


Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

This item and all items under it will not be crawled because the owner has set the No Crawl flag to prevent it from being searchable in SharePoint 2013:

 This item and all items under it will not be crawled because the owner has set the No Crawl flag to prevent it from being searchable in SharePoint 2013:

                                                                     

                     

  Issue: After configuring Search service application and set everything, when crawling sites giving the error” This item and all items under it will not be crawled because the owner has set the No Crawl flag to prevent it from being searchable”

 Cause: This error may appear in the crawl log when you are trying to crawl SharePoint sites. This is particularly likely for the My Sites host because this template has the flag set to No Crawl by default

  Solution: to Resolve the issue and avoid errors in Crawl log. Follow the below steps.

·        go to your My Sites URL

·        go to Site Settings.

·        Under Search ->go to Search and Offline Availability.

·        Set the flag to  Yes in Indexing site content “Allow this site to appear in search results.

      

                                                                                                                                                                                     

                                                               

Note: Check the Above settings and follow the same steps for Search site(site created with search template)

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

Unable to create the new search service application in SharePoint 2013

  Error creating new search service application in SharePoint 2013

 Sorry something went wrong, unable to create the new search service application.         

                                                

        

   Issue Details:

·        An unhandled exception occurred in the user interface.Exception Information: An object of the type Microsoft.SharePoint.Administration.SPIisWebServiceApplicationPool named "Search Service Application 1" already exists under the parent Microsoft.SharePoint.Administration.SPIisWebServiceSettings named "SharePoint Web Services".  Rename your object or delete the existing object.

                      Technical Details

                      Troubleshoot issues with Microsoft SharePoint Foundation.

                       Correlation ID: 0b7e5f9c-a8bc-c066-02a7-4f9923b0ae03

 Cause:

·        If you fill in the same application pool name for both the Search Admin Web Service and the Search Query and Site Settings Web Service and this application pool doesn't already exist yet, you will see this error, because it tries to create the application pool with that name twice while provisioning the service app 

    Solution:

·       Use different application pools for the Search Admin Web Service, Search Query and Site Settings Web Service

            

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!