Saving a default document in SharePoint 2010 document library

When we create a new document (ex: Word Document) in SharePoint 2010 document library, while saving the document you will notice the following dialog box,

Which means that the document is going to be saved on your local hard drive and not on the SharePoint site.

This issue seems to be by design in SharePoint 2010 when you do not have content type associated with the Document Library, but this behavior is not reproducible if we have a custom content type associated to the Document library.

Workaround fix:
Open Microsoft Word, click on File -> Options

Click on Trust Center in the dialog that opens

Next Click on Trust Center Settings

In Trust Center Settings  click Protected View tab and uncheck Enable Protected view for files located in potentially unsafe locations as shown below.

Click on OK to close the open dialogs and close Microsoft Word.

People Search not working

Problem: Created Search service application and configured Content Sources for crawl. Started the Full crawl and it was completed. Created Enterprise search site and able to see the search results, but when I searched for People search they were no results

Resolution:

Here are some of the steps to verify,

Check if User profile Service and User Profile Synchronization Service  is up and running (Navigate to Central Administration, go to System Settings > Manage Services on Server)

Does the default content access account has read permissions to the web application (Navigate to Central Administration, go to Application Management > Manage Web Application and click on your web application to select it. In the Ribbon, click on User Policy)

Check if you have “SPS3://” protocol is in the Content Sources URL list (Navigate to Central Administration, go to Application Management > Manage Service Application and click on Search Service Application. Go to Crawling > Content Sources and click on Content Sources)

Verify if the default Content Source account has “Retrieve People Data for Search Crawlers” . (Navigate to Central Administration, go to Application Management > Manage Service Application and click on User profile Service. In the Ribbon, click on Administrators)

If you need to make changes to any of the above, please run a Full crawl

People Search is working now.

List View Threshold Error

Problem: We have couple of document folders in SharePoint 2007 environment  with couple of Views. We migrated to SharePoint 2010 and when Users try to click the views pertaining to them they were getting “An error has occurred.  The attempted operation is prohibited because it exceeds the list view threshold enforced by the administrator”

Resolution:

1. Navigate to Central Administration.

2. Go to Application Management > Manage Web Application and click on your web application to select it.

3. In the Ribbon, click on General Settings drop-down and choose “Resource Throttling”.

4. In the “List View Threshold”, increase the value (by a factor of 2)) and click OK.

5. If the error persists, increase the value again until the error goes away.

Like to share the resolution so it might be useful for someone.

Cannot publish pages in SharePoint 2010

If you have created your SharePoint 2010 farm manually without running the farm Configuration Wizard, you might encounter this error when you try to publish a page

“The form cannot be rendered. This may be due to a misconfiguration of the Microsoft SharePoint Server State Service. For more information, contact your server administrator.”

The problem is stat the State service is not configured since the Farm Configuration Wizard has not been run.

1.Click Start, point to Administrative Tools, and then click Windows PowerShell Modules.

2. Create a service application by typing $serviceApp = New-SPStateServiceApplication -Name “My State Service”
3. Create a State Service database and associate it with a service application, by typing New-SPStateServiceDatabase -Name ”MyStateServiceDatabase” -ServiceApplication $serviceApp.
4.Create a State Service Application Proxy and associate it with the service application by typing New-SPStateServiceApplicationProxy -Name ”My State Service” -ServiceApplication $serviceApp -DefaultProxyGroup.

In the Manage Service Application, verify if you are seeing new State Service application.  Remember to verify that your web Application is associated with the State Service Application.

Once these instructions are completed, you should be able to publish pages

SharePoint 2010 Installation Step-by-Step

 Here are the list of steps/tasks I had performed to install SharePoint 2010 

Service Accounts

SharePoint 2010  accounts

Service Account	Role
Admin	SharePoint 2010 Installation account
FarmAdmin	SharePoint 2010 Farm admin account
Services	SharePoint 2010 Service account
Mysite	SharePoint 2010 My Site account
Userprofile	SharePoint 2010 User Profile Service account

Permissions

Permissions before Installation

Service Accounts	Local admin on Web Front	Local admin on Application Server	SQL Permissions
Admin	Yes	Yes	DB Creator, Security Admin
FarmAdmin	No	No	None
Services	No	No	None
Mysite	No	No	None
Userprofile	No	No	None

Login to the box with Admin account

Check for windows update

Create Downloads folder on the application drive (D)

Copy the SharePoint 2010 installation software

Click on Splash 

Click on Install software prerequisites

Click Next

Click Next

Pre requitse Installation is complete. Click Finish

on the splash screen click on Install SharePoint Server

Enter valid product key

Click Continue

Check I accept the terms of the License Agreements

Click Continue

Choose Server Farm eventhough you have single box so that this can be extended latter

Choose Complete

If you want to change the file location you can specify here. Only the log files will be created at this location as by default SharePoint installs on system drive

Click on Install Now

Run the SharePoint Configuratin Wizard

Click Next

 

Click Yes



Choose create new server farm, click next



Specify Database server, Database Name. Specfiy the Farm admin account and password here

Click Next



Specify the password for Farm set up and security. This is really cool feature in SharePoint 2010

Click Next


If you want any specific port number for your central admin site you need to specify here.

Click Next



Review your settings and click next





Created successfull, click Finish


If you like to participate select yes otherwise no

To configure each service manually, choose "No"

Change the SharePoint root web service to run under Farm admin account

Hope this helps someone for installation of SharePoint 2010

Good Luck

 

SharePoint 2010 Migration – Using Database attach method

PRE REQUITES

1) Make sure you have enough free disk space for Data/ Back up and Log files on the destination SQL server.
2) Granted DB Owner rights to SharePoint 2010 Install Account on all the Existing/Migrated Content database

COPY/RESTORE CONTENT DATABASE

Copy 2007 Content Database back up copy to the new SQL server.
Restore the Databases in the new SharePoint 2010 SQL environment.
VERIFYING THE CONTENT DATABASENext step is to verify the Content Database using Test-SPContentDatabase Windows PowerShell cmdlet
This cmdlet will test and verify that any custom components that are required for this content database has been installed and configured in the SharePoint 2010 environment.

Test-SPContentDatabase –Name <database name> -WebApplication <URL>

Launch the SharePoint 2010 Management Shell and type the above command, ensuring you have entered your
Information

1) Make sure you have enough free disk space for Data/ Back up and Log files on the destination SQL server.

Test-SPContentDatabase –Name WSS_Content_ABC -WebApplication http:/abcpoint


Review and Resolve the issues if any.

MOUNT CONTENT DATABASE
Next step is to mount the Content Database using Mount-SPContentDatabase Windows PowerShell cmdlet
This cmdlet will mount/Attach content database to the web application.

Mount-SPContentDatabase -Name "WSS_CONTENT_XYZ" -DatabaseServer "SQLSERVER" -WebApplication http://abc/

Review and Resolve the issues if any.

Security Overview for Reporting Services in SharePoint Integrated Mode

When you configure a report server to run in SharePoint integrated mode, the report server uses the authentication provider and permissions defined in the SharePoint Web application to control access to report server items and operations.

Windows Integrated Security Using Kerberos

If the SharePoint Web application is configured for Windows Authentication using Kerberos, the connection from the SharePoint Web application to the report server can use the impersonated or delegated credentials of the current Windows user. By using Windows integrated security with Kerberos and identity delegation, you can eliminate the classic "double-hop" issue wherein Windows credentials expire after a single connection

Windows or Forms Authentication and Trusted Accounts

If the SharePoint Web application is configured for Forms authentication or for Windows Authentication using NTLM, the connection to the report server is sent across the network under a predefined trusted account that has permission to impersonate a SharePoint user on the report server.

Reference link for this post: http://msdn.microsoft.com/en-us/library/bb283324.aspx