One.iam.com
Network Load Balancing Manager
New Cluster
When I add two.iam.com to the cluster, error message window pops up. The reason is because I use the same image for One and Two systems. I have to uninstall the NIC and reinstall NIC on two.iam.com.
Create a domain user iam\share
Before installing SharePoint, check:
One.iam.com:
After a web application created, you must create a site collection for it.
Check IIS:
Upload several documents to SharePoint site
Enable Search service
Do a search task
Assign a search server to SharePoint site
After I restart the computer:One, "The search request was unable to connect to the Search Service" message displays when I initiate a search.
Set the "Windows SharePoint Services Search" to Automatic startup type and start it.
Search is successful.
Check SQLServer databases
Two.iam.com
installing SharePoint
Start Windows SharePoint Servics Help Search
To force "Windows SharePoint Services Search" to crawl the content, first add the directory to System environment variable path
C:\program files\common files\Microsoft Shared\web server extensions\12\bin
Restart system
stsadm -o spsearch -action fullcrawlstart
[WSS_Search_Two].[dbo].[MSSCrawlHistory] is empty. Why?
Event Viewer--DCOM
Solution:
Detach and drop both WSS_Search_one and WSS_Search_two database from SQL Server.
And delete the database files and log files.
From SharePoint Central Administration, restart "Windows SharePoint Services Search" on both One and Two computers. Set the schedule to5 minutes.
Select Windows SharePoint Services search server:
Server:One
Or, Server: Two
From SQL server,
SELECT TOP 1000 [CrawlID]
,[ProjectID]
,[CrawlType]
,[RequestTime]
,[Status]
,[StartTime]
,[EndTime]
,[SuccessCount]
,[ErrorCount]
,[WarningCount]
FROM [WSS_Search_TWO].[dbo].[MSSCrawlHistory]
SELECT TOP 1000 [CrawlID]
,[ProjectID]
,[CrawlType]
,[RequestTime]
,[Status]
,[StartTime]
,[EndTime]
,[SuccessCount]
,[ErrorCount]
,[WarningCount]
FROM [WSS_Search_ONE].[dbo].[MSSCrawlHistory]
Even though both computers have the Windows SharePoint Search service running, at one time, only one server provides the search service to SharePoint Content.
To use the Windows Network Load Balancing, I create a Public Zone URL which points to the cluster's address.
Does the WNLB work?
Computer: One
Create an image file:logo.jpg and put it in c:\program files\common files\Microsoft Shared\web server extensions\12\Templates\images
Computer:Two
Create an image file:logo.jpg and put it in c:\program files\common files\Microsoft Shared\web server extensions\12\Templates\images
IIS authentication
Alternate Access Mappings for http://cluster.iam.com
IIS
Directory Security: only Basic authentication
If you shutdown only one server, the other one still provides the service.
Event ID: 2424
Source:Windows SharePoint Service
Gategory:Gatherer
Type:Error
Description: The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again. Context: Application 'Search', Catalog 'index file on the search server Search'
Event ID: 2436
Source: Windows SharePoint Service
Category:Gatherer
Type:Warning
Description: The start address <sts3://one/contentdbid={664b8fa0-c54a-4bf9-9c89-4ff52e76daff}> cannot be crawled.
Context: Application 'Search index file on the search server', Catalog 'Search'
Details:
Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify that the account you are using has "Full Read" permissions on the SharePoint Web Application being crawled. (0x80041205)
That is why I enable both "Integrated authentication" and "Basic Authentication".
Another reason is "Alternate Access Mappings".
When you create a web address host header for a web application, make sure that an alternate access mapping is created for it. The Gatherer uses Alternate Access Mappings (AAM).
When "Windows SharePoint Services Search" and "Windows SharePoint Services Timer" fail to start, I have to retype the password and assign "Logon as Service" right.
The definitions of "Alternate Access Mappings" work:
SharePoint 3.0 does not crawl the external site. SharePoint 2007 claims that it can crawl the external site. I haven't test it.
IIS authentication method
When accessing the SharePoint web application from a workstation of domain IAM.COM with access permissions, a logon window will not show. The Integrated Windows authentication serves the purpose.
When accessing the SharePoint web application from a computer outside the domain IAM.COM, a logon windows pops up. You have to provide a domain user, e.g. iam\administrator.
When accessing SharePoint web application by http://two.iam.com, the event ID: 8214 is recorded.
The description for Event ID ( 8214 ) in Source ( Windows SharePoint Services 3 ) cannot be found. Either the component that raises this event is not installed on your local computer, or the installation is corrupted. You can install or repair the component on the local computer, or contact the component manufacturer for a newer version.
If the event was saved from another computer or forwarded from a remote computer, you might have to include display information with the events when saving them or when setting up the forwarding s A request was made for a URL, http://two.iam.com, which has not been configured in Alternate Access Mappings. Some links may point to the Alternate Access URL for the default zone, http://one. Review the Alternate Access mappings for this Web application at http://one:46661/_admin/AlternateUrlCollections.aspx and consider adding http://two.iam.com as a Public Alternate Access URL if it will be used frequently. Help on this error: http://go.microsoft.com/fwlink/?LinkId=114854.
When accessing SharePoint web application by http://one.iam.com, the event ID: 8214 is recorded.
Solution:
Based on the above "Alternate Access Mappings"
Search for the same item: vfx1
For http://one, the search result shows http://one/.
For http://cluster.iam.com, the search result shows http://cluster.iam.com. If http://one appears in the search result for http://cluster.iam.com URL, it means that Alternate Access Mappings must have a mistake.
SharePoint 3.0 does not implement the feature of "Map to External Resource in Alternate Access Mappings. Even though the configuration is simple, you cannot confirm whether it works or not.
Alternate Access Mapping-----Map to External Resource
SharePoint Service 2010
Standalone Installation
Ex2.vanarts.com hosts a web site.
SharePoint 2010 is installed on Dean computer.
SharePoint 2010 Central Administration
---System Settings--Manage services on server
--------SharePoint Server Search---Search Service Application
--------Content Sources--New
------------Name:Vanarts College
------------Type start addresses below (one per line)
--------------------http://ex2/default.htm
----Crawl Settings
----------Only crawl within the server of each start address
Check "Start full crawl of this content source" and click OK button.
Accessing the SharePoint site: http://dean
---Site Actions---New Site
------Title: Kaiming Search
------URL name: http://dean/search
------Select Template ---Enterprise--Basic Search Center
Click Create button
Without "Map to External Resource" defined (by default), search for a content that is hosted on ex2.vanarts.com.
Suppose the web site has a registered domain name: www.1ask2.com.
SharePoint 2010 Central Administration
System Settings--Configure Alternate access mappings
Click "Map to External Resource"
----Resource Name: Kaiming Resource
----URL: http://www.1ask2.com
Click "Add Internal URLs"
-----Alternate Access Mapping Collection: Kaiming Resource
-----URL:http://ex2
-----Zone:Default
Click Save button
Do a search
The result page of search has the http://www.1ask2.com, which can globally be accessed.