Timeline for Managed Property is not Displayed for a List Column issue in SP 2013 Search Serv Application
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 23, 2017 at 12:18 | comment | added | Matthew McDermott | If that is an option, sure. But it is rather drastic. | |
| Mar 22, 2017 at 14:49 | comment | added | samolpp2 | My doubt, is if this kind if behaviour appears in this env, should i create a new search serv appln and perform all the steps again?its been created long back- 5 months before - after that, several installations performed on this farm.ie,workflow manager,SP2 upgrade etc . Am having WFE and SQL server separated . my doubt is, whether all these installations, configurations might have done something on this already existing search serv, appln?its strange that, newly created document library columns were perfectly working and showing in the cralwed properties section-eg:ows_testdoclibcolumn1 | |
| Mar 22, 2017 at 14:44 | comment | added | samolpp2 | yes, i have created another splist and with testlistcolumns and done a full crawl but still, i was getting the above error, but with few articles already mentioned about the above error by Wictor etc , i got the fix for that error and ran the timer job and it the error went off. Now i ran the full crawl and this time , the crawl is sucessfull and no errors.But in the ows properties section, there was no mentioning of newly created splist column , ie, ows_testsbulistcolumn1. | |
| Mar 22, 2017 at 13:46 | comment | added | Matthew McDermott | Ordinarily the lists are crawlable by default. Once you set it just do another full crawl. Let me know what you find once you get the crawl worked out. | |
| Mar 22, 2017 at 5:56 | comment | added | samolpp2 | i got error in the crawl errors: Error in the Microsoft SharePoint Server People Protocol Handler. " Could not find stored procedure 'Search_GetRepositoryTimePerCrawl'" | |
| Mar 22, 2017 at 5:46 | comment | added | samolpp2 | how to make the LIST IS CRAWLABLE? In the splist settings, i have ,made it as "YES" for the search settings of the lists's advanced settings --> allow items from this list to appear in search results Will there be any time delay for generating index / search contents or creating managed properties in a sp farm? will it take many hours or days to update the crawl db / and fetch data from crawl and populate the results in the search serv appln page ? | |
| Mar 21, 2017 at 15:00 | comment | added | samolpp2 | Yes, I have created the doc lib & splist in the same web its in my root web. I didn't check the crawl logs yet! | |
| Mar 21, 2017 at 14:58 | comment | added | Matthew McDermott | Is the list in the same web as the doc library? Are you certain that the list is crawlable? Check the Crawl Logs, the URL for the list should be there. If not you need to troubleshoot the crawl. | |
| Mar 21, 2017 at 14:40 | comment | added | samolpp2 | i have tested again with a new SPLIsT, with newly created 2 columnsand added some value and performed full crawl in my srch serv appln. but the crawled properties are NOT getting generated. At the same time, when i created a new document library and created 3 columns and uploaded a few documents into the doc lib with filled in metadata, and performed the full crawl , the doclib columns are appearing in the crawled properties, starting with ows_mycolumn1 . so there must be some problem with SPLIST thats not getting crawled by SP search engine. is there any resolution for this? | |
| Mar 21, 2017 at 14:00 | comment | added | samolpp2 | i have used a doc lib column and not site column. so i thought the managed property column generated after full crawl will be having this mycolumn1owstext format. but even in the cralwed property or managed property i am unable to see the column with ows_mycolumn1. amy problem with the search serv appln ? i did a index reset and performed a full crawl again, but that also failed! | |
| Mar 21, 2017 at 12:05 | history | answered | Matthew McDermott | CC BY-SA 3.0 |