Tuesday, June 24, 2008

Some useful references about Sharepoint 2007 Scalability and Performance

References

Scaling SharePoint 2007: Storage Architecture

The purpose of this white paper is three-fold. First, this document is intended to provide prescriptive guidance targeted at the storage subsystem for a highly scalable Office SharePoint Server 2007 implementation in order to facilitate architectural planning. Second, it is intended to provide techniques for monitoring scalability metrics for existing SharePoint implementations. Finally, it provides techniques for modifying the storage architecture of Office SharePoint Server 2007 systems that are suffering from poor performance due to the fact that the I/O burden on the storage subsystem has exceeded its capability.

(http://go.microsoft.com/fwlink/?LinkId=119399&clcid=0x409)

Evaluation Guide for Office SharePoint Server 2007

This evaluation guide is designed to give you a solid understanding of the design goals and feature set for Office SharePoint Server 2007 and a familiarity with the product implementation. It provides an overview of the solutions and benefits provided by Office SharePoint Server 2007, along with descriptions of new and improved features in the areas of portal, search, content management, business forms and integration, and business intelligence. It also provides a hands-on tour of the product's main feature areas and concludes with useful information for administrators and developers.

(http://go.microsoft.com/fwlink/?LinkId=119400&clcid=0x409)

Determine Hardware and Software Requirements

An installation of Office SharePoint Server 2007 can range from a single computer (stand-alone installation) to many computers (server farm). The requirements for your installation will depend on the availability and scaling requirements for your solution. This article describes the minimum and recommended hardware requirements based on whether you are deploying a stand-alone installation or a server farm. This article also lists the software prerequisites for installing Office SharePoint Server 2007.

(http://go.microsoft.com/fwlink/?LinkId=119403&clcid=0x409)

Planning Recommendations for Web Servers

Plan your Web servers by using the recommendations in this article to enhance system performance.

(http://go.microsoft.com/fwlink/?LinkId=119411&clcid=0x409)

Configure a Dedicated Front-End Web Server

Configure a dedicated front-end Web server for crawling (Office SharePoint Server 2007). Front-end Web servers are used by Office SharePoint Server 2007 to crawl content in SharePoint sites within your server farm. They are not used to crawl content that is external to your server farm, such as SharePoint sites in other server farms, Exchange Public folders, or file shares. Content that is external to the farm is accessed directly by the index server, without the need for the front-end Web server.

(http://go.microsoft.com/fwlink/?LinkId=92660&clcid=0x409)

Physical Topology Recommendations

The topology of your system's database tier, and your network, physical storage, and caching can significantly affect system performance. When you plan your hardware, remember that Office SharePoint Server 2007 is the last version of Office SharePoint Server 2007 that will run on 32-bit operating systems and databases.

(http://go.microsoft.com/fwlink/?LinkId=119415&clcid=0x409)

Physical Storage Recommendations

The disks and arrays you choose — and how you place data on those disks and arrays — can significantly affect system performance. If you are unfamiliar with Redundant Array of Independent Disks (RAID), see the following resources:

(http://go.microsoft.com/fwlink/?LinkId=119416&clcid=0x409)

Planning and Monitoring SQL Server Storage for Office SharePoint Server 2007: Performance Recommendations and Best Practices

This paper provides key recommendations and best practices to help administrators of SharePoint Products and Technologies to plan and monitor their SQL Server storage requirements to support optimal performance and operation of their server farms.

(http://go.microsoft.com/fwlink/?LinkId=119398&clcid=0x409)

Database Maintenance for SharePoint Products and Technologies

This white paper provides information and guidelines for maintaining the databases that host Microsoft SharePoint Products and Technologies data and configurations. It describes and provides examples of the database maintenance tasks that we recommend when using SharePoint Products and Technologies.

(http://go.microsoft.com/fwlink/?LinkId=117910&clcid=0x409)

Stsadm Operations

The articles in this section list and explain the operations you can perform by using the Stsadm command-line tool. Each article includes a description of the operation, syntax, required and optional parameters, values, and examples (when available).

(http://go.microsoft.com/fwlink/?LinkId=119417&clcid=0x409)

Managing Enterprise Metadata with Content Types

By managing enterprise metadata, an organization can make it easier for its members to find the content they are looking for when they need it—without overburdening them during the creation process.

(http://go.microsoft.com/fwlink/?LinkId=119418&clcid=0x409)

End-to-End Deployment Scenarios – Office SharePoint Server 2007 for Search

This chapter provides information and directions for deploying Microsoft Office SharePoint Server 2007 for Search as an end-to-end solution, whether on a single computer or in a simple server farm.

(http://go.microsoft.com/fwlink/?LinkId=119420&clcid=0x409)

Search Deployment

This white paper provides an overview of the rationale for an enterprise search solution, describes the features available in the various Microsoft products, and outlines solutions to several common search scenarios.

(http://go.microsoft.com/fwlink/?LinkId=119425&clcid=0x409)

Plan to Crawl Content

The purpose of this article is to help Shared Services Providers (SSP) administrators understand how Office SharePoint Server 2007 for Search crawls and indexes content and to help them plan to crawl content.

(http://go.microsoft.com/fwlink/?LinkId=80120&clcid=0x409)

Limit or Increase the Quantity of Content Crawled

For each content source, you can select how extensively to crawl the start addresses in that content source. You also specify the behavior of the crawl, sometimes called the crawl settings. The options you can choose for a particular content source vary somewhat based on the content source type that you select. However, most options determine how many levels deep in the hierarchy from each start address listed in the content source are crawled. Note that this behavior is applied to all start addresses in a particular content source. During operations, you might need to crawl some sites at deeper or fewer levels.

(http://go.microsoft.com/fwlink/?LinkId=119437&clcid=0x409)

Tuesday, June 10, 2008

One of the properties of the Web Part has an incorrect format

 

 

Web Part Error:

One of the properties of the Web Part has an incorrect format.
Windows SharePoint Services cannot deserialize the Web Part.
Check the format of the properties and try again

 

I have got this error while modifying a Custom Web Part when i added to it the properties Width and/or Height. Simply I renamed it and that's all.

 

 

 

Here there is the same error on other situation.

 

 

 

Lack of permissions for application pool account can cause Web Parts to not display on home page

If the account used for authenticating the application pool for Windows SharePoint Services does not have read and write permissions to the directory that Windows uses for temporary files, Web Parts may not display properly. When this occurs, the following error message appears:

Web Part Error: One of the properties of the Web Part has an incorrect format. Windows SharePoint Services cannot deserialize the Web Part. Check the format of the properties and try again.

  1. Locate the system temporary directory.
    1. Right-click My Computer, and then click Properties.
    2. On the Advanced tab, click Environment Variables.
    3. In the System variables list, note the directories for TEMP and TMP.
  2. Go to the directories listed for TEMP and TMP.
    1. Click Start, and then click Run.
    2. Type the path to folder that contains the folder associated with TEMP and/or TMP, and then click OK.
  3. Right-click on the folder for the temporary directory, and then click Sharing and Security.
  4. On the Security tab, verify that the application pool account for the content virtual server has Read and Write permissions in each of the directories.

For information about configuring the application pool account, see the Windows SharePoint Services Administrator's Guide.

Wednesday, June 04, 2008

javascript syntax error

This is just a memory on my blog about the "descriptive" message syntax error with a javascript code.
Just to fastly remember that sometimes it comes from this kind of line where i forgot the = character on an "if" sentence.

if (a=1)

where the correct sentence is

if (a==1)

Sometimes i got the "syntax error" message and sometimes "Object expected"