Tag Info

New answers tagged

0

Create result source with some custom search query Create Result Source with PowerShell Create new page How to create a page in powershell Add search result webpart to page in step 2, and configure it, it needs to use the result source created in step 1 Adding Web part on pages using PowerShell script Important note: In 99.9% of the cases, you'd ...


3

From the site your archiving via Site Settings go to Manage Query Rules (or from Search Service Application page i Central Admin go to Query Rules). On the Manage Query Rules page, select Recently Changed items and push the button New Query Rule. On the Add Query Rule page, enter a rule name, remove the default condition and follow the ling Change ...


0

Thanks a lot Jesus for your quick answer, yes I will definitely asked specific question. I will also go through all the the links you sent. Yes I am an advanced developer with HTML, CSS and kind of Intermediate with JAVASCRIPT, How I am going to use them without designer and no access to the server? can I use a third party editor. Please more detail on ...


0

You are tackling a lot of stuff for your first time out with SharePoint. The answer is YES you can do this. "How" you do it depends on the way your administrators deployed SharePoint and what services they made available to you. First - with Search. Some things do have to be configured in Central Admin, but not everything. More than likely for your ...


3

Those are not log files, it's your actual search index. It is recommended to move the index to it's own drive so that the index (or any other log files) cannot consume all disk space on the C drive. Moving the index means that you need to clone the search topology and then move the clone to another drive. This is kind of a complicated procedure as you have ...


0

Try with the content types. Limit the search results for respective content types. Let me know if you have any questions


0

Turned out to be an issue with RestSharp, and it overwriting the Content-Type header. The following resolved the issue: var request = new RestRequest { Method = Method.POST }; request.Parameters.Clear(); request.AddParameter( "application/json;odata=verbose", javaScriptSerializer.Serialize( requestBody ), ParameterType.RequestBody ); ...


-1

Open other Site Collection using SharePoint Designer and go to top path and copy the Control_SearchResults.js to same path at your Site Collection that has the problem.


0

If anyone has a problem like this and your using you own name as the search criteria, make sure you are not the account that is importing data or entering the data as it searches the modified by field and returns all items. This makes you think that its not filtering results. Duh I guess.


0

SharePoint uses a "Crawl Account" to read and access the crawled files. This account has to have READ permissions on the content sources. By default, security ACLs are also detected and end users who do not have access to the files will not see them in search results. There is nothing to configure. In SharePoint this would be SharePoint permissions, on a ...


1

As Waqas Sarwar mentioned, I had to start SharePoint Foundation Web Application on the Search Server to get rid of that message. When I stop it again and re-run the missing server side dependencies the error appears again. I now disabled the check, because I must not run two Web frontends because of some 3rd party licenses.


0

I've tested this in SharePoint Online (Wave 15) and found that data in lists in the app web IS searchable; Not only from the host web, but from other site collections that consume the search service. I haven't read anything about this issue being fixed, but it looks like it has. Do others find the same?


0

Couple of things to check. Run a Full crawl if not done before. Make sure the Search is crawling that document.You should check in the Crawl history /log if the specified file indexed. Check the crawl logs for potential error. Also try to upload the different 2007 files and run the full crawl and test it. from communications, looks like your problem with ...


0

I published now a Step-by-Step guide for the calculator in my Blog. Don't be afraIT.com to check it out.


0

ExecuteOrDelayUntilScriptLoaded(init,'sp.js'); function init(){ var cContext = new SP.ClientContext('siteurl'); var oList = cContext.get_web().get_lists().getByTitle('List name'); var camlQuery = new SP.CamlQuery(); camlQuery.set_viewXml('<View><Query><Where><Geq><FieldRef Name=\'ID\'/>' + '<Value ...


0

Depending in your requirements and how many servers in your farm, you can create a Search Service Application in Central Admin or through PowerShell. Since you mention you want a dedicated server you will probably have to use PowerShell for provisioning. I don't know your requirements for the 6 components of the SSA but this should help with the initial ...


0

Change the query to something like "*" so you get a result.


2

How many site collections are we talking about? Why do you have two search service applications? If you want to have a split on search service application's usage, then its better to have it at web application level from a logical architecture perspective. Central admin -> Application Management -> Service Application Association page to identify service ...


1

Each managed property shown in refiner, renders a div with a refinername attribute, which actually defines managed property's html mockup. Below is the sample code: //check the language var language = window.navigator.userLanguage || window.navigator.language; if(language == "en-US"){ //hide/show Managed property's div ...


1

The search box uses (as the name implies) the search engine, meaning that new files will not be returned before the search crawl has found them and added them to the search index. In Office 365 the search runs all the time and quite rapidly finds new items. You can if you like force a reindex of a document library from the library settings (but this will ...


0

You should use selectproperties as paul suggested After adding it your query should look like below _api/search/query?sourceid='d0aa2c2e%2D7709%2D46f1%2D835a%2D244f483e4b0e'&selectproperties='columnName','columnName2'


0

That sounds like trim duplicates hits you. go grab the searchquerytool https://sp2013searchtool.codeplex.com/ add your hostname in the connection pane and the site where your wiki is placed search for "webroot secureanywhere" toggle trimduplicates to false. If you have 2 results then - buy me a beer :) and use this script ...


0

Do an Index Reset followed by a full crawl - if that is an option for you.


3

I'm grasping at straws here, there isn't a lot of information on the topic about this. I did stumble upon a post that may give clues as to why it is happening and perhaps a work around: SPFile.MoveTo(), at first glance, looks to be a very straightforward method where a file can be moved from one folder to another. Trying to use it and have an ...


1

you can update the search results webpart to exclude the word tree by go to the search results page edit the page edit the search result webparts click change query add (and -SharePoint) to exclude the keyword from the search see image below ...


0

The simplest approach is to secure the document to just yourself. Then it will only appear in YOUR results and no one else.


0

If it is just one document in a document library of many files, I would go into Central Admin and create a Search Exclusion rule for the file and it won't appear in the index. It might be listed as Remove Search Results, I only have 2010 on prem atm and 2013 delivered via Office 365 so I can't verify the exact language in Central Admin of 2013 on prem. An ...


0

When using HNSCs, you must have NTLM configured on the Default zone your FBA-enabled web app. Additionally, you must also have a site collection that matches the host name of your web application. For instance, if your web app was set up on https://hnsc, you must also create a site collection on that web application at the https://hnsc address (you can do ...


0

Their are couple of reason for the access denied.You should check following things. Try to access the Web application with Default content access account. Disable the loop back check. Make sure the You are crawling the default Zone url of the web application make sure NTLM authentication is being used for the default zone. Make sure you have the root ...


0

Check if users have permission to view the search center site/site collection or if you haven't configured search center, then possible user don’t have the permission to view the search result page OSSSearchResults.aspx.


0

Use the following query {?{searchTerms} -ContentClass=urn:content-class:SPSPeople Path:{\SiteCollection.URL}/Form-ListURL/} Let me know if you have any questions


2

Once you have created a Managed property and made it searchable. Run full crawl. Create a managed property for the crawled property created for this property bag.Make the managed property searchable and retrievable. Use it in query just like any other normal managed property. for eg: Prop:Value


1

{Site.Url} will be the URL of the site where the WebPart is, so in your case that's the Search Center. When Microsoft is use the description URL of the site from where the query was issued. then it's due to them expecting you to configure a WebPart file and reuse that in many sites which without the token would require you the edit the WebPart after ...


0

The comments in that example do the best job of describing the crawl process that I've seen. The section that describes the incremental crawl BCS Model configuration is just below the section referenced by johnnyjob. The relevant bit is: Incremental crawl: This is the same as in a full crawl, unless several things are configured to enable your shim ...



Top 50 recent answers are included