However, during the test, the "error message 1" below popped up. It happened when I tried to deploy query and crawl component to more than one server. And "error message 2" came out when trying to search keywords from site, which make me feel worse.
Luckily, the error message itself points out the problem: something wrong with the shared folders. When come to "SharePointLocationDrive:\Program Files\Microsoft Office Servers\14.0\Data\Office Server\Applications", we can see the screenshot below:
My first guess is, the PowerShell script forgot to "reset" these shared folders during the re-installation. That guess turns out correct. So, to fix this problem, we need to delete "Search Service Application", then un-tick the "Share this folder" check box, then create "Search Service Application" again.
By the way, AutoSPInstaller is splendid!
-------------------- error message 1 ---------------------
Microsoft.Office.Server.Search.Administration.SearchConfigWizard+SearchConfigWizardException:
Topology provisioning failed due to an error.Topology activation was aborted
because of System.ArgumentException: File to copy \\PDSHA02\d18d40ce-9085-4564-8337-462fc3c00c7e-query-0\d18d40ce-9085-4564-8337-462fc3c00c7e-query-0\Projects\AnchorProject\Indexer\CiFiles\01020001.bsd
does not exist on PDSHA02. at
Microsoft.Office.Server.Search.Administration.CopyFilesJob.Initialize() at
Microsoft.Office.Server.Search.Administration.CopyFilesJob..ctor(SPService
owningService, SPServer serverToRunOn, String name, Guid searchApplicationId,
String[] sourcePaths, String[] destinationPaths) at
Microsoft.Office.Server.Search.Administration.SearchApi.RequestFileCopy(String
fileCopyName, String serverNameToRunOn, Guid searchAppId, String[] sourcePaths,
String[] destinationPaths) at
Microsoft.Office.Server.Search.Administration.QueryComponent.RequestRepartitionIndexesFiles(QueryComponent
component) at Microsoft.Office.Server.Search.Administration.QueryComponent.CopyRepartitionIndexes(QueryComponent
component) at
Microsoft.Office.Server.Search.Administration.QueryComponent.ExecuteCurrentStage().
To retry the activation, run the cmdlet Set-SPEnterpriseSearchQueryTopology
-Active. If the error persists, restart the activation by calling the
CancelActivate() method on the query topology object, and then calling
Set-SPEnterpriseSearchQueryTopology -Active. at
Microsoft.Office.Server.Search.Administration.SearchConfigWizard.WaitForTopologyTimerJobToFinish()
at Microsoft.Office.Server.Search.Administration.SearchConfigWizard.UpdateSearchApp()
at
Microsoft.Office.Server.Search.Administration.SearchConfigWizard.ProvisionSearchServiceApplication()
at
Microsoft.Office.Server.Search.Administration.SearchConfigurationJobDefinition.ExecuteTimerJob()
Microsoft.Office.Server.Search.Administration.SearchConfigWizard+SearchConfigWizardException:
Topology provisioning failed due to an error.An object of the type
Microsoft.Office.Server.Search.Administration.QueryComponentTransitionTimerJob
named "Query component 86f2a28c-9f0d-43fa-97c6-d4006ef01aa6-query-0
background processing" already exists under the parent
Microsoft.Office.Server.Search.Administration.SearchService named
"OSearch14". Rename your object or delete the existing object. at
Microsoft.Office.Server.Search.Administration.SearchConfigWizard.WaitForTopologyTimerJobToFinish()
at
Microsoft.Office.Server.Search.Administration.SearchConfigWizard.UpdateSearchApp()
at Microsoft.Office.Server.Search.Administration.SearchConfigWizard.ProvisionSearchServiceApplication()
at
Microsoft.Office.Server.Search.Administration.SearchConfigurationJobDefinition.ExecuteTimerJob()
-------------------- end of error message 1 ---------------------
-------------------- error message 2 ---------------------
09/19/2011 09:14:08.21
w3wp.exe (0x17F8)
0x13C4 SharePoint
Foundation
Topology
b9h6
Medium
The
configuration database was queried for a non-existent object with the id
2f2aa19c-c66a-4b87-8ce1-15e4ee98b043. Most commonly, this is caused by removing
an SPFeatureDefinition without writing upgrade code to remove references to the
feature from each site. 8032d8fe-3368-445e-b8d0-f634583844bd
09/19/2011 09:14:08.27
w3wp.exe
(0x17F8)
0x13C4 SharePoint
Foundation
Topology
fg5f High
The service application instance unprovisioning job has completed
for service application with name '040f792c-bb2a-4b38-9a5d-c60a21a51cfb' and
type 'Microsoft.Office.Server.Search.Administration.SearchAdminWebServiceApplication'.
8032d8fe-3368-445e-b8d0-f634583844bd
09/19/2011 09:14:08.27
w3wp.exe
(0x17F8)
0x13C4 SharePoint
Foundation
Topology
fg53
High Unprovisioning the service application with
name '040f792c-bb2a-4b38-9a5d-c60a21a51cfb' and type
'Microsoft.Office.Server.Search.Administration.SearchAdminWebServiceApplication'.
8032d8fe-3368-445e-b8d0-f634583844bd
09/19/2011 09:14:08.27
w3wp.exe
(0x17F8)
0x13C4 SharePoint Foundation
Topology
8xqz
Medium
Updating SPPersistedObject SearchAdminWebServiceApplication
Name=040f792c-bb2a-4b38-9a5d-c60a21a51cfb. Version: 17641 Ensure: False,
HashCode: 1825769, Id: 6b9ad0f7-dc6d-4465-b576-17c723da5b37,
Stack: at
Microsoft.SharePoint.Administration.SPPersistedObject.BaseUpdate()
at
Microsoft.SharePoint.Administration.SPIisWebServiceApplication.Update()
at
Microsoft.SharePoint.ApplicationPages.ServiceApplicationDeletePage.OkButton_Click(Object
sender, EventArgs e) at System.EventHandler.Invoke(Object
sender, EventArgs e) at
System.Web.UI.WebControls.Button.OnClick(EventArgs e)
at System.Web.UI.WebControls.Button.RaisePostBackEvent(String
eventArgument) at
System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl,
String eventArgument) at System.Web.UI.P...
8032d8fe-3368-445e-b8d0-f634583844bd
09/19/2011
09:14:08.27*
w3wp.exe
(0x17F8)
0x13C4 SharePoint
Foundation
Topology
8xqz Medium
...age.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean
includeStagesAfterAsyncPoint) at
System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint,
Boolean includeStagesAfterAsyncPoint) at
System.Web.UI.Page.ProcessRequest() at
System.Web.UI.Page.ProcessRequest(HttpContext context)
at ASP._admin_serviceapplicationdelete_aspx.ProcessRequest(HttpContext
context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
completedSynchronously) at
System.Web.HttpApplication.PipelineStepManager.ResumeSteps(Exception
error) at
System.Web.HttpApplication.BeginProcessRequestNotification(HttpContext context,
AsyncCallbac...
8032d8fe-3368-445e-b8d0-f634583844bd
09/19/2011
09:14:08.27*
w3wp.exe
(0x17F8)
0x13C4 SharePoint
Foundation
Topology
8xqz
Medium
...k
cb) at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest
wr, HttpContext context) at
System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr
managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32
flags) at
System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr
managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32
flags) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr
managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32
flags) at
System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr
managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32
flags) 8032d8fe-3368-445e-b8d0-f634583844bd
09/19/2011 09:14:08.27
w3wp.exe
(0x17F8)
0x13C4 SharePoint
Foundation
Runtime
tkau
Unexpected
System.InvalidOperationException: The Search Administration Web Service
Application "Search Administration Web Service for SharePoint Server
Search" cannot be deleted. at
Microsoft.Office.Server.Search.Administration.SearchAdminWebServiceApplication.Delete(Boolean
force) at
Microsoft.SharePoint.ApplicationPages.ServiceApplicationDeletePage.OkButton_Click(Object
sender, EventArgs e) at
System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Web.UI.WebControls.Button.OnClick(EventArgs
e) at
System.Web.UI.WebControls.Button.RaisePostBackEvent(String
eventArgument) at
System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl,
String eventArgument) at
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint,
Boolean includeS...
8032d8fe-3368-445e-b8d0-f634583844bd
09/19/2011
09:14:08.27*
w3wp.exe
(0x17F8)
0x13C4 SharePoint
Foundation
Runtime
tkau
Unexpected ...tagesAfterAsyncPoint)
8032d8fe-3368-445e-b8d0-f634583844bd
09/19/2011 09:14:08.37
w3wp.exe
(0x17F8)
0x13C4 SharePoint
Foundation
Monitoring
b4ly
Medium
Leaving Monitored Scope (Request
(POST:http://pdsha02:9000/_admin/ServiceApplicationDelete.aspx?id=6b9ad0f7dc6d4465b57617c723da5b37&IsDlg=1)).
Execution Time=21481.3949817644 8032d8fe-3368-445e-b8d0-f634583844bd
09/19/2011 09:14:09.27
w3wp.exe
(0x17F8)
0x15C0 SharePoint
Foundation
Topology
e5mc Medium
WcfSendRequest: RemoteAddress: 'http://pdsha01:32843/edc6c9a514bc42458bfaac67b4721dc2/MetadataWebService.svc'
Channel: 'Microsoft.SharePoint.Taxonomy.IMetadataWebServiceApplication' Action:
'http://schemas.microsoft.com/sharepoint/taxonomy/soap/IDataAccessReadOnly/GetChanges'
MessageId: 'urn:uuid:83b09c11-ef25-43e5-b469-e77bf3fe537a'
-------------------- end of error message 2 ---------------------
It is not very clear to me whether you eventually created it by PowerShell or manually through CA. It looks like you first created it with PowerShell, then deleted and created it via CA… Do I understand you correctly?
ReplyDeleteHow did you manage to create neat database names in that scenario?
Sorry for replying late.
ReplyDeleteI was trying to do the job through PowerShell script directly, and soon I found the excellent tool "AutoSPInstaller"(http://autospinstaller.codeplex.com/).
This tool can help to initialize the whole SharePoint environment easily, and I can't live without it now.