TwitterLinkedInBlog

Tuesday, October 19, 2010

FAST Search - Don't let the Byte Order Marks bite!

I recently ran into the situation described in this post:
The configuration wizard was failing on the non-admin nodes. In particular, I ran into checklist item 2, an invisible Byte Order Mark (BOM) at the beginning of the file. With the help of a friendly Microsoft engineer, I ran through the steps in checklist item 3 and the cmdlet, 'Set-FASTSearchIPSec -Create -Verbose', failed. This is described in the following kb article: http://support.microsoft.com/kb/2028971
It turned out that even though I was copying and pasting the deployment.xml using notepad to get rid of the BOM, it was the wrong copy of deployment.xml!
THE DEPLOYMENT.XML YOU MUST FIX IS LOCATED ON THE ADMIN NODE AT:
%FastSearch%\etc\config_data\deployment\deployment.xml
In order to see the BOM, or to verify that it’s gone, open the file in your favorite hex editor. I used HexEdit trial software. So think twice before using visual studio 2010 to author your FAST deployment.xml file. :)

FAST Search - Configuration Wizard Fails on Admin Node

We received the following error when attempting to run the configuration wizard on a FAST admin node (Edited for space):


StdError - resourcestoreinstaller.exe - C:\Windows\system32\inetsrv\appcmd.exe SET config "ResourceStore" /section:requestFiltering /verbs.allowUnlisted:false /commit:apphost - ERROR ( message:Unknown attribute "verbs.allowUnlisted".  Replace with -? for help. )

Exception - System.Management.Automation.RuntimeException: An error occurred while installing Resource store.


It turned out to be the number of processor on the admin node. There were 24. The limit is apparently 15. Once we reduced the number of processors to 4 in the bios, the configuration wizard completed successfully.

Tuesday, October 5, 2010

FAST Search - Failed to communicate with the WCF service

Problem: While attempting to run Get-FASTSearchMetadataCrawledProperty, I received the error, "Failed to communicate with the WCF service"

Solution: Added myself to FASTSearchAdministrators group, logged out, logged back in.

Reference: http://manish-sharepoint.blogspot.com/2010/01/wcf-service-error-while-executing.html

Monday, September 27, 2010

VS2010 - How to: Enable ECMA Client Object Model IntelliSense

http://msdn.microsoft.com/en-us/library/ff798328.aspx

<script src="/_layouts/MicrosoftAjax.js" type="text/javascript" />

<script src="/_layouts/SP.debug.js" type="text/javascript" />

<script type="text/javascript" src="/_layouts/SP.core.js" />

<script type="text/javascript" src="/_layouts/SP.UI.Dialog.js "/>

Friday, September 17, 2010

Todd Bleeker - Is that a SharePoint site?


SP2007:
http://[domain]/_layouts/images/CPVW.GIF
SP2010:
http://[domain]/_layouts/images/FGIMG.PNG

Tuesday, August 31, 2010

SP2010 - Share Link To Current Page

.aspx:
<asp:HyperLink ID="ShareHyperlink" runat="server" Text="Share" ToolTip="Share" />

function shareLinkInEmail(subject, body) {
var escapedSubject = escapeProperly(subject);
var escapedBody = escapeProperly(body);
window.location='mailto:?subject=' + escapedSubject + '&body=' + escapedBody;
}

c#:
ShareHyperlink.NavigateUrl = "javascript:shareLinkInEmail('Testing', 'Testing' + String.fromCharCode(13) + '" + Request.Url.Scheme + "://" + Request.Url.Host + ":" + Request.Url.Port + Request.RawUrl + "');";

Thursday, August 26, 2010

SP2010 - Sunil Yadav - Developer Dashboard

Copied and pasted directly from Sunil Yadav ...
http://www.sunilyadav.net/?tag=developer-dashboard-powershell
... because I'm tired of googling and finding outdated beta techniques.

The developer dashboard is the new feature addition to SPS 2010 diagnostics. The Developer dashboard provides detailed information such as components generating load on the system, code that executed on the page, query execution time, function by function level trace, WebPart load time etc.

Developer Dashboard Modes:
  1. On : Developer Dashboard is viewable on all pages that use the default master page.
  2. Off : Turns off the Developer Dashboard.
  3. OnDemand : Allows the user to toggle the Dashboard on and off.

The Developer Dashboard is disabled by default. One can enable the Developer Dashboard with the help of following methods.

1. Using STSADM.EXE
STSADM.exe -o setproperty -pn developer-dashboard -pv OnDemand

2. Using PowerShell
Open SharePoint 2010 Management Shell
Run following script on the Sharepoint 2010 Management Shell.
$devdashboard =[Microsoft.SharePoint.Administration.SPWebService]::ContentService.DeveloperDashboardSettings;
$devdashboard.DisplayLevel = 'OnDemand';
$devdashboard.Update()

3. Using Object Model
SPWebService service = SPWebService.ContentService;
service.DeveloperDashboardSettings.DisplayLevel=Microsoft.SharePoint.Administration.SPDeveloperDashboardLevel.OnDemand;
service.Update();