Showing posts with label MOSS2007. Show all posts
Showing posts with label MOSS2007. 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
-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:


   -webid <Web ID>

   -databasename <database name>

   -databaseserver <database server name>

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

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.

17 February, 2013

How to hide "Respond to this Survey"

Survey Purpose:
We use surveys to ask team members what they think about issues, how to improve your processes, and many other topics. You can collect the results by using several different types of questions, such as multiple choice, fill-in fields, and even ratings.

Problem Description:
How to hide "Respond to this Survey" when a user has already responded to the Survey

It’s simple but little bit tricky to implement as it involves user controls also.

Imp point to note:
·         The Rendering Template for the Survey List is in the defaulttemplates.ascx
Control under 12/Template/Control template.

·         The rendering template ID is ‘ViewToolBar. This template renders the "Respond
to this Survey", Actions menu and Settings menu in the toolbar.

·         This template is a generic template which is used by other lists as well.

·         "Respond to this Survey" is rendered by <SharePoint:NewMenu
AccessKey="<%$Resources:wss,tb_NewMenu_AK%>" runat="server" />.

How exactly it looks like:
<SharePoint:RenderingTemplate ID="ViewToolBar" runat="server">
<wssuc:ToolBar CssClass="ms-menutoolbar" EnableViewState="false" id="toolBarTbl"
ButtonSeparator="<img src='/_layouts/images/blank.gif' alt=''>"
RightButtonSeparator="&nbsp;&nbsp;" runat="server">
AccessKey="<%$Resources:wss,tb_NewMenu_AK%>" runat="server" />
AccessKey="<%$Resources:wss,tb_ActionsMenu_AK%>" runat="server" />
AccessKey="<%$Resources:wss,tb_SettingsMenu_AK%>" runat="server" />
<SharePoint:PagingButton runat="server"/>
<SharePoint:ListViewSelector runat="server"/>

Microsoft Recommendation:
1.    We cannot modify OOB defaulttemplates.ascx as this would be unsupported
2.    Make a copy of defaulttemplates.ascx under CONTROL TEMPLATES FOLDER of 12 hive
and rename it to CustomDefaultTemplates.ascx
What exactly needs to done/Resolution:
1.    To hide “Respond to this Survey” if a user has already responded to the survey,
Create a class which inherits from the Microsoft.Sharepoint.WebControls.NewMenu.

2.    In this override CreateChildControls and have your logic to hide unhide "Respond
to this Survey" based on your need.

3.    Build the class library and install the dll to the GAC.

4.    Modify the “ViewToolBar” in the custom ascx such that to render your custom
"Respond to this Survey" menu from the class library you created.

(Note: You need to add your assembly reference and register the tag prefix in the
Custom ascx control.)

5.    Next step is to render the custom rendering template to the "Survey List" so
     that the custom "Respond to this Survey" menu will be rendered in the toolbar.

6.    For this the "ToolbarTemplate" property of the View should be changed in the
schema.xml file of the Survey List definition.

7.    As modifying the OOB files are not supported, Copy the “SurveyList” folder from
12/Template/Features and paste in the same place as “CustomSurveysList”.
Change the feature ID of the “CustomSurveyList”

8.    Open the schema.xml file available under survey folder of “CustomSurveysList”
and add the “ToolbarTemplate=CustomViewToolBar” attribute to the “View BaseID=0”.

Example attached:
<View BaseViewID="0" FreeForm="TRUE" ReadOnly="TRUE" Type="HTML" ToolBarTemplate=" CustomViewToolBar ">

9.    Install and activate "CustomSurveysList"

10. Create a Survey List using CustomSurveyList template and we should be able to
achieve the functionality as required.

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

18 November, 2012

Sales Lead Pipeline Template Mystery

Before directly giving the problem description, let me brief some details regarding Sales Lead Pipeline template. This template belongs Microsoft Fab40 Package and comes under “Server Admin Application Templates”, detail reference:

Problem Description:
User created a Website with the Template "Sales Lead Pipeline". It works well, but there is a Workflow inside this Template to convert leads to accounts. This workflow only work with the side admin account (i.e. only for site collection administrators), all other accounts became an "access denied".

We can enter sales leads into the site but when we push the convert button, or use the convert workflow "Access Denied" is returned. User is a member of both the associated members and owners groups. So now the questions is-Do we really required to be a part of site collection admin group?

Which states that this is a bug in this template and there are some steps by which we can fix this.

Resolution Steps:
1)    Open your sales site with SharePoint Designer
2)    Go to the workflows
3)    Click on the "Convert" workflow with the right button
4)    Click on "Publish selected file"
5)    Choose any location
6)    Click publish

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

12 September, 2012

SSRS SharePoint Data Extension

Data processing extensions in Reporting Services enable you to connect to a data source and retrieve data. They also serve as a bridge between a data source and a dataset(used in SSRS )  If required custom data extensions  can be developed by using  .Net framework  and the unique extensibility architecture of Reporting Services  which enables  us to extend specific features of the product and its components.

SSRS SharePoint Data Extension is  a custom SSRS data processing extension that makes it possible to use Microsoft SQL Server Reporting Services 2005 /2008 for building reports over SharePoint data . This let us build sophisticated reports over SharePoint list, library, and InfoPath and document library. This lets you leverage all the power of Microsoft's reporting platform like exporting list data in multiple formats (Excel, PDF, CSV, XML  ... image), SSRS subscriptions to deliver report to email and file system.

Benefits of Extension
·         Many organizations use SharePoint lists /libraries  to keep track of critical business processes / enterprise data  and these data can be useful  for  business analysis and reporting , un fortunately there is no  out of box  data extension in SSRS 2005/2008  to support  SharePoint as an data source. This custom data extension helps in transform your SharePoint site into a fully fledged application by building sophisticated and customized reports 
·         With the help 0f this extension  SharePoint data can be exported to other formats  , use Reporting Services features to export the data into excel , word(SSRS 2008), XML .etc
·         This provides options to configure access permission to specific SharePoint data. You can build reports that will display data from sites and lists for which users do not have permissions because report can execute using the credentials you specify and if required it can be configured to use credentials of the user running the report.
·         This extension development in one time investment with approximate efforts of 2- 3 weeks. Later can be reused in all those projects which need reports to be generated from SharePoint data.
·         This extension can be extended / customized based on business requirement with fewer efforts.
·         This data extension has can use CAML (Collaborative Application Markup Languages)to query on SharePoint data which leads to increase in performance because only selected rows and column will be fetched from SharePoint
·         This support easy to design query and let the developer concentrate on report layout design. Because it abstracts complex web service API of SharePoint from SSRS report designer
·         This also can query on SharePoint user profile data

Alternative of SSRS SharePoint Data Extension

Out of Box XML- Data Processing Extension
·         Design of complex  xml structure 
·         No intelligence support
·         Doesn't Support CAML Query ,Fetches  all the Data from List/ library
·         Unable to do  Join, Union, Group
Third Party Data Extension  like  Enesys RS Data Extension
·         Costly alternative

Integrating AD RMS and SharePoint

By preparing SharePoint infrastructure to store IRM-protected documents, where the protection capabilities are embedded in the document, it will make these protected documents unsearchable since they cannot be tagged or indexed while the document contents are encrypted.  This is no longer the case with AD RMS and SharePoint 2007 since the IRM policies are only applied when the documents are downloaded and they are stored unencrypted in the libraries, hence making them index able and later searchable.

With SharePoint, IRM protection is available for files that are located in document libraries. SharePoint uses the access control list (ACL) on the library or list to determine the permissions that it applies to a document for the user downloading it. Protection includes the following options with integration of SharePoint with AD RMS:
·         Whether or not users can print documents that are rights managed.
·         Whether the user can run Microsoft Visual Basic for Applications (VBA) and other custom code in the file.
·         The number of days for which the license is valid; after the specified number of days, the license expires and the user must download the file again from the document library.
·         Whether to let users upload file types that do not support IRM.
·         Optionally, the date to stop restricting permissions to the document library; after the specified date passes, Office SharePoint Server removes all rights-management restrictions from the documents in the library.
There are basically three simple steps to integrate AD RMS with SharePoint 2007 as follows:
(Notes: If we are using Windows Server 2008, as it already includes AD RMS client, there is no need to install a separate Windows RMS client as in Windows Server 2003)

Add permissions for the SharePoint server to the AD RMS certification pipeline
·         Log on to the AD RMS server as a local administrator
·         Click Start, and then click Computer
·         Navigate to c:\Inetpub\wwwroot\_wmcs\Certification
·         Right-click ServerCertification.asmx, click Properties, and then click the Security tab
·         Click Advanced, click Edit, select the Include inheritable permissions from this object's parent check box, and then click OK two times
·         Click Edit
·         Click Add
·         Click Object Types, select the Computers check box, and then click OK
·         Type the name of the SharePoint web front-end server, and then click OK twice.
·         Repeat the above three steps for other web front-end servers
·         Click OK to close the ServerCertification.asmx Properties sheet. By default the Read & Execute and the Read permissions are configured
·         Reset IIS

Specify RMS server location in SharePoint using Central Administration
·         Open SharePoint 3.0 Central Administration site
·         Click Operations, and then click Information Rights Management
·         Select Use the default RMS server specified in Active Directory.
·         Click OK

Before installation of Windows Rights Management Services Client.

After installation of Windows Rights Management Services Client

Note:  Ensure that Windows Rights Management Services Client (WindowsRightsManagementServicesSP2-KB917275-Client-ENU-X64.exe) is installed on the server. It is very small installation and takes less time. It will come by default with Windows server 2008.

Enable IRM policy to control access to the contents of a document library
1.       Open a SharePoint site and go to the document library where we want to enable the IRM policy
2.       Click Settings, and then click Document Library Settings
3.       Under Permissions and Management, click Information Rights Management
4.       Select the Restrict permission to documents in this library on download check box
5.       In the Permissions policy title box, type in the policy title
6.       In the Permission policy description box, type in the policy description
7.       Click OK

SharePoint will now automatically apply AD RMS rights to the document when it is downloaded from the document library. These rights are determined by the user permission for that library. For example, a user who has Read permission will not be able to modify the document when it is downloaded from the document library.

Notes: When AD RMS protected documents (created outside SharePoint environment) are uploaded to the library with IRM policy enabled, the original document protection policy will supersede the library protection policy when those documents are downloaded or accessed by users.  AD RMS end-to-end security prevents SharePoint from decrypting documents created outside of the SharePoint environment, hence applying the SharePoint library IRM policy to those documents.