View Complete Post
The knowledge worker is greatly empowered if she is able to access information across the enterprise from a central access point. With the SharePoint Portal Server 2001 Search Service you can catalogue information stored in Exchange public folders, on the Web, in the file system, and even in Lotus Notes databases. This article discusses the use of ActiveX Data Objects and the Web-based Distributed Authoring and Versioning protocol for creating search solutions based on SharePoint Portal Server 2001.
MSDN Magazine April 2002
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.
Sharepoint 2010 Upgrade Question - A customer is currently running sharepoint 2007 on a 64bit windows 2003 OS with SQL 2005 sp2, they are looking to install/upgrade to Sharepoint 2010 and want to use the current SQL server,for the upgrade a new SharePoint
2010 environment will be built and for a short while they will have two instances of SharePoint running SP2007 and SP2010. The plan is to then manually migrate the data from SP2007 to SP2010 (ENT), the web and application servers will be newly built. From
research I think they have three options
1) Upgrade the current SQL 2005(SP2) instance to SQL 2008 R2 standard.
2) Install a new instance of SQL 2008 R2 on the same server and have both SQL 2005 & SQL 2008 running on the same server (Is this an option? Will sharepoint happily run from a SQL server running two SQL instances, do I have to be
careful regarding the installation and configuration, could I break the existing sharepoint farm doing this?)
3) Upgrade the current SQL server to SP3 and install a new instance of SQL 2005 SP3 and install SharePoint 2010 Enterprise here, again I have all the questions from point 2 above.
We are thinking of trying option 1, then 2, then 3, and obviously only moving to the next option if we come across a show stopper. H
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.
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?
We have two server farms:
1. MOSS 2007 Server Farm having Web application and its pages and content
2. SharePoint 2010 Farm having Enterprise Search 2010 with one Web Application using Search Template
We are trying to crawl the MOSS 2007 web application, which on a separate farm from the SharePoint 2010 box. We created the Search Service Application, Web Application and have associated the Web Application with the Search Service Application.
We have provided the scopes for searching the MOSS 2007 Web Application for its content and pages and also provided separate scope for searching people from the MOSS 2007 box using the appropriate SPS2/STS3 protocol.
We have also made a change in the Search Settings of the MOSS 2007 Site Collection to redirect the search to the SharePoint 2010 box, when any user uses the Search box of MOSS 2007. This works perfectly well.
Appropriate read-only rights have been given to the web application using the Central Administratoin web application policy.
The only issue we have is, when a user tries to visit the search results pages on the SharePoint 2010 box, and when displaying the search result, SP 2010 box hits MOSS 2007 box to fetch the require data and displays pop-up box for Authentication.
Is there anyway, where we can supress the Authentication