SharePoint Foundation 2013 search service crawl error

Hi all,
When I try to view the Crawl log of Search Service Application I am getting error something like below:-
I tried to figure out why this is happening but could not find the error details related to above Correlation ID.
Can you please help me & guide me in right direction. I am clueless how to fix this issue. Yesterday it was working fine but somehow it stopped working today and it even does not display the Crawl log. So it has become tough at least for me to
fix it.
Thanks for help.

Did you try a using the
Merge-SPLogFile cmdlet to retrieve the events that use this correlation ID?
Merge-SPLogFile -Path ".\example.log" -Correlation "0467d49c-c872-509e-ca23-16445ea822d4"
You can also check out my blog post, An even better way to get the real SharePoint error from the ULS logs which describes the
process for using Merge-SPLogFile
Jason Warren
@jaspnwarren
jasonwarren.ca
habaneroconsulting.com/Insights

Similar Messages

Sharepoint foundation 2013 search service crawl log

Hi all,
Whenever I try to open the crawl log in sharepoint foundation 2013 I am getting the following error. The error says nothing about the reason of failure to open the log.
If just shows the co-relation ID in technical details.
Correlation ID: d85cd49c-18f6-509e-ca23-13f39afa5192 (while trying to access the Crawl log)
Correlation ID: e85bd49c-e836-509e-ca23-1a3f0ece8c28 (while trying to access the Content source)
I searched a lot on the net but not able to find any solution to this.
Can you please help me
Thanks.

Can you please share details of this Correlation ID from ULS logs
http://itfreesupport.com/2014/12/sharepoint-2013-2010-uls-logging-to-troubleshoot/
If this helped you resolve your issue, please mark it Answered. You can reach me through http://itfreesupport.com/

Sharepoint foundation 2013 Search Service Application.

Hi all,
I want to configure search application for sharepoint foundation 2013. I have followed some of the web links.
But did not get success. Can you please provide me the working example of how to configure search application and run the crawl. And make sure the search is working correctly.
Thanks in advance for help.

Hi Vishwajeet,
According to your description, my understanding is that you want to configure SharePoint Foundation 2013 Search service application.
In SharePoint Foundation 2013, we cannot add the Search Service to SharePoint Foundation 2013 from the Central Administration GUI after selecting a manual configuration method. It seems that the ONLY way you can add the Search Service to SharePoint Foundation
2013 is by using the SharePoint Configuration Wizard.
More information, please refer to the link:
http://blog.ciaops.com/2012/12/search-service-on-foundation-2013.html
Best Regards,
Wendy
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]
Wendy Li
TechNet Community Support

SharePoint server 2013 Search Service App 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.
Thanks a lot.

Hi,
According to your post, my understanding is that SharePoint server 2013 Search Service App did not work on Windows server 2012 R2.
Please make sure you configure Search Service Application correctly. You can refer to:Create and configure a Search service application in SharePoint Server 2013
I recommend to created new Search Service Application, and made a full crawl. Then assigned the new SSA as the default SSA for webapplications. Finnlay checked the issue doesnt occur now,
If all search related components now are online, to keep the enviroonment clean, you can delete the old SSA.
Thank you for your understanding.
Best Regards,
Linda Li
Linda Li
TechNet Community Support

SharePoint Foundation 2013 - Search Configuration Issue - 2 App Servers and 2 Front-End Servers

Hi,
We have a SharePoint Foundation 2013 with SP1 Environment.
In that, we have 2 Front-End Servers and 2 App Servers. In the Front-End Servers, the Search Service is stopped and is in Disabled state and in the 2 App Servers in One App Server, Search is Online and in another Search is Starting but goes to Stopped sooon
after.
Originally, we had only 1 App Server and we were running our Search Service and Search Service Application in that. Now since the index location became full and we were unable to increase the drive there, we added one more App Server and now the issue is
Search is not properly getting configured in either of these App servers. What we want to do is run Search only in the new App Server, because we have a lot of storage space for Index locations here, but in the older App Server, not run Search at all. We
tried keeping the Search Service disabled and ran the below PowerShell Scripts, but none of the ones are working. These scripts are creating the Search Service Application, but the error of "Admin Component is not Online", "Could not connect
to the machine hosting SharePoint 2013 admin component" is coming up.
http://www.funwithsharepoint.com/provision-search-for-sharepoint-foundation-2013-using-powershell-with-clean-db-names/
http://blog.falchionconsulting.com/index.php/2013/02/provisioning-search-on-sharepoint-2013-foundation-using-powershell/
http://blog.ciaops.com/2012/12/search-service-on-foundation-2013.html
Can I get some help please?
Karthick S

Hi Karthick,
For your issue, could you provide the
detail error message of ULS log to determine the exact cause of the error?
For SharePoint 2013, by default, ULS log is at
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS
For troubleshooting your issue, you can try to run the SharePoint Products Configuration Wizard on your WFE servers and run the script for configuring the search service on SharePoint
Foundation:
[string]$farmAcct = "DOMAIN\service_Account"
[string]$serviceAppName = "Search Service Application"
Function WriteLine
Write-Host -ForegroundColor White "--------------------------------------------------------------"
Function ActivateAndConfigureSearchService
Try
# Based on this script : http://blog.falchionconsulting.com/index.php/2013/02/provisioning-search-on-sharepoint-2013-foundation-using-powershell/
Write-Host -ForegroundColor White " --> Configure the SharePoint Foundation Search Service -", $env:computername
Start-SPEnterpriseSearchServiceInstance $env:computername
Start-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance $env:computername
$appPool = Get-SPManagedAccount -Identity $farmAcct
New-SPServiceApplicationPool -Name SeachApplication_AppPool -Account $appPool -Verbose
$saAppPool = Get-SPServiceApplicationPool -Identity SeachApplication_AppPool
$svcPool = $saAppPool
$adminPool = $saAppPool
$searchServiceInstance = Get-SPEnterpriseSearchServiceInstance $env:computername
$searchService = $searchServiceInstance.Service
$bindings = @("InvokeMethod", "NonPublic", "Instance")
$types = @([string],
[Type],
[Microsoft.SharePoint.Administration.SPIisWebServiceApplicationPool],
[Microsoft.SharePoint.Administration.SPIisWebServiceApplicationPool])
$values = @($serviceAppName,
[Microsoft.Office.Server.Search.Administration.SearchServiceApplication],
[Microsoft.SharePoint.Administration.SPIisWebServiceApplicationPool]$svcPool,
[Microsoft.SharePoint.Administration.SPIisWebServiceApplicationPool]$adminPool)
$methodInfo = $searchService.GetType().GetMethod("CreateApplicationWithDefaultTopology", $bindings, $null, $types, $null)
$searchServiceApp = $methodInfo.Invoke($searchService, $values)
$searchProxy = New-SPEnterpriseSearchServiceApplicationProxy -Name "$serviceAppName - Proxy" -SearchApplication $searchServiceApp
$searchServiceApp.Provision()
catch [system.exception]
Write-Host -ForegroundColor Yellow " ->> Activate And Configure Search Service caught a system exception"
Write-Host -ForegroundColor Red "Exception Message:", $_.Exception.ToString()
finally
WriteLine
ActivateAndConfigureSearchService
Reference:
https://sharepointpsscripts.codeplex.com/releases/view/112556
Thanks,
Eric
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].
Eric Tao
TechNet Community Support

Team Foundation Server 2013 with SharePoint Foundation 2013 - Search not available?

Hello,
we installed a TFS 2013 and let it deploy SharePoint Foundation on the same server. We are now faced with the fact that search in the teamsites is not working. I tried to get that search service up and running in a number of ways but it appears
as if there's no search service at all.
I have seen all the blogs where people are explaining how to provision a search service application for SharePoint Foundation but none of these ways work.
So, my question... is it possible to get it working?
PS. Please don't advice to post this on the TFS forum... I'm coming from there. They just closed my question as answered with the advice to post it in the SharePoint forum.
TIA,
Bart

Well,
When you go to the Search Settings in the Site Actions menu of a site, a message is displayed that there's no search Service. Which is kind of normal since there's no Search Service Application provisioned.
When I go to Central Administration => Services on Server => There's no Search Service.
When I go to Central Administration and I run the configuration wizard, there's no search service application to be provisioned.
There's a Search Administration section in the General Settings but it only displays the upper section. The lower section (with the Search Service Application information) just gives me nothing. An animated loading icon.
I tried to provision the services with psconfig (psconfig -cmd services -install) but there's still no search service to be found anywhere. After this, I do have a Search Host Controller service but when I try to start it in Central Administration, it just
gives me an error.
I'm starting to think it's not a full SharePount Foundation which is shipped with TFS.
The only thing we want to achieve is that a user can search for a document he uploads in a team site which is created by TFS. Seems not possible... unless I'm missing something here.

SharePoint foundation 2013 Search is not working

Hi, Search was working 3 days back, but today its not working. So
1. I Recreated Search Service Application
2. Created Content Source and set full crawl.
3. And service application is associated to the web application also.
4. All Application pool id are running.
5. Created Search Site collection, even though search is not working.
The error message i got was shown below. How to resolve this issue. An help/thoughts.

Try to use word Home in search
Do we see site getting crawl in crawl logs
Navigate to the site for which you want to control the Web Parts in search results.
Click Site Actions, and then click Site Settings.
Under Site Administration, click Search and offline availability.
In the Indexing ASPX Page Content section, under
This site does not contain fine-grained permissions. Specify the site’s ASPX page indexing behavior ,
Always index all Web Parts on this site
http://office.microsoft.com/en-in/sharepoint-server-help/enable-content-to-be-searchable-HA010379092.aspx

Sharepoint Foundation 2010 - Search service cannot start

Hi,
I'm trying to start the Search Service on SharePoint Foundation 2010 SP2, but I get the following error:
Could not access the Search administration database. A generic error occurred while trying to access the database to obtain the schema version info.
However the search database is well created during the process and I've checked that Shared Memory is enabled for SQL Native Client.
Can you please suggest me on this
Thanks

Hi
Alemaitre,
If Shared Memory is enabled can you try below article
http://svengillis.blogspot.com/2011/09/could-not-access-search-administration.html
http://blog.arjanfraaij.com/2012/06/could-not-access-search-administration.html
or if this is the problem after installing any SP / CU then make sure you have successfully ran PSConfig on all servers
Let us know your results, thanks
Regards,
Pratik Vyas | SharePoint Consultant |
http://sharepointpratik.blogspot.com
Posting is provided AS IS with no warranties, and confers no rights
Please remember to click Mark As Answer if a post solves your problem or
Vote As Helpful if it was useful.

Sharepoint Server 2013 Search Issue

Hi,
running Sharepoint server 2013. search service application is not working properly. getting the below error message.
"Unable to retrieve topology component health states. This may be because the admin component is not up and running"
we have 2 tier sharepoint 2013 farm architecture. please find the below server details.
1. WFE & APP server (OS: Windows Server 2008 R2 SP1 and RAM: 8 GB)
2. database server (OS: Windows Server 2008 R2 SP1 and RAM: 8 GB)
I tried the following:
- installed the latest sharepoint server 2013 CU.
- OS is up to date.
- deleted and recreated Search Service Application
- The service account does have access to the search databases
- one account is used, domain\sp2013search, has all necessary permissions
Please help to fix the search issue.

Hi Raj0639,
According to your description, my understanding is that you got an error when you run SharePoint 2013 Search.
Firstly, please make sure that all servers are online, and connecting to others.
Please stop all search services on Manage services on server, then restart them. Please try to do as Amit said, compare the result.
If this issue still exists, please repair SharePoint 2013 under Control Panel, then compare the result.
Here is a similar post for you to take a look at:
http://social.technet.microsoft.com/Forums/en-US/a67b0d0f-4f5a-4412-8f83-a57eaff4be45/sharepoint-search-host-controller-does-not-start?forum=sharepoin
I hope this helps.
Thanks,
Wendy
Wendy Li
TechNet Community Support

SharePoint Foundation 2010: search error: "Your search cannot be completed because of a service error."

Hi,
I have SharePoint Foundation 2010 running on a single server with databases, with a second server in the farm serving as a 2nd app tier. Both server have the exact same versions of SharePoint loaded (according to the Central Admin site).
Whenever I try to run a search from any site in my SharePoint Foundation 2010 installation (in this example I typed "this is my query"), it hangs for 20-30 seconds while the IE status bar says:
Waiting for http://SERVER2010:80/tfs/SITE1/_layouts/searchresults.aspx?k=this%20is%20my%20query&u=http%3A%2F%2Ftfs2010db%2Ftfs%2FSITE1
Then it finally returns a results screen with an error that says: "Your search cannot be completed because of a service error. Try your search again or contact your administrator for more information."
Checking the SharePoint logs under C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS, the relevant entries say the following (items I deem important
bolded):
11/05/2011 18:22:25.88 w3wp.exe (0x35F0) 0x1908 SharePoint Foundation Monitoring nasq Medium Entering monitored scope (Request (HEAD:http://172.22.100.101:80/)) 11/05/2011 18:22:25.88 w3wp.exe (0x35F0) 0x1908 SharePoint Foundation Logging
Correlation Data xmnv Medium Name=Request (HEAD:http://172.22.100.101:80/) a7ab70a3-61bd-4d62-b5a4-cf77a45dafb9
11/05/2011 18:22:25.88 w3wp.exe (0x35F0) 0x1908 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Request (HEAD:http://172.22.100.101:80/)). Execution Time=3.33645756653429 a7ab70a3-61bd-4d62-b5a4-cf77a45dafb9
11/05/2011 18:22:50.73 w3wp.exe (0x35F0) 0x3148 SharePoint Foundation Monitoring nasq Medium Entering monitored scope (Request (POST:http://SERVER2010:80/tfs/SITE1/_layouts/searchresults.aspx?k=this%20is%20my%20query&u=http%3A%2F%2FSERVER2010%2Ftfs%2FSITE1))
11/05/2011 18:22:50.73 w3wp.exe (0x35F0) 0x3148 SharePoint Foundation Logging Correlation Data xmnv Medium Name=Request (POST:http://SERVER2010:80/tfs/SITE1/_layouts/searchresults.aspx?k=this%20is%20my%20query&u=http%3A%2F%2FSERVER2010%2Ftfs%2FSITE1)
fea6cc87-0404-497a-838e-5e154f422aa4
11/05/2011 18:22:50.73 w3wp.exe (0x35F0) 0x3148 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Request (POST:http://SERVER2010:80/tfs/SITE1/_layouts/searchresults.aspx?k=this%20is%20my%20query&u=http%3A%2F%2FSERVER2010%2Ftfs%2FSITE1)).
Execution Time=4.3055751499143 fea6cc87-0404-497a-838e-5e154f422aa4
11/05/2011 18:22:50.73 w3wp.exe (0x35F0) 0x3148 SharePoint Foundation Monitoring nasq Medium Entering monitored scope (Request (POST:http://SERVER2010:80/tfs/SITE1/_layouts/searchresults.aspx?k=this%20is%20my%20query&u=http%3A%2F%2FSERVER2010%2Ftfs%2FSITE1))
11/05/2011 18:22:50.73 w3wp.exe (0x35F0) 0x3148 SharePoint Foundation Logging Correlation Data xmnv Medium Name=Request (POST:http://SERVER2010:80/tfs/SITE1/_layouts/searchresults.aspx?k=this%20is%20my%20query&u=http%3A%2F%2FSERVER2010%2Ftfs%2FSITE1)
5e283c89-990f-4572-ae77-a1e6a5aad502
11/05/2011 18:22:50.75 w3wp.exe (0x35F0) 0x3148 SharePoint Foundation Logging Correlation Data xmnv Medium Site=/tfs/SITE1 5e283c89-990f-4572-ae77-a1e6a5aad502
11/05/2011 18:22:50.77 w3wp.exe (0x35F0) 0x3148 SharePoint Foundation Search Query dn6r High FetchDataFromURL start at(outside if): 1 param: start 5e283c89-990f-4572-ae77-a1e6a5aad502
11/05/2011 18:22:50.79 mssearch.exe (0x58A4) 0x2534 SharePoint Foundation Search QueryComponentSelection aee7 Medium
Did You Mean Suggester not found. [smart2.hxx:382] d:\office\source\otools\inc\search\common\ytrip\tripoli\smart2.hxx 5e283c89-990f-4572-ae77-a1e6a5aad502
11/05/2011 18:22:50.91 mssearch.exe (0x58A4) 0x2534 SharePoint Foundation Search Query Processor e0pg Medium 1dd958fb-b605-4b3b-a676-28a3cafb2eb6:
Query completed 125 ms, detailed time: Query stage execution ms times: 0 125 0 0 125 0 0 0 Query stage cpu ms times: 0 31 0 0 31 0 0 0 Query stage hit counts: 1 1 1 7 1 0 1 1 Cursor count: 260 Mapped page count: 164 Total index count: 7 [srequest.cxx:5526]
d:\office\source\search\native\ytrip\tripoli\cifrmwrk\srequest.cxx 5e283c89-990f-4572-ae77-a1e6a5aad502
11/05/2011 18:23:06.08 w3wp.exe (0x35F0) 0x3148 SharePoint Foundation Search Exceptions 1hjo
Medium Exception thrown: 0x80040e31 (d:\office\source\otools\inc\search\common\ytrip\tripoli\timeout.hxx:51 ip 0x000007FEECF099B7) 5e283c89-990f-4572-ae77-a1e6a5aad502
11/05/2011 18:23:06.08 w3wp.exe (0x35F0) 0x3148 SharePoint Foundation Search
Query Processor e2o1 High In CRootQuerySpec::Execute - caught exception: 0x80040e31, translated to: 0x80040e31 5e283c89-990f-4572-ae77-a1e6a5aad502
11/05/2011 18:23:06.08 w3wp.exe (0x35F0) 0x3148 SharePoint Foundation Search Administration 0000
High Log Query: More Information: Execution stopped because a resource limit was reached. No results were returned.
5e283c89-990f-4572-ae77-a1e6a5aad502
11/05/2011 18:23:06.08 w3wp.exe (0x35F0) 0x3148 SharePoint Foundation Web Parts 89a1
High Error while executing web part: Microsoft.SharePoint.Search.WebControls.Srhdc GenericException: Your search cannot be completed because of a service error. Try your search again or contact your administrator for more information.
---> System.ServiceProcess.TimeoutException: System error. at Microsoft.SharePoint.Search.Query.KeywordQueryInternal.Execute() at Microsoft.SharePoint.Search.Query.QueryInternal.Execute(QueryProperties properties) at Microsoft.SharePoint.Search.Query.Query.Execute()
at Microsoft.SharePoint.Search.WebControls.SearchResultHiddenObject.GetResultData() --- End of inner exception stack trace --- at Microsoft.SharePoint.Search.WebControls.SearchResultHiddenObject.get_ResultsReturned() at Microsoft.SharePoint.Search.Internal.WebControls.CoreRes...
5e283c89-990f-4572-ae77-a1e6a5aad502
11/05/2011 18:23:06.08* w3wp.exe (0x35F0) 0x3148 SharePoint Foundation Web Parts 89a1 High ...ultsWebPart.ModifyXsltArgumentList(ArgumentClassWrapper argList) at Microsoft.SharePoint.WebPartPages.DataFormWebPart.PrepareAndPerformTransform(Boolean
bDeferExecuteTransform) 5e283c89-990f-4572-ae77-a1e6a5aad502
11/05/2011 18:23:06.08 w3wp.exe (0x35F0) 0x3148 SharePoint Foundation Web Parts 89a2
High InnerException 1: System.ServiceProcess.TimeoutException: System error. at Microsoft.SharePoint.Search.Query.KeywordQueryInternal.Execute() at Microsoft.SharePoint.Search.Query.QueryInternal.Execute(QueryProperties properties) at Microsoft.SharePoint.Search.Query.Query.Execute()
at Microsoft.SharePoint.Search.WebControls.SearchResultHiddenObject.GetResultData() 5e283c89-990f-4572-ae77-a1e6a5aad502
11/05/2011 18:23:06.08 w3wp.exe (0x35F0) 0x3148 SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (DataBinding DataFormWebPart ()). Execution Time=15302.2074034549 5e283c89-990f-4572-ae77-a1e6a5aad502
11/05/2011 18:23:06.09 w3wp.exe (0x35F0) 0x3148 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Request (POST:http://SERVER2010:80/tfs/SITE1/_layouts/searchresults.aspx?k=this%20is%20my%20query&u=http%3A%2F%2FSERVER2010%2Ftfs%2FSITE1)).
Execution Time=15358.1002613461 5e283c89-990f-4572-ae77-a1e6a5aad502
11/05/2011 18:23:06.59 w3wp.exe (0x35F0) 0x58E0 SharePoint Foundation Monitoring nasq Medium Entering monitored scope (Request (GET:http://SERVER2010:80/tfs/SITE1/Shared%20Documents/SITE1_logo_sharepoint.png))
11/05/2011 18:23:06.59 w3wp.exe (0x35F0) 0x58E0 SharePoint Foundation Logging Correlation Data xmnv Medium Name=Request (GET:http://SERVER2010:80/tfs/SITE1/Shared%20Documents/SITE1_logo_sharepoint.png) f0d03f8e-d78b-4004-9a5f-3ee9955afa60
11/05/2011 18:23:06.59 w3wp.exe (0x35F0) 0x5C6C SharePoint Foundation General af71 Medium HTTP Request method: GET f0d03f8e-d78b-4004-9a5f-3ee9955afa60
11/05/2011 18:23:06.59 w3wp.exe (0x35F0) 0x5C6C SharePoint Foundation General af75 Medium Overridden HTTP request method: GET f0d03f8e-d78b-4004-9a5f-3ee9955afa60
11/05/2011 18:23:06.59 w3wp.exe (0x35F0) 0x5C6C SharePoint Foundation General af74 Medium HTTP request URL: /tfs/SITE1/Shared%20Documents/SITE1_logo_sharepoint.png f0d03f8e-d78b-4004-9a5f-3ee9955afa60
11/05/2011 18:23:06.60 w3wp.exe (0x35F0) 0x58E0 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Request (GET:http://SERVER2010:80/tfs/SITE1/Shared%20Documents/SITE1_logo_sharepoint.png)). Execution Time=9.75459171486879 f0d03f8e-d78b-4004-9a5f-3ee9955afa60
Not sure what "resource limit is reached" actually means. This SharePoint installation is running under regular SQL 2008 R2, and the
WSS_Content database is fairly small (10gig). I've reviewed the Search Service, the process account running it, the
WSS_SEARCH index database, and verified that the Content database is using the proper index database. Everything looks like it should be crawling/indexing/working fine. But the WSS_SEARCH
database isn't very large, so I'm not sure if the crawling is actually filling it with anything.
Not sure where to start seriously troubleshooting this. Any advice would be appreciated. Thanks.

Hi,
The query ran in tens of seconds. This indicates that at some point a bad plan compiled and stayed in the cache.
It may have gotten there because the statistics were out of date.
A possible way to keep this from happening is to rebuild statistics with full scan more frequently.
Try free the proc cache and see the result.
http://msdn.microsoft.com/en-us/library/ms174283(v=SQL.105).aspx
Thanks,
Rock Wang
Regards, Rock Wang Microsoft Online Community Support

Provision Search in SharePoint Foundation 2013 without Domain Controller / Active Directory - Domain accounts

Hi,
I have successfully setup SharePoint Foundation 2013 as single server farm with SQL Server Standard database in a DMZ environment using local accounts since DMZ doesn't have an Active Directory and hence Domain accounts using powershell as described
in https://theblobfarm.wordpress.com/2012/12/03/installing-sharepoint-2013-without-a-domain-controller
When I run Farm configuration wizard to provision search service application, I get an error:
ERROR: "The service application(s) for the service "Search Service Application" could not be provisioned because of the following error: I/O error occurred."
The log file logged the details of this error as:
ERROR: "Failed to create file share Analytics_e441aa1c-1a8d-4f0a-a079-58b499eb4c50 at D:\SharePoint Search\Office Server\Analytics_e441aa1c-1a8d-4f0a-a079-58b499eb4c50 (System.ArgumentException: The SDDL string contains an invalid sid or a sid
that cannot be translated."
After investigation, I found that potentially the error could be because the timer service is trying to setup a network share for analytics component (as part of provisioning search). It is trying to setup that share with a domain account that happens to
be a local user instead in this case and fails with error “System.ArgumentException: The SDDL string contains an invalid sid or a sid that cannot be translated”.
I got some pointer from the below thread
https://social.technet.microsoft.com/Forums/en-US/c8e93984-f4e5-46da-8e8a-c5c79ea1ff62/error-creating-search-service-application-on-sharepoint-foundation-with-local-account?forum=sharepointadmin
However, the above thread doesn't state that the solution worked.
I have tried creating share manually for Analytics_<Guid> folder but it doesn't work since every time farm configuration wizards is run it creates a new Analytics_<Guid> folder.
Since, I have setup SharePoint Foundation 2013 on a production environment I cannot test and trial various solutions.
Can some please guide me on how to successfully provision search for SharePoint Foundation 2013 setup as a single server farm with SQL Server Standard database in a DMZ environment using local accounts (without Active Directory - domain accounts).
Thanks in advance.
Himanshu

Microsoft documentation doesn't always specifically call out all products (Project Server isn't there, either). But it does apply. You'll need to stand up at least one Domain Controller, or allow port access back to a DC.
Preferably, set up SharePoint on the internal network and use a reverse proxy (which will terminate client connections at the reverse proxy) present in the DMZ.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Crawl Health Reports in Sharepoint Foundation 2013 Farm

I am getting the following error within a newly build SharePoint Foundation 2013 Farm. I would like to know how I go about resolving this issue:
When browsing to Central Admin --> Search Administration --> Crawl Health Reports, I receive the following error:
Sorry, something went wrong
Could not find any resources appropriate for the specified culture or the neutral culture. Make sure "Resources.MossChart.resources" was correctly embedded or linked into assembly "App_GlobalResources.kbifvsaw" at compile time, or
that all the satellite assemblies required are loadable and fully signed.
Technical Details
Troubleshoot issues with Microsoft SharePoint Foundation.
Correlation ID: 0b83a29c-2582-9044-9d87-fc1089e8f7ee
Date and Time: 7/8/2014 1:47:38 PM
When I browse to Central Admin --> Search Administration --> Crawl Health Reports, I receive the following error:
Sorry, something went wrong
Could not find any resources appropriate for the specified culture or the neutral culture. Make sure "Resources.MossChart.resources" was correctly embedded or linked into assembly "App_GlobalResources.kbifvsaw" at compile time, or
that all the satellite assemblies required are loadable and fully signed.
Technical Details
Troubleshoot issues with Microsoft SharePoint Foundation.
Correlation ID: 1b83a29c-0562-9044-9d87-f319e14ba795
Date and Time: 7/8/2014 1:48:43 PM
I suspect that both errors have the same root cause, but I could do with some assistance in resolving this. Do I need to install some Microsoft Chart Controls by any chance? I am assuming that as the links are there in SharePoint Foundation, that they should
be working within this edition of SharePoint.
Kevin Evans

Hi Kevin,
According to your error message, please make sure "Resources.MossChart.resources" was correctly embedded or linked into assembly "App_GlobalResources.kbifvsaw”, it seems like that mosschart.resx
and mosschart.en-US.resx missing or bad of the error web site.
To correct the problem you can manually deploy the resource files to the correct IIS Virtual Directory location. To deploy the resource files manually following the steps below.
1. Navigate to 'C:\Program Files\Common Files\Microsoft Shared\web server extensions\15\CONFIG\Resources'
2. Copy the files 'mosschart.resx' and 'mosschart.en-US.resx'.
3. Navigate to the IIS Virtual Directory of your SharePoint website
4. Paste 'mosschart.resx' 'mosschart.en-US.resx’ into the Virtual Directory's App_GlobalResources folder
5. Perform an IISRESET
6. Refresh your page.
Reference:
http://social.technet.microsoft.com/Forums/en-US/4a89e23c-a1c1-4b8a-99e9-4e1a36b8ecf8/web-analytics-errors?forum=sharepointadminprevious
Thanks,
Eric
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]
Eric Tao
TechNet Community Support

Duplicate Search Databases in SharePoint Foundation 2013 Farm

I seem to have 2 seperate issues with Search within my SharePoint Foundation 2013 Farm. This is a new Farm, so I can remove the search service application and re-create if this is a way that can clear the 2 issues I am experiencing.
Issue 1:
For some reason I have 2 instances of the following search related DB's:
SearchAdminDatabase
SearchAnalyticsReportingDatabase
SearchGathererDatabase
SearchLinksDatabase
1 instance of each of the databases all report database status of "No Action Required" and the other instance of all the DB's report a database status of "Not Responding".
Issue 2:
My search service application seems to be working fine as I am able to crawl content and retrieve results, however the DB's associted with this search service application are reported with the following warning within the SharePoint Health Analyzer. I have
been unable to run the Upgrade-SPContentDatabase command against these databases as I get a message saying that the content database could not be found:
Title
Databases running in compatibility range, upgrade recommended.
Severity
2 - Warning
Category
Configuration
Explanation
The following databases have versions that are older than the current SharePoint software, but are within the backwards compatible range:
Search_Service_Application_AnalyticsReportingStoreDB_a3c64b2f3b9b4a5d83383ec0b1ecfcf4,
Search_Service_Application_CrawlStoreDB_ffb8d716450242cc849a7f44f521bfc9,
Search_Service_Application_DB_0fe433c02db6435db85285e9fd83863e,
Search_Service_Application_LinksStoreDB_75efb2f689cf49f19c98a5a8155e47b7.
Remedy
To achieve optimal results from these databases, use Upgrade-SPContentDatabase to upgrade Content databases, or psconfig.exe to upgrade other databases. For more information about this rule, see "http://go.microsoft.com/fwlink/?LinkID=142697".
Kevin Evans

At time people create search service application and delete it. SA is deleted but database were not deleted for some reason. so these might be those stale database. You can delete them if you want
http://blogs.technet.com/b/tothesharepoint/archive/2011/12/19/find-active-databases-used-by-sharepoint-server-2010.aspx
If you want a report of all of your SharePoint databases that includes the GUIDs and related property values, use the SharePoint 2010 Management Shell.
There are several Windows PowerShell cmdlets you can use to find all of the SharePoint databases and then print this report to a text file. The quickest and perhaps easiest cmdlet is “Get-SPDatabase”. Run this cmdlet in the SharePoint
2010 Management Shell to list all of the SharePoint Server databases with properties for each one. From this potentially large list you can then obtain specific information such as the database ID by using additional syntax in your cmdlet. Similarly, also
in the SharePoint 2010 Management Shell, run “Get-SPDatabase | Sort-Object
disksizerequired -desc | Format-Table Name” and you will get a simple list of the names for each database. You can then print this list to a text file by adding, “| out-file c:\db.txt” to the end of the command.
For detailed information, see
Windows PowerShell for SharePoint Server 2010,
Database cmdlets,
Get-SPDatabase, and
Get-SPContentDatabase.
If this helped you resolve your issue, please mark it Answered

Error 503 after renaming SharePoint Foundation 2013 Server

We renamed a SharePoint Foundation 2013 server using the procedure outlined here:
http://www.bluesphereinc.com/blog/renaming-a-sharepoint-20102013-server/
Everything seemed to work fine until we tried to access the site afterwards. Now all we get when trying to access the site is the Error 503: Service is unavailable message. We can get into central administration without any problems.

Hi ,
According to your description, my understanding is that you encountered 503 error after renaming SharePoint Foundation 2013 Server.
For your issue, please refer to the actions as follow:
1.Check the web site properties in IIS. Under home directory tab, check the application pool value and then open that application pool from the application pools (separate node in the IIS tree). Click the
identity tab and see who is the pool assigned to. For the sake of testing, you can select "Predefined" and select local service from the drop down. Restart IIS and see if things work out for you. Http 503 error is generated by the IIS and it happens
when web server sends data stream back to the web site.
2.Verify that all SharePoint services are started, this error might occur because of changing the service account password. You may need to change the new password to application pool or SharePoint timer
service. Click the stopped application pool -> click advanced settings ->Identity ->click the user to retype the user ->Application Pool Identity dialog ->click set -> manually type the user name and password. Then restart the server.
If your issue persists, please provide detail error message of ULS log
to determine the exact cause of the error?
For SharePoint 2013, by default, ULS log is at
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS
Best Regards,
Eric
Eric Tao
TechNet Community Support

Sharepoint 2013 - Which Server Should Run Microsoft SharePoint Foundation Sandboxed Code Service

We have just deployed Sharepoint 2013 and also CRM 2011..
Our Sharepoint 2013 Environment has a WFE and an APP server and we have a CRM 2011 box.
We have been getting the following error in IE when Users in CRM are clicking on the Document Link under accounts which links to Sharepoint 2013
"This Content cannot be displayed in a frame
To help protect the security of information you enter into this website, the publisher of this content does not allow it to be displayed in a frame."
It seems like it is a IE Security Issue, but I am suspecting it could be the Microsoft SharePoint Foundation Sandboxed Code Service.
Which server should be running the Microsoft SharePoint Foundation Sandboxed Code Service| WFE or APP.
Also which server should run the Windows Service: SharePoint User Code Host
Thank you in advance.

Hi,
Please have a look at the following post:
http://technet.microsoft.com/en-us/library/jj219591.aspx
As it describes, the recommendation is for both services to start it on the Web Front End servers.
Cheers,
Vincent

SharePoint Foundation 2013 search service crawl error

Similar Messages

Maybe you are looking for