SharePoint Search crawl error for OWA OneNote notebooks

I am slowly working through an install of SharePoint 2013 to replace SharePoint 2010. It's the Enterprise edition - on prem.
I am in the process of setting up and testing search. I'm down to this last error.
The SharePoint item being crawled returned an error when attempting to download the item.
This error shows up when the crawl is attempted on One Note notebooks created using the OWA version of One Note.
The search file types include .one (One Note), but I noticed the link to these files does not include a .one extension. The link looks like this
http://site/site/Shared%20Documents/My%20site%20notebook?Web=1
We are concerned with eDiscovery and being able to search all documents in SharePoint. I understand the complexity of the notebook and that fact that it includes multiple files, but we still need to include it in our search if we are going to allow
it in SharePoint.
At this point, I haven't been able to find a solution - other than suppressing WOPI for One Note and only allowing Office 2013 full versions of One Note to be saved in SharePoint.

Does the Crawl account have Full Read on the User Policy of the Web Application in Central Admin -> Manage Web Applications -> User Policy?
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.

Similar Messages

SharePoint 2013 crawl error - The item may be too large or corrupt.

When crawling SharePoint content I am getting the following error on two lists
"The item may be too large or corrupt. You may also verify that you have the latest version of this IFilter"
I have seen a couple of posts regarding this error in SharePoint 2010 and SharePoint 2007 but nothing for 2013. I tried the fix for SharePoint 2010 which was to modify the MaxDownloadSize property of the SearchApplication using Powershell (I increased
it from 64 to 128). This had no effect, although I think this property might relate to documents rather than lists.
The two lists that are throwing the errors have previously been indexed successfully, however since an index reset this error is happening, The first list had 6000+ items - I thought the fact the list is large might be causing the problem however
the other list only has 800+ items in it. Each item in the list has two rich text fields which have a fair bit of html in them but not loads.
Can anyone shed any light on this problem?
Thanks,
Neil

So, in SharePoint 2007 the fix was changing registry settings, in 2010 it was running a couple of Powershell commands.
The fix in 2013 - well we're back to changing registry settings!
This was the fix supplied by Microsoft - change the following registry settings
Key
Default Value
New Value
HKLM\SOFTWARE\Microsoft\Office Server\15\Search\Global\GatheringManager\DedicatedFilterProcessMemoryQuota
104857600
209715200
HKLM\SOFTWARE\Microsoft\Office Server\15\Search\Global\GatheringManager\FilterProcessMemoryQuota
104857600
209715200
SharePoint 2013 - a step forward?

After upgrade SP-Crawl Error: The SharePoint item being crawled returned an error when attempting to download the item.

Hi All - After the upgrade, I am getting SP-Crawl Error for certain links. I check the Crawl component has proper permission.
Google is showing some article like
http://blog.karstein-consulting.com/2012/04/20/error-in-crawl-log-the-sharepoint-item-being-crawled-returned-an-error-when-attempting-to-download-the-item/
not sure if this resolution is referring to 2010 and/or 2013.
I checked the registery editor. I couldn't find 14.0 under the Office Server.
Any clue?
Regards,
Khushi
Khushi

I checked the web application policy the search crawl account has full read permission.
Crawl
Fiddler
Log Error referring the Correlation ID
01/06/2014 13:05:06.14 w3wp.exe (0x1698)                       0x0118 SharePoint Foundation
Monitoring                    nasq Medium Entering monitored scope (Request (GET:/sites/HR/Shared%20Documents/Benefits/Insurance%20Benefits/Life%20Insurance/Basic%20Life%20and%20ADD)).
Parent No
01/06/2014 13:05:06.14 w3wp.exe (0x1698)                       0x0118 SharePoint Foundation
Logging Correlation Data      xmnv Medium Name=Request (GET:<SiteURL>/sites/HR/Shared%20Documents/Benefits/Insurance%20Benefits/Life%20Insurance/Basic%20Life%20and%20ADD) e8b1679c-0476-70d4-9fcd-2cef5be44461
01/06/2014 13:05:06.14 w3wp.exe (0x1698)                       0x0118 SharePoint Foundation
Authentication Authorization agb9s Medium Non-OAuth request. IsAuthenticated=True, UserIdentityName=, ClaimsCount=0 e8b1679c-0476-70d4-9fcd-2cef5be44461
01/06/2014 13:05:06.15 w3wp.exe (0x1698)                       0x1738 SharePoint Foundation
General                       af71 Medium HTTP Request method: GET e8b1679c-0476-70d4-9fcd-2cef5be44461
01/06/2014 13:05:06.15 w3wp.exe (0x1698)                       0x1738 SharePoint Foundation
General                       af75 Medium Overridden HTTP request method: GET e8b1679c-0476-70d4-9fcd-2cef5be44461
01/06/2014 13:05:06.15 w3wp.exe (0x1698)                       0x1738 SharePoint Foundation
General                       af74 Medium HTTP request URL: /sites/HR/Shared%20Documents/Benefits/Insurance%20Benefits/Life%20Insurance/Basic%20Life%20and%20ADD e8b1679c-0476-70d4-9fcd-2cef5be44461
01/06/2014 13:05:06.17 w3wp.exe (0x1698)                       0x1738 SharePoint Foundation
Files                         aise3 Medium Failure when fetching document. 0x80070090 e8b1679c-0476-70d4-9fcd-2cef5be44461
01/06/2014 13:05:06.17 w3wp.exe (0x1698)                       0x1960 SharePoint Foundation
Monitoring                    b4ly Medium Leaving Monitored Scope (Request (GET:<SiteURL>/sites/HR/Shared%20Documents/Benefits/Insurance%20Benefits/Life%20Insurance/Basic%20Life%20and%20ADD)).
Execution Time=20.5461867360237 e8b1679c-0476-70d4-9fcd-2cef5be44461
01/06/2014 13:05:06.17 w3wp.exe (0x1698)                       0x1960 SharePoint Foundation
Monitoring                    b4ly Medium Leaving Monitored Scope (Request (GET:<SiteURL>/sites/HR/Shared%20Documents/Benefits/Insurance%20Benefits/Life%20Insurance/Basic%20Life%20and%20ADD)).
Execution Time=29.917489513332 e8b1679c-0476-70d4-9fcd-2549ba3ee9d4
01/06/2014 13:05:06.17 w3wp.exe (0x1698)                       0x1960 SharePoint Foundation
Monitoring                    nasq Medium Entering monitored scope (Request (GET:<SiteURL>nsurance%20Benefits%2fLife%20Insurance%2fBasic%20Life%20and%20ADD&FolderCTID=0x01200039DA632EEACF264685CF39D68A18F7C8)).
Parent No
Any clue?
Regards,
Khushi
Khushi

Strange issue in SharePoint Search

I just took over SharePoint farm from other admin who left. After that SharePoint search crawl broke. I recreated the SharePoint search with all the settings. But there is really strange issue happening now.
If domain A user log in to SharePoint and search, they see all the results, while users from domain B donot see any result. Why is this happening? Has anyone experienced this before?
Any help will be hugly appreciated.
Adit

Hi Adit,
Is SharePoint installed in domain A and domain B is a one-way trusted domain?
If yes, then the issue should occur because search results gets security trimmed while returning the results back to the domain B users.
I recommend to run the following Windows PowerShell command:
$searchapp = Get-SPEnterpriseSearchServiceApplication
$searchapp.SetProperty("ForceClaimACLs",1)
A full crawl is required to enable the new ACL format across the content.
More information is provided in the link below:
https://support.microsoft.com/kb/2344518?wa=wsignin1.0
Best regards.
Thanks
Victoria Xia
TechNet Community Support

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 Search Service Application isn't crawling.

Hi all,
I am new to Sharepoint 2013 and I do not know how to troubleshoot the issue of sharepoint search service.
My issue is that the sharepoint search service application is not crawling. How can I know the reason of this error and how to fix this.
Please help me.
Thanks.

Hi Vishwajeet,
if you facing any problem in search you can Use the crawl log and crawl-health reports to diagnose problems
which is best recommended practices from Microsoft.
http://technet.microsoft.com/en-us/library/dn535606%28v=office.15%29.aspx
for View Search diagnostic and also check all the search related service whether its running or not
http://technet.microsoft.com/en-us/library/jj219611%28v=office.15%29.aspx
Please Mark as Answer and Vote me if it help to resolve your issue

Search Crawl status throwing error

Hi,
We installed MOSS on our clients machine and Search has been problematic from the getgo.
When we have performed a forced restart on the osearch service (http://bruteforcesharepoint.blogspot.com/2009_04_01_archive.html), within the next couple of hours the crawler status wil be Error. But, search at this point is still working. Indexing basically
stops and event errors are thrown in the event logs, but searching is still possible.
Here are the symptoms:
the Crawl status is 'Error'
/ssp/admin/_layouts/searchsspsettings.aspx (Search Settings page) is throwing a HTTP 403 error : The website declined to show this webpage.
I can still get to the Search Administration, and when I go to view the Content Sources or view the crawl logs specifically, I get the same 403 error.
When I try to 'Reset all crawled content', that is when Search dies. I get the message an exception error message.
When I try to stop the Office SharePoint Search service in Central Admin, it hangs in the Stopping state. It'll only come out of this if I go through the task manger and manually force the process to stop and then start it again using the
stsadm -o osearch -action start -role index
command then search starts again. And I have to reset the crawled content and perform a full crawl (apart from also reconfiguring the indexer). I can successfully perform a full crawl, takes about 2 hours and it does an incremental crawl for the first
couple of increments. Then all of a sudden I get the follow errors in the event view log:
Error event ID: 1030
Source: Userenv
Desc: Windows cannot query for the list of Group Policy objects. Check the event log for possible messages previously logged by the policy engine that describes the reason for this.
And then we get thousands on the following error (the indexing schedule timer job basically stops working):
Error event id 6398
Source: Windows SharePoint Services 3
Desc: The Execute method of job definition Microsoft.Office.Server.Search.Administration.IndexingScheduleJobDefinition (ID b6d1868e-26a5-4ae2-b922-0f129fd77a61) threw an exception. More information is included below.
Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
Now before you ask me about permission, we have created an admin user called spadmin who has access to everything and is the default content access account as well. It is also spadmin that is running the osearch, not the network account.
Can anyone provide any insights into why we are experiencing this issue??? We have gone round in circles trying to figure out what we're doing wrong or whether this is a sharepoint issue.
any help would be much appreciated.
Cheers
danielle

hi danielle,
I was also in a same sort of situation, here is what i did:
1> locate the catalog file directory.
2>place CI dumps in the 12 hive/bin folder.
3>run the command
cidump -dump "catalog filedirectory location" -widset>c:\xyz.txt
4>search with the word "exception" if there is a hit eg
error:excetion caught xxxxxxxxx in shadow index xxxxxxxx then u need to delete this index.
5>run below command
cidump -removeindex "catalog filedirectory location" -i xxxxxxxxx
xxxxxxxx signifies the shadow index .
6> restart the searchservice manually,timersevice.
if the issue persists let us know
Moderator Note: NEVER propose your own posts as answers. The function is for proposing the good answers of
other people. Not for self-proposing.
(Also don't write let me know - these are forums not private conversations)

Acrobat - Convert Office documents to PDF so that it is crawled/indexed by SharePoint search

Hi there,
This is a hybrid question between Acrobat and SharePoint and I'll post on both forums....
Background:
In a fairly complex application we have a publishing server that utilizes Acrobat to convert Office documents to PDF using the Convert to PDF functionality.
We then publish that PDF to a library in SharePoint. We would like to have those published PDFs searchable by SharePoint search. Unfortunately there is something about these PDFs where SharePoint cannot crawl the content.
Note: I do realize that PDFs are not indexable by SharePoint out of the box and I have installed and configured the iFilter utility. I have been able to index and search for other PDFs, so I know the mechanism works. It just seems to be these
particular PDFs.
I have also manually "Saved as PDF" directly from Word/Excel and those PDFs are crawled by SharePoint....it just seems to be when Acrobat does its conversion. I'm sure it's just a simple configuration somewhere... I just don't know what I'm
looking for.
Another note: When I open the published PDFs, I am able to use Acrobat's search to find the text.... and the text is selectable; so it's not as if the conversion changed it to an image.
So....would anyone happen to have encountered this issue? Or does anyone know what makes a PDF indexable by SharePoint search?
Thanks in advance

Hi ,
According to your description, my understanding is that the PDFs which are converted from Office documents by Acrobat cannot be crawled in your SharePoint 2010.
For your issue, please make sure these PDFs version is 1.5(Acrobat 6.x) or above.
You can take steps as below for verifying:
Open your PDF using Adobe Reader.
Go to File -> Properties.
Check the PDF Version under Advanced section.
Best Regards,
Eric
Eric Tao
TechNet Community Support

How to view crawled documents of file system in the browser using sharepoint search

Hi,
I think this should be pretty obvious. However, somehow I am not able to do it. Here is what i am working on:
I created a folder on my D:\ drive on the SharePoint server. Added a few word documents there.Created a new content source in my Search Service Application and configured it to crawl above folder from file system. Ran a full crawl. All the documents are
crawled successfully. I can see the documents on the search page. Now, the problem is:
How can I open this document directly in the browser? Becuase the path i get is of the folder on the server. If this isn't possible then I think,there is no use of this feature. I just see the title and a short description of the document.
But, I think it should be possible. I just don't know how to do it.
Any ideas will be highly appreciated.

Hi Mohan,
According to your description, my understanding is that you want to open the documents in file shares in the browser by clicking the link in search results.
As the files are not stored in SharePoint, so we need to configure Office Web Apps for the documents to open the files in the browser.
Here is a similar thread for you to take a look:
http://social.technet.microsoft.com/Forums/sharepoint/en-US/70541f55-6a66-4d55-8f2c-9f9a356b9654/how-to-open-sharepoint-search-results-from-file-server-using-office-web-apps-server-2013?forum=sharepointsearch
Best regards.
Thanks
Victoria Xia
TechNet Community Support

Search Server Error - Illegal operation attempted on a registry key that has been marked for deletion

Hello,
I have a 5 server farm (DC, 2 WFEs, 1 SQL,1 CA w/ search) and am experiencing an issue when returning search results. This issue just started occurring recently, and basically the search page throws a correlation id whenever used. The error returned
is:
SearchServiceApplication::Execute--Exception: System.Runtime.InteropServices.COMException (0x800703FA): Illegal operation attempted on a registry key that has been marked for deletion. (Exception from HRESULT: 0x800703FA)
SearchServiceApplicationProxy::Execute--Error occured: System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: Illegal operation attempted on a registry key that has been marked for deletion. (Exception from HRESULT: 0x800703FA) (Fault Detail
is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is: System.Runtime.InteropServices.COMException: Illegal operation attempted on a registry key that has been marked for deletion. (Exception from HRESULT: 0x800703FA)
I even attempted to create an out of the box enterprise search site with OOB masterpages and I still am receiving this error.
I have also tried the ‘Do not forcefully unload the registry at user logoff’ registry edit, but it did not work.
Has anyone ran into this issue and has another solution other than the ‘Do not forcefully unload the registry at user logoff’ registry edit?
Thanks!

IISReset works for me (but after some time it fails again)
Check this posts: http://pacsharepoint.com/2011/11/sharepoint-search-illegal-operation.html
http://blogs.msdn.com/b/distributedservices/archive/2009/11/06/a-com-server-application-may-stop-working-on-windows-server-2008.aspx
hope it helps,

SharePoint search using Term-IDs doesn't work as expected for various document types and items

If items or documents are tagged with managed metadata terms from the term store (no social tags, but pre-defined terms), you can find this content later on (after crawler has finished) using the following URL query:
http://myserver/search/Pages/results.aspx?k="85f915a2-bd9e-4c94-a840-4323d37e8df9"
The guid is the term ID (from the term store).
Issue:
That works great for office documents. It seems to be not working for several file types like txt, zip, aspx (inside page libraries) etc. All file types are generally registered with search crawler and are found correctly using the normal search, e.g. for
the term name or other content. It also not works for me with custom lists that are tagged with a term.
Questions:
1. Is using this type of search url a documented and advised feature, to find content that is tagged with terms?
2. How to setup search to find this items and documents consistently with "normal" search AND by term ID?
Thanks, Frank
Thanks, SharePointFrank http://www.layer2.de/en/products/

Hello Frank,
SharePoint contents tagged with managed metadata Terms can be searched by doing a search on “TermName”, and the search result could be refined by managed metadata. Please ensure your SharePoint site content source was crawled and Managed Metadata
Service Application was running. Personally, using a TermID involved in the URL to search items tagged with metadata isn’t advisable due to difficulties when manipulating a ID number.
Fabian Williams has included a managed metadata search section in his informative walk through:
http://www.endusersharepoint.com/EUSP2010/2010/06/01/understanding-managed-metadata-in-sharepoint-2010-its-impact-on-taxonomy-navigation-and-search-part-1-focusing-on-managed-metadata-term-store-navigation-and-search/
Let me know if I misunderstand you.
Thanks & Regards.
Lily Wu || Microsoft Online Community Support Engineer || SharePoint

How to resolve "The server is unavailable and could not be accessed. The server is probably disconnected from the network." error in Sharepoint serach crawl.

Hi all,
I have created a content source in Search service application for a particular site collection "http://spwebapp/sites".
I performed reset crawl index of Search service application and then performed a full crawl.
But i get errors on running crawl on this content source for most of the files. The error is "The server is unavailable and could not be accessed. The server is probably disconnected from the network." Though the site is accessible.
But before performing reset index the crawl was working fine on this content source. Crawl is working fine for other site collections. Only one site collection is facing this problem. Please let me know if what I can do to resolve this error.
Thanks in advance.

Are you seeing any error messages in the URL related to the Gatherer? And in your content source, are there any site URLs that are no longer active or do you have any crawl rules set up that might be affecting access to the site collection?
I've seen this happen for a variety of reason, SSL issues, proxy issues, permissions issues. The Eventvwr and ULS logs should help you narrow down the real problem.
Sometimes this is an issue because the indexer and the site are sitting on the same box, you could try doing a disable loopback check to see if that resolves the issue and if it does then go through the hassle of setting up a specific LSA :
http://iedaddy.com/2009/04/sharepointdisable-loopback-check/
ieDaddy
Blog: http://iedaddy.com
Twit: @iedaddy

Application error in Event viewer Event ID :6398 The Execute method of job definition Microsoft.SharePoint.Search.Administration.SPSearchJobDefinition

Hi Friends,
On SharePoint 2010 application server I can see this error on event viewer for every one hour it is repeating. Please look at the screenshot below. I restarted the SharePoint search service 14 and SharePoint foundation search v4. but it is not solved
the issue.
Please look at the error below and help me to fix this issue .
Thanks
valmeekeshwar

Try this
https://sharemypoint.wordpress.com/2007/12/18/error-event-id-6398-and-6482-about-security-rights-of-osearch-service/
Stacy www.sharepointpapa.com

SharePoint ULS Diagnostic Logging for Runtime Error not captured

Hi Guys,
I have this weird issue whereby my development SharePoint server 2013 (one single box with DC, SQL, CA, Distributed Cache, Search, User Profile and also Visual Studio installed in it) does not log SharePoint Foundation - Runtime errorf for my web part or
appliaction pages
This development server is scheduled to shutdown after 8PM and will only be turn on in the 8AM next day.
Whenever i hit runtime error (such as my custom web part error), it generate a Correlation ID but when i go into the ULS (LOGS folder) to locate them, it is not being captured at all.
There is no additional configuration in the Diagnostic Logging in the Central Admin. Everything was left default.
Does anyone face this issue before?
Cheng

Hello Cheng,
there few things you can do,
1. first of all confirm that logging is working, log files are getting generated, and sharepoint tracing service is running.
2. as you have a correlation ID, use
Merge-SPLog with correlation parameter.
3. if step 2 does not give you anything, try enabling logging in verbose mode, go to CA -> monitoring -> configure diagnostic logging -> select all categories and select verbose in both the drop downs.
4. alternatively, you can try to enabled "callstack" and trun OFF "customerrors", it will display the same error as ULS log.
happy Troubleshooting :)
Thanks, Noddy

Search Crawl status = Paused for:External request

Just checked my search crawl history and it hasn't run in a week.
Saw another post that said it may be a Symmantec issue, but we're not using Symmantec.
Thanks,
Scott

Curious if you're on at least SP2 or Infrastrucuture Update? There were major changes to the search infrastucuture delivered in those releases
http://blog.dafran.ca/post/2013/08/16/SharePoint-2010-Scheduled-Crawls-not-Running.aspx1) Stop the Windows SharePoint Timer Service
2) Navigate to C:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config
3) Go into the single folder in there that has a GUID type name.
4) You see a whole bunch of XML files and a file cache.ini
5) Copy all the XML files to another folder somewhere (for backup), then delete them but do not delete cache.ini
6) Edit cache.ini to contain just the number "1" in the file - erase whatever is there and replace with "1"
7) Restart the Windows SharePoint Timer Service
8) You should see XML files being regenerated in the folder
http://social.technet.microsoft.com/Forums/sharepoint/en-US/26883a1b-13f8-4614-9552-e8ca910987c9/scheduled-crawls-not-running

SharePoint Search crawl error for OWA OneNote notebooks

Similar Messages

Maybe you are looking for