Site Collection level Search Scopes after Upgraded to 2013

In SharePoint 2010 we have good amount of site collection level search scopes and it has been heavily used in search scope down.
Please correct me if any of my below statement is wrong
1.After migration these scopes cannot be used and it will not appear in search drop down.
2.Only opition I have is to create Result Source and Configure search navigation at Site Level?
3.For Result Sources to appear in drop down I need to have individual search page for every custom result source.
I would really appreciate your inputs
Thank you
Vijay

1. Usually 2010 Search Scopes can be used after migrating to 2013. What you can't do is edit them or create new ones. However, I've had mixed luck with them. About 75% seem to work, with the rest being broken beyond repair.
2. If the migrated scope doesn't continue to work your only real option is a REsult Source. To add them to the dropdown you will need to configure the navigation at the Site level.
3. Result sources can re-use result pages used by other Result sources. You need a Result source for each entry, but that result source may point to the same page as another result source.
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.

Similar Messages

Cannot create Site Collection in new Webapplication after upgrade to SP1

Hello,
after upgrading my SharePoint Server 2013 (small Farm with one SP and one SQL) I am not able to create new site collections in new web application. Furthermore I am facing trouble when creating a new web application which I suspect is a connected problem.
Environment:
SharePoint 2013 ENU with german language pack upgraded to SharePoint 2013 SP1. Both parts are upgraded (SharePoint and Language pack). Afterwards I have done a psconfigui to upgrade the DB which works fine. Only one DB (BDC is still running in compatibility
mode).
Everything is running on a single server on Windows Server 2012.
Problem(s)
When I create a new web application it tooks a very long time (3 + minutes) and ends with an error message (Sorry something went wrong !). If I close this message I can see the new web application and also its content DB. If I then try to add a new site
collection into this new web application it fails (Sorry something went wrong).
I suspect this is a connected error, but I have now idea what is going on. Everythings else seems to work...
Any idea or support would be great.
Thanks in advance
Martin

You can get issues if you hit a time out message during the creation process. How does it work if you create a site collection using PowerShell?
You can extend the timeout duration this is for web application creation but might be of use here too: http://blog.babunski.me/2013/07/17/sharepoint-404-error-while-creating-a-new-web-application/
Do you get any error messages when you create the site collection?

Sharepoint 2013 search broken after upgrade from 2013 foundation to 2013 ent.

Hello
I have tried many of the suggestions that I have found in the forums for this issue but non have worked as of yet.
I have sharepoint 2013 sp1 running on server 2012 R2 connected to SQL 2012 DB, which was upgrade from SharePoint foundation 2013. Everything is working with the exception of the search. the errors are below.
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (1d094485-eab9-458d-a363-4b5e8704048f).
Reason: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
Technical Support Details:
System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
   at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
   at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)
For some reason this is using the farm account which is not the account used for the search service but has full access to the sites and databases. So I'm not sure what or where it is getting an access denied error. Is there any way to find what it is trying
to access? BTW I have disabled the loopback check, verified it has correct access to %windir%\tasks and recreated the search service many times, changed application pool accounts
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (1d094485-eab9-458d-a363-4b5e8704048f).
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)
Any help you can provide would be greatly appreciated.

Hi ,
According to your description, my understanding is that you encountered the error Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance
after you upgraded SharePoint 2013 Foundation to SharePoint Server 2013.
For troubleshooting your issue, please try adding the farm account on the Server local administrator group and see if it is related to permission issue. Then try stopping the Timer Service, clearing
the Configuration Cache and restarting the Timer Service:
http://www.social-point.com/sharepoint-2010-event-id-6482-application-server-administration-job-failed-for-service-instance-microsoft-office-server-search-administration-searchserviceinstance
Best Regards,
Eric
Eric Tao
TechNet Community Support

Managed custom properties at site collection level when used as refiner returns no value in search result web part

I have created certain crawled properties and mapped them to the OOB managed properties( refineable active ) in search schema at site collection level and tried to use them as refiner in the search
site at farm level but it returns no value.
But when i use the same crawled property and map it to a service level OOB metadata property ( refineable active ) and use it in search as refiner it returns result , Can you help as to why this difference is there.
What steps should i do so that site level refiners also work in the enterprise search
Thanks in advance

Hi Dextar,
According to your description, my understanding is that you want to create a site level refiner in SharePoint 2013.
Here is a detailed blog you can refer to:
http://blogs.technet.com/b/tothesharepoint/archive/2013/11/11/how-to-add-refiners-to-your-search-results-page-for-sharepoint-2013.aspx
Be aware that any changes in the manage property required full crawl.
Best Regards,
Eric
Eric Tao
TechNet Community Support

Document ID - Property field shows on item view property page after deactivating the Document ID Service features at Site Collection level

Hi,
When a site collection was created, I enabled the Document ID feature at site collection level. Then some item was created in a document library as well as list libarary
Now it was decided that we dont want the Document ID feature so I disable the feature from Collection feature list
Still when a user view the property of a document it shows the Document ID property with the ID (when click on the ID it shows the message that
This Site Collection is not configured to use Document IDs.
Troubleshoot
issues with Microsoft SharePoint Foundation.
Correlation ID: 9640ac9f-4b9c-4ae8-9f0b-402ed7e3b3c5) Is there anything that I should do so that DOcument ID property does not show on the document property page... I tried
to looked at the content type to see if I can remove the document ID but I could not find the Document ID as a property that can be removed from the type

Hi,
I would just remove the column from the view. You can make views for each list, it you look under the list by Clicking List while the list is open, you should see a link in the ribbon which say "Modify view" click this link.
This link will open the edit view page you can then uncheck the box for the column which will remove it form that view.
According to this
http://msdn.microsoft.com/en-us/library/ee559302.aspx
Deactivating the feature removes links to the Site Collection Settings page, makes the page that is used to look up document IDs no longer available, turns off the document ID service, and stops assigning document IDs. The server does not remove the columns
that it adds at the site level when the feature is first activated so that, even after deactivation, the existing document IDs are preserved. After the feature is deactivated, users who try to use a static URL to look up an item by its document ID see an error
message indicating that "This Site Collection is not configured to use document IDs."
The Document id service will add new columns to the document content type and the document set content type.
It also adds an event receiver which should be deactivated when you deactivate the doc id service.
Theoretically. You should be able to go in and remove the columns from the document type, and then force an update.
Thanks,
Rock Wang
Rock Wang TechNet Community Support

How to set Document Library Item Limit at Site Collection level?

Hi,
I have SharePoint which contains one Site collection with many Sites. Each sites has many document library.
Actually my requirement is, End Users wants to see only 10 items per page in document library. We can manually set by using "Item Limit" option but i could not set that for around 150 document libraries.
Is there any possible to set that in Site Collection level?
Thanks & Regards
Poomani Sankaran

You can run for each loop and use below code
http://get-spscripts.com/
#Get the site and list
$web = Get-SPWeb "http://portal/sites/testsite"
$list = $web.GetList(($web.ServerRelativeUrl.TrimEnd("/") + "/Shared Documents"))
#Get the list view to be changed
$newview = $list.Views["Sort by modified date"]
#Set the mobile and default mobile view properties
$newview.MobileView = $true
$newview.MobileDefaultView = $true
#Update the view configuration
$newview.Update()
$web.Dispose()
$web.Lists[0].Views[0].RowLimit=30
$web.Lists[0].Views[0].Update()
How you can get all list using powershell
http://sharepointrelated.com/2011/11/28/get-all-sharepoint-lists-by-using-powershell/
If this helped you resolve your issue, please mark it Answered

The Specified name is already in use while activating Publishing feature at site collection level in Moss2007

Hi,
Please suggest on this "The Specified name is already in use while activating Publishing feature at site collection level in Moss2007"
The specified name is already in use.
A list, survey, discussion board, or document library cannot have the same name as another list, survey, discussion board, or document library in this Web site. Use your browser's Back button, and type a new name. at Microsoft.SharePoint.Library.SPRequestInternalClass.CreateList(String
bstrWebUrl, String bstrTitle, String bstrDescription, String bstrListUrl, String bstrFeatureId, Int32 lTemplateID, String bstrDocTemplateType, ListQuickLaunchOptions qlOpt)
at Microsoft.SharePoint.Library.SPRequest.CreateList(String bstrWebUrl, String bstrTitle, String bstrDescription, String bstrListUrl, String bstrFeatureId, Int32 lTemplateID, String bstrDocTemplateType, ListQuickLaunchOptions qlOpt)

there are some OutBox list/libraries being created when you activate publishing features, make sure those names not being used: check this post for more detail..
http://social.technet.microsoft.com/Forums/sharepoint/en-US/f7e93d26-c2a1-42c2-b191-dc48f734684b/the-specified-name-is-already-in-use-error?forum=sharepointgenerallegacy
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

The SharePoint Server Publishing Infrastructure feature must be activated at the site collection level before the Publishing feature can be activated.

Hi All,
I am trying to activate the Publishing feature for a SharePoint website using a custom Site Definition File. The problem I am getting
is when I try to use the custom site template I get an error message:
New-SPSite : The SharePoint Server Publishing Infrastructure feature must be activated at the site collection level before the Publishing feature can be activated.
The custom
Site Definition File snippet is show below:
<?xml
version="1.0"
encoding="utf-8"?>
<Project
Title="SiteDefinition1"
Revision="2"
ListDir=""
xmlns:ows="Microsoft
SharePoint"
xmlns="http://schemas.microsoft.com/sharepoint/">
<NavBars>
</NavBars>
<Configurations>
    <Configuration
ID="0"
Name="SiteDefinitionDelegateControls2">
      <Lists/>
      <SiteFeatures>
        
        <Feature
ID="{3bae86a2-776d-499d-9db8-fa4cdc7884f8}"
Name="FeatureDefinition/15/3bae86a2-776d-499d-9db8-fa4cdc7884f8"
/>
        
        <Feature
ID="{a392da98-270b-4e85-9769-04c0fde267aa}"
Name="FeatureDefinition/15/a392da98-270b-4e85-9769-04c0fde267aa"
/>
      ...Other Site Features
      </SiteFeatures>
     <WebFeatures>
        
     <Feature
ID="{94c94ca6-b32f-4da9-a9e3-1f3d343d7ecb}"
Name="FeatureDefinition/15/94c94ca6-b32f-4da9-a9e3-1f3d343d7ecb"/>
     ... Other Web Features
      </WebFeatures>
      <Modules>
        <Module
Name="DefaultBlank"
/>
      </Modules>
    </Configuration>
</Configurations>
<Modules>
    <Module
Name="DefaultBlank"
Url=""
Path="">
      <File
Url="default.aspx">
      </File>
    </Module>
</Modules>
</Project>
I hope you can help
Colin

As the error says. The Publishing Infrastructure feature must be activated at the Site Collection level where you are creating a new site PRIOR to turning on the Publishing feature. So if you are trying to use this site definition to create a
new Site Collection then its not going to work. If you are trying to create a sub site then make sure that Publishing Infrastructure is enabled in the site collection before trying to create a sub site with this site definition.
Internally Microsoft does this for the Publishing Portals using custom code. Here's an article that discusses how to do it in SharePoint 2010.
http://msdn.microsoft.com/en-us/library/office/gg615465(v=office.14).aspx
Compare what's in the article to one of the Publishing templates available out of the box in 2013 and you should be able to find the assembly that is used to load the Publishing features.
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.

Usage reports are not getting in site collection level

Verifiedthatusage
data collection is enabled.
Verified that Analytics Usage, Feature Use, and
Page Requests are selected under the
Events to Log.
Verified that jobs Microsoft SharePoint Foundation Usage Data Import and
Microsoft SharePoint Foundation Usage Data Processing scheduled and are working fine under
Log Collection Schedule
Verified that Analytics Usage definition Receivers is defined.
Verified that Page Request usage definition Receivers is defined.
Verified that both managed accounts (admin & service accounts) is having permissions to database in production environment.
Verified that Search crawl also working fine.
Usage File is getting created successfully-see attached
(typically found
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS\Request Usage)
In this folder, a .usage file should be getting created if all above steps are healthy and working correctly. Ideally we will see a *.tmp file and periodically
a *.usage file is getting generated.
As a last option we have tried by re-creating the Usage service application with above steps.

The amount and variety of formatting makes reading your post very difficult.
You have contradictory information there; is this for SharePoint 2013, if so this is in the wrong forum, or is this for 2010 in which case your title is misleading.
You have not described your issues very clearly. I believe that you cannot see site collection analytics, are these blank/empty or throwing an error? Are the usage files appearing in the expected location?
Have you checked the timer jobs that run nightly to compile the analytics reports?

Cannot search messages after upgrading to iOS8!!!

After upgrading my iPhone5S to iOS8 yesterday, I noticed that it cannot search Messages for information. To be exact, it only searches messages that have been sent/received after the upgrade. It seems it hasn't cached older messages and keeps ignoring them when searching for something. Any help? Is it a bug?
iPhone 5S, iOS 8

I am having this same issue. I live in Korea and changing the language to Korean made the messages searchable, but when I changed back to English, the problem returned and I was unable to search all my messages via the search window in the messages app, but then, after about 5 minutes, the messages app crashed, and after that, the problem was resolved. Gotta sat that I'm so far unimpressed with ios 8; seemingly not ready for Primetime.

Cannot search messages after upgrading to iOS7!!!

After upgrading my iPhone4 to iOS7 today, I noticed that it cannot search SMS Messages for information. To be exact, it only searches messages that have been sent/received after the upgrade. It seems it hasn't cached older messages and keeps ignoring them when searching for something. Any help? Is it a bug?

Same problem here with 4S updated to IOS 7 via OTA.
I have solved the problem by connecting the phone to Itunes, backing up, re-installing IOS7 and restoring from the backup.
Now everything is fine and all messages are indexed.
I hope this helps!
F.

Can we set List View Lookup Threshold at site collection level ?

Hello,
Presently, we have requirement to set the List View Lookup Threshold at Site Collection/Sub-Site level instead of web application level.
Could you please let me know, are there any ways to set
List View Lookup Threshold setting at Site Collection/Sub-Site level
in SharePoint 2010 using Powershell/Object Model
Also, it would be helpful if you colud let me know, upto what extent , we can drill down List View Lookup Threshold setting i.e. SubSite/List/Library-Folder.
Thanks in advance !
Regards,
Sagar Acharya
Email - [email protected]

Hi Sagar,
We cannot set list view threshold value at sitecollection/subsite level. It can only be set at web application level.
However we can bypass the 5000 limit using PowerShell command by setting “Enable Throttling”= false for particular list.
Reference link:
http://pravahaminfo.blogspot.in/2012/10/how-to-increase-list-view-threshold.html
Thanks,
Somnath Matere

Old files are unable to be searched via Search Functionality after upgrade

After upgrading TREX to version 7, older files prior to upgrade are now unable to be indexed. Only new files coming in are indexed properly.
Thanks in advance for the help!

Hi Lorcan, thanks for your response!
Anyway, checking Indexing Monitor, all statuses are in RED (Unknown Error: null). Although there are number of documents indexed properly, these files are the new files after the upgrade. The old ones are not indexed.
I have logged OSS already, but still no help.
Thanks!

Pro grammatically create three sub-folders with specific name under each of root folders in site collection level??

Hi,
i have a document library Named "Digital" in a site collection. In that document library i have bunch of customer folders with different customer name. My requirement is i need to create three sub-folders (like Images, Processed, Status) each of
customer folders. so how can i automate to create sub-folders with specific name. can i use object model or power shell to achieve this one.
Thanks in advanced!

Hi Murugesa,
Thanks for your help. i was trying to create folder inside document library using your code. but unfortunately i cant debug code and cannot create folder inside customers folder. Following is the code, basically i am creating a SharePoint project and adding
an item as class file and deploying to share point site and then trying to debugging code, but break-point showing as yellow circle. i checked solution has been deployed to the server but still not creating any folder. It will be very helpful if you can describe
all the steps. should i create console application?
Appreciated !!
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using Microsoft.SharePoint;
namespace Add_Sub_Folders
class Create_Folders
public void Sub_Folders()
var foldersList = new List<string>();
SPSecurity.RunWithElevatedPrivileges(delegate()
try
using (var site = new SPSite(SPContext.Current.Site.Url.ToString()))
using (var web = site.OpenWeb())
web.AllowUnsafeUpdates = true;
foreach (SPFolder folder in web.GetFolder("http://nyc01d1sptmp01:8080/Shared%20Documents/").SubFolders)
if (folder.Url.ToString() != "Shared Documents/Forms" && folder.Url.ToString() != "Shared Documents")
foldersList.Add(folder.Url);
SPFolder subFolder = web.GetFolder(folder.Url);
subFolder.SubFolders.Add("Draft");
subFolder.SubFolders.Add("Status");
subFolder.SubFolders.Add("Final");
folder.Update();
web.AllowUnsafeUpdates = false;
catch (Exception ex)
ex.Message.ToString();

BIAS SoundSaver Input Level Not Working after upgrade from Win 8 to 8.1

Have been using BIAS SoundSaver for INport software to digitize music LPs and cassette tapes to load on MP3 player. Worked fine with Windows 8. However, now that I have upgraded to Win 8.1, I can get sound of LPs and cassette tapes but the Input Level that controls the recording level on the software no longer functions. My computer is an HP ENVY Phoenix h9-1355 Desktop Computer with IDT High Definition Audio CODEC. I am wondering if the problem may be with the audio drivers installed on the computer.
This question was solved.
View Solution.

Hi @Alkay
I see that you are having sound issues after your 8.1 upgrade. Did you update to the 8.1 versions of the drivers?
They may be found here: HP ENVY Phoenix h9-1355 Desktop PC Drivers
Is it only the one application seeing this problem?
Malygris1
I work on behalf of HP
Please click Accept as Solution if you feel my post solved your issue, it will help others find the solution.
Click Kudos Thumbs Up on the right to say “Thanks” for helping!

Site Collection level Search Scopes after Upgraded to 2013

Similar Messages

Maybe you are looking for