Microsoft Land

Archive for August 2011

If the search results are not appearing for Specific set of users and are visible to Administrators of the site, it could be configuration issue.  Also make sure that there are no fine grained permissions / target audience configured on the document libraries / lists which are stopping users from viewing the results.

Goto the Site Settings of the site which is Configured in the Search Service.  Under site administration -> Search and Offline Availability will be one of the Option.  In this page you will have the option to configure the Search settings for the Site.  Make sure “Always Index all webparts on ths site” is selected and “Allow site to appear in search results” is marked as “Yes”.

Once done, run a full crawl of the site and try the Search again.  Results will appear.

Analytics for Twitter is an useful freeware add-in based on PowerPivot and allows users to search Twitter and create dashboard views on Tweet statistics inside Excel 2010.  Users can use any combination of search terms, including #hashtags, @mentions, @users, and keywords to search Twitter using their documented APIs, perform comparative analysis on tweets, as well as depict the tone of the tweets using a customizable tone dictionary of terms.  The workbook comes with several sheets that provide insights into the query terms.

With this FREE add-in, you can:

  • Perform up to 5 parallel Twitter Searches (limited to 1500 results per query per day).
  • Drive ad-hoc analysis of tweets by day, by hour, by tweeters, by #hashtags and @mentions.
  • Customize your views (using slicers, DAX formulas or reference tables).
  • Setup Tone Dictionary

Analytics for Twitter works only with the latest versions of Microsoft Excel 2010 and of Microsoft® PowerPivot for Excel 2010.

Just wanted to Share a Script which will help in checking if the Logged in User belongs to a SharePoint user group and based on it disable some controls in editfrm.aspx on Custom List.  It uses JQUERY.

 ExecuteOrDelayUntilScriptLoaded(disableControls, “sp.js”);
function disableControls()
{
clientContext = new SP.ClientContext();
groupCollection = clientContext.get_web().get_siteGroups();
group = groupCollection.getById(21); //The ID of the SharePoint user group
users = group.get_users();
clientContext.load(group);
clientContext.load(users);
currentUser = clientContext.get_web().get_currentUser();
clientContext.load(currentUser);
clientContext.executeQueryAsync(Function.createDelegate(this,
this.onQuerySucceeded), Function.createDelegate(this,
this.onQueryFailed));
RefreshCommandUI();
}
function onQuerySucceeded()
{
if(users.get_count() >0)
{
UserExistInGroup = false;
for(var i=0; i < users.get_count(); i++)
{
if(users.itemAt(i).get_loginName() == this.currentUser.get_loginName())
{
UserExistInGroup = true;
break;
}
}
}
if (UserExistInGroup)
{
var p=$(‘input[title=Priority'); //Name of the columns that needs to be disabled
var i=$('input[title=Range]‘); //Name of the columns that needs to be disabled
$($(p)[0]).attr(‘disabled’,false);
$($(i)[0]).attr(‘disabled’,false);
}
else
{
var p=$(‘input[title=Priority');
var i=$('input[title=Range');
$($(p)[0]).attr(‘disabled’,true);
$($(i)[0]).attr(‘disabled’,true);
}
}
function onQueryFailed(sender, args)
{
var p=$(‘input[title=Priority');
var i=$('input[title=Range]‘);
$($(p)[0]).attr(‘disabled’,true);
$($(i)[0]).attr(‘disabled’,true);
}

We are having a .NET 4.0 Web Site which is using URL Routing.  This basically returns a structured XML which will be consumed by a Data Connection in Infopath form on Demand.

http://msdn.microsoft.com/en-us/magazine/dd347546.aspx

It starting throwing error all of a sudden and when enabled Failed Request Logging on IIS 7 it had below message.

Warning ModuleName=”ManagedPipelineHandler”, Notification=”EXECUTE_REQUEST_HANDLER”, HttpStatus=”400″, HttpReason=”Bad Request”, HttpSubStatus=”0″, ErrorCode=”The operation completed successfully

So initial thought was that we had some issue with the Routing mechanism but everything was great.  So later when debugging the same on DEV found that there is an internal error in Database Connection which throwed an error / which was not even getting logged because of the Log size.

Some error messages are quite confusing, better not to trust them and follow by what they say. Saves time.


My Tweets

Error: Twitter did not respond. Please wait a few minutes and refresh this page.

Follow

Get every new post delivered to your Inbox.

Join 119 other followers