Available drive space is less than twice the value of physical memory. This is dangerous because it does not provide enough room for a full memory dump with continued operation

SharePoint Health Analyzer is a good feature or we call it as a revolution for SharePoint administrators as it helps you to detect the issues in your farm and keep the SharePoint up and working without any worries :)

It’s very important to take an immediate action in reference to the critical errors which are reflecting in the health analyzer.

Overview of SharePoint Health Analyzer

http://msdn.microsoft.com/en-us/library/ee534957(v=office.14).aspx

SharePoint Health Analyzer rules reference (SharePoint Foundation 2010)

http://technet.microsoft.com/en-us/library/ff686788(v=office.14).aspx

SharePoint Health Analyzer rules reference (SharePoint Server 2010)

http://technet.microsoft.com/en-us/library/ff686816(v=office.14).aspx

As per the error message, make sure that the mention drive is having enough space as per the Microsoft recommendations. If you are pretty sure that space is already there and still you are getting that error in the health analyzer then you need to follow the following theory which has been explained by MVP-PAUL STORK

This theory suggest- “the threshold is built into the code and can't be changed.  You can go into the configuration for the Health Analyzer and turn off that particular rule.  To do this go to Central Administration and navigate to Monitoring > Health Analyzer > Review Rule Definitions.  Then find the specific rule, edit it and disable it.  It will stop telling you that the disks are running out of space.  I'm also not sure that this rule only pertains to the drive where you have your log files, but the only thing you can do is disable the rule.  There is no way to edit it.”

What you can check to free up the space:

-       Check the log files which are stored on the drive – this consumes most of the space

-       Check the backup files which are present over there

-       Check the old deployment files which are present on the same drive

-       Check the software’s which has been used long way back and still using the same space

-       Check the misc stuff which we kept during any critical situations (example: any files, tools etc)

As per Microsoft MSFT- Rock Wang—“This rule checks disk space as a proportion of the RAM on the computer. When disk space is less than twice the RAM on the computer, the health rule triggers an error. When disk space is less than five times the RAM on the computer, the health rule triggers a warning. Accordingly, server computers with lots of RAM are more likely to experience a failure of this rule.”

Once you remove the unnecessary stuff or irrelevant data from the mention drive then click on “Reanalyze now” so that it will verify the error and shows the results immediately.

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

You can’t delete a site that has subsites

Cannot Delete Subsite

Error deleting a website “/Teamsite/SP2010”. You can’t delete a site that has subsites

If you are facing this error message then there are multiple ways to delete it. Let’s look at those details and let me know in case of any queries/doubts based on the same.

-Subsite console

-Site collection console

-SPD 2010

-STSADM utility

-PowerShell utility

-Content and structure

Imp Note:

-You need to make sure that which subsite you are trying to delete and

-How many nested subsites are present underneath?

-Logged in account that you are using to delete that subsite

-Make sure you don't have any meeting workspaces on your site

Let’s look into each category by exploring thoroughly:

Subsite Console:

-Login to SharePoint site with administrator account.

-Click "Team Site" on the top of the "Admin" Page.

-Navigate to the subsite you prefer to delete.

-Click "Site Actions", and then click "Site Settings".

-Click “Delete this site” under "Site Actions".

-Click "Delete" Button, and then click "OK" to confirm.

Site Collection Console:

-Login to the SharePoint site collection with admin account

-Site actions

-Site settings

-Site administration

-Sites and workspaces

-You will see a list of subsites which are present underneath the site collection

-In the right hand side, you will find the option of delete

-Click on delete and it will ask you to confirm the details

-Click OK

-That’s it and you are done.

SharePoint Designer 2010 Console:

-Click start

-All programs

-Microsoft Office SharePoint Designer 2010

-File

-Open site

-Enter the site collection URL

-Once the site will be open then you will see the complete hierarchy

-You will see a separate section named as “Subsites”

-Click on it and you will see the number of subsites in the right hand side

-Right click on the subsite that you want to delete

-Click OK and you are done.

Content and structure:

-Site Actions -> Site Settings

-Site Administration: Content and Structure

-In the left column, move to the parent of the main site to be deleted

-In the right column, choose the site to be deleted (Your Site in our example)

-Menu: Actions -> Delete

-Note: Deleting the selected sites will permanently delete all content and user information. All subsites in this site will also be permanently lost. Do you want to continue? Click OK.

STSADM Utility:

stsadm -o deleteweb

   -url <URL name>

For deleting a site within an orphaned site collection or an orphaned site within a site collection:

   -force

   -webid <Web ID>

   -databasename <database name>

   -databaseserver <database server name>

POWERSHELL Utility:

Remove-SPWeb "http://ursite/" -Confirm:$false

Reference:

http://technet.microsoft.com/en-us/library/cc262877(v=office.12).aspx

http://technet.microsoft.com/en-us/library/cc288016(office.12).aspx

 

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…

Thank you.

Code Blocks are not allowed in this file error in 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.

SharePoint Connections

SharePoint Connections will help corporations get more out of SharePoint. 

Fall 2012 SharePoint Connections is your independent, technical conference, offering you the latest information about SharePoint 2013 as well as how to use SharePoint 2010 and earlier SharePoint versions to their fullest potential. Our SharePoint experts teach you the latest SharePoint technical knowledge and how to apply it to your situation. 

At SharePoint Connections, Microsoft SharePoint MVPs and SharePoint technical trainers interact with you and your peers, members of the SharePoint community, in workshops and one on one. You'll learn from experts who will teach you techniques to make SharePoint work in the real world. And you'll get your questions answered and come away with knowledge that will benefit your company, your coworkers, and yourself. 

Who will be speaking at SharePoint Connections? Experienced technical presenters, who have taken SharePoint apart, studied it thoroughly, used it in the real world, and figured out how it works. We choose speakers based on their SharePoint expertise, their technical knowledge about administration or development issues, and their ability to explain what they know so you understand it. 

Don't miss SharePoint Connections if you are a SharePoint admin or developer who needs technical information and real-world help with SharePoint's many challenges, including

• Administering SharePoint
• Developing for SharePoint
• Customizing and integrating SharePoint into your business
• Fine-tuning your deployment
• Making SharePoint work for your end-users' needs
• Plus SQL Server and SharePoint, SharePoint and Visual Studio, SharePoint performance, search in SharePoint, SharePoint social features, and so much more!

Use one of the two ways to register today!

Online Registration or Phone 203-400-6121

Courtesy:  https://www.devconnections.com

Reference:http://www.devconnections.com/shows/fall2012/default.aspx?s=192&amp;CID=EM092712SPProM1&amp;utm_source=penton&amp;utm_medium=email&amp;utm_campaign=PromoInt_CON_CM_F12_SP_SPPro_092712

Metalogix Content Migration and Upgrade for Microsoft SharePoint Server 2010

Microsoft’s SharePoint Products and Technologies have brought robust Enterprise Content Management and Collaboration capabilities to an increasing number of organizations in recent years. The popularity of the previous versions, such as Windows SharePoint Services 2.0 and 3.0, SharePoint Portal Server 2003 and Microsoft Office SharePoint Server (MOSS) 2007, led many organizations to deploy SharePoint to various business units, frequently on a large scale.

Many organizations are now looking toward the SharePoint 2010 wave of products, including SharePoint Foundation 2010 and Microsoft SharePoint Server 2010, because of key functionality improvements in the software. These include the integration of the Office ribbon into SharePoint sites, a more scalable services architecture, document management improvements, enterprise taxonomy and many more.

Unfortunately, the migration path provided by Microsoft does not always address organizations’ needs.

The out-of-box upgrade approaches available from Microsoft suffer from fairly significant limitations.

These approaches:

·         Do not support gradual upgrades

·         Do not support granular migration

·         Do not allow administrators to reorganize content during migration

·         Have limited support for 32-bit source systems

·         Do not support upgrades from SharePoint 2003 directly to SharePoint 2010

These limitations present organizations looking to upgrade to SharePoint 2010 with significant planning challenges that will limit both proof of concept and full implementations. Organizations must also ensure that the upgrade approach they select will not jeopardize the content on the existing platform.

Fortunately, Metalogix has released version 4 of SharePoint Site Migration Manager (SSMM 2010), a tool to migrate content from legacy SharePoint 2003/2007 technologies directly to SharePoint 2010.

SSMM 2010 allows organizations to take advantage of SharePoint’s new features without putting their valuable content at risk. SSMM 2010 provides significant advantages over existing migration tools and techniques, allowing for flexible migration between SharePoint versions and farms, granular migration, Power Shell support, reorganization of sites, templates, and databases during the process, as well as many other enhanced capabilities. Unlike some content migration options, SSMM 2010 uses only SharePoint’s fully supported APIs to migrate content, which ensures that it will not affect existing support agreements with Microsoft.

Key Benefits

·         Migrates SharePoint Sites, Lists and Libraries between Servers with full fidelity.

·         Upgrade from SharePoint 2003 and SharePoint 2007 to SharePoint 2010.

·         Re-Organize and re-template your SharePoint Content.

·         Manage your upgrade with zero downtime.

·         Migrate to the cloud or hosted SharePoint environments and reduce infrastructure costs.

Supported Source Systems

·         SharePoint Portal Server (SPS) 2003

·         Windows SharePoint Services (WSS) v2

·         Microsoft Office SharePoint Server (Moss) 2007

·         Windows SharePoint Services (WSS) v3

·         SharePoint Server 2010

·         SharePoint Foundation 2010

·         SQL Server 2000, 2005, and 2008 Unattached SharePoint databases (Read Only)

·         Microsoft Online Services (MOS) [a.k.a BPOS, Exchange Online, or SharePoint Online ] Standard and Dedicated Versions

Key Features

Easy to Use

Run your migration with a tree-based, copy-and-paste-style user interface that is similar to the familiar Windows File Explorer.

Reorganize or re-template sites during migration

Re-define site structure while migrating. Split Sites and Site collections into multiple targets and re-template Sites. Administrators and content owners can define what content is migrated.

Migrate all list types

Migrate Document Libraries, Issues, Tasks, Contacts, Announcements, Discussions and Custom Lists while preserving views, metadata, and user-edit information.

Retain your valuable data

Preserve all views, version chains, metadata, and user-edit information.

Migrate Permissions

Map and migrate site permissions from WSSv2/SPS 2003 and WSSv3/MOSS 2007 to SharePoint 2010 easily.

Migrate Web Parts

Migrate all out-of-the-box and custom web parts from WSSv2/SPS 2003 and WSSv3/MOSS 2007 sites to SharePoint 2010.

Connect to multiple sites

Connect to multiple SharePoint sites, across any number of servers, for easy consolidation or distribution of your SharePoint data.

Work remotely

Do all the heavy lifting for your SharePoint migration from the convenience of your own machine. SharePoint Site Migration Manager connects to any SharePoint site that you can access with your browser -- even those outside your organization’s intranet.

PowerShell Enabled

Access and extend all SharePoint Site Migration Manager Functionality via PowerShell commandlets, to script and automate all migration functionality.

Migrate from live sites and unattached content databases

SharePoint Site Migration Manager provides native capabilities to migrate directly from unattached content databases to live sites, eliminating the need to build temporary farms. Simply point to an unattached database extracts the data directly and migrate it into a live SharePoint 2010 environment.

Distribute the Workload

Use SSMM to delegate and distribute migration efforts across the organization to individual departments or content owners. This reduces IT workload, enhances buy-in on the new target system, and improves decision-making in terms of content re-organization. You can manage a distributed workload because SharePoint Site Migration Manager reads and writes only to the supported SharePoint APIs, so content is security trimmed properly. Content owners simply need read access to their source sites using the SSMM client, along with write access to their new target locations.

Latest Version

SharePoint 2010

SharePoint Foundation 2010

Microsoft SharePoint Server 2010

SharePoint Site Migration Manager 2010