Cannot browse to All People in SharePoint 2010

We used to normally visit All people in Sharepoint 2007 to Delete the user from the Site collection :)

Where is it in Sharepoint 2010 ?

The “All People” view is the best way to list out all the users having access to the SharePoint site.

When a admin navigates to the “People and Groups” section in a SharePoint 2007 site,

he sees a link called “All People” in the left hand navigation.

Clicking on this link brings up a view of all the users across all the groups in the site.

But this “All People” view is hidden in SharePoint 2010 and the link is also missing in the “People and Groups” section.

However one can still navigate to this view in a SharePoint 2010 by following the below mentioned steps :

 

• Navigate to the “People and Groups” section.
• Click on any of the groups.
• Locate the “MembershipGroupId” query string parameter from Url in the address bar
• Replace the value in the “MembershipGroupId” query string parameter with 0.
• Reload the page and it will populate the “All People” View.

Code blocks are not allowed in this file SharePoint 2010

Hello Everybody,

Today I worked on one critical issue which belongs to our development environment. We have migrated one web application from production environment to development for testing purpose. Migration has been successful but we were facing an exception while browsing the web application.

Error Message:

An error occurred during the processing.

Code blocks are not allowed

Troubleshoot issues with Microsoft SharePoint Foundation.

Server Configuration:

·         2 SharePoint Servers

·         SQL server 2008 R 2

·         Windows Server 2008 R2

·         SharePoint Version: SP2010

Troubleshooting done:

1.    Tried accessing the system pages i.e. settings.aspx, viewlsts.aspx etc. every system was opening fine without any issues. So the issue is with the home page only…

2.    Tried accessing the web part maintenance page, it opened without any issues. We closed the webparts which are present on the home page-just to make sure that there is no problem with the existing webparts. Checked the home page again but same issue.

3.    Tried changing the master page as were able to open the system pages (by appending _layouts/changesitemasterpage.aspx). We changed to different one as we are using custom master page. Checked the results again but same problem.

4.    Opened the site in SharePoint Designer 2010 and checked the status of master page as well as the home page. It was fine and without customization too.

Note: if you see any of these pages in customizable state then I would suggest you to take the backup and try ‘reset to site definition” option.

Obviously, next question will arise- what exactly it will do? Yes, it will reset your page to default state. It means you will lose your customizations. But issue will be resolved and you can customize the page again as per your requirements.

5.    Checked the windows application as well as SP logs (Location: \14\Logs). I would suggest you to analyze these logs before continuing your troubleshooting.

What is my observation\Understanding?

·         Code blocks are only processed for custom pages deployed in the root virtual directory of a site if the code it considered safe.

·         This code is considered safe only if the page is served directly from the file system. As soon as it becomes unghosted for any reason, the code is no longer considered safe and the error shown in the symptom occurs.

Resolution:

As our production web application was working without any issues so I compared the web.config of both the applications. Analyze the code line by line with the production web.config and that’s it. I found the one which was missing in the web.config that belongs to my development web application.

Note: I would suggest you to take a proper backup before making any changes in the web.config file.

What I did? What kind of entries I added in the web.config file?

Here we go:-

In you web.config, you need to search the tag name as “<PageParserPaths>”

Once you find that then make the following  entry:

<PageParserPaths>

    <PageParserPath VirtualPath="/apps/*" CompilationMode="Always"

              AllowServerSideScript="true" IncludeSubFolders="true" />

</PageParserPaths>

After adding this entry then IISRESET is mandatory.

Tried accessing the site and the issue has been resolved.

Happy SharePoint once again…

If you have any queries/questions regarding the above mentioned information then please let me know, Thank you.

Excel Cannot Connect to SharePoint List

One interesting issue that i came accross today .

The user had created a list .

When he selects list Actions => Export to spreadsheet

Excel opens up and Displays 'Security' dialog box by giving the option of 'ENABLE' and 'DISABLE'.

User Clicks on the Enable button then we get the 'Import Data' dialog box , and then he clicks OK.

As soon as he clicks the OK button  an error message comes up Excel Cannot Connect to SharePoint List or at times it may also happen that you may receive the following error : Cannot connect to the server at this time. Changes to you Data cannot be saved.

I researched and found a solution to the issue shared by one of my friend

http://sharepointknowledgebase.blogspot.in/2011/06/excel-cannot-connect-to-sharepoint-list.html

It says :

 Generally we start our troubleshooting from the SharePoint side as what is wrong with my SharePoint site, Is there any problem in the SharePoint list, Does the Office which is installed on the machine is causing the problem ? Is there any site collection feature turned off? Is there any problem in the SP-Database? Problem with the IIS? so things are there by which we can think off but don't waste your time in doing all these things as I have done all these things and the resolution is quite simple which you can implement without any help.

1. Open the Internet Explorer
2. Tools
3. Internet Options
4. Advanced Settings
5. Scroll downwards and reach towards the section named as "Security"
6. CHECK FOR SERVER CERTIFICATE REVOCATION--which is by default checked
7. Unchecked it
8. Apply and Ok
9. Close all the internet explorers (IE) and open your SharePoint site in a new IE i.e. Browser/Explorer
10. You should be able to export the spreadsheet without any problems/issues.
Thanks to Amol Ghuge .

Site Collection Quotas

When you set a quota limit for storage, you can set two values: a warning value and a maximum value. When a site collection passes the warning limit, an e-mail message is sent to the site administrator and owner notifying them that their site collection is near to their storage quota. E-mail messages are sent daily until the storage level drops below the warning level. When a site collection meets the maximum limit, another e-mail message is sent to the owner and administrator, and no new content can be added to the site collection.

There are 2 important questions based on site quotas, such as:

How to manage quota template?

How to Change an existing quota template?

Let’s see and understand the complete process:

How to create a quota template

1.   Click Start, point to All Programs, point to Administrative Tools, and then click SharePoint Central Administration.

2.   On the Central Administration page, under Component Configuration, click Manage quotas and locks.

3.   On the Manage Quotas and Locks page, click Manage Quota Templates.

4.   On the Manage Quota Templates page, in the Template name area, select create a new quota template.

5.   In the Template to start from box, select a template to base your new template on.

6.   In the New template name box, type the name to use for your new quota template.

7.   In the Storage Limit Values section, select the Limit site storage to a maximum of: MB check box, and then type the amount of storage to allow at a maximum.

8.   Select the Send warning e-mail when site storage reaches MB check box, and then type the amount of storage to allow before sending a warning e-mail message.

9.   When you click OK, the new template is added to the list of available templates, and the page is refreshed.

How to Change an existing quota template?

1.   Click Start, point to All Programs, point to Administrative Tools, and then click SharePoint Central Administration.

2.   On the Central Administration page, under Component Configuration, click Manage quotas and locks.

3.   On the Manage Quotas and Locks page, click Manage Quota Templates.

4.   On the Manage Quota Templates page, in the Template name area, select edit an existing template.

5.   In the Template to modify box, select the quota template you want to change.

6.   Update the options you want to change, and then click OK.

7.   When you click OK, the template is updated, and the page is refreshed.

Please let me know in case of any further queries/questions regarding the above mentioned information. I would be more than happy to help you as well as resolves your issues, Thank you J J

What are the different Types of Upgrade method used in Sharepoint 2010

Before you run any process to upgrade from Microsoft Office SharePoint Server 2007 to Microsoft SharePoint Server 2010, you have to determine which upgrade approach to take.

Use the information in this article to help compare the pros and cons for each approach and to review information about special cases that might influence your approach

Approach	Description	Pros	Cons
In-place upgrade	You can install SharePoint Server 2010 on the same hardware. You can also upgrade the content and settings in the server farm as part of a single process.	Farm-wide settings are preserved and upgraded. Customizations are available in the environment after the upgrade, although manual steps may be required to upgrade or rework them.	Servers and farms are offline while the upgrade is in progress. The upgrade proceeds continuously. Consequently, you must allocate enough time for all content to be upgraded in sequence.
Database attach upgrade	You can upgrade the content for the environment on a separate farm. The result is that you do not upgrade any of the services or farm settings. You can upgrade the databases in any order and upgrade several databases at the same time. While each database is being upgraded, the content in that database is not available to users.	You can upgrade multiple content databases at the same time, which results in faster upgrade times overall than an in-place upgrade. You can use a database attach upgrade to combine multiple farms into one farm.	The server and farm settings are not upgraded. You must manually transfer settings that you want to preserve from the old farm to the new farm. Any customizations must also be transferred to the new farm manually. Any missing customizations may cause unintended losses of functionality or user experience issues. Copying databases over a network takes time and bandwidth. You must plan for that. You need direct access to the database servers.