View Complete Post
I have Sharepoint 2010 Foundation with Search Server Express installed. The Sharepoint was an upgrade from WSS v3 and search server express 2003.
After the upgrade whenever users search from the main site I get web part errors displayed on the search page. I think because it is trying to use the old search server express which is no longer installed.
Search Server Express 2010 is now installed and a Search Center web page can be viewed however when searching via the entire sites I site the web page with web part errors.
Any thoughts or any further information you require I can provide.
Can I get some clarification on a couple of points?
Firstly, what is the recommended installation path for SPFoundation and Search Server Express on the same server. Do I just install SSE 2010? Or SPF 2010 and then SSE 2010?
Secondly, when the two are installed together how do I add the a SSE 2010 search center link to my SPF 2010 site so I can search all crawled content? I've created crawls of Exchange public folders and file shares but when I use the built-in site search
box it's only returning content crawled from the local site and not anything from the other crawls.
Anyone know how to setup so that Sharepoint 2010 crawls Sharepoint 2003 people?
We have tested adding a new content source called People with a content source type of sharepoint and used sps://site.domain.com/site$$$people as the start address.
When trying to SAVE/OK we get the following error.
The start address "sps://site.domain.com/site$$$people" is not valid for this content source type.
i am using Sharepoint 2010 and FAST Search Server for Sharepoint 2010. i am confused with FAST Server for Sharepoint 2010 Installation. i search for a long time to find a proper documentation regarding Installation, Configuration and other details about
FAST Search 2010. but still i couldn't find proper, organized document about these topics. please someone give me a Simple, and complete guide to install and configure FAST Search Server for Sharepoint 2010. i am in the middle of a project, so please any urgent
help is really appreciated. please help guys. thanx
Hi, I am using Fast for Sharepoint and I have created a simple Employee database in SQL server 2008 and I am trying to crawl this database.
Using Sharepoint designer, I have created an external repository and I have configured it to look at my test database. After trying to crawl this database - I get two successfyul documents crawled - which are just junk documents. And 5 errors.
The errors say:
Error while crawling LOB contents. ( IEntity could not be found using criteria 'Id=2502'. )
I also noticed that if I was to disable "Defaul Action" from the BDC configuration, then I get all successful crawled documents. However, if I click on any of those documents in the search page, then it brings me to "unkown page".
This makes sense since Default Action (View Profiles) is disabled. Does anyone know how to avoid this error message above without having to disable Defaul Action check box?
P.S. I can also see that the connection between SQL Server - BDC - SP is working since when I create a user profile page, I can see that data populate.
We have to index a fileshare that is outside of our windows domain. We cannot create a windows domain trust, because of this we use a crawl rule with a specific account that is capable to index the share in that domain. The crawl ends succesfully and we
can see that the data has been indexed. Our users can login fine on the search webapp, but unfortunately we cannot see any results while searching.
I assume this is because of the file acl's of that specific share and that the query engine automatically filters based on the logged in username on the webapplication? How can i make the query engine ignore the original file acl's of the indexed data?
According to the following TechNet article
http://technet.microsoft.com/en-us/library/ff381239.aspx, "Do not install FAST Search Server 2010 for SharePoint on the same server as SharePoint Server 2010." is commented in the Important section but there are no justifications to this "non-recommended"
approach. I've searched for an explanation but only found one entry that mentioned for performance reason.
Would you please provide me with an article to substantiate this performance or some other reasons as to why FAST Search Server "should" be installed on its own box?
Does Search Server 2010 Express include Sharepoint Foundation? Or do I need to install Sharepoint first and then install Search Server on top? This is for a brand new install on a single server.