SharePoint Support

Subtitle

Blog

view:  full / summary

Missing/Required binary files on one Web-front-end after installed the CU aug 2010 hotfix

Posted by dubeyashish.r12@gmail.com on October 28, 2013 at 8:45 AM Comments comments (0)
Try running the command: "Get-SPProduct -local" on each server in the FARM, this will redocument the Patches installed in the configuration Database. Then run the command: psconfig -cmd upgrade -inplace b2b -wait -force



Caching in SharePoint 2010

Posted by dubeyashish.r12@gmail.com on September 18, 2013 at 2:25 AM Comments comments (0)

SharePoint Server 2010 provides three types of caches that help improve the speed at which Web pages load in the browser.

a. The BLOB cache.

 

b. The Page Output Cache.

 

c. The Object Cache.

 

Page output and object cache require that you activate the ‘SharePoint Server Publishing’ feature located in the site features of your web site.


BLOB cache:


SharePoint Server 2010 provides a disk-based cache that stores files that are used by Web pages to help them load quickly in the browser, and reduces the load on the database server when it uses those files. The BLOB cache is stored directly on the hard disk drive of a front-end Web server computer. By default, the BLOB cache is off and must be enabled to use the functionality it provides. When you enable the BLOB cache on your front-end Web server, you reduce the load on the SharePoint Server 2010 database server created by read requests from Web browsers. You enable the BLOB cache in the Web.config file of the Web application to which you want to apply it. The changes that you make to the Web.config file will be applied to all site collections within the Web application. To configure and Setup BLOB Caching read here.


Page output cache profiles:


The second caching option you have with SharePoint 2010 is ASP.net Output Cache. This is an in-memory cache that saves rendered ASPX pages. Using Output cache improves performance in two ways first it reduces the amount of SQL calls. Second it reduces workload on the WFE because pages do not need to be re-rendered. Along those lines if the pages are anonymous, then no SQL check needs to be done at all present the cached pages. Microsoft testing concluded a ninefold improvement in throughput when compared to having to render the page every time it was rendered. To configure and Setup Output Caching read here.


Object cache


Object cache is the third caching option we have for SharePoint 2010. What Object cache does is stores metadata about SharePoint Server objects (like SPWeb, SPSite, SPList, etc.) on the WFEs. When a page is rendered, if there is data that needs to be retrieved through these objects, the SQL Server will not be hit. Features of SharePoint that uses Object cache are publishing, content query web part, navigation, search query box and metadata navigation. These features are specifically written to use the Object cache API instead of the SharePoint API directly. Developers writing custom functionality can also tap into the Object cache API. To configure and Setup Output Caching read here.



Reference:

http://blogs.msdn.com/b/kunal_mukherjee/archive/2011/01/10/caching-in-share-point-2010-best-practice.aspx

SharePoint 2010 Server Roles

Posted by dubeyashish.r12@gmail.com on August 16, 2012 at 3:35 PM Comments comments (0)

Depending on the size of your SharePoint 2100 deployment, you may have one or more SharePoint servers assigned to serve specific purposes, or roles, including these:


Web server: This server (also known as a front-end Web server) hosts all Web pages, Web Parts, and Web services used when your server farm receives a request for processing.


Application server: This server hosts the service applications running in the farm, such as Visio Services.


Database sever: This server stores most of the data associated with a SharePoint 2010 implementation — including configuration settings, administration information, data associated with the service applications, and user content.


Query server: This server is responsible for querying the index, finding the matching content, and then sending the content back to the Web servers for presentation to users.


Crawl server: This server crawls (accesses and catalogs) content sources and then propagates the results to the query servers. The crawl server uses a crawl database to store the URLs of all sources crawled.


Roles aren't assigned directly to a server; instead, a server assumes a specific role in your configuration depending on what components it has installed, the services it runs, and its location within your server farm.


 

Some key differences between stsadm export and backup operations

Posted by dubeyashish.r12@gmail.com on July 12, 2012 at 4:15 AM Comments comments (0)

Stsadm –o backup/restore


With the URL and filename parameters, it allows you to backup either a site collection or web application. You can basically consider the file generated more or less as a SQL dump of (a part of) your content database.


It preserves the GUID of every object except the GUID of the Site: when you restore the backup, SharePoint generates a new GUID for the site collection.


This was done on purpose, among others things because Sites table in configuration database uses SiteID as the primary key.


This is very important because it allows you to restore the backup in the same farm in which you did the backup. You can even restore the same backup several times in the same farm, but you must always restore in a different content database, because the GUID of every other object remains unchanged.


This operation is designed to take an exact copy of a site collection, no data will be changed, transformed or lost.


Stsadm –o export/import


This is the only standard operation (not talking about possibilities with custom code) that allows you to backup data of a sub site (SPWeb object), but it can also export a site collection, an entire web application, or a single list. It generates a new GUID for every objects such as sites, sub sites, lists and items.


Another difference is that you can restore the content in an existing site, the behavior with existing data is defined with the parameter updateversions in import operation.


A major drawback of this operation is that it does not preserves workflows instances, associations, history and tasks. Every workflow association must be recreated and there is no way to restore the running instances from original site.


Contrary to the backup operation, it does not matter on which content database you run import operation, and you can restore a top site as a subsite, and reciprocally (except for sites with publishing feature where it is not supported: http://blogs.technet.com/b/stefan_gossner/archive/2009/05/27/limitations-of-stsadm-o-export-import-related-to-publishing-sites.aspx).


This operation is good for merging content of sites, and decide how to handle identical data between source and target. Very important, do not forget to use includeusersecurity parameter in both export and import if you wish to preserve information relative to permissions and other properties such as documents authors.

 

Difference between Web Application,Site Collection and Sites?

Posted by dubeyashish.r12@gmail.com on July 12, 2012 at 2:30 AM Comments comments (0)

Web Application

On top of the hierarchy is the web application. In technical terms, this is a web site in IIS (with an associated application pool). A default web site listens for incoming HTTP requests on port number 80. But we can create additional web sites, having different port numbers or IP addresses. We can configure each IIS web application independently. We can have one web application configured in anonymous access one in integrated authentication etc.

The SPWebApplication objects represent a SharePoint Web Application, which essentially is an IIS virtual server. Using this class we can do some high level operations. Please find some of the actions you can perform.

Create a web application

Collect all the features in a particular web application

Delete a web application

Some administrative task for the web application.

Site Collection

The Site Collection is the root site of the web site. Below the Site Collection, there can be one or more Sites. A Site Collection is a collection of SharePoint sites;  i.e. a SharePoint site collection is a logical grouping of multiple SharePoint sites.

There are many reasons to go with separate site collection in SharePoint. Some of the features are listed below.

Dedicated Recycle bins Dedicated usage Reports Site collection administrator option for each site collection We can set search scopes, keywords, etc We can deploy features specific to a site collection Each site collection has Galleries for web parts, master pages, content Type etc Administrators can set Site quota templates for Site collection (Max Size of the Site collection) Database maintenance options Backup / Restore abilities Content Deployments options A user assigned as a site collection administrator has full rights on the existing site as well as any other sites that would be created in the same site collection. We can define Security groups, users and their authorization rights independently for each Site collection. Another main advantage is easy to take backup/Restore site collection. As SharePoint is all about data and data should be properly authenticated / authorized to proper users. By defining the structure in site and site collection we can now define roles and responsibilities according to data.

Site

Site is a collection of web pages which is used to store information in an organized way. Site stores list of documents, discussion, events, task and many other types of information. Site provides controlled access to share information among user;  i.e. only authorized users are allowed to access shared information. You can have multiple sites under each site collection; each site can have multiple sub sites also.

 

Move site collections to a new database (split a content database)

Posted by dubeyashish.r12@gmail.com on June 6, 2012 at 3:25 PM Comments comments (0)

You can split the database to move the growing site collections to another database or to another server.

Split a content database:

You can use this procedure to split a content database that is associated with your site collections. The process of moving a site collection between databases consists of exporting the site collection URL data to a file and then importing the data to a new database.


Split a content database (move a site collection to a different database) :

1.At a command prompt on the drive where SharePoint Products and Technologies is installed, change to the following directory:

%COMMONPROGRAMFILES%\Microsoft shared\Web server extensions\12\Bin


2.Type the following command, and then press ENTER: Stsadm -o enumsites -url<URL> ><path/file name>.xml


where url is the address of the Web application that contains the site collection that you want to move, and path/file name is the name of the XML file that you want to create with the site collection data.


This creates an XML file that contains all of the site collection URLs in the current database.


3.Open the XML file that you created in a text editing application. If there are any URLs for site collections that you do not want to move, be sure to delete them from the file. The only URLs that should remain in the XML file should be for the site collections that you want to move.

 

Note:There is no need to change the site count or any of the other site collection information in the file. Only the URLs are relevant to this procedure.


4.Type the following command, and then press ENTER:Stsadm -o mergecontentdbs -url<URL>-sourcedatabasename<database name>-destinationdatabasename<database name>-operation 3 -filename<file name>


where url is the address of the Web application that contains the site collection that you want; sourcedatabasename is the name of the database that you want to move the site collection from; destinationdatabasename is the name of the database that you want to move the site collection to; operation 3 is the “Read from file” operation; and file name is the name of the file that contains the site collection URLs that you want to move.


5.Restart IIS by typing the following command, and then pressing ENTER:iisreset /noforce

Link:http://technet.microsoft.com/en-us/library/cc825327%28v=office.12%29.aspx


 



SharePoint 2010: Ten points to pay attention for a good infrastructure

Posted by dubeyashish.r12@gmail.com on March 14, 2012 at 2:10 AM Comments comments (0)

SharePoint PirateSharePoint 2010: Ten points to pay attention for a good infrastructure

#1 Limit your SQLWhen you install SharePoint 2010 on a complete mode with a SQL SERVER 2008R2, there is an option on the properties of the server, that you can limit the RAM usage. If you don’t limit the usage, it will use 2.1 petabytes.

The default value for SQL Server 2008R2 Maximum Server Memory setting is 2,147,483,647 MB. Therefore, SQL Server will use all available memory for its own use.

 #2 Use different users for your environmentWhen you will configure Web Applications, Service Applications … Do not forget to create for each of these Applications a user.

The main raison is that when this service or user will get an error it will be easy for us to know with service has failed. (EVENT VIEWER)

Second raison is that on IIS7, the application pool names are getting GUID. So we can have more information just on regarding the username: 

 If we had the same user for each service, we could never know which GUID was for witch Service.

(1 first) The e6266ed1faa2406cbae0bbbf33f6e4ba is my Access Service.. 

#3 Use a Warm up ScriptYes, everybody knows SharePoint is slow, and in many cases it’s extremely slow. But there are many solutions therefore. The best solution is to use a WARM UP script.It will compile everything, and your SharePoint will be very faster.

Download link: http://www.gokanozcifci.be/subsite/warm-up-script-for-sharepoint-2010.html ;

Download link: http://spwakeup.codeplex.com/ 

#4 Disable unused warnings on SharePointThe SharePoint Health Analyzer detected a condition requiring your attention. Drives are at risk of running out of free space.

This is an example of a BETA warning on SharePoint; it can be disabled on Review Job Definitions. Do the same of each job that you think that’s unusual for you.

 #5 SQL BROWSERStart your SQL BROWSER service on services.msc on your SQL Server. It is a very useful tool that helps you to see each warning, error … on the SQL Server

It will show you more information about the login failure’s with an explicit SQL ID.

 #6 Service ConnectionsWhen you will create a new WEB APPLICATION SharePoint will attach each service on your WEB APPLICATION. Even the one that you don’t need, so in place of using de “default” value use the custom value on Central Administration

 #7 Made a SHORTCUT 14/Made a Shortcut to the desktop of you 14 document and it will be easier to check your logs and many other things.

 #8 DisableloopbackCheckWhen you use the fully qualified domain name (FQDN) or a custom host header to browse a local Web site that is hosted on a computer that is running Microsoft Internet Information Services (IIS) 5.1 or a later version, you may receive an error message that resembles the following:

HTTP 401.1 - Unauthorized: Logon Failed

This issue occurs when the Web site uses Integrated Authentication and has a name that is mapped to the local loopback address.

Download Link: http://www.gokanozcifci.be/subsite/DisableLoopbackCheck.html ;

 #9 Use a PowerShell Script for downloading prerequisites.SharePoint prerequisites installer will install “everything” that he thinks that it will be ever used. But in many of cases it’s not true. Take this script modify it and download the applications that “you” need..

Download Link: http://www.gokanozcifci.be/subsite/download-prerequirements-sharepoint-2010-powershell.html ;

 #10 don’t use port 80 for Central AdministrationWhen you will install SharePoint Server/Foundation, it will ask to give a Port number for Central Administration; give everything but don’t give 80 (http protocol). So you can hide your Central administration from possible attacks. It will give a standard IIS page. 

Alternet access mapping to browse site within intranet

Posted by dubeyashish.r12@gmail.com on March 12, 2012 at 2:05 AM Comments comments (0)

1. Go to Central Administration for your WSS or MOSS instance.

2. Click on the Operations Tab.

3. Click on Alternate Access Mappings under Global Configuration.

4. You should now see a list of yourweb applications, switch over to the one you want to map to the new URL by selecting it from the drop down on the right side.

5. Click on Edit Public URLs and change the desired zone URL type to your new domain name. You can also change your internal URLs also by clicking Add Internal URLs.

6. Now you’ll have to switch over to your DNS server.

Within the DNS Management Console and Under Forward Lookup Zones:

7. Add a new Primary Zone with your new domain name.

8. Add a new Host (A) to the recordsand point the IP Address to the sharepoint server.

9. Done.

Link:http://blog.henryong.com/2007/01/17/alternate-access-mapping-in-sharepoint/

 

Adding quick launch in web part zone page SharePoint 2010

Posted by dubeyashish.r12@gmail.com on February 21, 2012 at 6:10 AM Comments comments (0)

When you create a webpart page on SharePoint 2010 or 2007for that matter, the quick launch will vanish.

With SharePoint 2010 you also need to delete the following:

1. Open site in SharePoint Designer

 2. Remove below code 

< style type="text/css">

body #s4-leftpanel {

display:none;

}

.s4-ca {

margin-left:0px;

}

</style>

 3. Remove below code

<asp:Content ContentPlaceHolderId="PlaceHolderLeftNavBar"

runat="Server"></asp:Content>

The quick launch will now display on the web part page.

 http://buyevich.blogspot.in/2010/09/sharepoint-2010-how-to-add-back.html


Rss_feed