Search Service Distribution in SharePoint 2013

Hi
We have 
 APP 1, APP2, WFE1, WFE2, INDEX servers in the farm. Question is should we run the search service on all servers?
Thanks,
srabon

you can make an independent search server rather than running search services on each of them

Similar Messages

  • How to create Search Service Application in SharePoint 2013

    When I am Creating Search Service Application through SharePoint Central Administration I am getting the error:
    Path of how I created It:
    Central Administration->Application Management->Manage Service Applications
    Here Click on New and Select Search Service Application
    How Should I create new search service application?
    As I want to create crawled Property and manage property for Search Center in SharePoint On Premises.

    Hi darsh,
    For creating a new search service application, you can refer to the blog:
    http://technet.microsoft.com/en-us/library/gg502597.aspx
    http://blogs.technet.com/b/praveenh/archive/2013/02/07/create-a-new-search-service-application-in-sharepoint-2013-using-powershell.aspx
    http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=378  
    For your issue , please refer to the article:
    http://praveensharepointknowledgebase.wordpress.com/2012/05/29/error-while-creating-search-service-application/ 
    Best Regards,
    Eric
    Eric Tao
    TechNet Community Support

  • Installed SQL Reporting Services 2012 on SharePoint 2013 Server. SQL Reporting Service not available In the list of runnning services or new service applications

    Hi I'm trying to setup SQL reporting services in a SharePoint 2013 farm consisting of:
    4 WFE's
    4 App Servers (NLB Central Admin x 4 servers)
    4 App Severs for SSRS (Light limited SharePoint services running)
    I've installed SSRS 2012 SP1 by following the guide (http://msdn.microsoft.com/en-us/library/gg492276.aspx) on one of the SSRS SharePoint 2013 servers and ensuring Reporting Services - SharePoint and Reporting Services Add-in for SharePoint Products is selected.
    All completed without errors and I have even upgraded to SP2 for troubleshooting but no joy.
    I've then gone into SharePoint Central Admin and I cannot see SQL Reporting Service available In the list of runnning services on the server I have just installed SSRS on and going to manage service applications I cannot see in the new dropdown menu SQL
    Reporting Services.
    I have ran the following commands in the SHarePoint management shell:
    Install-SPRSService and Install-SPRSSeviceProxy
    and
    get-spserviceinstance -all |where {$_.TypeName -like "SQL Server Reporting*"} | Start-SPServiceInstance
    The reply was that the service was already online on the server.
    So in powershell all seems ok but it does not appear in central administration.
    I have also moved Central Administration to the SSRS SharePoint server too.
    Any other suggestions? Here is the same problem but in SP2010 (http://social.technet.microsoft.com/Forums/office/en-US/6a21cc05-1f9b-49ad-a9bb-44aa5b3ce312/action?threadDisplayName=after-installing-sql-reporting-services-service-for-sharepoint-2012-service-is-not-in-the-list-of)
    In my lab environment of a 4 server SP2013 farm it worked immediately when i installed it on the app server (CA host) so I dont think it is my install strategy.
    I guess my next attempt is to install SSRS on an app server with central administration hosted.
    Thanks

    I had the same issue on 2 different environments.
    I had 2 application servers. One had Central Administration. I installed SSRS on the other one and it never appeared in the Service Applications in SharePoint.
    When I also provisioned Central Administration on the other application server and went to the service applications using Central Admin on that server, the SSRS service application was there.
    Since then I always install SSRS on the server which hosts Central Admin. No issues then.

  • PowerShell command To configure Access Service 2010 in sharepoint 2013 server

    HI ,
    can any body give reference for Powershell command for
    Access Service 2010
    I am currently able to run powershell command for
    Access Service .
    But in sharepoint 2013,Access Service 2010 is a new service, but i am not able to see any refernce blog for command.

    Hi,
    According to your description, you want to configure Access Service 2010 in SharePoint 2013 server by using a Windows PowerShell.
    Take a look at an articles about configuring services and service applications in SharePoint 2013:
    http://technet.microsoft.com/en-us/library/ee794878(v=office.15).aspx
    Updates on how to do a lot of these (include
    configure Access Service 2010 ) with PowerShell haven't really been released yet. 
    Here is an article about configuring a service application by using a Windows PowerShell script (SharePoint Server 2010), you can use as a reference:
    http://technet.microsoft.com/en-us/library/gg983005(v=office.14).aspx
    Best Regards,
    Lisa Chen
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Lisa Chen
    TechNet Community Support

  • Advanced Search Web Part in SharePoint 2013

    I would like to know more about advance search web part in SharePoint 2013. How it looks and implementation ?

    Hi,
    Please go through below video/links for more details on SharePoint 2013 Search and associated feature.
    http://www.youtube.com/watch?v=T1J_pMD7V_4
    https://social.technet.microsoft.com/forums/sharepoint/en-US/99e6d5f2-76da-4fdd-8464-24159f12cee1/advanced-search-box-web-part-is-missing
    Hope this helps you.
    Regards
    Soni K

  • Set up Search Service App For SharePoint server 2013 on Windows server 2012 R2 not working

    Hi all,
    I installed SharePoint server 2013 on Windows  server 2012 R2 using VirtualBox.  I created a DC(domain controller) server with a domain set up on one VM and it has SQL server 2012 SP1 installed. Then SharePoint 2013 on another VM was set up to access
    the DC server.  Everything seems working except Search Service App which cannot be sucessfully set up. Creation process for Search service app says Successful and 4 search databases were created and look fine. But when I navigate to search service app
    admin page, it gives error info:
    System status:  The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component '386f2cd6-47ca-4b3a-aeb5-d9116772ef16' in search application 'Search Service Application 1' is in
    a good state and try again.
    Search Application Topology:  Unable to retrieve topology component health states. This may be because the admin component is not up and running.
    From event viewer, I see following errors:
    (1) Error From source: SharePoint Server
    Application Server Administration job failed for service instance  Microsoft.Office.Server.Search.Administration.SearchServiceInstance
    (b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
    Reason: The object you are trying to create already exists. Try again using a different name.  
    Technical Support Details:
    System.Runtime.InteropServices.COMException (0x80040D02): The object you are trying to create already exists. Try again using a different name.  
       at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
       at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean
    isAdministrationServiceJob)
    (2) Error From source: SharePoint Server Search
    Could not access the Search database. A generic error occurred while trying to access the database to obtain the schema version info.
    Context: Application '386f2cd6-47ca-4b3a-aeb5-d9116772ef16'
    (3) Warning from source: SharePoint Server Search
    A database error occurred. Source: .Net SqlClient Data Provider Code: 8169 occurred 0 time(s) Description:  Error ordinal: 1 Message:
    Conversion failed when converting from a character string to uniqueidentifier., Class: 16, Number: 8169, State: 2    at
    System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
    (4) Error From source: SharePoint Server
    Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance
    (b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
    Reason: The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have been upgraded.  
    Technical Support Details:
    System.Runtime.InteropServices.COMException (0xC0041235): The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have
    been upgraded.  
    Since separate DC server and SharePoint server do not work, I installed SharePoint 2013 on DC server ( so DC server has everything on it now ) but it gives exactly same result. Later I installed SharePoint 2013 SP1 and still have the same problem with Search
    Service app. I spent two weeks tried all suggestions available from Web and Google but SharePoint Search Service simply does not work. Config and other databases work but why Search Service has this issue seemingly related to search DB.
    Could anybody please help out? You deserve a top SharePoint consultant award if you could find a solution. I am so frustrated and so tired by this issue.    This seems also to be a SP set up issue.
    Thanks a lot.

    Using new Search Service App wizard to create SSA is always a success. I could delete existing SSA and recreate it and no problem. It says successful but when I open Search Admin page from CA, it gives me errors as mentioned.
    Now I used the following PS script for creating SSA from Max Mercher, but it stays at the last setps in following script:
    Add-PsSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue
    $IndexLocation = "C:\Search"  #Location must be empty, will be deleted during the process!
    $SearchAppPoolName = "SSAPool"
    $SearchAppPoolAccountName = "mydomain\admin"
    $SearchServiceName = "SSA"
    $SearchServiceProxyName = "SSA Proxy"
    $DatabaseServer = "W12R2DC1"
    $DatabaseName = "SSA"
    $spAppPool = Get-SPServiceApplicationPool -Identity $SearchAppPoolName -ErrorAction SilentlyContinue
    if (!$spAppPool)
     $spAppPool = New-SPServiceApplicationPool -Name $SearchAppPoolName -Account $SearchAppPoolAccountName -Verbose
    $ServiceApplication = Get-SPEnterpriseSearchServiceApplication -Identity $SearchServiceName -ErrorAction SilentlyContinue
    if (!$ServiceApplication)
    # process stays at the following step forever, already one hour now.  
    $ServiceApplication = New-SPEnterpriseSearchServiceApplication -Name $SearchServiceName -ApplicationPool $spAppPool.Name -DatabaseServer  $DatabaseServer -DatabaseName $DatabaseName
    Account mydomain\admin is an farm managed account, domain admin account, in WG_ADMIN role, It is in all SQL server roles and is DBO. I see search DBs are already on SQL server. From Event viewer, I got following errors in sequence:
    (1) Crawler:Content Plugin under source Crawler:Content Plugin 
    Content Plugin can not be initialized - list of CSS addresses is not set.
    (2) Warning for SharePoint Server Search
    A database error occurred. Source: .Net SqlClient Data Provider Code: 8169 occurred 0 time(s) Description:  Error ordinal: 1 Message: Conversion failed when converting from a character string to uniqueidentifier., Class: 16, Number: 8169, State: 2   
    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
    (3) Error for SharePoint Server Search
    Could not access the Search database. A generic error occurred while trying to access the database to obtain the schema version info.
    Context: Application 'cbc5a055-996b-44a7-9cbc-404322f9cfdf'
    (4) Error for SharePoint Server
    Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
    Reason: The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have been upgraded. 
    (5) Error Shared Services for SharePoint Server Search 
    Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
    Reason: The object you are trying to create already exists. Try again using a different name. 
    Technical Support Details:
    System.Runtime.InteropServices.COMException (0x80040D02): The object you are trying to create already exists. Try again using a different name. 
       at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
       at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob
    Above errors keep being generated. Last step for SSA creation stay there forever.  Any clue what is really going on?  Thanks.

  • SharePoint 2010 search webservices compatibility with SharePoint 2013

    Please let us know whether the SharePoint 2010 search webservice is compatible with SharePoint 2013.
    When we try to hit the SharePoint 2013 search service with the query developed in the Sharepoint 2010 , we are getting "System.Not supported" exception as response from server.
    Below is the search query we are using:
    "<soap:Envelope xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\" xmlns:soap=\"http://schemas.xmlsoap.org/soap/envelope/\">"
                + "<soap:Body>"
                + "<Query xmlns=\"urn:Microsoft.Search\">"
                + "<queryXml>"
                + "&lt;QueryPacket xmlns=\"urn:Microsoft.Search.Query\"&gt;"
                + "&lt;Query&gt;"
                + "&lt;Range&gt;&lt;StartAt&gt;1&lt;/StartAt&gt;&lt;Count&gt;50&lt;/Count&gt;&lt;/Range&gt;"
                + "&lt;SupportedFormats&gt;"
                + "&lt;Format&gt;urn:Microsoft.Search.Response.Document:Document&lt;/Format&gt;"
                + "&lt;/SupportedFormats&gt;"
                + "&lt;Context&gt;"
                + "&lt;QueryText type=\"MSSQLFT\"&gt; SELECT fileName,Title,Path,Write,SiteName,URL,FileExtension,isDocument,contentClass FROM scope() WHERE CONTAINS(Path, SITE_PORT)
    and (contentClass = 'STS_Web' OR contentClass = 'STS_ListItem_DocumentLibrary' OR contentClass = 'STS_List_DocumentLibrary') ORDER BY lastModifiedTime DESC &lt;/QueryText&gt;"
                + "&lt;/Context&gt;"
                + "&lt;/Query&gt;"
                + "&lt;/QueryPacket&gt;"
                + "</queryXml>"
                + "</Query>"
                + "</soap:Body>"
                + "</soap:Envelope>";
    Please  help

    Hi Raghuramk,
    is the web service is a search query web service? if yes, i suppose sharepoint 2013 already deprecated,
    Search Query web service
    Description: The Search Query web service is deprecated in SharePoint 2013.
    In SharePoint Server 2010, the Search Query web service exposes the SharePoint Enterprise Search capabilities to client applications. This enables you to access search results from client and web applications outside the context of a SharePoint site.
    Reason for change: The Search Query web service is deprecated because the client object model (CSOM) and a new REST-based web service are available for developing Office-wide extensibility scenarios. The CSOM exposes the same functionality
    as the Search Query web service, and a larger set of functionality for stand-alone client applications.
    http://technet.microsoft.com/en-us/library/ff607742.aspx#section2
    Regards,
    Aries
    Microsoft Online Community Support
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Hybrid Search not working from SharePoint 2013 Online to SharePoint On-premise

    Hi,
    I have setup a SharePoint 2013 Hybrid environment setup with the following –
    Windows Server 2012 R2
    SharePoint Server 2013 with April 2014 CU
    SQL Server 2014
    ADFS 3.0 using SSO with Web proxy and DirSync
    SharePoint 2013 Online tenant on Office 365 Enterprise Subscription
    I have configured the Hybrid following the article
    http://technet.microsoft.com/en-us/library/jj838715(v=office.15).aspx and configured Hybrid Search. The hybrid environment was working fine including Search both ways initially
    but after upgrade to April CU 2014 (along with upgrade to SQL 2014 from SQL 2012), now search from SharePoint online to SharePoint in-Premise is not working anymore.
    I am still able login with the federated IDs in both the environments and get results from SharePoint Online in SharePoint in-Premise environment.
    I have already tried most of the troubleshooting steps mentioned at
    http://technet.microsoft.com/en-us/library/dn518363(v=office.15).aspx
    Now every time, we perform a search in our SharePoint Online site, which is configured to show hybrid results from SharePoint in-premise, we don’t get results from in-premise and instead we see the following error logged in SharePoint
    In-premise Web Server –
    Error - An exception occurred when trying to issue security token: Exception of type 'System.ArgumentException' was thrown. Parameter name: value.
    And ULS log shows the following – Even though the message seems apparent that there could be duplicate users in user profile Application, but that’s not the case. There are just 2 unique users added there.
    06/04/2014 12:58:41.59 w3wp.exe (0x1C88)                       0x2494  SharePoint Portal Server     
            User Profiles                      ae0sx               
    Unexpected       Error trying to search in the UPA. The exception message is 'System.ArgumentException: Exception of type 'System.ArgumentException' was thrown.  Parameter name: value     at Microsoft.SharePoint.Administration.Claims.SPIdentityProviders.GetIdentityProviderType(String
    value)     at Microsoft.Office.Server.Security.UserProfileIdentityClaimMapper.SearchUsingNameIdOrThrow(UserProfileManager upManager, String nameId, String nameIdIssuer)     at Microsoft.Office.Server.Security.UserProfileIdentityClaimMapper.GetSingleUserProfileFromClaimsList(UserProfileManager
    upManager, IEnumerable`1 identityClaims)'  4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1C88)                       0x2494  SharePoint Foundation        
            Monitoring                         b4ly        Verbose                
    Leaving Monitored Scope (Executing the user mapping operation in GetMappedIdentityClaim()). Execution Time=1.4449                4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1C88)                       0x2494  SharePoint Portal Server     
            User Profiles                      ae0su    High       The set of claims
    could not be mapped to a single user identity. Exception Exception of type 'System.ArgumentException' was thrown.  Parameter name: value has occured.      4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1C88)                       0x2494  SharePoint Foundation      
              Monitoring                         b4ly        Verbose
                    Leaving Monitored Scope (Inside SPIdentityClaimMapperOperations.GetClaimFromExternalMapper(); calling the registered SPIdentityClaimMapper). Execution Time=1.5596            
    4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1C88)                       0x2494  SharePoint Foundation       
             Claims Authentication                    ae0tc               
    High       The registered mappered failed to resolve to one identity claim. Exception: System.InvalidOperationException: Exception of type 'System.ArgumentException' was thrown.  Parameter name: value ---> System.ArgumentException:
    Exception of type 'System.ArgumentException' was thrown.  Parameter name: value     at Microsoft.SharePoint.Administration.Claims.SPIdentityProviders.GetIdentityProviderType(String value)     at Microsoft.Office.Server.Security.UserProfileIdentityClaimMapper.SearchUsingNameIdOrThrow(UserProfileManager
    upManager, String nameId, String nameIdIssuer)     at Microsoft.Office.Server.Security.UserProfileIdentityClaimMapper.GetSingleUserProfileFromClaimsList(UserProfileManager upManager, IEnumerable`1 identityClaims)    
    --- End of inner exception stack trace ---     at Microsoft...            4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59*               w3wp.exe (0x1C88)                      
    0x2494  SharePoint Foundation                 Claims Authentication                        
    ae0tc     High                    ....Office.Server.Security.UserProfileIdentityClaimMapper.GetSingleUserProfileFromClaimsList(UserProfileManager
    upManager, IEnumerable`1 identityClaims)     at Microsoft.Office.Server.Security.UserProfileIdentityClaimMapper.<>c__DisplayClass2.<GetMappedIdentityClaim>b__0()     at Microsoft.SharePoint.SPSecurity.<>c__DisplayClass5.<RunWithElevatedPrivileges>b__3()    
    at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)     at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param)     at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated
    secureCode)     at Microsoft.Office.Server.Security.UserProfileIdentityClaimMapper.GetMappedIdentityClaim(Uri context, IEnumerable`1 identityClaims)     ...           
    4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1C88)                       0x2494  SharePoint Foundation        
            Claims Authentication                    af3zp               
    Unexpected       STS Call Claims Saml: Problem getting output claims identity. Exception: 'System.InvalidOperationException: Exception of type 'System.ArgumentException' was thrown.  Parameter name: value ---> System.ArgumentException:
    Exception of type 'System.ArgumentException' was thrown.  Parameter name: value     at Microsoft.SharePoint.Administration.Claims.SPIdentityProviders.GetIdentityProviderType(String value)     at Microsoft.Office.Server.Security.UserProfileIdentityClaimMapper.SearchUsingNameIdOrThrow(UserProfileManager
    upManager, String nameId, String nameIdIssuer)     at Microsoft.Office.Server.Security.UserProfileIdentityClaimMapper.GetSingleUserProfileFromClaimsList(UserProfileManager upManager, IEnumerable`1 identityClaims)     ---
    End of inner exception stack trace ---     at Microsoft.O...       4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1C88)                       0x2494  SharePoint
    Foundation                 Claims Authentication                    fo1t               
    Monitorable       STS Call: Failed to issue new security token. Exception: System.InvalidOperationException: Exception of type 'System.ArgumentException' was thrown.  Parameter name: value ---> System.ArgumentException:
    Exception of type 'System.ArgumentException' was thrown.  Parameter name: value     at Microsoft.SharePoint.Administration.Claims.SPIdentityProviders.GetIdentityProviderType(String value)     at Microsoft.Office.Server.Security.UserProfileIdentityClaimMapper.SearchUsingNameIdOrThrow(UserProfileManager
    upManager, String nameId, String nameIdIssuer)     at Microsoft.Office.Server.Security.UserProfileIdentityClaimMapper.GetSingleUserProfileFromClaimsList(UserProfileManager upManager, IEnumerable`1 identityClaims)    
    --- End of inner exception stack trace ---     at Microsoft.Office.Server.Secu...    4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59*               w3wp.exe (0x1C88)                      
    0x2494  SharePoint Foundation                 Claims Authentication                   
    fo1t                Monitorable       ...rity.UserProfileIdentityClaimMapper.GetSingleUserProfileFromClaimsList(UserProfileManager upManager, IEnumerable`1
    identityClaims)     at Microsoft.Office.Server.Security.UserProfileIdentityClaimMapper.<>c__DisplayClass2.<GetMappedIdentityClaim>b__0()     at Microsoft.SharePoint.SPSecurity.<>c__DisplayClass5.<RunWithElevatedPrivileges>b__3()    
    at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)     at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param)     at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated
    secureCode)     at Microsoft.Office.Server.Security.UserProfileIdentityClaimMapper.GetMappedIdentityClaim(Uri context, IEnumerable`1 identityClaims)     at Microsoft.ShareP...    4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59*               w3wp.exe (0x1C88)                      
    0x2494  SharePoint Foundation                 Claims Authentication                   
    fo1t                Monitorable       ...oint.IdentityModel.SPIdentityClaimMapperOperations.GetClaimFromExternalMapper(Uri contextUri, List`1 claims)    
    at Microsoft.SharePoint.IdentityModel.SPIdentityClaimMapperOperations.ResolveUserIdentityClaim(Uri contextUri, ClaimCollection inputClaims)     at Microsoft.SharePoint.IdentityModel.SPIdentityClaimMapperOperations.GetIdentityClaim(Uri contextUri,
    ClaimCollection inputClaims, SPCallingIdentityType callerType)     at Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.GetLogonIdentityClaim(SPRequestInfo requestInfo, IClaimsIdentity inputIdentity, IClaimsIdentity outputIdentity,
    SPCallingIdentityType callerType)     at Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.EnsureSharePointClaims(SPRequestInfo requestInfo, IClaimsIdentity outputIdentity, SPCallingIdentityTy...     4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59*               w3wp.exe (0x1C88)                      
    0x2494  SharePoint Foundation                 Claims Authentication                   
    fo1t                Monitorable       ...pe callerType)     at Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.AugmentOutputIdentityForRequest(SPRequestInfo
    requestInfo, IClaimsIdentity outputIdentity)     at Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.GetOutputClaimsIdentity(IClaimsPrincipal principal, RequestSecurityToken request, Scope scope)     at Microsoft.IdentityModel.SecurityTokenService.SecurityTokenService.Issue(IClaimsPrincipal
    principal, RequestSecurityToken request)     at Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.Issue(IClaimsPrincipal principal, RequestSecurityToken request)              
    4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1C88)                       0x2494  SharePoint Foundation        
            Monitoring                         b4ly        Verbose                
    Leaving Monitored Scope (SPSecurityTokenService.Issue). Execution Time=6.3185          4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1C88)                       0x2494  SharePoint Foundation        
            Monitoring                         nass       Verbose                
    ____CPU Cycles=12774004          4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1C88)                       0x2494  SharePoint Foundation        
            Monitoring                         nass       Verbose                
    ____Execution Time=6.3185       4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1C88)                       0x2494  SharePoint Foundation        
            Monitoring                         nasq      Verbose                
    Entering monitored scope (CleanUpSecurityTokenServiceOperation). Parent ExecuteSecurityTokenServiceOperationServer                4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1C88)                       0x2494  SharePoint Foundation        
            Monitoring                         b4ly        Verbose                
    Leaving Monitored Scope (CleanUpSecurityTokenServiceOperation). Execution Time=0.0282     4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1C88)                       0x2494  SharePoint Foundation        
            Monitoring                         nass       Verbose                
    ____CPU Cycles=14832078          4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1C88)                       0x2494  SharePoint Foundation        
            Monitoring                         nass       Verbose                
    ____Execution Time=0.0282       4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1C88)                       0x2494  SharePoint Foundation        
            Monitoring                         b4ly        Medium                 
    Leaving Monitored Scope (ExecuteSecurityTokenServiceOperationServer). Execution Time=7.2841         4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1C88)                       0x2494  SharePoint Foundation        
            Monitoring                         nass       Verbose                
    ____WebPart Events Offsets=0                4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1C88)                        0x2494  SharePoint Foundation        
            Monitoring                         nass       Verbose                
    ____User Address=       4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1C88)                       0x2494  SharePoint Foundation     
               Monitoring                         nass       Verbose
                    ____=00000000-0000-0000-0000-000000000000 4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1C88)                       0x2494  SharePoint Foundation        
            Monitoring                         nass       Verbose                
    ____Log Correlation Id=4c8b979c-f112-d050-9764-c445282f9184               4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1C88)                       0x2494  SharePoint Foundation        
            Monitoring                         nass       Verbose                
    ____Service Calls=0        4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1C88)                       0x2494  SharePoint Foundation        
            Monitoring                         nass       Verbose                
    ____Claims Counter=0  4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1C88)                       0x2494  SharePoint Foundation        
            Monitoring                         nass       Verbose                
    ____Critical Events=0    4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1C88)                       0x2494  SharePoint Foundation        
            Monitoring                         nass       Verbose                
    ____ULS Large Gap=      4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1C88)                       0x2494  SharePoint Foundation        
            Monitoring                         nass       Verbose                
    ____Execution Time=7.2841       4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1C88)                       0x2494  SharePoint Foundation        
            Monitoring                         nass       Verbose                
    ____CPU Cycles=0          4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1C88)                       0x2494  SharePoint Foundation        
            Monitoring                         nass       Verbose                
    ____Current SharePoint Operations=0  4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1C88)                       0x2494  SharePoint Foundation        
            Monitoring                         nass       Verbose                
    ____SPRequest Objects=2          4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1C88)                       0x2494  SharePoint Foundation        
            Monitoring                         nass       Verbose                
    ____Distributed Cache=0            4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1C88)                        0x2494  SharePoint Foundation        
            Monitoring                         nass       Verbose                
    ____SQL Query Count=0              4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1C88)                       0x2494  SharePoint Foundation        
            Monitoring                         nass       Verbose                
    ____Current User=        4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1C88)                       0x2494  SharePoint Foundation        
            Monitoring                         nass       Verbose                
    ____Request Management=     4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1C88)                        0x2494  SharePoint Foundation        
            Monitoring                         nass       Verbose                
    ____Page Checkout Level=Published     4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1C88)                       0x2494  SharePoint Foundation        
            Logging Correlation Data               77a3                Verbose              
    Ending correlation. Transfer to 4c8b979c-f112-d050-9764-c834ee4cf36d 4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1C88)                       0x2494  SharePoint Foundation        
            Unified Logging Service                 cn4g                Verbose
                  Trace level override is turned off.             4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1C88)                       0x2494  SharePoint Foundation        
            Logging Correlation Data               77a3                Verbose              
    Ending correlation.          4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1EEC)                       0x26BC SharePoint Foundation        
            Monitoring                         nasq      Verbose                
    Entering monitored scope (CleanUpSecurityTokenServiceOperation). Parent ExecuteSecurityTokenServiceOperationCaller:http://docs.oasis-open.org/ws-sx/ws-trust/200512/RST/Issue     4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1EEC)                       0x26BC SharePoint Foundation        
            Monitoring                         b4ly        Verbose                
    Leaving Monitored Scope (CleanUpSecurityTokenServiceOperation). Execution Time=0.0257     4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1EEC)                        0x26BC SharePoint Foundation        
            Monitoring                         nass       Verbose                
    ____Execution Time=0.0257       4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1EEC)                       0x26BC SharePoint Foundation     
               Monitoring                         nass       Verbose
                    ____CPU Cycles=2377140            4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1EEC)                       0x26BC SharePoint Foundation        
            Monitoring                         b4ly        Verbose                
    Leaving Monitored Scope (ExecuteSecurityTokenServiceOperationCaller:http://docs.oasis-open.org/ws-sx/ws-trust/200512/RST/Issue). Execution Time=13.2855           4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1EEC)                       0x26BC SharePoint Foundation        
            Monitoring                         nass       Verbose                
    ____Execution Time=13.2855    4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1EEC)                       0x26BC SharePoint Foundation        
            Monitoring                         nass       Verbose                
    ____CPU Cycles=0          4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1EEC)                       0x26BC SharePoint Foundation        
            Claims Authentication                    fsq7               
    High       SPSecurityContext: Request for security token failed with exception: System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: Exception of type 'System.ArgumentException' was thrown.  Parameter name:
    value (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is: System.InvalidOperationException: Exception of type 'System.ArgumentException' was thrown.  Parameter name: value ----> System.ArgumentException:
    Exception of type 'System.ArgumentException' was thrown.  Parameter name: value    at Microsoft.SharePoint.Administration.Claims.SPIdentityProviders.GetIdentityProviderType(String value)     at Microsoft.Office.Server.Security.UserProfileIdentityClaimMapper.SearchUsingNameIdOrThrow(UserProfileManager
    upManager, ...                4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59*               w3wp.exe (0x1EEC)                      
    0x26BC SharePoint Foundation                 Claims Authentication                        
    fsq7       High       ...String nameId, String nameIdIssuer)     at Microsoft.Office.Server.Security.UserProfileIdentityClaimMapper.GetSingleUserProfileFromClaimsList(UserProfileManager
    upManager, IEnumerable`1 identityClaims)    --- End of inner ExceptionDetail stack trace ---    at Microsoft.Office.Server.Security.UserProfileIdentityClaimMapper.GetSingleUserProfileFromClaimsList(UserProfileManager upManager,
    IEnumerable`1 identityClaims)     at Microsoft.Office.Server.Security.UserProfileI...).       4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1EEC)                        0x26BC SharePoint Foundation        
            Claims Authentication                    8306               
    Critical   An exception occurred when trying to issue security token: Exception of type 'System.ArgumentException' was thrown.  Parameter name: value.               4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1EEC)                       0x26BC SharePoint Foundation        
            Monitoring                         b4ly        Verbose                
    Leaving Monitored Scope ([S2S] Getting token from STS and setting Thread Identity). Execution Time=16.83       4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1EEC)                       0x26BC SharePoint Foundation        
            Monitoring                         nass       Verbose                
    ____Execution Time=16.83         4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1EEC)                       0x26BC SharePoint Foundation        
            Monitoring                         nass       Verbose                
    ____CPU Cycles=7084490            4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1EEC)                       0x26BC SharePoint Foundation        
            Monitoring                         b4ly        Medium                 
    Leaving Monitored Scope (Application Authentication Pipeline). Execution Time=20.6415             4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1EEC)                       0x26BC SharePoint Foundation        
            Monitoring                         nass       Verbose                
    ____Execution Time=20.6415    4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1EEC)                       0x26BC SharePoint Foundation        
            Monitoring                         nass       Verbose                
    ____CPU Cycles=14789795          4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1EEC)                       0x26BC SharePoint Foundation        
            Application Authentication          ajezs                High       SPApplicationAuthenticationModule:
    Error authenticating request, Error details { Header: {0}, Body: {1} }.  Available parameters: 3001000;reason="There has been an error authenticating the request.";category="invalid_client" {"error_description":"Exception
    of type 'System.ArgumentException' was thrown.\u000d\u000aParameter name: value"} .       4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59 w3wp.exe (0x1EEC)                       0x26BC SharePoint Foundation    
                General                               
    8nca       Medium                  Application error when access /_vti_bin/sites.asmx, Error=Exception of type 'System.ArgumentException' was thrown. 
    Parameter name: value   at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.ReadResponse(Message response)     at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst, RequestSecurityTokenResponse&
    rstr)     at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst)     at Microsoft.SharePoint.SPSecurityContext.SecurityTokenForContext(Uri context, Boolean bearerToken, SecurityToken
    onBehalfOf, SecurityToken actAs, SecurityToken delegateTo, SPRequestSecurityTokenProperties properties)     at Microsoft.SharePoint.SPSecurityContext.SecurityTokenForApplicationAuthentication(Uri context, SecurityToken onBe...           
    4c8b979c-f112-d050-9764-c834ee4cf36d
    06/04/2014 12:58:41.59*               w3wp.exe (0x1EEC)                      
    0x26BC SharePoint Foundation                 General                      
             8nca                Medium               ...halfOf)    
    at Microsoft.SharePoint.IdentityModel.SPApplicationAuthenticationModule.<>c__DisplayClass4.<GetLocallyIssuedToken>b__3()     at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)    
    at Microsoft.SharePoint.IdentityModel.SPApplicationAuthenticationModule.ConstructIClaimsPrincipalAndSetThreadIdentity(HttpApplication httpApplication, HttpContext httpContext, SPFederationAuthenticationModule fam)     at Microsoft.SharePoint.IdentityModel.SPApplicationAuthenticationModule.AuthenticateRequest(Object
    sender, EventArgs e)     at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()     at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)  
    4c8b979c-f112-d050-9764-c834ee4cf36d
    Any ideas?
    Anupam Shrivastava

    I am experiencing the same issue. Don't have the answer yet about what's wrong exactly. And my SSO works fine too.
    I know precisely what makes the SharePoint throw the ArgumentException, but I can't yet figure out how to influence this behavior. I will respond back if I find out, but I hope the following will create an "aha moment" for someone.
    So the SP Online issues an OAuth request to the on-prem SharePoint. If verbose logging is on for the Claims category, you may see how it reads these claims. One of them is this:
    Claim['nii':'urn:federation:microsoftonline']
    Using this claim and the nameid claim the profile mapping logic then reports the following immediately before the error (Set User Profiles to verbose to see this):
    Creating encoded sid for nameid '100300008b29cb02' and nameidissuer 'urn:federation:microsoftonline'
    Inspecting this logic with Reflector, I can see that it then attempts to infer the identity provider type from the nameidissuer, and throws the exception, because "federation" is not what it expects. It expects either "windows", "trusted" or "forms" for
    the provider type.
    So the user's actions to lead to this error were as follows:
    1. I connect to the Office 365 portal, and get redirected to my ADFS server (same domain for the ADFS server, on-prem SharePoint, and the user accounts).
    2. I log on, and from the SP Online portal I issue my search query using a result source configured as per the Hybrid TechNet guidance.
    So thanks in advance for any suggestions, on what it could be.

  • Search not working in SharePoint 2013 RTM

    I recently setup SharePoint 2013 Development environment on a VM with complete farm install on a same machine. I configured setup using configuration wizard and added some documents to the root site. As soon as I searched it gave “Some Error Occured” message.
    On checking error logs, I found that it gave message:
    Ims::Execute–Error
    occured: System.ServiceModel.EndpointNotFoundException: There was no endpoint listening
    at
    net.tcp://<machine name>/6A7919/QueryProcessingComponent1/ImsQueryInternal that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. Server stack trace: 
    at
    System.ServiceModel.Channels.ConnectionUpgradeHelper.DecodeFramingFault(ClientFramingDecoder decoder, IConnection connection, Uri via, String contentType, TimeoutHelper& timeoutHelper) 
    Then it had:
    w3wp.exe:
    Query processing component ‘net.tcp://<server ip address>/QueryProcessingComponent1/ImsQueryInternal’ changes its status to ‘Failed’.
    w3wp.exe:
    All query processing components are in ‘Failed’ status.

    Hi 
    I have come in this morning and the Search ( Query processor)  looks broken this I configured successfully a few weeks back. 
    I have looked on the server logs and coincidently, there is is an issue in IIS with the app pool
    The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
    {61738644-F196-11D0-9953-00C04FD919C1}
    and APPID
    {61738644-F196-11D0-9953-00C04FD919C1}
    to the user MYDOAMIN\SP_AppPoolSharePoint SID (S-1-5-21-1257006630-411654553-1540833222-8803) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.
    I know some of the guys were playing with running visual studio and on the dev server so I need to find out what they might have done .. Sigh

  • Search not working in SharePoint 2013 - Event ID 1314 - Crawler:Gatherer Plugin

    I have one web application and three host-named site collections. I had read an article that I just need to have the web application URL in the content source for the search to work, but that didn't resolve my issue.
    https://webapplication - main root web application
    https://staff.domain.com - Host name site collection
    https://services.domain.com Host name site collection
    https://sharepoint.domain.com host name site collection.
    I have also created the registry entry for BackConnectionHostNames also.
    Under Search Application topology I have all green check marks, but searchable items are listed as 0.
    I am getting the following errors on my SharePoint 2013 server.
    The start address https://sharepoint.domain.com cannot be crawled.
    Context: Application 'Connect_Search', Catalog 'Portal_Content'
    Details:
    This URL is part of a host header SharePoint deployment and the search application is not configured to crawl individual host header sites. This will be crawled as a part of the host header Web application if configured as a start address.  
    (0x80040de4)
    The start address https://webapplication cannot be crawled.
    Context: Application 'sharepoint_Search', Catalog 'Portal_Content'
    Details:
    The secure sockets layer (SSL) certificate sent by the server was invalid and this item will not be crawled.   (0x80041223)
    The start address https://services.domain.com cannot be crawled.
    Context: Application 'sharepoint_Search', Catalog 'Portal_Content'
    Details:
    This URL is part of a host header SharePoint deployment and the search application is not configured to crawl individual host header sites. This will be crawled as a part of the host header Web application if configured as a start address.  
    (0x80040de4
    The start address https://staff.domain.com cannot be crawled.
    Context: Application 'Sharepoint_Search', Catalog 'Portal_Content'
    Details:
    This URL is part of a host header SharePoint deployment and the search application is not configured to crawl individual host header sites. This will be crawled as a part of the host header Web application if configured as a start address.  
    (0x80040de4)
    any help would be greatly appreciated.

    Hello Derek,
    as I see you are using Host Named Site Collections.
    You have two Problems.
    First:
    The start address https://webapplication cannot be crawled.
    Context: Application 'sharepoint_Search', Catalog 'Portal_Content'
    Details:
    The secure sockets layer (SSL) certificate sent by the server was invalid and this item will not be crawled.   (0x80041223)
    You Need to fix this first!! You have a Problem with your SSL Certificate!
    The Webapplication is where normally the Search Crawler would enter the crawl in a Host Named Site Collection Scenario.
    As soon as you fix this, remove the entries for your Host Named Site Collections from the Crawler. Just leave your Webapplication in it. The HNSC will be crawled automatically. This is the following of your Errors:
    The start address https://services.domain.com cannot be crawled.
    Context: Application 'sharepoint_Search', Catalog 'Portal_Content'
    Details:
    This URL is part of a host header SharePoint deployment and the search application is not configured to crawl individual host header sites. This will be crawled as a part of the host header Web application if configured as a start address.  
    (0x80040de4
    Be sure that you created your Webapplication NOT
    AS A HOST NAMED WEB APPLICATION!
    If you can check everything I mentioned above, your search should hopefully start to work.
    King regards!

  • Configure Search Across farms in sharepoint 2013

    Hi,
    I'm setting up a farm to share services across differente farms but for some reason search isn't working. 
    I have done everything I thk i should, exchange certs, create trust relationship, publish service, service permissions, connect remote service app, s2s auth etc. I added the remote site url on the crawler, it runs without erros, then I created a result source
    with remotesharepoint but when I test I get an Unauthorized (401), or when I search on my Enterprise search.
    In the consumer farm I'm getting this error on the ULS: 
    SPApplicationAuthenticationModule: Error authenticating request, Error details: Header: 3000006;reason="Token contains invalid signature.";category="invalid_client", Body: {"error_description":"Invalid JWT token. Could not
    resolve issuer token."}
    I have changed my PS command according this guy(http://steve.thelineberrys.com/following-sites-across-farms-with-sharepoint-2013-mysites/)  that had the same problem but with the UPS, without any luck.
    What am I doing wrong? Does anyone had the same problem? Thks alot
    http://pontodepartilha.blogspot.com

    I am now able to search and get results from the Consumer site collection (crawler runs without errors) on a Search Portal on the Publisher farm.
    But everytime I try to open the Result Sources on my consumer site collection  for example I get a
    "Addresses for this application have not yet been fetched."
    I dont get service toplogy/permission errors on ULS, but I have tried the script harbar posted:
    http://social.technet.microsoft.com/Forums/sharepoint/en-US/fb52cfd8-bdb5-45b2-a86b-a23f8179a8b7/addresses-for-this-application-have-not-yet-been-fetched?forum=sharepointadminprevious
    Any ideas? Tk you.
    http://pontodepartilha.blogspot.com

  • Reporting Services in both SharePoint 2013 connected and native mode?

    Is it possible to configure Reporting Services (SQL Server 2014) to support both SharePoint 2013 connected mode and local Report Server in native mode on the same server using multiple instances of RS? The reason for this setup is to avoid having to purchase
    SharePoint Enterprise CALs for other users than analysts and still be able to publish standard reports to all employees.
    Management and analysts -> Custom reports published through SharePoint 2013 Enterprise (SP2013 ECALs and SQL Server 2014 core license). Data alerts and Power View enabled if possible.
    All employees -> Standard reports published through Native Mode Report Server (SQL Server 2014 core license). Possible subscriptions.
    I find the official documentation a bit lacking in this area but can't find anything stating against the above. It would be greatly appreciated if someone could confirm before planning the installs.
    What I'm aiming for is somewhat similar to the "2 Tier Topology" described at: Example
    License Topologies and Costs for SQL Server 2014 Self-Service Business Intelligence
    With the difference that there is a separate SQL Server 2014 server used both by SharePoint and as a standalone BI-server.
    SharePoint EE + SQL Server 2014 EE
    Excel Services
    SSRS Add-in (Reporting Services, Power View)
    SQL Server DB for SP Content, Configuration and Service Application DB:s
    SQL Server 2014 EE - SharePoint + Standalone for BI
    SSRS SharePoint Mode
    SSRS Native Mode
    SSAS (Not in SharePoint mode, skipping PowerPivot for now. Would Power View still work?)
    SQL Server DB for Data Warehouse
    = 1 x SharePoint EE Server Licence, 2 x SQL Server 2014 EE Server Licenses?
    Deployment
    Topologies for SQL Server BI Features in SharePoint - Actually gives a good overview in the section "PowerPivot for SharePoint
    2013 and Reporting Services Three Server Deployment". Just remove PowerPivot Service from Server 1 and change the Analysis Services in Server 2 to a regular native multidimensional mode. Server 2 would also be used for native Reporting Services.
    Fallback or even beneficial option to install SSRS in SharePoint mode on the SQL Server instance used for content and configuration?

    Hi Daniel Wikar,
    As per my understanding, you want to install two SQL Server instances on the same server, and configure one of the Reporting Services to SharePoint integrated mode, another to native mode.
    According to my knowledge, multiple instances of Reporting Services on the same computer, where one instance runs in SharePoint integrated mode and the other instance runs in native mode is supported. But we must run all report server instances at the same
    level. For example, if we are using SQL Server 2014, all report server instances must be SQL Server 2014.
    Besides, Analysis Services and Reporting Services can be installed as standalone servers, in scale-out configurations, or as shared service applications in a SharePoint farm. Installing the services in a farm enables BI features that are only available in
    SharePoint, including PowerPivot for SharePoint and Power View.
    For more information about Feature Comparison of SharePoint and Native Mode and Supported and Unsupported Configurations, please refer to the following documents:
    http://msdn.microsoft.com/en-us/library/ms157231.aspx
    http://technet.microsoft.com/en-US/library/bb510781(v=SQL.105).aspx
    For detailed information regarding to the license issue, please call
    1-800-426-9400,
    Monday through Friday, 6:00 A.M. to 6:00 P.M. (Pacific Time) to speak directly to a Microsoft licensing specialist. For international customers, please use the Guide to Worldwide Microsoft Licensing Sites to find contact information in your locations.
    You can also visit the following site for more information and support on licensing issues:
    http://www.microsoft.com/licensing/mla/default.aspx
    If you have any more questions, please feel free to ask.
    Thanks,
    Wendy Fu
    If you have any feedback on our support, please click
    here.

  • Is Quick View (preview of file contents under search results) supported in SharePoint 2013 Foundation?

    We recently deployed SharePoint 2013 Foundation but can't make Quick View (seeing the contents of a file when you hover the mouse cursor over it) work in the search results.
    All Site Collection/Site Features are turned on.  Not sure what else to do.
    Does anyone have this feature working in SharePoint 2013 Foundation?
    Thank you!

    Hi Charlie,
    To view the Preview of the Search Results you need to Install/Configure Office Web Apps Server in your farm.
    Please check the below links for reference.
    http://technet.microsoft.com/en-us/library/ee855124(v=office.15).aspx
    http://technet.microsoft.com/en-in/library/ff431687(v=office.15).aspx
    If you think is helpful,Vote As Helpful! And if you see a reply being an answer to the question of the thread, click Mark As Answer.
    Mahesh

  • Services Deployment in SharePoint 2013 Decision

    As mentioned in the link, there are 2 ways that we can deploy services in SharePoint 2013 farm, one is traditional approach and other streamlined approach. How do we know which one we should go for?
    http://technet.microsoft.com/en-us/library/jj219591.aspx
    Thanks, Ram Ch

    For small to medium farms there's not that much practical difference. It's only in large farms or farms with abnormal workloads that they vary notably. Compare the 10k user models in both and play spot the difference.
    The traditional design was never that sensible in its purest form, it was based on an overly stylised view of the classic three tier architecture model. It worked but was frequently shifting into the Streamlined approach anyway when you actually came down
    to it.
    Go with Streamlined, it's not going to be a materially different design to a traditional approach but it gets you there faster.

  • How to check user profile service working in sharepoint 2013?

    HI All,
    How to check user profile service working or not in sharepoint 2013? Thanks.

    Hi,
    Select which OU's you want to synchronize, then check if all users in those OU's have a user profile in the user profile service application.
    Nico Martens - MCTS, MCITP
    SharePoint 2010 Infrastructure Consultant / Trainer

Maybe you are looking for