SharePoint 2010 Server Name: sp2010-1.contoso.com

DC and Exchange Server 2010 on same machine: dc.contoso.com

Domain: contoso.com

Step1: Installing and Configuring SMTP Server on the SharePoint Server

Install SMTP Server from Server Manager-> Add Features

 

After installation go to IIS 6.0 Manager from Administrative Tools. Make sure that the SMTP Service is started on the SharePoint Server.

Right click on the SMTP Server name and then click on Properties.

 

The properties for General Tab in my scenario. I am using IP address as all unassigned, you can use a dedicated IP. I have kept the default settings.

 

 

 

The properties for Access Tab in my scenario.

The properties for Messages Tab in my scenario are default settings.

The properties for Delivery Tab in my scenario are default settings.

The properties for LDAP Routing Tab in my scenario are default settings.

The properties for Security Tab in my scenario are default settings.

Step2: Create Send and Receive Connectors in Exchange 2010

--------------------------------------------------------------

Send Connector

--------------------------------------------------------------

Go to Exchange Management Console on the Exchange Server

Expand Microsoft Exchange On-Premises

Click on Hub Transport under Organization Configuration

Create a Send Connector according to your requirement. I have created it with following settings. Please refer the following screenshots.

 

Click on New Send Connector… and follow the wizard.

 

Type the name of the Send Connector. Select the intended use for it. In my case it is Internal.

Then click on Next.

 

Add new SMTP Address Space.

 

Type the FQDN of the SharePoint 2010 Server. Click on OK.

 

Click on Next after the Address space is added.

 

In the Network settings. Click on Add, to add a Smart Host i.e. the SharePoint Server which has SMTP Service running and configured.

Click on OK and then Next.

 

In the authentication settings select None and click on Next.

 

Click on Next.

 

It will now show the summary. Click on New and a New Send Connector will get created.

 

New Send Connector is created.

 --------------------------------------------------------------

Receive Connector

--------------------------------------------------------------

Go to Exchange Management Console on the Exchange Server

Expand Microsoft Exchange On-Premises

Click on Hub Transport under Server Configuration

Create a New Receive Connector according to your requirement. I have created it with following settings. Please refer the following screenshots.

 

Provide the name and what would be the intended use. Then click on Next.

 

Add the range of IP Addresses where this connector will receive the emails from. Then click on Next.

Click on New, so that the connector gets created.

 

The newly created connector is displayed in the list.

Go to Properties of the connector and select appropriate permissions. I have selected following.

Step3: Test SMTP connectivity from SharePoint Server to Exchange Server

Make sure you can telnet the Exchange Server from your SharePoint Server of port 25(default setting assuming it is the same in your environment).

 

Step4: Configure Outgoing email settings

Browse to SharePoint 2010 Central Administration Site

Go to E-Mail and Text Messages(SMS)

Click on Configure outgoing e-mail settings link

 

 

Type the FQDN of your local SharePoint SMTP Server, from and reply-to address. Also, select the character set, I have kept default. Click on OK.

 

Step5: Configure Incoming E-Mail settings

Browse to SharePoint 2010 Central Administration Site

Go to E-Mail and Text Messages(SMS)

Click on Configure incoming e-mail settings link

 

In this case, I am using Directory Management Service(DMS) in Advanced Mode.

You can configure the DMS by using either the automatic settings mode or the advanced settings mode.

To enable this service on your own server or server farm running SharePoint Server 2010, Central Administration application pool account must have write access to the container that you specify in Active Directory(AD). This requires an Active Directory administrator to set up the organizational unit (OU) and the permissions on the OU.

DMS configuration options

When you configure the DMS to create distribution groups and contacts in Active Directory, you must provide the following information:

- Name of the AD container where new distribution groups and contacts will be created. This must be provided in the following format:

     OU=ContainerName, DC=DomainName, DC=TopLevelDomainName

- Name of the SMTP server to use for incoming e-mail (or accept the default SMTP server if one exists). This must be provided in the following format:

     Server.subdomain.domain.top-level_domain

- In this case, sp2010-1.contoso.com

 

- Whether to accept messages from only authenticated users.

 

- Whether to allow users to create distribution groups from SharePoint sites. If you choose yes for this option, you can also choose whether users can do any combination of the following actions:

      Create a new distribution group.

      Change a distribution group's e-mail address.

      Change a distribution group's title and description.

      Delete a distribution group.

 

I have made the following selections, please refer the screenshots.

 

 

NOTE: After the above configuration is done users can configure the lists to receive incoming emails and configure alerts.

THIS POST APPLIES TO

• SharePoint Server 2010

Along with the above error if the user browses to the SSP Admin site and clicks on Search Settings following error is thrown:
The search service is currently offline. Visit the Services on Server page in SharePoint Central Administration to verify whether the service is enabled. This might also be because an indexer move is in progress.

Additionally, in the event log on the Index Server you may see following errors:

------------------------------------

Event Type:    Error
Event Source:    Windows SharePoint Services 3
Event Category:    General
Event ID:    27745
Date:        12/15/2009
Time:        10:00:00 PM
User:        N/A
Computer:    SERVERNAME
Description:
The description for Event ID ( 27745 ) in Source ( Windows SharePoint Services 3 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: #50071: Unable to connect to the database SharePoint_ConfigDB on SERVERNAME.  Check the database connection information and make sure that the database server is running..

------------------------------------

Event Type:    Error
Event Source:    Office SharePoint Server
Event Category:    Office Server General
Event ID:    7888
Date:        12/15/2009
Time:        10:00:00 PM

User:        N/A
Computer:    SERVERNAME
Description:
A runtime exception was detected. Details follow.
Message: Cannot generate SSPI context.

Techinal Details:
System.Data.SqlClient.SqlException: Cannot generate SSPI context.
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.SSPIError(String error, String procedure)
   at System.Data.SqlClient.TdsParser.SNISSPIData(Byte[] receivedBuff, UInt32 receivedLength, Byte[] sendBuff, UInt32& sendLength)
   at System.Data.SqlClient.TdsParser.ProcessSSPI(Int32 receivedLength)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
   at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
   at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
   at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
   at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
   at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
   at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
   at System.Data.SqlClient.SqlConnection.Open()
   at Microsoft.Office.Server.Data.SqlSession.OpenConnection()
   at Microsoft.Office.Server.Data.SqlSession.ExecuteNonQuery(SqlCommand command)
   at Microsoft.Office.Server.Data.SqlDatabaseManager.HasAccess(String user)
   at Microsoft.Office.Server.Administration.SharedResourceProvider.SynchronizeConfigurationDatabaseAccess(SharedComponentSecurity security)
   at Microsoft.Office.Server.Administration.SharedResourceProvider.SynchronizeAccessControl(SharedComponentSecurity sharedApplicationSecurity)
   at Microsoft.Office.Server.Administration.SharedResourceProvider.Microsoft.Office.Server.Administration.ISharedComponent.Synchronize()

------------------------------------

Event Type:    Error
Event Source:    Office SharePoint Server
Event Category:    Office Server Shared Services
Event ID:    6482
Date:        12/15/2009
Time:        10:00:00 PM

User:        N/A
Computer:    SERVERNAME
Description:
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (186d46cf-1f2b-4b6b-bee5-8d1fdd6595bd).

Reason: Could not access the Search service configuration database 

Techinal Support Details:
Microsoft.Office.Server.Search.Administration.DatabaseException: Could not access the Search service configuration database   ---> System.Runtime.InteropServices.COMException (0xC004122D): Could not access the Search service configuration database 
   at Microsoft.Office.Server.Search.Administration.MSSITLB.IGatherApplications2.Mount(String bstrName)
   at Microsoft.Office.Server.Search.Administration.GathererApplication.ProvisionGathererApplication()
   at Microsoft.Office.Server.Search.Administration.GathererApplication.Provision()
   at Microsoft.Office.Server.Search.Administration.OSSIndexGathererApplication.Provision()
   at Microsoft.Office.Server.Search.Administration.SearchApi.<>c__DisplayClass20.<AddApp>b__1f()
   at Microsoft.Office.Server.Search.Administration.SearchApi.RunOnServer[T](CodeToRun`1 remoteCode, CodeToRun`1 localCode, Boolean useCurrentSecurityContext, Int32 versionIn)
   --- End of inner exception stack trace ---
   at Microsoft.Office.Server.Search.Administration.SearchApi.RunOnServer[T](CodeToRun`1 remoteCode, CodeToRun`1 localCode, Boolean useCurrentSecurityContext, Int32 versionIn)
   at Microsoft.Office.Server.Search.Administration.SearchApi.AddApp(Role role)
   at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.InstallGathererApplicationIf()
   at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
   at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

------------------------------------

Event Type:    Error
Event Source:    Office Server Search
Event Category:    Gatherer
Event ID:    10034

Date:        12/15/2009
Time:        10:00:00 PM

User:        N/A
Computer:    SERVERNAME
Description:
Could not access the Search service configuration database.

Context: Application 'a28d676e-5f73-476d-1212-a80c32826604'

Details:
    Unspecified error
(0x80004005)

------------------------------------

Event Type:    Error
Event Source:    Office Server Search
Event Category:    Gatherer
Event ID:    10036

Date:        12/15/2009
Time:        10:00:00 PM

User:        N/A
Computer:    SERVERNAME
Description:
A database error occurred.

Source: Microsoft OLE DB Provider for SQL Server
Code: 0 occurred 1 time(s)
Description: Cannot generate SSPI context

Context: Application 'a28d676e-5f73-476d-1212-a80c32826604'

------------------------------------

Event Type:    Error
Event Source:    Windows SharePoint Services 3
Event Category:    Database
Event ID:    5586

Date:        12/15/2009
Time:        10:00:00 PM

User:        N/A
Computer:    SERVERNAME
Description:
Unknown SQL Exception 0 occured. Additional error information from SQL Server is included below.

Cannot generate SSPI context.

------------------------------------

This issue may happen if the time on the Servers in the SharePoint Farm is not in sync with the Domain Controller. Verify that the time on the Servers in the SharePoint Farm is in sync with the Domain Controller.

THIS POST APPLIES TO

• Microsoft Office SharePoint Server 2007

• If the computer that is running Windows SharePoint Services has insufficient free disk space that is available to host the restored Windows SharePoint Services Web site. This issue may also occur if the Windows SharePoint Services database has reached its maximum allowed size.

https://support.microsoft.com/kb/926061

• There is some issue with network or the Network Interface Cards(NIC) are not operating at same bandwidth on the SQL Server and the SharePoint Server. In this case there is possibility of timeout happening.

• TCP Chimney is enabled on the SQL Server and the SharePoint Server.

• A SQL query timeout is happening.

You can try to resolve this issue by following the steps given below:

• Disable TCP Chimney on the SQL Server and the SharePoint Server and reboot the servers.

• Check the event viewer on the SharePoint Server where you are trying the restore from and see if you see event id stating there was a long running SQL query(xxxx seconds) which was cancelled because it exceeded the threshold of xxxx seconds. If you see the event id then on the SQL Server disable the query governor that prevents long-running queries and set remote query timeout to 0(which means no timeout).

i.e. Go to “SQL Server Properties->Connections” and uncheck “Use query governor to prevent long-running queries”. Also, set “Remote query timeout” to 0.

• Verify that NIC on the SQL Server and the SharePoint Server are operating at same bandwidth and updated the NIC drivers.

• Verify that the SQL Server Drive that is hosting the DBs(Content DB and Temp DB) has adequate free space, 2 to 4 times the backup size(this is an approx figure). Also, the SharePoint Server from where the restore is done should have adequate free space, 2 times(this is an approx figure) the backup size.

NOTE: Always note the modifications that you make, so that if necessary they can be reverted.

THIS POST APPLIES TO

• Microsoft Office SharePoint Server 2007
• Microsoft Windows SharePoint Services 3.0

After you install SP2 for WSS 3.0 the crawl and in turn the search does not work for host header mode sites. The issue happens on the web app which does not have a top level site collection.

In the event log, following error is seen:

Event Type:           Warning

Event Source:       Windows SharePoint Services 3 Search

Event Category:    Gatherer

Event ID:                2436

Date:                      8/6/2009

Time:                      11:30:10 AM

User:                      N/A

Computer:             HMC35WSS02

Description:

The start address <sts3://hmc35wss02-7.earthhmc35.com/contentdbid={71473f09-c10f-433e-b55b-8d32439b3339}> cannot be crawled.

Context: Application 'Search index file on the search server', Catalog 'Search'

Details:

                The object was not found.   (0x80041201)

To resolve the issue August CU(https://support.microsoft.com/kb/973410) can be installed.

THIS POST APPLIES TO

• Windows SharePoint Services 3.0

The issue can happen if the Master Pages gallery does not have correct permissions. To resolve this issue verify whether the site owners have at least read  permission to the Master Pages gallery.

You can find the Master Pages gallery at: https://sharepointsite/_catalogs/masterpage/Forms/AllItems.aspx

2. For a site having Collaboration Portal template applied

The issue can happen if the Master pages and page layouts  gallery does not have correct permissions. To resolve this issue verify whether the site owners have at least read only permission to the Master pages and page layouts gallery and additionally the Style Resource Readers group has read permission to the Master pages and page layouts gallery.

You can find the Master pages and page layouts gallery at: https://sharepointsite/_catalogs/masterpage/Forms/AllItems.aspx

THIS POST APPLIES TO

• Microsoft Office SharePoint Server 2007

Home Page

·         Windows SharePoint Services 3.0

·         Office SharePoint Server 2007

·         Windows SharePoint Services 2.0

·         SharePoint Portal Server 2003 

Downloadable Content

·         Office SharePoint Server 2007 Technical Library

·         Search Server 2008 Technical Library

·         Windows SharePoint Services 3.0 Technical Library

·         SharePoint Portal Server 2003 Administrator's Guide

·         SharePoint Portal Server 2003 Help

·         Windows SharePoint Services 2.0 Administrator's Guide

·         Windows SharePoint Services 2.0 Help

• Microsoft Office SharePoint Server 2007
• Microsoft Search Server 2008
• Microsoft Windows SharePoint Services 3.0
• Microsoft SharePoint Portal Server 2003
• Microsoft Windows SharePoint Services 2.0

When users try to run spell check on any of the list items in a SharePoint web application they get the following error:

"Spelling did not complete properly. If this problem persists, notify your system administrator."

The issue occurs because following user permissions for the web application are not checked.

1. Use Remote Interfaces.

2. Use Client Integration Features.

To resolve this issue, check the following user permissions for the web application from "Central Administration > Application Management > User Permissions for Web Application".

1. Use Remote Interfaces.

2. Use Client Integration Features.

THIS POST APPLIES TO

• Microsoft Office SharePoint Server 2007
• Microsoft Windows SharePoint Services 3.0

On a SharePoint Server 2007 blog site, you have a posts lists, which has several posts in it. When you do a full crawl of the content source, the posts list is crawled successfully. However, when you do a search for a word in the individual post the search doesn't returns the URL of the individual post but it returns the URL of the posts list.