Showing posts with label SharePoint2010. Show all posts
Showing posts with label SharePoint2010. Show all posts

25 February, 2013

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:
 
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.

06 February, 2013

error 503 and unable to access the MOSS site


Problem Description:
Gets error 503 and unable to access the MOSS site anymore after installing a German language pack

Error Message:
503, service is unavailable

Farm Configuration:
Product / Version / Bit: SP2010/14.0.6335.0000/X64
Operating System / Service Pack/Bit: Win 2k8 R2 /SP2/X64
Farm Configuration: 3 WFE
Hardware (Physical/virtual): Hyper-V
Database Used: SQL server 2008 R2

Troubleshooting Done:
1.   Tried accessing all the sites, just to make sure that the problem is restricted to one site or across the whole farm
2.   Reviewed SharePoint logs
3.   Checked event logs
4.   Checked the connectivity between SQL and SharePoint
5.   Checked the application pools are running or not

Cause:
§  Found out that the applications pools are all stopped and that’s why the sites not running.
§  It looks like when the language pack is installed and then the issue started happening.


Resolution:
§  Started the application pool one by one and tried accessing the sites
§  All sites are accessible now without any issues…

Additional Notes:
§  Noticed that one of the content DB (WSS_content_ABC) shows that a few sites are not upgraded to SharePoint 2010.
§  Detached the content Database and attached it back to the same web application, just to make sure that the DB gets upgraded.

Product Applies To:
§  SharePoint 2010
§  SharePoint 2007

If you have any queries/questions then please let me know, thank you.

21 October, 2012

There was an error in callback


Problem Description:
When you search for user accounts using "Browse" People-Picker icon, the following error message may occur and the user accounts may not be resolved

Error Message:
"There was an error in callback".

Probable cause:
This issue normally happens if WSS_WPG group does not have any permissions on this registry key "HKEY_LOCAL_MACHINE\Software\Microsoft\Shared Tools\Web Server Extensions\14.0\Secure".

By default, WSS_WPG group has FULL control access to the above mentioned registry key.

This particular key contains a binary value called AppCredentialKey – it is used to encrypt/decrypt the data passed by PeoplePicker-SearchADForests. This key is created using setapppassword command and used in one way trust relationships. Application pool accounts need at least read access to the above mentioned registry key for successful People Picker behavior.

Resolution
1)      Check WSS_WPG group permissions and confirm whether the application pool account of the web application present in that group 
2)      Later check the registry key - "HKEY_LOCAL_MACHINE\Software\Microsoft\Shared Tools\Web Server Extensions\14.0\Secure" and identify permissions allocated for WSS_WPG group in the Permissions window of the registry key.
3)      If WSS_WPG group does not present in Permissions window, add the 'WSS_WPG' group with read or full control permissions.  

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.

18 August, 2012

Error: 0xE0000021 OneNote needs a password to sync some of your notebooks. Click here to see the list of sections and notebooks that require passwords.

Problem Description:
You can’t sync from an OneNote 2010 notebook to SkyDrive, and you receive the following 0xE0000021 error message:

Error Message:
Error: 0xE0000021
OneNote needs a password to sync some of your notebooks. Click here to see the list of sections and notebooks that require passwords.

Probable causes:
Problems syncing OneNote notebooks with your SkyDrive may occur for one or more of the following reasons:
1)   This issue can occur if you have not installed the latest updates.
2)   You may not have the latest version of Windows Live Sign-in Assistant.
3)   This issue can be caused by a conflict with multiple Live IDs.

Resolution:

Method 1: Install the latest updates

Installing any important, recommended, and optional updates can often correct problems by replacing out-of-date files and fixing vulnerabilities. To install the latest updates, click the link specific to your version of Windows and follow the steps in that article:

Note: For Microsoft Office 2010 users, installing the latest updates will include Service Pack 1 (SP1). SP1 includes updates to OneNote 2010 that may resolve issues syncing OneNote notebooks with your SkyDrive account. OneNote 2010 SP1 uses Windows Live Essentials to log onto Windows Live SkyDrive and improves how OneNote synchronizes with SkyDrive.

For an overview of Office SP1 improvements, see Description of Office 2010 SP1 .

Install Windows updates in Windows 7

Install Windows updates in Windows Vista

Install Windows updates in Windows XP

If installing the latest updates did not resolve your issue, continue to method 2.

Method 2: Install the latest version of Windows Live Sign-in Assistant

Issues syncing OneNote notebooks with your SkyDrive account can be resolved by updating to the latest version of Windows Live Sign-in Assistant. Windows Live Sign-in Assistant is part of Windows Live Essentials which also includes Windows Live Messenger, Photo Gallery, Movie Maker, Mail, and more. To resolve this issue, Windows 7 and Windows Vista users can install the latest version of Windows Live Essentials or to install only the Windows Live Sign-in Assistant, click the link specific to your version of Windows:

Windows 7 and Windows Vista

Windows XP

Note: If you need to uninstall and then reinstall Windows Live Essentials, see How to remove and reinstall Windows Live Essentials .

If installing the latest version of Windows Live Sign-in Assistant did not resolve your issue, continue to method 3.

Method 3: Remove Windows Live IDs from Credential Manager

This step applies to Windows 7, and Windows Vista

Credential Manager allows you to store credentials such as user names, and passwords that you use to log on to websites. Sometimes Credential Manager may not be able to acquire log on credentials, and removing your Windows Live IDs may resolve the issue.

Here’s how to remove your Windows Live IDs from Credential Manager:

This step applies to Windows 7, and Windows Vista

For Windows 7
1)   Close OneNote.
2)   Open User Accounts by clicking the Start button, clicking Control Panel , clicking User Accounts and Family Safety (or clicking User Accounts , if you are connected to a network domain), and then clicking User Accounts .
3)   In the left pane, click Manage your credentials.
4)   Click the vault that contains the Live ID credential that you want to remove.
5)   Click the Live ID credential that you want to remove, and then click Remove from vault .
6)   Repeat step 5 until you have removed all of your Live ID credentials from the vault.
7)   Open the OneNote notebook you want to sync.
8)   Click Web.
9)   Sign in with your Windows Live ID and password, and try to sync your OneNote notebook with SkyDrive.

For Windows Vista
1)   Close OneNote.
2)   Open User Accounts by clicking the Start button, clicking Control Panel, clicking User Accounts, and then clicking User Accounts.
3)   On the Advanced Tab, click Manage Passwords.
4)   Click the name of the credential that you want to remove, and then click Remove
5)   Repeat step 4 until you have removed all of your Live ID credentials.
6)   Open the OneNote notebook you want to sync.
7)   Click Web.
8)   Sign in with your Windows Live ID and password and try to sync your OneNote notebook with SkyDrive.

16 August, 2012

Send to OneNote button is missing

Problem Description:
When you work in Microsoft Outlook, Microsoft Office OneNote 2007 buttons or OneNote 2010 buttons may be missing as follows: 

• When you work in an e-mail item, the Send to OneNote button is missing. 
• When you work in a calendar item or in a task item, the Notes about This Item or the Linked Meeting Notes button is missing. 

This issue may occur when the OneNote add-in is disabled in Outlook or if the Outlook Integration has not been installed.

For Windows Vista or Windows 7

1.  Click Start, type programs and features in the Search box, and then press ENTER. 
2.  Right-click on the version of Office or OneNote that is installed, and then click Change. 
3.  Select Add or Remove Features, and then click Continue. 
4.  Expand Microsoft OneNote. 
5.  Expand Send to OneNote Add-ins. 
6.  If there is an X next to Outlook Integration, click on the X, and then click Run from My Computer. 
7.  Click Continue. 

To enable the OneNote add-in in Outlook, follow these steps.

For Outlook 2010
1.  On the File menu, click Options. 
2.  Click Add-ins. 
3.  If OneNote Notes about Outlook Items is listed under Inactive Application Add-ins, follow these steps: 
• In the Manage box, click COM Add-Ins, and then click Go. 
• In the COM Add-Ins dialog box, click to select the OneNote Notes about Outlook Items check box, and then click OK. 

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 J Thank you.