Pages

14 March, 2013

SharePoint Server 2010 provides three types of
caches that help improve the speed at which Web pages load in the browser: the
BLOB cache, the page output cache, and the object 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.
These files are known as binary large objects (BLOBs), and the cache is known
as the BLOB cache.

Configuring cache settings for a Web
application.

You enable and configure the BLOB
cache, and make configuration changes to the page output cache profiles and the
object cache in the Web.config file in the Web application to which you want to
apply those changes. The changes you make to the Web.config file will be
applied to all site collections within the Web application

Note : Please take a backup of the
web.config before you make any changes to the file

To configure BLOB cache settings

1.Verify that you have the
following administrative credentials: You must be a member of the
Administrators group on the local computer to configure the BLOB cache
settings.

3.In Internet Information
Services (IIS) Manager, in the Connections pane, click the plus sign (+) next
to the server name that contains the Web application, and then click the plus
sign next to Sites to view the Web application or applications that have been
created.

4.Right-click the name of the
Web application for which you want to configure the disk-based cache, and then
click Explore. Windows Explorer opens, with the directories for the selected
Web application listed.

5.Right-click web.config, and
then click Open.

6.If the Windows dialog box
appears, select Select a program from a list of installed programs, and then
click OK.

9.In this line, change the
location attribute to specify a directory that has enough space to accommodate
the cache size.

Microsoft strongly recommends that you
specify a directory that is not on the same drive as where either the server
operating system swap files or server log files are stored.

10.To add or remove file types from the list of
file types to be cached, for the path attribute, modify the regular expression
to include or remove the appropriate file extension. If you add file
extensions, make sure to separate each file type with a pipe (|)

11.To
change the size of the cache, type a new number for maxSize. The size is
expressed in gigabytes (GB), and 10 GB is the default.

It is recommended that you not set the cache
size smaller than 10 GB. When you set the cache size, make sure to specify
a number large enough to provide a buffer at least 20 percent bigger than the
estimated size of the content that will be stored in the cache.

12.To enable the BLOB cache, change the enabled
attribute, from "false" to "true".

13.Save the Notepad file, and then close it.

When you save a change to the web.config file,
the Web application in Internet Information Services (IIS) 7.0 automatically
recycles. This recycling can cause a brief interruption in service to sites
contained in that Web application, and users can lose session stateWhen 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.

Some
webparts are belongs to SharePoint_AdminContent database. While debugging
further on this, we tried to find out the leaf names as well as dir names are a
part of which links/URL’s exactly but we didn’t find anything. That’s strange
to troubleshoot further.

The GUIDS which are belongs
SharePoint_AdminContent Database are as follows:

[baf5274e-a800-8dc3-96d0-0003d9405663]

[9eba9c17-3b89-a2e7-a3cf-0ee3d7c2adb1]

[07f48b68-2e69-c86a-ebe4-16359e03ebc2]

[23091f6c-295d-4493-504c-1714a20d65a2]

[7d319bdd-d90e-7861-b7f0-2f9f4cec3004]

[c744e2b2-158c-c2f8-2f80-54bf046ff644]

[36f2680f-4855-f100-da5b-5dd1d07ae62b]

[b36f9dfe-325a-1b44-e6bb-645dcf79c770]

[0a60f514-1dea-8537-b588-64ee5e224da3]

[9f56656f-6aa3-0d55-a812-711bf65864ea]

Further
research on this, we came to a conclusion that this is a known issue regarding
this GUIDS belongs to AdminContent DB and we can certainly ignore that. This
will gets fixed in the next CU.

[MissingWebPart]
WebPart class [a03a7e7e-aab8-9045-8bf2-54d79ff53595] (class
[PowershellWebpart.PowershellWebPart.PowershellWebPart] from assembly
[PowershellWebpart, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=0bf26c041eeaa3b0]) is referenced [1] times in the database
[WSS_Content_Sharepoint.SP2010], but is not installed on the current farm.
Please install any feature/solution which contains this web part. One or more
web parts are referenced in the database [WSS_Content_Sharepoint.SP2010], but
are not installed on the current farm. Please install any feature or solution
which contains these web parts.

As we can
see, the error gives you a “WebPart class” GUID, the name of the content
database, and how many times it is referenced in the database but no site
collection link.

Following SQL query will be used to
find out the site ID, LEAF name and Directory name.