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.

Disabled accounts in AD show up in SharePoint as active profiles

Problem Description:

If the proper filer is not applied in import connections then it can lead to hundreds of unwanted / disabled profile in ssp database. Sometimes due to IT audits we want to get rid of those profiles from SharePoint.

Product Applies:

1.    MOSS2007 (Microsoft Office SharePoint Server 2007)

2.    WSS3.0 Windows SharePoint Services 3.0)

Error Message: N/A

What exactly I did? How exactly I configured and came to know about the issue?

1.    In AD, I have created lots of user and disabled few of them.

2.    Configured SSP to import user profile by using the default filter

(&(objectCategory=person)(objectClass=user).

3.    That’s it-Problem started and found lots of profiles in view user profile.

Resolution:

·         At first apply filter (&(objectCategory=person)(objectClass=user)(

!(userAccountControl:1.2.840.113556.1.4.803:=2))) to just import active profiles in

connection.

·         Run full profile import three times back to back.

·         After that you will find users in view user profile > Profile Missing from import.

·         You can manually delete these unwanted profile or wait till clean up job delete them.

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

Built-in SharePoint web services

SharePoint server structures information by Web Sites. Each Web Site has many Lists. Lists are used to store concrete data using List Items: links to files, contacts, appointments, etc. List Items has fields with necessary values. The user is able to customize these fields to store data.

SharePoint installation comes with good collection of built in web services that can be used to work with SharePoint. SharePoint Webservices installed in “_vti_ “bin folder ((%COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\12\ISAPI).

Here are the built-in web services in SharePoint.

• http://server:5966/_vti_adm/Admin.asmx - Administrative methods such as creating and deleting sites
• http://server/_vti_bin/Alerts.asmx - Methods for working with alerts
• http://server/_vti_bin/DspSts.asmx - Methods for retrieving schemas and data
• http://server/_vti_bin/DWS.asmx - Methods for working with Document Workspaces
• http://server/_vti_bin/Forms.asmx - Methods for working with user interface forms
• http://server/_vti_bin/Imaging.asmx - Methods for working with picture libraries
• http://server/_vti_bin/Lists.asmx - Methods for working with lists
• http://server/_vti_bin/Meetings.asmx - Methods for working with Meeting Workspaces
• http://server/_vti_bin/Permissions.asmx - Methods for working with SharePoint Services security
• http://server/_vti_bin/SiteData.asmx - Methods used by Windows SharePoint Portal Server
• http://server/_vti_bin/Sites.asmx - Contains a single method to retrieve site templates
• http://server/_vti_bin/UserGroup.asmx - Methods for working with users and groups
• http://server/_vti_bin/versions.asmx - Methods for working with file versions
• http://server/_vti_bin/Views.asmx - Methods for working with views of lists
• http://server/_vti_bin/WebPartPages.asmx - Methods for working with Web Parts
• http://server/_vti_bin/Webs.asmx - Methods for working with sites and sub sites

Retain look up column values in export list template

It is known issues that on exporting list items, look up column values are lost.

If the list is very big, it might not be possible to fix that manually. This problem occurs since list template does look up on a table using GUID, on creating a list template and exporting to a different site, this GUID changes, hence it is no longer able to retain the values.

Steps to retain look up column values in export list template

Suppose I have a list “Category” which has a look up column “sub category” which refers to list “Sub Categories”. I assume you have already created a look up list “Sub Categories” in the destination web.

1. Browse to the source Web’s lookup list “Sub Category” and choose Modify settings and columns.
2. Copy the source lookup list GUID from the URL.It should be a sequence of numbers and letters similar to:  %7BFFA47BF8%2D849C%2D4F20%2D9C50%2D173D2F5B6725%7D
3. Browse to the destination Web’s lookup list and choose Modify settings and columns.
4. Copy the destination lookup list GUID from the URL.Similar as point 2.
5. Delete %2D from the string and replace with a dash sign (-). There should be no dash sign (-) at the start and the end. GUID should be in the following format: FA47BF8-849C-4F20-9C50-173D2F5B6725
6. Save the source Web’s list that contains a lookup column “Category” to the lookup list as a list template called category.stp.
7. Export the list template STP from the source list template gallery to the file system.
8. Rename the category.stp file to category.cab so Windows can open it.
9. Open the file, right click on the manifest.xml file and export it to the file system.
10. Edit the manifest.xml file; find the source Web’s lookup list GUID and replace it with the destination Web’s lookup list GUID.
11. Save the manifest.xml file.
12. Open a VS.NET command prompt.
13. Run the makecab command as: makecab manifest.xml category.stp
14. Import the new STP into the destination Web’s list template gallery. You will need to delete it if it has previously been imported.