Showing posts with label sharepoint server 2010. Show all posts
Showing posts with label sharepoint server 2010. Show all posts

25 April, 2012

Not able to download audit reports


Auditing is an important feature in SharePoint. Auditing maintains a log of the actions performed on content in a site collection. Administrators can retrieve the entire history of actions — from a particular user or date range.

If you want to learn as how to configure audit settings then please refer the following article: http://office.microsoft.com/en-us/sharepoint-server-help/configure-audit-settings-for-a-site-collection-HA010099726.aspx

Coming back to the main point: One of our clients has raised a ticket with us by mentioning: They are not able to download ‘content viewing’ reports.

What exactly is happening as they are not able to download?
·         Open the SharePoint site on which you are working on
·         Site actions
·         Site settings
·         Site collection administration section
·         Audit log reports
·         Whenever we clicks on ‘content viewing report’ to download
·         It prompts for credentials
·         After entering the correct username and password, it keeps the login prompt as it is and finally ‘you are not authorized to view this page’

What is the reason behind this issue / proper explanation?
Audit settings can be configured at the site collection level only. The logs are maintained in the dbo.AuditData table of the respective content database.

You will find an excellent explanation here:

Resolution:
stsadm -o trimauditlog
   -url <URL name>
   -date <YYYYMMDD>
   -databasename <database name>
   [-databaseserver] <database server name>

Important instructions:
·         If you are providing the site collection URL then there is no need to provide database name as well as database server name
·         Let’s assume that your client wants the audit data in between 21 September 2011 to 25 April 2012 then the date parameter will be 20110921, so the data before this will be deleted or u can call it as trimmed.

Note: This operation is available after the Infrastructure Update for Microsoft Office Servers is installed. This functionality is available only by using Stsadm.

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 issuesJ J

20 April, 2012

Key Improvement in SharePoint

Microsoft Share point technologies have matured to great extent since its beginning back in 2000’s. Throughout these years Microsoft provided a step further in every release of the SharePoint version and the technologies relating to the SharePoint services are converging and integrating to the current time.

In 2001 Microsoft provided the Version 1 of SharePoint services knows as “SharePoint Team Services v.1” along with “SharePoint Portal Server 2001”. The team services and portal server were managed as different entities.

In 2003 Microsoft released another server solution known as “Content Management Server 2002” along with upgraded release of SharePoint technologies  such as “Share Point Portal server 2003” and a renamed version of services known as “Windows SharePoint Services v2”. The Windows SharePoint Services v2 and SharePoint Portal Server 2002 were closely integrated while Content Management Server 2001 was a stand alone.

In 2006 Microsoft released another increment to the its Windows SharePoint Services with Version 3, with lot of new advancements and on the top of these SharePoint services are built the new SharePoint Servers. Microsoft released the first (beta) version of the new office system code named as “Office 12”.  Office “12” suit includes a range of SharePoint Servers of which Content Management Server and Portal Server are an integral part of the suit. The SharePoint Servers of office 2007 suit are called MOSS 2007.An Overview of MOSS 2007

MOSS 2007 provides the so many features to an organization’s enterprise level computing requirements. The feature set is divided into the following categories:

1.    Platform Service.    
 Platform Services is the core for the MOSS 2007 architecture. All the features of MOSS 2007 are based on the advancements in the platform services. Platform services component of the MOSS 2007 architecture provides these listed features.
-- Workspaces Management
-- Security
-- Storage
-- Server Topology Management.
-- Site Model

Microsoft Share point technologies have matured to great extent since its beginning back in 2000’s. Throughout these years Microsoft provided a step further in every release of the SharePoint version and the technologies relating to the SharePoint services are converging and integrating to the current time.

Collaboration feature area of MOSS 2007 provides rich support for various kinds of communication and collaboration needs across the enterprise, within departments and among teams. The feature set under collaboration includes the following.
-- Documents/tasks/calendars
-- Blogs
-- Wikis
-- E-mail integration
-- Outlook integration
-- Offline documents/lists

2.    Portal.
 Portal Area of the MOSS 2007 architecture provides support for integrating different types of web sites and site collection into one Portal. There can be as many portals as required by the enterprise. The Portal features provide a lot more advancement and easiness for creating these site collections and portals. The features provided in this area are:
-- Enterprise Portal template
-- Site Directory
-- My Sites
-- Social networking
-- Privacy control

3.  Search.
 The search area of the MOSS 2007 architecture provided improvements by the following features:
-- Enterprise scalability
-- Contextual relevance
-- Rich people and business data search          
-- Content Management.

As discussed earlier that content management was provided in earlier version of SharePoint technologies as a different standalone server, but in MOSS 2007 this functionality has been provided as an out of the box feature. The Content Management provides the following improvements to the SharePoint Experience.
-- Integrated document management
-- Records management
-- Web content management with policies and workflow

5. Business Forms.

With the advent of Windows Workflow Foundation, it was needed that the business process forms used in the workflows produced by the WWF be saved and routed with an engine kind of mechanism. Therefore the MOSS 2007 included a Forms Server which is solely responsible for managing the business forms across enterprise in a workflow. The business forms area provides the following features:
-- Rich and Web forms based front-ends
-- Pluggable Single Sign-On (SSO)

6. Business Intelligence.

Since the SharePoint servers have been very successful in the enterprise wide aggregation of communication and information there needed such services which can display the business related data to the related departments and teams. So that everyone having appropriate rights to view the business related data can access and analyze the various kinds of information on the portal. The Business Intelligence feature area provides exactly the required things. This includes:
-- Server-based Excel spreadsheets
-- Server-based Excel data visualization
-- Report Centers
-- Business Intelligence Web Parts
-- Key Performance Indicators (KPI) / Dashboards
-- Key Improvements in MOSS 2007 / Limitations in SharePoint Portal Server 2003

Let’s talk in details about the major improvement in MOSS 2007 (the limitations and pain points in SharePoint Portal Server 2003). The following list is a brief overview of which features the SharePoint Portal Server 2003 does not provided, but are now provided as Part of MOSS 2007.
-- Multi-Lingual
-- Authentication
-- Extranet portal addresses/aliases/maps
-- Fine-Grained Access Control per list item permissions
-- Workflows
-- Backup / Restore
-- Aggregation of information and lists
-- Navigation usability
-- Report Center and Dash boards
-- Tasks & Calendar Sync with outlook
-- Site Customization
-- Offline documents and lists.
-- Search improvements.
-- Metadata Management
-- Usage Reporting
-- Listings Usability

These limitations/paint points have been addressed with the help of improved and integrated MOSS 2007 architecture. These limitations have been addressed by different feature areas (as discussed earlier) of MOSS 2007. The following sections elaborate on the few of the major improvements which are made to counter these limitations. These are discussed per Feature Area.
Platform Services

Platform Services is the core advancement in the MOSS 2007 and many of the improved features are provided in this category. From the above mentioned list. The improvements provided by Platform Services are.

Multi-Lingual
Supports installation of multiple language packs to the same server so that each web can have its own language, thus providing support for multilingual web sites as well

Authentication
With the help of ASP.Net 2.0 the Platform Services provides features such as ASP.Net pluggable Authentication and web form authentication.

Extranet
Deployment of extranets with the help of Reverse proxy support and alternate access URLs is made possible.

Fine-Grained Access Control
In SharePoint Portal Server 2003 only Document Library (List) level access was supported where as now there is a per item level security defined.
Workflow
Platform Services provides support for Windows Workflow Foundation. 

Backup / Restore
Improved backup / restore including wastebasket and VSS support

Aggregation
Aggregation support by the help of Cross-web list parts is provided.

Navigation
Improved Look & Feel and navigation by using master pages and Security-trimmed UI is provided.

Site Customization
Customization enhancements with the help of templates, feature extensibility and ASP.Net Master Pages are supported.

Collaboration
 The feature set provided under the category of collaboration have some very important improvements in MOSS 2007 as compared to the SharePoint Portal Server 2003.  The core improvement areas are Document Libraries and Outlook Integration and synchronization.

 Document Library Improvements
In the Document Library Improvements, it now supports the
Checking out of documents from document library to local folders
Major and minor version tracking
Version management
Multiple content types within same document library, and
A tree view of Document Library

Outlook integration improvements
In the Outlook integration improvements, it supports
reading and writing to SharePoint objects such as calendar, tasks, contacts, discussions, and documents from within outlook client.
Moreover it supports for synchronization with offline documents which have been checked out for edit in Microsoft outlook from SharePoint Document library.
Also it supports for calendars and Task’s two way synchronization.


Portal

The feature area of portal also has a bit of good improvement which includes the following.
Portal Site
-- Integration with Windows SharePoint Services
-- Intranet Portal Template – Topics, Site Directory

 People and Expertise Search
-- People specific search “tab”
-- Social network support

My Site
-- Improved Public Page, Personal homepage
-- Targeting and personalization
-- Easier targeting – Distribution lists and Security Groups

Profile store improvements
-- Scalability, flexible schema, LDAP synchronization

Business Intelligence (BI)

Microsoft SharePoint Portal Server technology didn’t provide any support for the enterprise or business related information to be shared and viewed on the SharePoint portal sites. In MOSS 2007, Microsoft have envisioned and achieved the goal of improving organizations by providing business insights to all employees leading to better, faster, more relevant decisions with the help of new improvements and new features of SharePoint Portal Server.

MOSS 2007 provides these supports with the help of the following features:
-- Excel client/Excel Services
-- Dashboards & Key Performance Indicators

Excel Client is used for creating the spreadsheets and then is published to the MOSS 2007 document libraries. The Excel Services provides features of displaying the Excel files as reports in the web browser.

Dashboard Enables guided and optimized analysis of data by the user/employee. This data is stored in the Dashboards in the form of Aggregate workbooks, reports, scorecards, etc. the Dashboards make the information relevant within in the reports etc. also it annotate data with additional information

10 April, 2012

How to start the Trace service


The Windows SharePoint Services Tracing (SPTrace) service is used by Windows SharePoint Services 3.0 to manage trace output of the call stack. When trace logging is enabled, administrators can specify the path used to store the trace logs. This log file is reused by many applications that are built on top of Windows SharePoint Services 3.0.

The Microsoft SharePoint Foundation Tracing (SPTrace) service is a required service on all Microsoft SharePoint Foundation servers. If this service is stopped, error messages are not logged on the server.

How to Start the Trace service:
1. Log on to the SharePoint Foundation server as an administrator.
2. In a Command Prompt window, type the following at the command prompt:
3. net start SPTrace


I hope the above mentioned information will be helpful to you to get some insight regarding SharePoint tracing service. In case of any issues/queries regarding the 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 January, 2012

Saving a site as a template

You can save a site as a template at any time using the template option (Save site as template) on the Site Settings page in SharePoint. SharePoint Designer 2010 make it easy by providing a Save as Template option in the ribbon, which takes you to this page in SharePoint. Once you save the template, a solution file is created and stored in the Solution Gallery where you can download or activate the solution.

To save your site as a template using SharePoint Designer 2010, perform the following steps:

1. Open your site in SharePoint Designer 2010.
2. On the Site tab, in the Manage group, click Save as Template


 3.This takes you to the Save as Template page in SharePoint.

4. Specify a name to use for the template file in the File name field.
5. Specify a name and description for the template in the Template name and Template description fields.
6. To include the content of the site in the site template, check the Include Content box.
Note: Including the content of the site can increase the size of the template significantly. Keep in mind that the default size limit for a site template is 50 MB but may be less in your organization.

7. Click OK to save the template.
8. If all of the components on the site are valid, the template is built, and you see a message that says Operation Completed Successfully.
9. To download or activate the solution from the solution gallery, click the user solution gallery link and follow the steps in the procedure below.
10. Or, to return to your site, click OK.



 

Activating the site template in the solution gallery

Once you’ve saved your site as a template, a solution file (.wsp) is created and stored in the Solution Gallery for the site collection. From here, you can download or activate the solution.

To activate your site template, perform the following steps:

1. Browse to the top level site of your site collection in SharePoint.
2. Click Site Actions and choose Site Settings.
3. Under Galleries, click Solutions.
4. To activate your solution, click the pull-down menu beside your solution, and choose Activate


5. On the activate solution confirmation screen, click Activate.
Your solution now has an activated status in the Solution Gallery.
6. To download the solution, just click its name in the Solution Gallery.
7. In the File Download dialog box, click Save, and browse to the location where you want to save the solution.

What gets saved in a template

When you save your SharePoint site as a template, you’re saving the overall framework of the site. Most of the objects in a site are included and supported by the template.
There are a number of objects and features not supported however.


Supported


Lists
Libraries
External Lists
Data source connections
List views and data views
Custom forms
Workflows
Content Types
Custom Actions
Navigation
Site pages
Master pages
Modules
Web Templates


Not Supported


Customized permissions
Running workflow instances
List item version history
Workflow tasks associated with running workflows
People/group field values
Taxonomy field values
Publishing pages and publishing sites
My Sites

What is a SharePoint site template

SharePoint site templates are pre-built definitions designed around a particular business need. You can use these templates as they are to create your own SharePoint site and then customize the site as much as you like. You’re probably familiar with the default site templates, like Team Site, Blog site, and Group Work Site as shown here.
SharePoint Site Template

You can create your own site template based on a site you’ve created and customized in SharePoint. This is a powerful feature in SharePoint that allows you to create a custom solution and then share that solution with your peers, the broader organization, or outside organizations. You can also package the site and open it in another environment or application like Microsoft Visual Studio and further customize it there.
When you save your site as a template, you create a Web Solution Package, or WSP. A WSP is a CAB file with the solution manifest. The solution you create gets stored in the Solution Gallery for the SharePoint site collection. From there, you can download a copy of the solution or activate it on the server.

Installing SharePoint Designer

Choose the 32-bit or 64-bit version of Microsoft Office

Article Office 2010 is available in both 32 bit and 64 bit versions. 64 bit Office 2010 is good if you work with much larger sets of data. If not, we’re recommending...

Keep earlier versions of Office programs when installing Office 2010

Article This article warns that earlier versions of Office are removed when you install Office 2010. It also tells how to keep the earlier version of Office programs.

10 January, 2012

How Recycle Bin Works

Recycle Bin has two stages:
  • First stage: When you delete a file from your site or My Site, it goes into the "end user" recycle bin, and stays there for up to 14 days from the time you deleted it. You can remove the file earlier by manually removing (or restoring) it. Items in the first stage count against your site quota. If you deleted the file accidentally, you (or the site collection administrator) can restore it. To restore an item from this stage of the recycle bin, click Recycle Bin, check the box next to the item to restore, and then click Restore selection.
  • Second stage: When an item is removed from the first stage, it goes to the Site Collection Recycle Bin, where it remains for another 14 days before it is purged (i.e., removed entirely). Items in this second stage do not count against your site's quota. The size of the second stage is equal to one quarter of your site quota (i.e. with a 10 GB quota, an additional 5 GB is allocated to the second stage Recycle Bin). If you exceed your second stage quota, the system automatically purges the oldest items to make room for new items. Only site collection administrators are able to access and restore files in the Site Collection Recycle Bin. To restore an item from the Site Collection Recycle Bin:
    1. On the site actions menu, select site collection
    2. Under "Site Collection Administration", select Recycle bin.
    3. Check the box next to the item or items to restore, and then click Restore Selection In the confirmation box, click OK.

Delete a site collection

1-Select the site collection you want to delete from the drop-down menu on the Delete Site Collection page

2-After selecting Change Site Collection from the drop-down menu, you will see a list of site collections displayed for the Web application that you have most recently accessed.

3-To display a list of site collections for a different Web application, use the Web Application drop-down menu located at the upper-right of the page

Note: When you delete a site collection, all the content is deleted within it, including subsites, lists, and libraries. Therefore, you should perform a backup of the content database containing the site collection or export the site collection first

4-After clicking OK on the Select Site Collection page, you will see the Delete Site Collection page displayed again with the entire path of the site collection shown along with a Delete button.

5-Click Delete and then click OK on the confirmation dialog box to delete the selected site collection.

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

Create site collections

You can create new top-level site collections when you create your Web application or any time later using the Create Site Collections option in Application Management. You can create a top-level site collection using either the root URL of an unextended Web application or a managed path such as /sites or any other wildcard inclusion path you have created.When creating a new site collection, you will provide the following information.
  • Title and description
  • Website address using either the root of the Web application or a URL path
  • A site template that will be used to create the new site collection
  • A site collection administrator and a secondary administrator if required
  • A quota limit template if required
Make sure  to choose the correct Web application before creating the site collection so the collection is available in the correct Web application.

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

create a new quota template

Site quote templates are used to restrict the amount of content a site collection can contain. By default, there is one quota template defined for the user’s personal sites (My Sites). This default quota setting is 100 MB of data for each user’s My Site.

  1. Click Quota Templates.
  2. Select Create A New Quota Template.
  3. Select a template to start from; the default is New Blank Template.
  4. Specify a name for your new quota template.
  5. Specify a maximum storage limit for this quota template in megabytes (MB).
  6. Specify a warning storage limit for this quota template in megabytes.
  7. Optionally, specify the number of points that can be reached by user solutions.
  8. Optionally, specify the number of points that must be reached to trigger an e-mail warning to be sent.
If you have any queries regarding the above mentioned information then please let me know, Thank you

List and library limits


Limit
Maximum value
Limit type
List row size
8,000 bytes per row
Boundary
File size
2 GB
Boundary
Documents
30,000,000 per library
Supported
Major versions
400,000
Supported
Items
30,000,000 per list
Supported
Rows size limit
6 table rows internal to the database used for a list or library item
Supported
Bulk operations
100 items per bulk operation
Boundary
List view lookup threshold
8 join operations per query
Threshold
List view threshold
5,000
Threshold
List view threshold for auditors and administrators
20,000
Threshold
Subsite
2,000 per site view
Threshold
Coauthoring in Microsoft Word and Microsoft PowerPoint for .docx, .pptx and .ppsx files
10 concurrent editors per document
Threshold
Security scope
1,000 per list
Threshold