Alternative to Disable Loop Back Check in SharePoint 2010

The Loop Back Check disables the server from calling itself by using its host name.  As an alternative to disabling loop back check,

Add a new "Multi-String Value" registry to the key "BackConnectionHostNames" HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\

Add hostnames (one per line).
 

FAST ESP - FSIS

I happened to troubleshoot an issue with "FAST ESP - FSIS" . The Syslog has been repeatedly logging the following warning msgs & the CTSFlows were running forever without any progress & no errors (kinda stuck there).

• Subsystem operation queue full (session xxx, ops yyyy->zzzz), sleeping xx seconds before resubmitting operation set... 
• session_status (235): Sparequeue too full for operation of size 53879040 from session id xxx
• api_queue: Apiqueue too full for operation of size 53879040 from session id xxx
• api_queue: The operation with session id xxx and size of 53879040 bytes is larger than the configured max api queue size of 52428800 bytes. Please reduce batch size or increase max api queue size for optimal performance.  

These information struck me to look & change API queue size and that lead me to these MSDN support articles

http://support.microsoft.com/kb/2017114
http://support.microsoft.com/kb/2535170 

Changes are :

1. %FASTSEARCH%\etc\config_data\RTSearch\webcluster\rtsearchrc.xml.
in Admin Server Only => Added  maxQueueSize="524288000" (in bytes, i.e 500 MB) to the <options...> node and save the file

2. Reload the configuration from the AdminServer Node: Syntax: nctrl reloadcfg

3. Restart of all indexer processes (in all the Nodes whereever "RTS Indexer" is configured and running).
Use "nctrl stop indexer" and "nctrl start indexer" from all indexer nodes or via the System Management tab in the ESP Admin GUI.

Following these changes, CTSFlow, and nodes all just started working.

   

Powershell Error : Get-SPSolution..The local farm is not accessible.

For a relatively new user who's just added to the farm, even if the user is a Farm Admin, receives one of the following errors especially when deploying a WSP:


"The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered."

followed by this error

"Get-SPSolution : Cannot access the local farm. Verify that the local farm is pr
operly configured, currently available, and that you have the appropriate permissions to access the database before trying again."

Resolution:

1. Login as the Farm Setup user 
2. Launch SP2010 Managementshell
3. Run ADD-SPSHELLADMIN -USERNAME domain\UsertobeAdmin

ASP.NET MVC 4 & Web API

ASP.NET MVC 4 & Web API

WCF Discovery Object Model & Announcements and Announcement Client

WCF Discovery Object Model The WCF discovery feature enables components to announce their availability. If configured to do so, a service sends Hello and Bye announcements. Clients or other components can listen for such announcement messages and act on them. : Discovery Announcements and Announcement Client

WCF Intermediaries with Binding Switching

WCF Intermediaries with Binding Switching

Message Security in WCF

Message Security in WCF