Enable Anonymous Access in SharePoint 2010

 Its not difficult to configure anonymous access in MS SharePoint 2010. Not much different then SharePoint 2007 set up, the only difference is the GUI or the Ribbon.



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

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

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

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

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

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

7. Now, web application will allow anonymous access to be set.

 After Which , navigate to your top level site collection for the web application.

Click the Site Actions > Site Settings. Under Users and Permissions click Site permissions

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


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

Cannot add an existing SharePoint 2007 list to a Office Access 2007 database

One of my users had this issue .

The user was trying to add an existing list to a access 2007 db . and was getting an error .

Error : You do not have the necessary permissions to use the '<ListName>' object. Have your system administrator or the person who created this object establish the appropriate permissions for you .

After we did some research i found a KB article for the same .

http://support.microsoft.com/kb/924739

In this the Cause is mentioned as

This problem occurs because the Access 2007 database engine disallows columns that have names that contain more than 64 characters

To work around this problem, use only column names that contain less than 64 characters in Windows SharePoint Services lists

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section

Please check out the Steps to reproduce the problem in the KB article (link) provided.