Difference between Explicit and Wildcard Inclusion

Explicit Inclusion includes only the specific path you set. Use explicit inclusions, for example, if you want Windows SharePoint Services to manage a specific path, such as /portal, but not any possible sites below it, such as /portal/webapplication.

Wildcard Inclusion includes any sites below the path you set, so you don’t have to add them individually. This is the type of inclusion to use for Self-Service Site Creation, when you want users to be able to create top-level Web sites underneath a specific path, such as /<sites>.

Example

For example, using an explicit inclusion, you are saying that http://<site>/dept/ is a site collection without the possibility of any site collections below it; however, wildcard exclusion allows you to create site collections under http://<site>/dept/

How to remove special characters out of a field in InfoPath

– Right Click on the field
– Click on Text Box Properties
– Click on (Fx) next to Value
– Click on Insert Function
– Select translate
– Click Ok
– Click ‘double click to insert field’ and select the field that you want to modify
– Complete the formula using the following format

translate(field,”special characters to be replaced”,”replace with”)

translate(Field, “!@#$%^&*()-=+:;”, “”)

 

Attach databases and upgrade to SharePoint Foundation 2010

When you upgrade from Windows SharePoint Services 3.0 to Microsoft SharePoint Foundation 2010 by using the database attach upgrade approach, you upgrade only the content for your environment and not the configuration settings. Using a database attach upgrade approach is useful when you are changing hardware or want to reconfigure your server farm topology as part of the upgrade process. For more information about how to choose an upgrade approach, see Determine upgrade approach (SharePoint Foundation 2010).

The first step in the process is to set up a new environment to host the upgraded content. If you have not yet set up and configured the new environment, follow the steps in Prepare the new SharePoint Foundation 2010 environment for a database attach upgrade to do so. You must create a Web application in the new environment for every Web application in the old environment, copy any server-side customizations, configure services, and apply any farm settings to the new environment.

After you set up the new environment, you can use the procedures in this article to detach and then reconnect the databases to perform the actual upgrade. This article contains the steps required to perform a standard database attach upgrade and a database attach upgrade with read-only databases.

More Information: http://technet.microsoft.com/en-us/library/cc287634.aspx

Both Windows SharePoint Services Usage logging and Office SharePoint Usage Processing must be enabled to view usage reports. Please contact your administrator to ensure that these services are enabled.

When click on “Site Usage Reports” under “Site Administration” in “Site Settings” page, the following message displayed:

Both Windows SharePoint Services Usage logging and Office SharePoint Usage Processing must be enabled to view usage reports. Please contact your administrator to ensure that these services are enabled. 

Both Windows SharePoint Services Usage logging and Office SharePoint Usage Processing must be enabled to view usage reports. Please contact your administrator to ensure that these services are enabled.

Solution:
You have to enable two options. Open “Central Administration” – “Operation” and click on “Usage analysis processing” under “Logging and Reporting” and check “Enable Logging”. Then, move to “Shared Service Provider”, Click on “Usage reporting” under “Office SharePoint Usage Reporting” and check both options.

SharePoint Workflow Pause Action takes longer

The delay time is effected by the timer job interval, which has a default value of five minutes. Therefore, normally, the minimum pause time will be 5 minutes. You can change the default timer job interval by using STSADM (e.g. stsadm -o setproperty -propertyname “job-workflow” -propertyvalue “every 1 minutes between 0 and 59” -url http://localhost ), however, there may be some performance implications if a large number of workflows runs on your farm.

There were some issues with workflows not resuming when using the action. A hotfix for the issue is available here: A Microsoft Windows Workflow Foundation timer does not resume correctly after reloading a workflow and in KB951297