Link for several sharepoint problem and solution
Monday, April 25, 2011 | Author: vrey
Answer: SharePoint 2010 Timer Service keep failing
http://social.technet.microsoft.com/Forums/en/sharepoint2010setup/thread/10564f92-edc8-4bdf-929d-1fed015b6b00
Supported by: Fix the SharePoint DCOM 10016 error on Windows Server 2008 R2
http://www.wictorwilen.se/Post/Fix-the-SharePoint-DCOM-10016-error-on-Windows-Server-2008-R2.aspx

Events: 3351
SQL database login for 'SharePoint_Config' on instance '[DBServer]' failed. Additional error information from SQL Server is included below.
Login failed for user '[Domain]\[MachineName]$'.
Solution: http://technet.microsoft.com/en-us/library/ee662513.aspx
Just add '[Domain]\[MachineName]$' to your SQL Logins. Do not forget to add this login to all database you have on [DBServer] (optional, you can just add to several DB, based on Windows Error Log).

Error:An object of the type Microsoft.SharePoint.Administration.SPWindowsServiceCredentialDeploymentJobDefinition named "windows-service-credentials-FIMSynchronizationService" already exists under the parent Microsoft.Office.Server.Administration.ProfileSynchronizationService named "FIMSynchronizationService".  Rename your object or delete the existing object.
Solution: Suddenly appear on Monitoring, Check Job Status, Delete "windows-service-credentials-FIMSynchronizationService"

Warning: Object Cache: The super user account utilized by the cache is not configured. This can increase the number of cache misses, which causes the page requests to consume unneccesary system resources.
To configure the account use the following command 'stsadm -o setproperty -propertyname portalsuperuseraccount -propertyvalue account -url webappurl'. The account should be any account that has Full Control access to the SharePoint databases but is not an application pool account.
 Additional Data:
 Current default super user account: SHAREPOINT\system
Solution: http://technet.microsoft.com/en-us/library/ff758656.aspx
I'm using [Domain]\[MachineName]$ as a portalsuperuseraccount

Error 5555:
Failure trying to synch web application 8c314f31-dec1-41dc-844b-73f894c33f03, ContentDB 705970e4-7422-41b8-ae42-c2e58da27848  Exception message was Microsoft.Office.Server.UserProfiles.UserProfileApplicationNotAvailableException: No User Profile
Solution:http://social.technet.microsoft.com/Forums/en/sharepoint2010setup/thread/ff3b7ecc-ae43-4c64-8745-4beb28f92c39

How to grant the "Replicating Directory Changes" permission for the Microsoft Metadirectory Services ADMA service account
http://support.microsoft.com/kb/303972

Problem: Managed Metadata Service – The required feature is not enabled for this column type
Solution: stsadm -o activatefeature -id 73EF14B1-13A9-416b-A9B5-ECECA2B0604C -url http://
This will activate the required feature.
Using Cmdlet with Powershell 2010
Tuesday, April 19, 2011 | Author: vrey
get-spserviceinstance | where-object { $_.typename -match "user*" }
get-spserviceinstance | select-object typename, status
get-spfeature | where-object { $_.displayname -match "custom*" }

add-spsolution -literalpath C:\customfeature.wsp
stsadm -o deploysolution -name customfeature.wsp -immediate -allowgacdeployment -url http://sharepoint:123

stsadm -o enumsolutions
stsadm -o retractsolution -name customfeature.wsp -url http://sharepoint:123 -immediate
stsadm -o execadmsvcjobs
stsadm -o deletesolution -name customfeature.wsp -override
stsadm -o canceldeployment -id 41db30bc-e54a-4791-91b5-df20d64f701f
stsadm -o deactivatefeature -name monthlyblogpost -url http://sharepoint:123
Failed to find the XML file at location '14\Template\Features\customfeature\feature.xml' -> here is the location where the feature is installed
uninstall-spfeature -id 4a33037a-23bb-42c5-b494-ee54eaadb212

Built Result:
Active Deployment Configuration: Default
Run Pre-Deployment Command:
Skipping deployment step because a pre-deployment command is not specified.
Recycle IIS Application Pool:
Recycling IIS application pool 'SharePoint - 123'...
Retract Solution:
Deactivating feature 'CustomFeature_Feature1' ...
Retracting solution 'CustomFeature.wsp'...
Deleting solution 'CustomFeature.wsp'...
Add Solution:
Found 1 deployment conflict(s). Resolving conflicts ...
Deleted file 'http://sharepoint:123/_catalogs/wp/CustomFeature_VisualWebPart1.webpart' from server.
Adding solution 'CustomFeature.wsp'...
Deploying solution 'CustomFeature.wsp'...
Activate Features:
Activating feature 'CustomFeature' ...
Run Post-Deployment Command:
Skipping deployment step because a post-deployment command is not specified.
========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========
========== Deploy: 1 succeeded, 0 failed, 0 skipped ==========

Source: Steps To Install WSP file in STSADM
Enable Anonymous Access in SharePoint 2010
Sunday, April 17, 2011 | Author: vrey
Here are 8 simple steps on how to set up anonymous access in MS SharePoint 2010. It is not much different then SharePoint 2007 set up, the only difference is the GUI or the Ribbon.

 

1. Starting in Central Administration, under Application Management, click on the Manage web applications.

 

Anonymous Access Set Up Step 1

2. Make sure you select the site you want to enable anonymous access and click on the Authentication Providers icon.

Anonymous Access Set Up Step 2

3. On the Authentication Providers pop-up window click on the Default zone.

Anonymous Access Set Up Step 3


4. Under Edit Authentication, check Enable anonymous access and click Save.

Anonymous Access Set Up Step 4

5. Going back to Web Application Management click on the Anonymous Policy icon.

Anonymous Access Set Up Step 5

6. Under Anonymous Access Restrictions select your Zone and set the Permissions to None – No policy and click Save.

Anonymous Access Set Up Step 6

7. Now, web application will allow anonymous access to be set. So, navigate to your top level site collection for the web application. Click the Site Actions > Site Settings. Under Users and Permissions click Site permissions.

Anonymous Access Set Up Step 7

8. Under Permission Tools, click Anonymous Access icon and set the permissions to Entire Web site and click OK.

Anonymous Access Set Up Step 8


Anonymous Access Set Up Step 8

Anonymous Access Set Up

That’s all, folks! If you followed these steps properly you should have now Anonymous Access enabled.


Source: Enable Anonymous Access in SharePoint 2010

Error Message when checking names: Name does not resolve and following error displayed:



No exact match was found. Click the item(s) that did not resolve for more options.


Using People Picker displays this error:





In Event Log you will see the error below.

If you look events that occurred just before the event 8307 An exception occurred in All Users claim provider when calling SPClaimProvider.FillHierarchy() you will notice few Alternate Access Mapping Errors (event id: 8059). They seems to be irrelevant but that’s exactly the cause. You are missing AAM mapping that user is using to access the site where name resolution was attempted. There might be million other reasons for error you chasing but try this first and make sure you have AAM configured. Note, batteries not included and reboot or IIS reset not required for AAM updated to take effect


Log Name:      Application
Source:        Microsoft-SharePoint Products-SharePoint Foundation
Date:          1/29/2011 7:33:36 PM
Event ID:      8307
Task Category: Claims Authentication
Level:         Error
Keywords:      
User:          Domain\loginID
Computer:      serverName.domain.com
Description: An exception occurred in All Users claim provider when calling SPClaimProvider.FillHierarchy(): Object reference not set to an instance of an object..

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-SharePoint Products-SharePoint Foundation" Guid="{6FB7E0CD-52E7-47DD-997A-241563931FC2}" />
    <EventID>8307</EventID>
    <Version>14</Version>
    <Level>2</Level>
    <Task>47</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2011-01-30T00:33:36.620650000Z" />
    <EventRecordID>51361</EventRecordID>
    <Correlation ActivityID="{C8CF965E-3F41-490C-9D96-75EA8F84BE3E}" />
    <Execution ProcessID="3076" ThreadID="4888" />
    <Channel>Application</Channel>
    <Computer><serverName.domain.com></Computer>
    <Security UserID="<SID of the user who experienced the error>" />
  </System>
<EventData>
    <Data Name="string0">All Users</Data>
    <Data Name="string1">SPClaimProvider.FillHierarchy()</Data>
    <Data Name="string2">Object reference not set to an instance of an object.</Data>
</EventData>
</Event>
How to get User Data from the Active Directory
Sunday, April 03, 2011 | Author: vrey

Introduction

Last month the project manager asked me write to find all users information from the Active directory and which all fields are missing information for particular user. I was trying to search in Internet for information about .NET Active Directory examples, I could not able to find much information on the net, it prompted me write an article on this topic.
In this article, I will explain how to use Active Directory class and retrieve data from the component classes. You can cut and past below code lines and execute it but you need to pass domain name in Directory Entry constructor. Following example taken from one of my developed projects and modified for easy to understand.
I assumed that you have a general understanding of active directory before using this example.

Step 1:

Add System.DirectoryServices.Dll (from Project Add reference)
System.DirectoryServices provides easy access to active directory from managed code. This namespace contains two components classes, DirectoryEntry and DirectorySearcher.

Step 2:

Using System.DirectoryServices
Directory Entry Class: this class encapsulates a node or object in the active directory hierarchy. Use this class for binding to objects, reading properties and updating attributes.

Step 3:

DirectoryEntry entry = new DirectoryEntry("LDAP://DomainName");
Directory Searcher: It will perform queries against the active directory hierarchy

Step 4:

DirectorySearcher dSearch = new DirectorySearcher(entry);

Step 5:

String Name="Richmond";
The Filter property supports for the all filter the information of the active directory.
// l = city name

Step 6:

dSearch.Filter = "(&(objectClass=user)(l=" + Name + "))";
Executes the search and returns a collection of the entries that are found.

Step 7:

This function checks active directory field is valid or not. Add this member function to you class.
Public static string GetProperty(SearchResult searchResult, 
 string PropertyName)
  {
   if(searchResult.Properties.Contains(PropertyName))
   {
    return searchResult.Properties[PropertyName][0].ToString() ;
   }
   else
   {
    return string.Empty;
   }
  }

Step 8:

// get all entries from the active directory.
// Last Name, name, initial, homepostaladdress, title, company etc..
 foreach(SearchResult sResultSet in dSearch.FindAll())
    {
          
     // Login Name
     Console.WriteLine(GetProperty(sResultSet,"cn"));
     // First Name
     Console.WriteLine(GetProperty(sResultSet,"givenName"));
     // Middle Initials
     Console.Write(GetProperty(sResultSet,"initials"));
     // Last Name
     Console.Write(GetProperty(sResultSet,"sn"));
     // Address
 string tempAddress=GetProperty(sResultSet,"homePostalAddress");

     if(tempAddress !=string.Empty)
     {
          string[] addressArray = tempAddress.Split(';');
      string taddr1,taddr2;
      taddr1=addressArray[0];
      Console.Write(taddr1);
      taddr2=addressArray[1];
      Console.Write(taddr2);
     }
     // title
     Console.Write(GetProperty(sResultSet,"title"));
     // company
     Console.Write(GetProperty(sResultSet,"company"));
     //state
     Console.Write(GetProperty(sResultSet,"st"));
     //city
     Console.Write(GetProperty(sResultSet,"l"));
     //country
     Console.Write(GetProperty(sResultSet,"co"));
     //postal code
     Console.Write(GetProperty(sResultSet,"postalCode"));
     // telephonenumber
     Console.Write(GetProperty(sResultSet,"telephoneNumber"));
     //extention
     Console.Write(GetProperty(sResultSet,"otherTelephone"));
    //fax
     Console.Write(GetProperty(sResultSet,"facsimileTelephoneNumber"));
 
    // email address
     Console.Write(GetProperty(sResultSet,"mail"));
     // Challenge Question
     Console.Write(GetProperty(sResultSet,"extensionAttribute1"));
     // Challenge Response
     Console.Write(GetProperty(sResultSet,"extensionAttribute2"));
     //Member Company
     Console.Write(GetProperty(sResultSet,"extensionAttribute3"));
     // Company Relation ship Exits
     Console.Write(GetProperty(sResultSet,"extensionAttribute4"));
     //status
     Console.Write(GetProperty(sResultSet,"extensionAttribute5"));
          // Assigned Sales Person
     Console.Write(GetProperty(sResultSet,"extensionAttribute6"));
     // Accept T and C
     Console.Write(GetProperty(sResultSet,"extensionAttribute7"));
     // jobs
     Console.Write(GetProperty(sResultSet,"extensionAttribute8"));
   String tEmail = GetProperty(sResultSet,"extensionAttribute9");
 
     // email over night
   if(tEmail!=string.Empty)
   {
      string em1,em2,em3;
    string[] emailArray = tEmail.Split(';');
      em1=emailArray[0];
      em2=emailArray[1];
      em3=emailArray[2];
      Console.Write(em1+em2+em3);
      
   }
     // email daily emerging market
     Console.Write(GetProperty(sResultSet,"extensionAttribute10"));
     // email daily corporate market
   Console.Write(GetProperty(sResultSet,"extensionAttribute11"));
     // AssetMgt Range
     Console.Write(GetProperty(sResultSet,"extensionAttribute12"));
     // date of account created
     Console.Write(GetProperty(sResultSet,"whenCreated"));
   // date of account changed
     Console.Write(GetProperty(sResultSet,"whenChanged"));
}

Step 9:

This step is optional, you can replace code inside foreach with this code below.
if (sResultSet != null)  
{  
    // user exists, cycle through LDAP fields (cn, telephonenumber etc.)  
    ResultPropertyCollection fields = sResultSet.Properties;
    foreach (String ldapField in fields.PropertyNames)  
    {  
        // cycle through objects in each field e.g. group membership  
        // (for many fields there will only be one object such as name)  
   
        foreach (Object myCollection in fields[ldapField])   
           Console.WriteLine(String.Format("{0,-20} : {1}",   
                    ldapField, myCollection.ToString()));  
    }  
} 

You can see properties in Active Directory in ADSearch User Property Attributes

Source: How to get User Data from the Active Directory - CodeProject and
Querying and Updating Active Directory Using C# (C Sharp) and
.Net Directory Services Programming - C# - Part 3
I was recently attempting to add a new managed metadata type site column to an existing SharePoint 2010 site collection but when I tried to select a term set I saw the following error:
The required feature is not enabled for this column type
This had me a little confused.  I checked all of the features against another SharePoint 2010 server that was working as expected and everything appeared to be the same.
A search on Google revealed that there are actually some features that are not listed in the site features or site collection features that can (somehow) become disabled and will then need to be manually activated using STSADM.
STSADM -o activatefeature -id 73EF14B1-13A9-416B-A9B5-ECECA2B0604C -url http://sitecollection -force
These links were very helpful:
http://dotneteers.net/blogs/aghy/archive/2010/03/14/activating-managed-metadata-feature-on-your-web-application-in-sharepoint-2010.aspx
http://jasonlochan.blogspot.com/2010/04/managed-metadata-service-required.html
http://www.sharepoint4developers.net/en-nz/post/required-feature-metadata-column.aspx