Please use Windows 2008 R2 SP1 + full updates as OS prerequisite to avoid the Search provisioning problem.The deployment guide doesn't mention specifically to install all updates, however this will be fixed in the next version of documentation. <o:p></o:p>
Alpesh Nakar's Blog
Alpesh
Just SharePointJust SharePoint Updates
Online SharePoint Saturday IndiaJune 25 2011
Contributing AuthorSharePoint 2010 Unleashed
MCTS: SharePoint 2010 Configuration MCITP: SharePoint 2010 Administrator
The three updates before installing the bits plus Windows Update did not solve the issue for me either.
I am trying to restore a SP2010 SSA using the database attach of the admin database.
Two items missing from all instructions that I have found:
Instructions say that if the process times out (which it has repeatedly for me), you must delete the database you were trying to restore and create an new one from the SQL backup. Don't forget to add permissions again. Yuck!
But now, the Hosting service is hung in starting mode again!
Where did I put that drawing board?
Daniel Webster MCT, MCSE: Security + Internet, MCSA, MCTS: MOSS07 Co-author, Microsoft SharePoint Server 2010 Administrator’s Pocket Consultant Contributing author, Microsoft SharePoint Server 2010 Administrator’s Companion http://www.linkedin.com/in/wdanielwebster www.summit7systems.com
Paul Stork SharePoint Server
MVP Senior Solutions Architect: BlueChip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.
teh*remo
Did a clean install on another system and I'm now seeing the same issue that you are with the Search Service. Usage Proxy still didn't start, but fixing that didn't fix the search service like it did last time. I guess it was just a matter of timing.
I did find out one new thing. If you read the installation guide online you'll find out that the prereqs installer doesn't install all the necessary hot fixes. There are three additional hotfixes that should be installed AFTER PSconfig.exe but before you actually start building out the system. Here are the links to download them.
and here's the article where they are referenced. Check step #6
http://technet.microsoft.com/en-us/library/ee805948(v=office.15)#PrepareServers
Paul Stork SharePoint Server
MVP Senior Solutions Architect: BlueChip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.
Paul Stork SharePoint Server
MVP Senior Solutions Architect: BlueChip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.
Hi Paul. The Usage proxy was not started, so I provisioned as you described. Unfortunately, it did not seem to make any difference. I am still getting the same event log as described in my original post and search has not changed.
Can you please clarify whether you were using SQL 2012 and separate servers for SQL, SharePoint and DC? Thanks!
Just interested if the Search Hosting service is started in Services on the Server.
I am having issues with creating a working search solution as well and that seems to be hanging for me.
Daniel Webster MCT, MCSE: Security + Internet, MCSA, MCTS: MOSS07 Co-author, Microsoft SharePoint Server 2010 Administrator’s Pocket Consultant Contributing author, Microsoft SharePoint Server 2010 Administrator’s Companion http://www.linkedin.com/in/wdanielwebster www.summit7systems.com
Take a look at the proxy for the Usage Service App. I suspect you will find that it is in a stopped state (At least it has been in the 4 farms I've setup so far on 2013). Once I re-provision usage and the Usage Proxy goes to started the problems I had with Search go away, Particularly the error message in Topology. here's the powershell I run to fix Usage.
$UP = Get-SPServiceApplicationProxy | where {$_.TypeName -like "Usage*"}
$UP.Provision()
Paul Stork SharePoint Server
MVP Senior Solutions Architect: BlueChip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.
Environment and topology setup:
Separate DC, SharePoint, SQL server.
SharePoint Server running Windows 2008 R2 SP1 with SharePoint 2013 Beta
SQL Server running Windows 2008 R2 SP1 with SQL Server 2012 [not installed SP1 CTP]
After creating the Search Service Application, the following issues arise:
In PowerShell, all search components are listed as available.
The following appears in the event viewer:
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (cf15c8c7-1980-4391-bd97-17de75c4dd5d).
Reason: Failed to connect to system manager. SystemManagerLocations: net.tcp://sp13beta/E0C7FF/AdminComponent1/Management
Technical Support Details:
System.InvalidOperationException: Failed to connect to system manager. SystemManagerLocations: net.tcp://sp13beta/E0C7FF/AdminComponent1/Management ---> System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at net.tcp://sp13beta/E0C7FF/AdminComponent1/Management/NodeController that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
Server stack trace:
at System.ServiceModel.Channels.ConnectionUpgradeHelper.DecodeFramingFault(ClientFramingDecoder decoder, IConnection connection, Uri via, String contentType, TimeoutHelper& timeoutHelper)
at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.SendPreamble(IConnection connection, ArraySegment`1 preamble, TimeoutHelper& timeoutHelper)
at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.DuplexConnectionPoolHelper.AcceptPooledConnection(IConnection connection, TimeoutHelper& timeoutHelper)
at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade)
at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Microsoft.Ceres.CoreServices.Services.Node.INodeControllerManagementAgent.get_NodeName()
at Microsoft.Ceres.CoreServices.Tools.Management.Client.AbstractSystemClient.TryConnect(Uri nodeManagementUri, ICollection`1 locationsToTry, ICollection`1 triedLocations, ICollection`1 nodeSystemManagerLocations)
--- End of inner exception stack trace ---
at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)
Search has been recreated multiple times manually, first with using separate application pool IDs for search admin and query services. Later attempts used only the farm service account as app pool IDs, with no change in results. Also tried creating search through the ‘evil’ farm configuration wizard, with no change in results.
Hi,
I was setting up SharePoint 2013 on Windows Server 2012 with SQL 2012.
I also had the problems described obove:
Search Administration in Central Admin:“Unable to retrieve topology component health states. This may be because the admin component is not up and running.”
I did the whole search configuration via PowerShell. I always got an error while activating the search topology ($SearchTopology.Activate()).
My Solution: I gave db_owner rights on all search databases and local admin rights on all search servers to the search service account. After activating the topology I could remove those rights again.
Search works now for me. Sutiuation reminds me of installing the user profile service in sp14. :-)
Same issue for me as well with:
1 x Server 2012 DC
1 x SharePoint Foundation 2013 & SQL 2012 Express on member Server 2012
Local SharePoint content is a source for crawl but not enabled. When enabled simply gets stuck on "Started".
Anyone have a solution?
Thanks Robert Crane [MVP-Office365] www.ciaops.com
I am now getting this with Windows Server 2012 on both SharePoint 2013 server and SQL 2012 server after a reboot.
Regards
Nigel