SaurabhKV

SharePoint Page Layout Error: Only Content controls are allowed directly in a content page that contains Content controls

2009-10-13T08:06:00Z

I recently built a SharePoint feature to provision custom master pages and page layouts for a client. Overall the solution worked pretty well until one day, while making changes to one of the page layouts, I saw the following error: Only Content controls are allowed directly in a content page that contains Content controls.

Since other blog entries, referenced at the end of this article, can explain the background I'll get right to the cause and the solution. The cause is improper case for the <asp:Content> control tags in my page layout. A few contorls used a lower case "c" instead of an uppercase "C" in the word content. The page layout that had trouble had tags that looked like: <asp:content> instead of <asp:Content>. The specific offending tag is the one associated with the page title (<asp:Content ContentPlaceholderID="PlaceHolderPageTitle" runat="server">). The solution was as simple as correcting the case of the tag name and all worked well.

Aggregating content with the Content Query Web Part (CQWP)

2009-10-12T20:06:00Z

In most web content management projects based on SharePoint the Content Query Web Part is used for aggregating content. Out of the box it have a few styles, but seems a little limited. With a little tweaking you can display the information you want in the way you want it.

There are mainly three parts involved here:

The web part itself
The ItemStyle.xsl
The ContentQueryMain.xsl

The xsl files is defining how the content is displayed for the end users. The ItemStyle define the style for each item (like a row in a table), while the ContentQueryMain.xsl defines the surrounding (like the table around the rows). By exporting the web part you will find that there are plenty of properties not available in the user interface. The ones I change the most are:

CommonViewFields add columns that you can use in the web part.

<property name="CommonViewFields" type="string">Priority,Choice;PublishingStartDate,DateTime;Ingressbilde,Image;Ingress,HTML</property>

The Image field can be a little tricky

DataColumnRenames changes the name of the input column name to another name. Makes it easier to build the xsl when there are several fields that should be treated as they were the same. Here I rename Ingress to Description

<property name="DataColumnRenames" type="string">Ingress,Description</property>

ItemXslLink and MainXslLink can be pointed to your own XSL-stylesheet for how you want to display the items and what styles you want to make available for the users.

<property name="ItemXslLink" type="string" >/Style Library/XSL Style Sheets/MyItemStyle.xsl</property>

<property name="MainXslLink" type="string">/Style Library/XSL Style Sheets/MyContentQueryMain.xsl</property>

Update: Remember that both ItemXslLink and MainXslLink is server relative. So if your site collection is in the managed path /Sites/ then the xsl-links must reflect that. So for a Site Collection http://example.com/sites/department you will have this property

<property name="ItemXslLink" type="string" >/sites/department/Style Library/XSL Style Sheets/MyItemStyle.xsl</property>

Update end

To set the default style you set the ItemStyle property:

<property name="ItemStyle" type="string">MyNewsArchive</property>

Inside the ItemStyle.xsl you can add several styles. I like to add one that displays all data (columns) that is available to use. This view is developer friendly, but very user unfriendly.

<xsl:template name="ShowXML" match="Row[@Style='ShowXML']" mode="itemstyle">
    <xsl:for-each select="@*">
        <br />
        Name: <xsl:value-of select="name()" />
        <br />
        Value:<xsl:value-of select="." />
    </xsl:for-each>
</xsl:template>

Feature stapling doesn’t work with STP

2009-07-30T17:57:49Z

Feature stapling doesn’t work with STPs file(Site Template File)

Feature Stapling

2009-07-10T06:17:33Z

Causes the attachment of a Feature to all new instances of sites that use a given site definition, without modifying the site definition or creating code routines to activate the Feature on each site. Also known as a feature site template association,

Real World Example

A developer creates a Feature and to add it to every new Web site that is based on a specific site definition. The developer creates a feature-stapling Feature that includes mappings between the Feature and site definition

Technical Details

Feature stapling is implemented through a Feature that is specifically designed to staple other Features to one or more site definitions. Feature stapling allows a Feature to be stapled to any new sites created from any site definition or from specific site definitions based on the template name identified in the appropriate WEBTEMP.xml file.

Following is an example of feature stapling that associates the Feature with only the STS site definition templates.

Xml

Following is an example of feature stapling that associates the Feature with all site definitions.

Xml

Support Details

Feature stapling starts only when the feature stapling entry is added. To add the Features to existing sites, or to sites later added through a restoration process, you must associate the Features with the sites by using some other method.

IIS Service Unavailable Error on a 64 bit operating system

2009-06-24T17:08:36Z

PROBLEM:
If you find this error in the event log when starting an iis service on a 64 bit operating system (personally this happened to us with SharePoint). (This is also followed by a Service Unavailable error when trying to use the application):

Event Log: Could not load all ISAPI filters for site/service. Therefore startup aborted

SOLUTION:
It can be fixed by rebuilding asp.net. You can only run asp.net 1.1 in 32 bit mode and you can run asp.net 2.0 in either 32 bit mode or 64 bit mode.

ASP.NET 1.1
1. Click start, run and type this in:
cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1
2. Click start, run and type this in:
%SYSTEMROOT%\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i
Note:Make sure ASP.NET 1.1 is Allowed in the Web service extension list in Internet Information Services Manager.

AND

ASP.NET 2.0 (32-bit)
1. Click start, run and type this in:
cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1
2. Click start, run and type this in:
%SYSTEMROOT%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i
Note: Make sure ASP.NET 2.0 (32 bit) is Allowed in the Web service extension list in Internet Information Services Manager.

ASP.NET 2.0 (64-bit)
1. Click start, run and type this in:
cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 0
2. Click start, run and type this in:
%SYSTEMROOT%\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe -i
Note: Make sure ASP.NET 2.0 (64 bit) is Allowed in the Web service extension list in Internet Information Services Manager.

Note: Change 2.0.50727 to whatever build of the framework you have.

SharePoint JavaScript – Page Load Add function: _spBodyOnLoadFunctionNames

2009-06-22T12:27:16Z

In most cases SharePoint pages are based on a master page that contains the “body” element. These content pages can’t directly add a function to the body’s onload event. In order to work around this limitation, SharePoint provides the “_spBodyOnLoadFunctionNames” array. When the body is loaded, the onload event handler executes each function whose name is contained in this array. We added “FunctionName” to the array so that it would run when the body’s onload event fires.

Adding SharePoint Search to IE7

2009-06-18T23:00:33Z

The following registry file can be used to add MOSS search to the list of IE7 search providers ... so you can access it from the top right search box.
(Rename xxxx with the name of your MOSS machine)

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\SearchScopes\Intranet]
"DisplayName"="Search Intranet"
"URL"=http://xxxx/searchcenter/pages/search_results.aspx?k={searchTerms}&s=Intranet
[HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\SearchScopes\People]
"DisplayName"="Search people"
"URL"="http://xxxx/searchcenter/pages/people_results.aspx?k={searchTerms}"

Save the contents to a text file and rename to a .REG suffix. Then double click the file to invoke it

OR ----

Click Here

The search request was unable to connect to the Search Service

2009-06-18T17:46:30Z

The WSS project I was working, we have to implement a search mechanism, it should search all the stuff. But the problem, I didn’t see the SharePoint search, and how the results will getting display? While clicking on the search button it will throws an error like “The search request was unable to connect to the Search Service”. I have tried lot of things like changing the Search service running permissions, etc. But nothing happened. And from one MSDN blog I got that I have to start the Indexing service, which is disabled by default. I have logged as Administrator and started the Indexing service from Administrative Tools > Services. Then Indexing Service. Changed the properties, disabled to manual. And started the service. Then I resets the IIS. Clicked Search, in the WSS screen

WoW ! it is giving some results.

About source variations

2009-06-18T13:38:05Z

Many companies operate globally, and even in their home market, companies often must appeal to customers who speak different languages. This diversity often requires that publishing sites be tailored for different cultures, markets, and geographic regions.

Overview

Maintaining a number of different versions, or "variations," of publishing sites or pages is difficult and time consuming because it can be difficult to coordinate the creation and updating of content between the variations.

To simplify this process, site owners can define a series of site variations and mark one as the primary, or source, variation. Changes to the source variation can be automatically or manually propagated to target variations. Updates to the source variation ensures that the changes are made in all other target variations. To enable integration with third-party translations services, this system is integrated with workflow and the import and export of content. When translation is completed, updates can be imported and sent for final approval through the workflow system.

Configure variation settings

To enable variation features, you must configure variation settings for your publishing sites or pages.

Note You can have only one variation within a site collection. Multiple source variations are not supported.

Starting at the top-level site of a site collection, on the Site Actions menu , point to Site Settings, and then click Modify All Site Settings.
On the Site Settings page, under Site Collection Administration, click Variations.
In the Variation Home section, type the location in which the source and the target variations will be created.
In some cases, it might not be the entire site collection that is being translated. It could just be the News section of the site that you want to define as a variation. Click Browse, and then navigate to the section of the site you want to set as the common location for all the variations, both source and targets.
In the Automatic Creation section, do one of the following:
- If you want to automatically create a copy of all variations — for example, French, Spanish, and German translations of a Web site or page — click Automatically create site and page variations.
- If you want the owner of a site or page to determine when a site or page is created, click Do not automatically create site and page variations.
In the Recreate Deleted Target Page section, determine what happens when a variation page is deleted and its variation source is updated. For example, if a variation source is in English and a target variation page, which is in Japanese, is deleted by the site owner of the Japanese site, determine whether a target Japanese page is re-created when the source page is republished.
To determine whether a deleted target page is re-created, do one of the following:
- If you don't want a new target page to be created when the source page is republished, click Do not recreate a new target page when the source page is republished.
- To re-create a new target page when the source page is republished if the previous target page has been deleted, click Recreate a new target page when the source page is republished.
To send e-mail notification that new subsite or page of a target site is created, or when a target page is updated with revisions from the source variation, click the Send e-mail notification to owners when a new site or page is created or a page is updated by the Variation system.
If a subsite is created, an e-mail message is sent to the owner of the parent subsite in which the new subsite is created. If a target page is updated as a result of a change made to its source variation, a message is sent to the owner of the site in which the page list exists.
In the Resources section, determine whether you want a new page variation to use the same resources as the source page or to use copies of these resources that are created in the location of the new page variation. Do one of the following:
- To use existing resources, click Reference existing resources.
- To copy the resources, click Copy resources.
  If the source variation page includes an image that is in a global site collection and is accessible to everyone, you may want to continue to use that image. However, if the source variation page references resources that are local to that site, you may want to either copy the resources so that they are local to the target site or continue to reference them from the source variation.
Click OK.

About variation labels - SharePoint Server - Microsoft Office Online

2009-06-18T13:36:50Z

Publishing sites can be tailored for different cultures, markets, and languages. Variation settings enable site owners to create and maintain a number of different versions, or "variations," of publishing sites or pages. Variation labels are the names given to each of the variants. For example, variant labels could be language names — such as English, French, or German — or devices, such as French personal digital assistant (PDA) or Spanish mobile phone.

Create a variation label

On the Site Actions menu , point to Site Settings, and then click Modify All Site Settings.

On the Site Settings page, under Site Collection Administration, click Variation Labels.

On the Variation labels page, click New Label.

In the Label and Description section, type the name you want in the Label Name box.
The name you use will be the string that is used in the URL.

In the Description box, type a description to help users understand the purpose of the label. This description is optional.

In the Display Name section, type a name in the Display Name box. Display names are usually localized versions or user-friendly versions of a label.
The display name will appear in the Site Management Tool hierarchy.

In the Locale section, select the locale for the variation. The locale determines the formatting for items such as date, time, and currency.
If you have Language Packs installed on your server, you can click the Language box to select a language. This will dictate what language the variation label's site will be provisioned in.

In the Hierarchy Creation section, select the portion of the source hierarchy that you would like to copy. Do one of the following:

To create a hierarchy of publishing sites and all pages, click Publishing Sites and All Pages.

To create a hierarchy of just publishing sites, click Publishing Sites Only.

To create a hierarchy at the root, click Root Site only.

To select the variation label you are creating as the source variation, select the Set this variation to be the source variation check box.

In the Select the Publishing site template you want to use box, select the template to use to build this site.
Important The settings in the Source Variation section cannot be modified after variation hierarchies have been created.

Click OK.

On the Variation Labels page, click Create Hierarchies.

Note When you navigate to the root of your site, you are redirected according to your browser's current language preferences.

Tip On certain master pages that include the Variation Picker Control, a control in the upper-right corner of your browser enables you to switch between the variation labels in your site.

Use a variation label in a page layout - SharePoint Server - Microsoft Office Online

2009-06-18T13:30:02Z

Depending on your customers' needs, you may want to use a different page layout for every variation label. A variation label might differ because of issues such as right-to-left languages, branding, and format constraints as with handheld devices.

You can map a page layout to a variation label by specifying a preferred layout.

On the Site Actions menu , point to Site Settings, and then click Modify All Site Settings.
If you are not at the root of your site, under Site Collection Administration, click Go to top level site settings.

On the Site Settings page, under Galleries, click Master pages and page layouts.

Point to the page layout you want to map to the variation label, click the arrow that appears, and then click Check Out.

Point to the page layout again, click the arrow that appears, and then click Edit Properties .

In the Variations section, under Available Labels, select a label from the list.

Click Add to move the label to the Labels for Layout box.

Click OK.

Check in the file.
Note Changes to page layouts are subject to the versioning and approval process in effect in the Master Page and Page Layout Gallery.

Variations requires SharePoint Web Parts

2009-06-18T07:50:45Z

These last few days we have become aware of an important limitation regarding variations in SharePoint Server. The thing is that when using variations, web parts need to be inherited from the SharePoint WebPart class (Microsoft.SharePoint.WebPartPages.WebPart) and not from the ASP.NET WebPart class (System.Web.WebControls.WebParts.WebPart). If it is inherited from ASP.NET WebPart class, you will receive an InvalidCastException exception during variation propagation. This occurs when variations tries to cast your Web Part class to Microsoft.SharePoint.WebPartPages.WebPart before calling the PublishingPage.FixWebPartUrlsForVariation() method. I consider this a bug since it could easily be fixed by checking the type before trying to cast.

Configure IE To Prompt For Credentials For Trusted Sites ~ Windows Fanatics

2009-06-16T15:26:20Z

Internet Explorer can be configured to prompt for credentials when connecting to servers requiring authentication. For example, IE can prompt you for a user name and password when you connect to servers in Trusted sites that require authentication, as opposed to using the credentials you are logged on with.

To configure IE to prompt for credentials for Trusted sites:

Open Internet Explorer.

From the Tools menu, click Internet Options.

Select the Security tab.

Click the Trusted sites Web content zone.

Click the Custom level button.

From the list of settings, scroll to the end and select the button beside Prompt for user name and password.

Click OK.

Click OK to close the Internet Options window.

Configure IE To Prompt For Credentials For Trusted Sites ~ Windows Fanatics

Post-installation steps

2009-06-13T19:55:30Z

After Setup finishes, your browser window opens to the home page of your new SharePoint site. Although you can start adding content to the site or you can start customizing the site, we recommend that you perform the following administrative tasks by using the SharePoint Central Administration Web site.

· Configure incoming e-mail settings You can configure incoming e-mail settings so that SharePoint sites accept and archive incoming e-mail. You can also configure incoming e-mail settings so that SharePoint sites can archive e-mail discussions as they happen, save e-mailed documents, and show e-mailed meetings on site calendars. In addition, you can configure the SharePoint Directory Management Service to provide support for e-mail distribution list creation and management. For more information, see Configure incoming e-mail settings (Office SharePoint Server).

Configure incoming e-mail settings

Before you can enable incoming e-mail on the server that is running Office SharePoint Server 2007, you must have configured the SMTP service on front-end Web servers in the farm and the Active Directory and DNS Manager on the domain controller, or you must know the name of other servers that are running these services.

This procedure configures the settings that are used for incoming e-mail. You can also configure options for safe e-mail servers and the incoming e-mail display address.

Important:

Membership in the Administrators group of the Central Administration site is required to complete this procedure.

Configure incoming e-mail settings

1. On the top navigation bar, click Operations.

2. On the Operations page, in the Topology and Services section, click Incoming e-mail settings.

3. If you want to enable sites on this server to receive e-mail, on the Incoming E-mail Settings page, in the Enable Incoming E-Mail section, click Yes.

4. Select either the Automatic or the Advanced settings mode.

If you select Advanced, you can specify a drop folder instead of using an SMTP server.

5. If you want to connect to the Microsoft SharePoint Directory Management Service, in the Directory Management Service section, click Yes.

a. In the Active Directory container where new distribution groups and contacts will be created box, type the name of the container in the formatOU=ContainerName, DC=domain, DC=com, where ContainerName is the name of the organizational unit in Active Directory, domain is the second-level domain, and com is the top-level domain.

Note:

The Central Administration application pool account must be delegated the Create, delete, and manage user accounts task for the container. Access is configured in the properties for the organizational unit in Active Directory.

b. In the SMTP mail server for incoming mail box, type the name of the SMTP mail server. The server name must match the fully qualified domain name in the MX entry for the mail server in DNS Manager.

c. To accept only messages from authenticated users, click Yes for Accept messages from authenticated users only. Otherwise, click No.

d. To allow creation of distribution groups from SharePoint sites, click Yes for Allow creation of distribution groups from SharePoint sites. Otherwise, click No.

e. Under Distribution group request approval settings, select the actions that will require approval. Actions include the following:

· Create new distribution group

· Change distribution group e-mail address

· Change distribution group title and description

· Delete distribution group

6. If you want to use a remote SharePoint Directory Management Web Service, select Use remote.

. In the Directory Management Service URL box, type the URL of the Microsoft SharePoint Directory Management Service that you want to use.

a. In the SMTP mail server for incoming mail box, type the name of the SMTP mail server. The server name must match the fully qualified domain name in the MX entry for the mail server in DNS Manager on the domain server.

b. To accept messages from authenticated users only, click Yes for Accept messages from authenticated users only. Otherwise, click No.

c. To allow creation of distribution groups from SharePoint sites, click Yes for Allow creation of distribution groups from SharePoint sites. Otherwise, click No.

7. If you do not want to use the Microsoft SharePoint Directory Management Service, click No.

8. In the Incoming E-Mail Server Display Address section, type a display name for the e-mail server (for example, mail.fabrikam.com) in the E-mail server display addressbox.

Tip:

You can specify the e-mail server address that is displayed when users create an incoming e-mail address for a list or group. Use this setting together with the Microsoft SharePoint Directory Management Service to provide an e-mail server address that is more user-friendly.

9. In the Safe E-Mail Servers section, select one of the following options:

· Accept mail from all e-mail servers

· Accept mail from these safe e-mail servers. If you select this option, type the IP addresses (one per line) of the e-mail servers that you want to specify as safe in the corresponding box.

10. In the E-mail Drop Folder section, in the E-mail drop folder box, type the name of the folder in which Microsoft Windows SharePoint Services polls for incoming e-mail from the SMTP service.

This option is available only if you selected advanced mode.

11. Click OK.

Configuring incoming e-mail on SharePoint sites

After configuring incoming e-mail settings, site administrators can configure e-mail enabled lists and document libraries. For more information about e-mail enabled document libraries, see the Help documentation for site administrators.

Contact addresses created for these document libraries appear automatically in Active Directory Users and Computers under the organizational unit for Office SharePoint Server 2007, and must be managed by the administrator of Active Directory. The Active Directory administrator can add more e-mail addresses for each contact. For more information about how to manage contacts in Active Directory, see the Help documentation for Active Directory.

Alternatively, the Exchange Server computer can be configured by adding a new Exchange Server Global recipient policy to automatically add external addresses that use the second-level domain name and not the subdomain or host for Office SharePoint Server 2007. For more information about how to manage Exchange Server, see the Help documentation for Exchange Server.

· Configure outgoing e-mail settings You can configure outgoing e-mail settings so that your Simple Mail Transfer Protocol (SMTP) server sends e-mail alerts to site users and notifications to site administrators. You can configure both the "From" e-mail address and the "Reply" e-mail address that appear in outgoing alerts. For more information, see Configure outgoing e-mail settings (Office SharePoint Server).

Configure outgoing e-mail settings

Important:

Membership in the Farm Administrators group of the Central Administration site is required to complete this procedure.

Configure outgoing e-mail settings

1. On the top navigation bar of the SharePoint Central Administration Web site, click Operations.

2. On the Operations page, in the Topology and Services section, click Outgoing e-mail settings.

3. On the Outgoing E-Mail Settings page, in the Mail Settings section, type the SMTP server name for outgoing e-mail (for example, mail.example.com) in the Outbound SMTP server box.

4. In the From address box, type the e-mail friendly address as you want it to appear to e-mail recipients.

5. In the Reply-to address box, type the e-mail address to which you want e-mail recipients to reply.

6. In the Character set menu, select the character set that is appropriate for your language.

7. Click OK.

· Create SharePoint sites When Setup finishes, you have a single Web application that contains a single SharePoint site collection that hosts a SharePoint site. You can create more SharePoint sites collections, sites, and Web applications if your site design requires multiple sites or multiple Web applications.

· Configure Workflow settings Specify whether users can assemble new workflows and if participants without site access should be sent documents in email attachments so they can participate in document workflows. For more information, see Configure workflow settings.

Configuring workflow settings

Note:

Membership in the Administrators group of the Central Administration site is required to complete this procedure.

Configure workflow settings

1. On the top navigation bar, click Application Management.

2. On the Application Management page, in the Workflow Management section, click Workflow settings.

3. On the Workflow Settings page, in the Web Application section, the current Web application is displayed in the Web Application menu. To configure the settings for a different Web application, click Change Web Application, and then select a new Web application on the Select Web Application page.

4. In the User-Defined Workflows section, select Yes if you want to enable user-defined workflows, or select No if you do not want to enable user-defined workflows.

5. In the Workflow Task Notifications section, under Alert internal users who do not have site access when they are assigned a workflow task, select Yes if you want internal users without site access to be sent an e-mail alert when a task is assigned to them. Users attempting to complete the task by using the link in the alert will be directed to the Request Permissions page. If you do not want internal users without site access to be sent an e-mail alert when a task is assigned to them, select No.

6. Under Allow external users to participate in workflow by sending them a copy of the document, select Yes if you want documents to be sent to external users by e-mail when those users are part of the workflow but they do not have access permissions to the documents. If you do not want documents to be sent to external users who do not have access permissions, select No.

Note:

If the object in the workflow is not a document but a list item, the list item properties are displayed in a table as part of the e-mail message.

7. Click OK.

· Configure diagnostic logging settings You can configure several diagnostic logging settings to help with troubleshooting. This includes enabling and configuring trace logs, event messages, user-mode error messages, and Customer Experience Improvement Program events. For more information, see Configure diagnostic logging settings.

Configuring diagnostic logging settings

Note:

Membership in the Administrators group of the Central Administration site is required to complete this procedure.

Configure diagnostic logging settings

1. On the top navigation bar, click Operations.

2. On the Operations page, in the Logging and Reporting section, click Diagnostic logging.

3. On the Diagnostic Logging page, in the Customer Experience Improvement Program section, under Sign Up for the Customer Experience Improvement Program, select one of the following options:

o Yes, I am willing to participate anonymously in the Customer Experience Improvement Program (Recommended).

o No, I don't wish to participate.

If you select Yes, users can decide whether they want to report Customer Experience Improvement Program events to Microsoft.

4. In the Error Reports section, under Error reporting, select one of the following:

o Collect error reports.

If you select this option, you can also select or clear two options to control how error reports are collected:

o Periodically download a file that can help identify system problems.

o Change this computer's error collection policy to silently send all reports. This changes the computer's error reporting behavior to automatically send reports to Microsoft without prompting users when they log on.

o Ignore errors and don't collect information.

5. In the Event Throttling section, in the Select a category menu, select a category of events:

1. In the Least critical event to report to the event log menu, select the least-critical event to report to the event log for the selected category.

2. In the Least critical event to report to the trace log menu, select the least-critical event to report to the trace log for the selected category.

In the Trace Log section, in the Path text box, type the local path to use for the trace log on all servers in the farm. The location must exist on all servers in the farm.

0. In the Number of log files text box, type the maximum number of files that you want to maintain.

1. In the Number of minutes to use a log file text box, type the number of minutes to use each log file.

Click OK.

· Configure antivirus protection settings You can configure several antivirus settings if you have an antivirus program that is designed for Office SharePoint Server 2007. Antivirus settings enable you to control whether documents are scanned on upload or download and whether users can download infected documents. You can also specify how long you want the antivirus program to run before it times out, and you can specify how many execution threads the antivirus program can use on the server. For more information, see Configure antivirus settings.

Administrative credentials

Membership in the Administrators group of the Central Administration site is required to complete this procedure.

Configure antivirus settings

1. On the top navigation bar, click Operations.

2. On the Operations page, in the Security Configuration section, click Antivirus.

3. On the Antivirus page, in the Antivirus Settings section, select one or all of the following:

o Scan documents on upload

o Scan documents on download

o Allow users to download infected documents

o Attempt to clean infected documents

4. Click OK.

· Configure search You can configure several search and index settings to customize how Office SharePoint Server 2007 crawls your site content or external content. For more information, see Configure the Office SharePoint Server Search service (Office SharePoint Server).

· Configure Excel Services Before you can use Excel Services, you must start the service and add at least one trusted location. For more information about doing this, see Configure Excel Services.

About Excel Services configuration

· Trusted file locations These are SharePoint document libraries, UNC paths, or HTTP Web sites that have to be explicitly trusted before Excel Calculation Services is allowed to access them. For more information, see Add a trusted file location.

· Single sign-on SSO enables authentication against external data sources without having to provide authentication credentials more than once. SSO authentication is required in a trusted subsystem environment. For more information, see Start the Single Sign-On service and Manage settings for single sign-on.

· Trusted data providers These are databases that reside outside of the Excel Services farm and that Excel Calculation Services is explicitly configured to trust when processing data connections in workbooks. Excel Calculation Services attempts to process a data connection only if the connection is to a database that has been added to the Excel Services trusted data providers list. For more information, see Add a trusted data provider.

· Trusted data connection libraries These are SharePoint document libraries that contain Office data connection (.odc) files that are used to manage workbook connections to trusted data providers. In the trusted subsystem model, front-end Web servers and application servers running Excel Calculation Services trust the accounts of the associated Office SharePoint Server 2007 applications. For more information, see Add a trusted data connection library.

· User-defined functions These are functions that enable users to extend the functionality of Excel Web Services. For more information, see Enable user-defined functions.

Rounded Corners in Internet Explorer: Staying Ahead of the Curve

2009-06-13T19:05:48Z

Rounded Corners in Internet Explorer: Staying Ahead of the Curve