Thursday 17 May 2012

Alternate Access Mapping

for more info please info please visit http://www.sharepointreferences.wordpress.com

InfoPath form library forms cannot be filled out in a Web browser

InfoPath form library forms cannot be filled out in a Web browser

One or more of the following might be causing this:
The Render form templates that are browser-enabled by users check box in Central Administration is cleared.
The following Windows PowerShell command has been run:
Set-SPInfoPathFormsService -AllowUserFormBrowserRendering $false.
Solution:
Enable browser rendering of user forms by using Central Administration
Verify that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group.
In Central Administration, on the Home page, click General Application Settings.
On the General Application Settings page, in the InfoPath Forms Services section, click Configure InfoPath Forms Services.
On the Configure InfoPath Forms Services page, in the User Browser-enabled Form Templates section, select the Render form templates that are browser-enabled by users check box.
Click OK at the bottom of the page.

Using power shell
Enable browser rendering of user forms by using Windows PowerShell
Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
On the Start menu, click All Programs.
Click Microsoft SharePoint 2010 Products.
Click SharePoint 2010 Management Shell.
At the Windows PowerShell command prompt, type the following command:
Set-SPInfoPathFormsService -AllowUserFormBrowserRendering $true

for more info please info please visit http://www.sharepointreferences.wordpress.com

Built-in accounts are used as application pool or service identities.

Built-in or local computer accounts are used as an application pool identity or service identity.

Using built-in accounts as application pool identities or as service identities is not supported in a farm configuration. Built-in accounts include Network Service, Local Service, and Local System.

Solution:

Change the identity that is used for the service or application pool

Verify that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group.
On the Central Administration Home page, click Security.
On the Security page, in the General Security section, click Configure service accounts.
On the Service Accounts page, in the Credential Management section, in the upper drop-down list, click the service or application pool for which you want to change the identity.
In the Select an account for this componentlist, click the domain user account that you want to associate with the service or application pool.If you want to register the account that you selected on the SharePoint Foundation 2010 farm, click Register Managed Account.
Click OK.

for more info please info please visit http://www.sharepointreferences.wordpress.com

SharePoint 14 Hive Directory Structure

Microsoft has replaced the “12 hive” structure that we had in SharePoint 2007 with “14 Hive” structure in 2010.

Some of the folders in 14 hive are :

Program Files\Common files\Microsoft Shared\Web Server Extensions\14 -
This directory is the installation directory for core SharePoint Server files.

Program Files\Common files\Microsoft Shared\Web Server Extensions\14\ADMISAPI -
This directory contains the soap services for Central Administration. If this directory is altered, remote site creation and other methods exposed in the service will not function correctly.

Program Files\Common files\Microsoft Shared\Web Server Extensions\14\CONFIG -
This directory contains files used to extend IIS Web sites with SharePoint Server. If this directory or its contents are altered, Web application provisioning will not function correctly.

Program Files\Common files\Microsoft Shared\Web Server Extensions\14\LOGS -
This directory contains setup and run-time tracing logs.

Other newly added folders are :

Program Files\Common files\Microsoft Shared\Web Server Extensions\Policy -

Program Files\Common files\Microsoft Shared\Web Server Extensions\UserCode -
This directory contains files used to support your sandboxed solutions.

Program Files\Common files\Microsoft Shared\Web Server Extensions\WebClients -
This directory contains files related to the new Client Object Model.

Program Files\Common files\Microsoft Shared\Web Server Extensions\WebServices -
This directory contains new wcf or .svc related files.

Note : You should rewrite and recompile any code that refers to files and resources in “12″ Hive structure.For example, if you have redeployed all of your files into the “14″ folder and emptied your “12″ folder, any references to files under the “12″ folder will not work.

for more info please info please visit http://www.sharepointreferences.wordpress.com

SharePoint Architecture

SharePoint 2007 Architecture

In shared service provider we have

search service, exel calc service

user profiles.

Business data catalog.

for Project Server 2007

we have Project Web access

Info path services

we need to instal sharepoint product and technologies for completion of sharepoint server 2007. here in wss we have Config, Content, Workflow which are the basic, comes with wss, we need to install on top wss to get all the other options. In client apps(i.e integration) sharepoint server supports only IE browser, office client, one note, infopath, project. here sharepoint desinger is not built in.

Sharepoint 2010 Architecture

in 2010 shared service provider is changed to Sharepoint service application.

and wss is changed to sharepoint foundation.

in sharePoint service application it supports search service, exel cal service, user profiles, business data connectivity, infopath service, word conversion service, powerpoint broadcast service, web analytical service, visio graphic service, managed metadata, performance point, and for sharepoint foundation it has sanboxed code service, usage and health logging, config, content, workflow. and for integration i.e. client apps, sharepoint 2010 supports both IE and firefox, office clients, one note, infopath, project, outlook, rss viewers, sharepoint workspace, sharepoint designer, visio, Access.

for more info please info please visit http://www.sharepointreferences.wordpress.com

Search Configuration Part 3

Search Scopes

Search scopes define specific areas that users can search in, when performing searches from SharePoint. This gives you the flexibility to limit search results to specific content areas in your SharePoint environment.

Here are the following steps to configure a search scope. I am using a scope called Data Forms as an example, so you can repeat these steps for whatever search scope you wish to configure.

Create a content source that corresponds to the search scope you are configuring.
When you create the new content source, make sure you add the subsite location (or folder) in the Start Addresses that correspond to the area you want the search scope to crawl content for. Also select Custom – specify page depth and server hops options under Crawl Settings, with an unlimited page depth, so the crawler crawls all content under the start address you specify. Depending on how your content is structured, you may find it more appropriate to select one of the other crawl settings options. Press OK when finished.
You need to create a crawl rule to include the address that corresponds to your search scope, so the crawler knows to include the content. Click on Manage Crawl Rule, under the Crawling section (on the left hand side links) to navigate to the page to create crawl rules.
Click on New Crawl Rule, and enter the appropriate URL in the Path entry area. Select Include all items in this path, under the Crawl Configuration area. Selecting Exclude all items in this path will exclude the content in this rule. The three checkboxes are not necessary, unless you have specific data that has special crawling considerations. Press OK when finished.
The next step is to create the actual search scope. Click on the Scopes link under Queries and Resultssection (in the left hand links area). This will display a page that lists all the search scopes in the system.
Clicking on New Scope will display a page that allows you to create a new search scope. Give the new search scope a title. You can leave the Target Results Page selection to the default results page (unless you have a custom search results page created). Click OK when finished.
You now need to add a couple of rules to the search scope, so right mouse click the newly-created search scope, and select Edit Properties and Rules.
The Scope Properties and Rules page will display. This screen allows you to create rules that determine what content is included or excluded for this search scope.
Click on New Rule to create another new rule for this search scope. For our rule, we are including all the content from the appropriate URL that corresponds to the subsite for the search scope. Select Web Addressfrom the Scope Rule Type section, and select the Folder option from the Web Address section, and enter the appropriate URL. Under the Behavior section, select the Include option. Press OK when finished.
As a last step, make sure you run full crawls on the entire site. This should update the crawled content, and you should be able to perform searches in your SharePoint environment.

for more info please info please visit http://www.sharepointreferences.wordpress.com

Search Configuration part 2

Crawling Configuration

Now that the service application is properly configured, the next step is to setup the search crawl, so content is included when a user performs a search.

Open Central Administration and click your search service application (under Application Management à Manage Service Applications).
You are now taken to the main area where you can specify all the configuration information for search in SharePoint 2010, including content sources, search crawls, search scopes, and crawl rules.
In order to setup a search crawl for a SharePoint site, click on the Content Sources link, under the Crawlingsection (on the left hand side of the page). This page will display the content sources for the search (Local SharePoint Sites is created by default). Right mouse click on Local SharePoint Sites to display the context menu, and select Edit.
The Edit Content Source page is displayed, and this is where you configure the content source. You are able to specify what URLs the content source will look through when crawling (under the Start Addressessection). You can also setup a crawl schedule for the content source, specify priority for the content source, as well as kick off a full crawl when you press the OK button.

for more info please info please visit http://www.sharepointreferences.wordpress.com

Search Configuration part1

Search Configuration

In order for your SharePoint site to be searchable, you must first create and configure a Search Service application. To do so, follow these steps:

Open Central Administration, and click on the Manage Service Applications link, under Application Management:
Click on the New icon in the ribbon (under the Create section), and select Search Service Application:
The following dialog will appear, with entry fields to enter information needed to create the new Search Service Application. Enter a Service Application Name, and select ‘None’ under FAST Service Application. For the Search Service Account, you can create a managed account to associate with the Search Service Application (I kept the default Network Service account selection, for simplicity).
You will then need to create a new application pool for the Search Admin Web Service. You can select an existing application pool by selecting one from the dropdown list, under the Use existing application poolselection. To create a new application pool, select the Create new application pool selection, and enter an appropriate name for your application pool. For the application pool security account, you can use a predefined account (I used the default Network Service account), or you can create a new managed account if you wish to have greater control over the service account.
You will also need to create an application pool for the Search Query and Site Settings Web Service. You can select an existing application pool by selecting one from the dropdown list, under the Use existing application pool selection. To create a new application pool, select the Create new application poolselection, and enter an appropriate name for your application pool. For the application pool security account, you can use a predefined account (I used the default Network Service account), or you can create a new managed account if you wish to have greater control over the service account. Press the OK button when you are ready to create the new search service application.
A dialog will appear when the system has successfully created the new search service application. PressOK to close this dialog.
Returning to Central Administration, you should now see two (2) new service applications.
The next step is to verify that the user(s) you selected as service accounts have the proper permissions for Search. Scroll down the list of service applications to find the User Profile Service Application and click on the whitespace next to it (so the ribbon changes). Click on the Administrators button in the ribbon, under theOperations section.
A dialog will appear, with a listing of all the administrator accounts. Find the account(s) you specified for the service accounts (when configuring the search service application), and verify that the Retrieve People Data for Search Crawler checkbox is checked. In this example, the NT AUTHORITY\NETWORK SERVICE account was used as the service accounts, so that is the only account I need to verify. Press OK when you are finished.
The next step is to verify that the service account(s) you selected as service accounts have read access to your SharePoint site. Go back to Central Administration, and under Application Management, click theManage Web Applications link.
Click on whitespace next to the SharePoint – 80 web application and select the User Policy button in the ribbon (under the Policy section).
A dialog will appear. Verify your service account(s) have Full Read permissions. In this example, the NT AUTHORITY\NETWORK SERVICE account was used as the service accounts, so that is the only account I need to verify. Press OK when finished.

for more info please info please visit http://www.sharepointreferences.wordpress.com

Active Directory (AD)

Active Directory (AD) is a directory service created by Microsoft for Windows domain networks. It is included in most Windows Server operating systems. Server computers that run Active Directory are called domain controllers.

Active Directory provides a central location for network administration and security. It authenticates and authorizes all users and computers in a Windows domain type network—assigning and enforcing security policies for all computers and installing or updating software. For example, when a user logs into a computer that is part of a Windows domain, Active Directory verifies the password and specifies whether the user is a system administrator or normal user.^[1]

Active Directory uses Lightweight Directory Access Protocol (LDAP) versions 2 and 3, Kerberos and DNS.

for more info please info please visit http://www.sharepointreferences.wordpress.com