Here are some simple steps to get Federated search results to work in SharePoint 2010. Its actually really simple, Kudos to the search team. Note that this sets up a new Bing federated result, there is already one in there, but this walks you through setting up from scratch.
Enjoy!
Chris
Exercise 1 – Setup Federation
Purpose: Learn to pull in outside search results (federation)
from Bing.
Result:Federated search results
Task 1 – Configure your Search Application
Open SharePoint Central
Administration
Click “Application
Management”
Click “Manage service applications”
Click “My Search Application”
Click “Federated Locations”
Click “New Location”
For location name, type
“Bing”
For display name, type “Bing”
For description type,
federated results from Bing Search provider”
For author, type “Microsoft”
For version type “1.0.0.0”
Leave the Trigger as “Always”
NOTE your options,
prefix and pattern can be applied to the search keywords in deciding to
send a query to the federated provider
Run a search for “SharePoint”,
you should get no federated results
Click “Site settings->Edit
Page”
Find the “Top federated
results” web part
Click “Edit web part”
Select “Bing”
Click “OK”
Run a search for “SharePoint”,
you should get back a single federated result (the top one):
Click “Site Actions->Edit
Page”
NOTE: you may have to click back to the home page, run a search
and then click “Site Actions->Edit Page”, there seems to be an issue
with resending the same query in Beta
Edit the Top Federated
Results web part, expend “Display Properties”
In “Results Per Page”, set it
to 3
Click “Ok”, rerun your
search, you should now see the top 3 results:
So you read my last post and decided that maybe SandBoxed Solutions isn't that great of an idea. You decided to implement a Solution Validator to limit what your ole developers are doing.
You got the validator created and you installed it, but then realized, its not quite right. So, you undeploy it right? Oh, wait, every object that goes in the Object hierarchy table has to have a "public" contructor for deserialization (ie, pulled out of the ConfigDB and turned into memory). Otherwise you get a nice error in Visual Studio and/or Central Admin and you won't be able to retract the solution.
Exception in RefreshCache. Exception message : "MySolutionValidator.MySolutionValidator cannot be deserialized because it does not have a public default constructor."
K, if you followed the little article up there, then you'll notice that particular piece is missing! Now your stuck…how do you get it out? Well, you gotta run a command against the config database: NOTE: This is a highly dangerous operation, if you mess it up, your Farm gets deleted!
delete from Objects where properties like '%MySolutionValidator%' –or to be more safe, the full assembly name
You could also run the following stsadm command provided you do the query to find the id in the Config database:
select id, properties from Objects
where properties like '%MySolutionValidator%'
STSADM -o deleteconfigurationobject -id “id retrieved from object table”
This will clear the object and the retract will succeed. This will be the case for ANYTHING that goes into the object hierarchy table.
So what is this you ask? Well, I did a little digging, I watched the Timer Job and the query it sent ( to the content database of the central admin site):
SELECT tp_WebPartTypeId, COUNT(1), tp_Assembly, tp_Class FROM AllWebParts (NOLOCK) WHERE tp_WebPartTypeId IS NOT NULL GROUP BY tp_WebPartTypeId, tp_Assembly, tp_Class
You get back a result set that has a null for the tp_Assembly column for the web part. What is this web part you ask, well it is the Microsoft.Office.Server.Search.WebControls.SearchTopologyView web part
in the Microsoft.Office.Server.Search, Version=14.0.0.0,
Culture=neutral, PublicKeyToken=71e9bce111e9429c assembly.
If you do a query to see where these 6 instance are:
select * from AllWebParts where tp_WebPartTypeId = '8D6034C4-A416-E535-281A-6B714894E1AA'
You will see that the web part exists on two pages:
SearchAdministration.aspx
SearchFarmDashboard.aspx
Open those pages, notice…It DOES exist!
Now, here is the funny thing – rerun the queries. As soon as you open those pages, the databsae gets updated and the error will go away. Weird!!!
When creating a custom User Profile Property, be sure to check the "Default User Profile Subtype" checkbox. If you don't you won't see the property on the manage properties page and won't be able to get to it through the UI.
However, I figured a way to get to it…just paste in the browser (to get your appid just click on another property to edit, then change the name query string):
And you will be able to get to it and check the checkbox
Another issue, when you click the "Add new mapping", if you don't select anything, it will add the "Select Attribute" to your mappings, this is obviously wrong and will not make your ForeFront Sync happy.
Also note that after adding a new property, your log will get several "Sync" errors for each site collection saying you don't have that property in the site!
[UPDATE] – In RTM, the checkbox will be checked by default…woohoo, now you just gotta hope the admins don't uncheck it!
Sooo, I have this lovely app def file, that uploads perfectly. But when I go to use one of the entities in a list column, I get this interesting issue (notice that I don't get columns, but the first named TypeDescriptor):
Fair enough, I'll remove the wrapper from around my return
columns from the query. This USE to work in 2007 by the way:
Re-upload, and whalla…it works like it did in 2007!
But, on adding an item with item resolution, you get this lovely error:
The root TypeDescriptor with Name 'Reader' belonging to Method with Name 'Find_Customers', of Entity with Name 'Customers' and Namespace 'Northwind' has a TypeName that is not assignable to System.Data.IDataReader or is not a Collection TypeDescriptor, which is necessary when using LobSystems of Type Database.
Fair enough, sooo, I go and change it in the app def file:
ReturnTypeDescriptor of MethodInstance with Name 'Find_Customers_Instance' on
Entity (External Content Type) with Name 'Customers' in Namespace 'Northwind'
should not be a Collection TypeDescriptor for MethodInstances of Type
'SpecificFinder'
Not alot of people actually installed antivirus software on their SharePoint 2007 environments. The unfortunate thing is, only Microsoft had something that would actually plug in (as far as I know anyway and I did a lot of research). The only solution has been ForeFront security (NOTE: this is NOT the same thing as ForeFront Identity). If you are on SharePoint 2007, you should know that they released SP3 of ForeFront security a few months ago, I just now found out which really shows you how important it is in the community (ie, not very). You should download and install the new SP3!
One piece of software that you should start out testing and considering for your 2010 environment is the Microsoft Forefront Protection 2010 for SharePoint Beta 2. It is also available for download from here.
SessionState is removed from the IIS 6.0 system.web section
FULL IIS 7.0 "system.webServer" section has been added
Modules removed
OutputCache
FormsAuthenciation
UrlAuthorization
WindowsAuthentication
RoleManager
Session
Handlers removed
SPHttpHandler!!! – everything is done via the modules!
System.Workflow.ComponentModel.WorkflowCompiler
In SP2010, you cannot use a "While", "ConditionedActivityGroup" or a "Replicator" activity in SharePoint web applications. They have set "Authorized" to "False"!!! – WHY?
Rather than all types in mscorlib, they have explicitly set it so you can only use
Guid
DateTime
Boolean
Double
String
Hashtable
ArrayList
DebuggableAttribute
ComplationRelaxationAttribute
RuntimeCompatibilityAttribute
Int32
TimeSpan
Generic Collections
New authorized types
SPItemKey
SPWorkflowUserContext
New assemblies
Microsoft.Office.Access.Server.Application
Microsoft.Office.Workflow.Actions
Four new location settings with a timeout of 3600ms:
_layouts/UploadEx.aspx
_layouts/ctdmsettings.aspx
_layouts/policyconfig.aspx
_layouts/metanavsettings.asxp
Two new location settings with webServices protocol clear:
_vti_bin/EwaInternalWebService.json
_vti_bin/DynamicGridContent.json
New location settings random:
_layouts/pptInsertPicture.aspx
_vti_bin/powerpointBroadcastHost.asmx
_vti_bin/powerpointBroadcastHost_1_0.asmx – what the heck is this for I wonder?
_vti_bin/present.asmx
Two new appSettings keys – why the hell these are here and not a config section is beyond me!
I hearby delcare that Jeremy Thake at SharePointDevWiki.com has full permission to use any content on ArchitectingConnectedSystems.com with full permissions to reproduce the content displayed here!
NOTE: This is an older version of the install. If you want RTM steps, go here
From fresh hardware to full SharePoint 2010 dev install, everything you need is right here! No Login required like some other sites! Keep in mind these steps are NOT for production (you wouldn't run your site on beta software would you, even if you did, I hope you paid for it). These steps will change at RTM. Some things to note:
1) install is using admin account (several of us just couldn't get ALL the features to work with separate service account in Beta) 2) we don't need loopback fix as all the sites are using specific ports instead of host headers.
Also, if you don't want to do a domain controller install, you could consider this route (http://bit.ly/4oAhpm), but my steps here may not work if you do.
Click
“Install Hyper-V Integration Services” in the autoplay
Click
“Ok” to upgrade/install
Click
“Yes” to restart
Login
to the server as administrator
Click
“Start->All Programs->Windows Update”
Click
“Turn on now”
Click
“Install now” to install latest windows update software
In the
“Server Manager” window that opens:
Click
“Configure Remote Desktop”
Click
“Allow connections from computers running any version…”
Click
“OK”
Click
“OK”
Click
“Configure IE ESC”
Click
“Off” for both administrators and users
Click
“OK”
Click
“Go to Windows Firewall”
Click
“Windows Firewall properties”
For
domain, private, public, set the firewall status to “Off”
Click
“OK”
Click
“Add Features”
Click
“SMTP server”
Click
“Add Required Role Services”
Click
“Next”
Click
“Next”
Click
“Install”
Click
“Close”
Run
Windows Update, get all critical updates
Click
“Install Updates”, install all updates
Click
“Restart Now”
Install
Microsoft Update
Run
Microsoft update, install any updates
Click
“Restart Now”
Install
Server 2008 Service Pack 2 (if it didn’t get installed from Microsoft
Update)
Restart
after install
Click
“Start”
Right
click “Computer”, select “Properties”
Under
computer name, click “Change settings”
For
description, type “sharepoint2010”
Click
“Change”
Set
the computer name to “sharepoint2010”
Click
“Ok”
Restart
the virtual machine
Run Windows
Update, get all critical updates
Click
“Install Updates”, install all updates
Click
“Restart Now”
At this point, keep your image as a
Windows Server 2008 base image!
Copy the base image sharepoint2010
vhd, rename to server2008sp2base and put in a safe place!
Open a
command prompt, run dcpromo, setup a domain called “contoso.corp”
Click
“Next”
Click
“Next”
Select
“Create a new domain…”
Click
“Next”
Enter
contoso.corp, click “Next”
Select
“Windows Server 2008”, click “Next”
Click
“Next”
Click
“Yes, the computer will use…”
Click
“Yes”
Click
“Next”
For
password, type “Pa$$w0rd”
Click
“Next”
Click
“Next”, active directory will setup itself up
Restart
the machine after AD is finished
At this point, keep your image as a
Windows Server 2008 base image!
Copy the base image sharepoint2010
vhd, rename to server2008sp2_AD and put in a safe place!
Create
the following domain users, set their password to “Pa$$w0rd” and that they
can’t change the password and the password doesn’t expire.
Click
“Start->Administrative Tools->Active Directory Users and Computers”
Expand
contoso.corp
Select
“Users”, right click and select “New->User”
For
name and user logon, type sp_system
Click
“Next”
For
Password, type “Pa$$w0rd”
Uncheck
“User must change…”
Check
“User cannot change password”
Check
“Password never expires”
Click
“Next”
Click
“Finish”
Install
SQL Server 2008 SP1 – If you don’t have slipstreamed sp1, install the
setup files for SP1, then install sql 2008, then the full SP1 (but you may
need the new Installer which is in the SQL 2008 base install/non-sp1).
Insert
the Server 2008 iso (with SP1)
Click
“installation”
Click
“New SQL Server standalone…”
On “Setup
Support Roles”, click “Ok”
On “Setup
Support Files”, click “Install”
Click
“Next”
On
product key, click “Next”
Click
“I accept the license terms”
Click
“Next”
Check
the following:
i. Database Engine
ii. SQL Server Replication
iii. Full-Text Search
iv. Analysis Services
v. Reporting Services
vi. Business Intelligence Development Studio
vii. Client Tools Connectivity
viii. Integration Services
ix. Client Tools Backward Compatibility
x. Management Tools – Basic
xi. Management Tools – Complete
xii. Microsoft Sync Framework
Click
“Next”
Click
“Next”
On
“Disk Space”, click “Next”
For
all accounts, type “contosoadministrator” and “Pa$$w0rd” for password
Click
“Next”
Click
“Mixed Mode” authentication radio button
For
password, type “Pa$$w0rd”
Click
“Add Current User”
Click
“Next”
Click
“Add Current User”
Click
“Next”
On
report Services, click “Install, but do not configure…” radio button
Open SQL Management Studio, make sure
your version is 10.00.2714 or later!
Open
SQL Server Management Studio, this is for the initial setup process to run
Open the SQL configuration manager Click “Start->All programs->Microsoft SQL Server 2008->Configuration Tools->Sql Server Configuration manager
Expand “SQL Server Network Configuration->Protocols for MSSQLSERVER”
Enable:
Named Pipes
TCP/IP
Restart the sql service
Install/attach
the demo databases (Northwind, pubs, adventureworks2000,
adventureworksDW).These can be
downloaded or installed from the instructor dvd.
i. Find and download, run AdventureWorksDBScripts.msi
ii. Open c:program filesmicrosoft sql
server100 oolsSamplesadventureworks data warehouseinstawdb.sql
iii. Run on sharepoint2007 (make sure you don’t get any
errors, if you do fix them – likely need to copy the .csv files to a directory)
iv. Open c:program filesmicrosoft sql
server100 oolsSamplesadventureworks OLTPinstawdb.sql
v. Run on sharepoint2007 (make sure you don’t get any
errors, if you do fix them – likely need to copy the .csv files and rename the
.mdf and .ldf to install the database)
Run Windows
Update, get all critical updates
Click
on all available updates
Click
“Ok”
Click
“Install Updates”
Click
“Restart Now”
At this point, keep your image as a
base image!
Copy the base image sharepoint2010 vhd,
rename to server2008sp2_sql2008sp1_cu and put in a safe place!
Install
“Office 2010”
Click
“I accept the terms…” check box
Click
“Continue”
Click
“Install Now”
Click
“Close”
Open
“Word 2010”
Click
“Use recommended settings”
Click
“Ok”
Open
Office Word 2010 to setup the initial settings
Install
“Visio 2010”
Enter
your product key
Click
“Continue”
Click
“I accept the terms…” check box
Click
“Continue”
Click
“Install Now”
Click
“Close”
Install
“Microsoft SharePoint Designer 2010”
Click
“I accept the terms…” check box
Click
“Continue”
Click
“Install Now”
Click
“Close”
Install
“Visual Studio 2010”
Insert
the iso into the image
Click
“Install Visual Studio 2010”
Click
“Next”
Click
“I have read and accept…”
Click
“Next”
Click
“Full”
Click
“Install”
When/if
prompted, restart, the install will start up again when rebooted
When/if
prompted, restart, the install will start up again when rebooted
Click
“Finish”, close the intaller
Open “Visual
Studio 2010”, select c# development settings
Copy the base image sharepoint2010
vhd, rename to server2008sp2_sql2008sp1_cu_vs2010 and put in a safe
place!
Install
“SharePoint 2010” Prereqs
NOTE: (BE SURE YOU ARE LOGGED IN AS
CONTOSOADMINISTATOR)
Insert
the DVD/start the install
Click
“Install Prerequisites”
i. NOTE: this
step will require internet access!
Click
“Next”
Click
“I accept the terms…”
Click
“Next”
i. All pre-reqs will be downloaded and installed (this
could take 45 minutes)
ii. Even on Server 2008, your setup may download SP2 for
Server 2008 and install, if it does, a reboot will be required.After reboot, continue the install via the
prompts
iii. Install will continue by installing application server
role and the other prereqs
Install
“SharePoint 2010” product
Click
“Install SharePoint Server”
Enter
your trial product key
i. PKXTJ-DCM9D-6MM3V-G86P8-MJ8CY
Click
“Continue”
Click
“I accept…”
Click
“Server Farm”
Select
“Complete…”
Click
“Install Now”
Click
“Close” (uncheck the run
configuration wizard)
Ensure proper permissions are
setup (these steps will fix the CryptographicException error):
Right click on the
folder ('%CommonProgramFiles%Microsoft SharedWeb Server Extensions14),
select “Properties”
Select “Security” tab
Click “Edit”
Click “Add”
For the user type
“Network Service”
Click “OK”
Grant the user Full
Control
Click “OK”
Click “OK”
At this point, keep your image as a
base image!
Copy the base image sharepoint2010
vhd, rename to server2008sp2_sql2008sp1_cu_vs2010_NoConfigure and put in
a safe place!
Ensure that ”Classic
Mode Authentication” is enabled
For Port, type “100”
Under Application
Pool, Select Create new Application Pool
For Name, type
“SharePoint – ALL”
For security account,
select “contosoadministrator”
For the database name,
change to “wss_content_100”
Click “Ok”, your web
application is being created:
i. NOTE: In
Production, you should always type a meaningful name for your content
databases!
Click the “Create Site
Collection” Link
For Title, type “My
Team Site”
For Template, Under
Collaboration select Team Site
For Primary Site
Collection administrator, type “Administrator”
Click “Ok”
Create the “Portal Site”
Click “Application
Management”
Click “Manage Web
Applications”
In the Ribbon, click
“New”
Ensure that ”Classic
Mode Authentication” is enabled
For Port, type “112”
Under Application
Pool, Select “Use Existing Application Pool”
For Name, type
“SharePoint – ALL”
For the database name,
change to “wss_content_112”
Click “Ok”, your web
application is being created:
Click the “Create Site
Collection” Link
For Title, type “My
Portal Site”
For Template, Under “Publishing”
select “Publishing Site”
For Primary Site
Collection administrator, type “Administrator”
Click “Ok”
Make
the quicklaunch bar horizontal and add the following items to quicklaunch
(you can do this by navigating to the respective program icon in the start
menu, right click, Add To Quick Launch)
SharePoint
Designer 2010
Visio
2010
Visual
Studio 2010
SQL
Server Management Studio
Visual
Studio Command Prompt
i. Available under start->Microsoft Visual Studio
2010->Visual Studio Tools->Visual Studio Command Prompt
A
Shortcut to the 14 hive
Enterprise library
console
Services
Applet
i. Available under Start->Administrative
Tools->Services
IIS
Manager
i. Available under Start->Administrative
Tools->Internet Information Services (IIS) Manager
SharePoint
Central Administration Console
i. Available under Start->Programs->Microsoft
SharePoint 2010 Products->SharePoint 2010 Central Administration
SharePoint
2010 management Shell
i. Available under Start->Programs->Microsoft
SharePoint 2010 Products->SharePoint 2010 Management Shell
Add C:Program
FilesCommon FilesMicrosoft Sharedweb server extensions14BIN to the
Path variable
Right
click My Computer, select “Properties”
Click
“Advanced system settings”
Click
“Environment variables”
Under
system variables section, click path, click Edit
Go
to the end of the string append, “;C:Program FilesCommon
FilesMicrosoft Sharedweb server extensions14BIN”
Uninstall
bad programs
Click
Start->Control Panel
Click
“Programs and features”
Uninstall
“Visual Studio 2010 Beta 2 Tools for SQL Server Compact ENU”
# Configure FAST Search Server to trust SharePoint Security Token Service certificate
Set-FASTSearchQRProxyMOSSConfiguration -STSThumbprint $sharepointSTSCert.Thumbprint -RestartServices true
Open the C:FASTSearchinQRProxyService.exe.config
Uncomment the following line
that starts with:
<!--<binding
name="HTTP_CLAIMS_INSECURE">...
Enable HTTPS searching by
running the following commands