23 August, 2012

Need to disable word breaker in the SharePoint 2010 search engine

A word breaker is a component that is used to break strings of text into individual words during the indexing and querying processes. During the indexing process, text is extracted from content items as an unbroken string of characters. Word breakers reestablish where each word in the string of characters begins and ends. Additionally, word breakers separate compound words so that users receive a query result on a portion of the original compound word and also on the individual terms that compose the compound word. Word breakers also convert numbers and dates from content items into a standard form.

Each language has a different word breaker. The indexing engine determines which word breaker to use and, if more than one language is detected, can use more than one word breaker for text that comes from a single document. If a word breaker does not exist for a particular language, the neutral word breaker is used.

Problem Description:
Need to disable word breaker in the SharePoint 2010 search engine.

Note: No such OOB feature available in SPS 2010

1)   On the SharePoint Server(s) open Registry Editor (Start -> type “Regedit” and hit enter).
2)   Point to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\14.0\Search\Setup\ContentIndexCommon\LanguageResources\Default\Swedish
3)   Rename string WBreakerClass to e.g.: WBreakerClassOLD, WBreakerClassSWE or any other name which will remind you of the original string.
4)   Point to Edit -> New -> String Value and name it; WBreakerClass
5)   Double click this string and paste {9DAA54E8-CD95-4107-8E7F-BA3F24732D95} as Value data and click OK
6)   Close the Registry Editor
7)   Point to Start -> Administrative Tools -> Services
8)   Right click on SharePoint Server Search 14 and click on Restart
9)   Close the Services window

v  Open Central Admin and point to:
§  General Application Settings
§  Farm Search Administration
§  open the Search Service Application
§  click Content Sources from the left navigation menu

10. Click on the content source and hit Start Full Crawl
11. Wait for the Full Crawl to complete and try searching again.

You can always revert to old search behavior by renaming the string WBreakerClass to WBreakerClassOLD (or just delete it) and rename the original WBreakerClassSWE back to WBreakerClass.
Of course you have to repeat step 6 to 9.

Authentication vs. Authorization: A gereral Tip.

It is easy to confuse the mechanism of authentication with that of authorization. In many host-based systems (and even some client/server systems), the two mechanisms are performed by the same physical hardware and, in some cases, the same software.

It is important to draw the distinction between these two mechanisms, however, since they can (and, one might argue, should) be performed by separate systems.

What, then, distinguishes these two mechanisms from one another?
Authentication is the mechanism whereby systems may securely identify their users. Authentication systems provide an answers to the questions:
  • Who is the user?
  • Is the user really who he/she represents himself to be?
An authentication system may be as simple (and insecure) as a plain-text password challenging system (as found in some older PC-based FTP servers) or as complicated as the Kerberos system described elsewhere in these documents. In all cases, however, authentication systems depend on some unique bit of information known (or available) only to the individual being authenticated and the authentication system -- a shared secret. Such information may be a classical password, some physical property of the individual (fingerprint, retinal vascularization pattern, etc.), or some derived data (as in the case of so-called smartcard systems). In order to verify the identity of a user, the authenticating system typically challenges the user to provide his unique information (his password, fingerprint, etc.) -- if the authenticating system can verify that the shared secret was presented correctly, the user is considered authenticated.

Authorization, by contrast, is the mechanism by which a system determines what level of access a particular authenticated user should have to secured resources controlled by the system. For example, a database management system might be designed so as to provide certain specified individuals with the ability to retrieve information from a database but not the ability to change data stored in the datbase, while giving other individuals the ability to change data. Authorization systems provide answers to the questions:
  • Is user X authorized to access resource R?
  • Is user X authorized to perform operation P?
  • Is user X authorized to perform operation P on resource R?
Authentication and authorization are somewhat tightly-coupled mechanisms -- authorization systems depend on secure authentication systems to ensure that users are who they claim to be and thus prevent unauthorized users from gaining access to secured resources.

Service Applications in SharePoint 2010: Continued:

Readers as promised with all of you, I am writing up in continuation with my previous article of the Services Applications in SharePoint 2010.

Microsoft SharePoint Server 2010 includes a set of service applications that you can use to share services across Web applications. In some cases, you can also share service applications across farms. You can manage service applications by using Central Administration or by using Windows PowerShell 2.0.

Below are the details on the Service Applications and the detailed study link for them.

Service application references:

Access Services:
Access Services in Microsoft SharePoint Server 2010 is a service that allows users to publish an Microsoft Access 2010 Web database to a SharePoint site. When an Access Web database is published to SharePoint Server 2010, a site is created to host the Web database, plus it moves all of the database objects and data to a SharePoint list on that site.
Access Services administration:

Business Data Connectivity:

Microsoft Business Connectivity Services are administered primarily by using the Business Data Connectivity service. Administrators of Business Data Connectivity service applications can perform operations on the source of data for those applications to maintain security and ensure appropriate access to data.
Business Data Connectivity service administration (SharePoint Server 2010):

Document Conversion:
Microsoft SharePoint Server 2010 supports installing document converters on the server that let users transform documents from one format to another.

Conversions can be run either from the user interface or programmatically, such as from a custom workflow. The relationship between a source document and its transformed counterpart is maintained.
Manage document conversions (SharePoint Server 2010):

Excel Services:
Excel Services in Microsoft SharePoint Server 2010 provides several methods to extend the capabilities of Excel Calculation Services, customize applications and workbooks, and also allow developers to incorporate Excel Services into their solutions.Excel Services in Microsoft SharePoint Server 2010 provides the ability to connect to external data sources and refresh this data.Excel Services administration (SharePoint Server 2010)

Managed Metadata Service:
Managed metadata is a hierarchical collection of centrally managed terms that you can define and then use as attributes for items in Microsoft SharePoint Server 2010.
Managed metadata administration (SharePoint Server 2010)

To use PerformancePoint Services in Microsoft SharePoint Server 2010, you must configure a PerformancePoint Services service application. Once you have created the service application, you must provide data access to the users. This can be done by using the unattended service account, or by configuring Kerberos delegation.
PerformancePoint Services administration (SharePoint Server 2010)

Search ServiceEnterprise search administration (SharePoint Server 2010)

Secure Store:
In Microsoft SharePoint Server 2010, the Secure Store Service replaces the single sign-on (SSO) feature of Microsoft Office SharePoint Server 2007. The Secure Store Service is a claims-aware authorization service that includes a secure database for storing credentials.The Secure Store Service is an authorization service that runs on an application server. The Secure Store Service provides a database that is used to store credentials. These credentials usually consist of a user identity and password, but can also contain other fields that you define. For example, SharePoint Server 2010 can use the secure store database to store and retrieve credentials for access to external data sources. The Secure Store Service provides support for storing multiple sets of credentials for multiple back-end systems.Configure the Secure Store Service (SharePoint Server 2010)

State Service:

State Service is a shared service that is used by some Microsoft SharePoint Server 2010 components to store temporary data across related HTTP requests in a SQL Server database. In SharePoint Server 2010, the State Service is required by InfoPath Forms Services (including out of the box and custom workflow forms), the SharePoint Server 2010 Chart Web Part, and certain Microsoft Visio 2010 scenarios that do not use Microsoft Silverlight 3.Manage the State Service (SharePoint Server 2010)

Visio Graphics Service:

The Visio Graphics Service is a Microsoft SharePoint Server 2010 service application that allows users to share and view Visio web drawings using Visio Services. The service application also enables data-connected Microsoft Visio 2010 web drawings to be refreshed and updated from different data sources.Visio Graphics Service administration (SharePoint Server 2010):

User Profile Service:

User Profile Service is a shared service in Microsoft SharePoint Server 2010 that enables the creation and management of user profiles that can be accessed from multiple sites and farms. Administration of User Profile Service applications is much simpler in SharePoint Server 2010 and can be delegated to a service application administrator by the farm administrator.User Profile Service administration (SharePoint Server 2010):http://technet.microsoft.com/en-us/library/ee721050.aspx

Word cannot publish this post

Posts are an essential part of a blog. They are typically journal-like entries that contain information, ideas, and opinions. They are displayed in chronological order, starting with the most recent posts.

You can create a post on a SharePoint blog by using a Web browser, if you have permission to contribute to the Posts list. You don't need additional tools or programs to create content, add pictures, apply formatting, and insert hyperlinks. To post comments to a blog, you must have permission to contribute to the Comments list. In some cases, comments must be approved before they will appear on the site.

Problem Description:
User attempts to publish the Blog post from Word 2010 to SharePoint Blog it fails with following error message  

Word cannot publish this post

To verify the error message that you receive, press Ctrl+Shift+I. The following number is displayed in the lower-right corner of the error message dialog box:


Probable Cause:
The error is due to Document opened in Compatibility Mode (.doc) format the .doc format disables the features required to publish the Document to Blog Site. While reviewing Blog Template in Word 2010 noticed some of the options were grayed out. Example: Home Page, Insert Category, Open Existing Icon. 

Following settings were configured in User workstation:   

1.   File | Options | Save | Save Files in this format | Word 97 – 2003 Document Format (*.doc)
2.   File | Options | Advanced | Scroll to Compatibility Options | Lay out this document as if created in Microsoft Word 2003

This is working as designed and to work around the issue user needs to switch the document format (*.docx).

If you have any queries/questions regarding the above mentioned information then please let me know.
I would be more than happy to help you as well as resolves your issues J Thank you.

Description of the Office 2010 hotfix package (Mso-x-none.msp): June 26, 2012

Issues that this hotfix package fixes

1.   When you open a protected workbook from a Microsoft SharePoint 2007 site in Microsoft Excel 2010, Excel 2010 crashes.

2.   Assume that you try to insert a picture into Microsoft Word 2010, Excel 2010 or Microsoft PowerPoint 2010 by using a URL on a computer that is running Windows XP. The URL contains the characters "_vti_bin" or "_layouts". In this situation, these characters are replaced with the characters "_sharedtemplates".
For example, assume that you open a Word 2010 document on a computer that is running Windows XP. You try to insert a picture by using a URL such as http://server/_vti_bin or http://server/_layouts. In this situation, the URL is changed to http://server/_sharedtemplates.

3.   Assume that you have a macro in Word 2010 that saves a Word document to a SharePoint library and then checks out the document.  In this situation, you receive the following error message:
6092: This document cannot be checked out.

When you try to apply a Digital Rights Management (DRM) template to restrict permissions for an Office 2010 file in an Active Directory Rights Management Services (AD RMS) environment, you receive the following error message:

An unexpected error has occurred while trying to restrict permission to your document. Contact your administrator for assistance.

This issue occurs when the following conditions are true:
·         The hotfix described in Microsoft Knowledge Base (KB) article 2584066 is installed on the computer.
·         The text ":443" appears in the URL of the service connection point (SCP) for AD RMS.

4.   2687278: (http://support.microsoft.com/kb/2687278/ )
64-bit edition of Office 2010 does not import images from TWAIN devices

22 August, 2012

blocked file types in SharePoint Server 2010

Listed below are all file types that are blocked by default.
Microsoft Access project extension
Microsoft Access project
Application file
ASP declarations file
ASP.NET Web handler file. Web handlers are software modules that handle raw HTTP requests received by ASP.NET.
ASP.NET Web Services source file
Active Server Pages
Microsoft Visual Basic class module
Batch file
Compound index
Certificate file
Compiled HTML Help file
Java class file
Microsoft Windows NT command script
Microsoft MS-DOS program
Configuration file
Control Panel extension
Security certificate
Script file
Windows dynamic-link library
Microsoft Visual FoxPro compiled program
Help file
HTML program
Script file
HTML document
Internet Information Services file
Internet database connector file
Internet data query file
Internet Naming Service
Internet Communication settings
Internet Document Set file
JScript Encoded script file
Korn Shell script file
Microsoft Access stored procedure
Microsoft Access add-in program
Microsoft Access program
Microsoft Access MDE database
Microsoft Access data file
Microsoft Access workgroup
Microsoft Access wizard program
Microsoft Common Console document
Microsoft Agent script helper
Microsoft Agent script helper
Microsoft Agent script helper
Microsoft Agent script helper
Microsoft Agent script helper
Microsoft Agent script helper
Microsoft Windows Installer package
Windows Installer patch package file
Visual Test source files
Microsoft Office profile settings file
Photo CD image or Microsoft Visual Test compiled script
Shortcut to MS-DOS program
System file
Program source file
Printer file
Microsoft Outlook personal folder file
Registration entries
ACT! database maintenance file
Windows Explorer command file
Screen saver
Script file
Windows shortcut
Shell Scrap object
HTML file that contains server-side directives
HTML file that contains server-side directives
Simple Object Access Protocol file
HTML file that contains server-side directives
Uniform Resource Locator (Internet shortcut)
Microsoft Visual Basic Scripting Edition (VBScript) file
VBScript Encoded Script file
VBScript file
Windows Script file
Windows Script Component
Windows Script file
Windows Script Host settings file