SharePoint 2013 Search not provisioning correctly
-
Thursday, July 19, 2012 10:08 AM
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:
- The search topology displays the following message: “Unable to retrieve topology component health states. This may be because the admin component is not up and running.”
- The default content source “Local SharePoint Sites” is inconsistent. It doesn’t always appear after creation of Search, sometimes with start addresses of existing web apps listed already, other times not.
- Starting a full crawl results in stuck in ‘starting’.
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.
All Replies
-
Thursday, July 19, 2012 11:17 AM
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. -
Thursday, July 19, 2012 11:33 AM
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
-
Thursday, July 19, 2012 11:52 AMHi Daniel. Yes, Search Host Controller service is started. Haven't noticed any issues with the service itself not being started at any point.
-
Thursday, July 19, 2012 12:29 PM
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!
-
Thursday, July 19, 2012 3:43 PMI am having the same error message “Unable to retrieve topology component health states. This may be because the admin component is not up and running.” and when I try to run a crawl it hangs in the "Starting" state. In my case everything is on one machine and it's a domain controller. I am wondering if it has something to do with the fact that its a DC, because in another environment I connected to a domain and search worked fine
-
Thursday, July 19, 2012 7:26 PMI'm using seperate servers, but using SQL 2008.
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. -
Saturday, July 21, 2012 1:54 PM
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. -
Saturday, July 21, 2012 2:55 PM Installing all the Windows updates solved the problem for me....So yes, the hotfixes might do the trick as well...
- Edited by superkeks0r Saturday, July 21, 2012 2:56 PM
- Proposed As Answer by Neil Barkhina Monday, July 23, 2012 12:23 PM
- Marked As Answer by dplotnikov - mvpMVP, Editor Tuesday, July 31, 2012 4:29 PM
-
Monday, July 23, 2012 12:23 PMInstalling the windows updates fixed it for me, Thanks superkeks0r!
- Edited by Neil Barkhina Monday, July 23, 2012 12:24 PM typo
-
Tuesday, July 24, 2012 6:05 PMI had the same issue, installing all the Windows Updates fixed the issue. I had a clean install of Server 2008 R2 SP1, there were 55 Important Windows Updates that it installed, now everything works great.
teh*remo
-
Thursday, July 26, 2012 12:52 PMInstalling the 3 hotfixes I referenced above was not enough for me. However like other's here running Windows Update and installing all the important updates finally fixed it for me also. I'm not real happy with that answer since I'm doing a client install on a server that is behind a firewall. I can't run windows update on that server. so now I have to go get the list of 55 updates, download them all manually, and install them. I would really like to know which ones are actually needed that aren't on the prerequisites list.
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. -
Thursday, July 26, 2012 1:27 PM
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:
- PowerShell does not use the SQL alias created by cliconfg. You must add to HOSTS file.
- PowerShell cmdlet does not add permissions to the restored admin database. You must manually give the farm account, account running the script, and search service account dbo on the database.
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
-
Friday, July 27, 2012 6:25 AMSame here, the 3 hotfixes didn't solve the problem - ended up doing the updates and that resolved the issue.
Alpesh Nakar's Blog
Alpesh 
Just SharePoint
Just SharePoint Updates
Online SharePoint Saturday India
June 25 2011 
Contributing Author
SharePoint 2010 Unleashed
MCTS: SharePoint 2010 Configuration
MCITP: SharePoint 2010 Administrator
-
Friday, July 27, 2012 1:23 PM
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>
-
Friday, July 27, 2012 5:09 PMThat's really NOT an acceptable answer. A lot of companies place SharePoint installations behind a firewall where running Windows Update is impossible. when I ran Windows updated on my dev environment I had to apply 53 important updates post Service pack 1. Microsoft has already identified 3 updates that weren't included in the prerequisites installer. They need to identify which of the 53 updates are needed for Search to initialize or at the very least list them out with where to download them. Simply telling people to run Windows update to patch their environment isn't good enough.
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. -
Monday, July 30, 2012 1:28 PM
The deployment documentation that was provided with the SharePoint2013 Preview has a missing pre-requisite.
(This pre-req was not missing in Beta1 and Beta1 Refresh deployment doc)
A documentation bug has been filed.
The pre-requisite is to fully update your server before installing SharePoint.
As for the provisioning the SSA, It is recommended to use the config wizard. The PS cmdlet have changed from O14 and the new cmdlets have not been documented yet.
-
Monday, July 30, 2012 5:17 PMAs I mentioned above. Its not really acceptable to just say "fully update your server". This is absolutely no help at all for corporate clients who have rules about applying untested updates or which isolate test servers behind firewalls and don't allow access to the Internet. At the very least you need to provide a comprehensive list of the necessary prerequisites.
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. -
Tuesday, July 31, 2012 8:52 AM
Not until yesterday have I had a chance to troubleshoot further on this issue, but have also found that Windows Update resolved the issue. But as Paul stated, would be good to know from Microsoft what specific hotfix[es] resolved the issue.
-
Tuesday, July 31, 2012 10:45 AM
Hi, Paul.
Can you list that 53 updates which applied on your dev environment?
-
Tuesday, July 31, 2012 1:27 PM
Here's the list of the 53 updates installed by Windows Update. Please also note the 3 hotfixes mentioned in the online installation documentation (and an earlier reply) that should also be installed.
Security Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server 2008 R2 SP1 for x64-based Systems (KB2656356)
Security Update for Windows Server 2008 R2 x64 Edition (KB2690533)
Security Update for Windows Server 2008 R2 x64 Edition (KB2584146)
Security Update for Windows Server 2008 R2 x64 Edition (KB2570947)
Security Update for Windows Server 2008 R2 x64 Edition (KB2658846)
Security Update for Windows Server 2008 R2 x64 Edition (KB2685939)
Security Update for Windows Server 2008 R2 x64 Edition (KB2667402)
Security Update for Windows Server 2008 R2 x64 Edition (KB2698365)
Security Update for Windows Server 2008 R2 x64 Edition (KB2425227)
Security Update for Windows Server 2008 R2 x64 Edition (KB2511455)
Security Update for Windows Server 2008 R2 x64 Edition (KB2654428)
Security Update for Windows Server 2008 R2 x64 Edition (KB2655992)
Security Update for Internet Explorer 8 for Windows Server 2008 R2 x64 Edition (KB2544521)
Cumulative Security Update for Internet Explorer 8 for Windows Server 2008 R2 x64 Edition (KB2699988)
Security Update for Windows Server 2008 R2 x64 Edition (KB2536275)
Security Update for Windows Server 2008 R2 x64 Edition (KB2643719)
Security Update for Windows Server 2008 R2 x64 Edition (KB2688338)
Update for Windows Server 2008 R2 x64 Edition (KB2506014)
Cumulative Security Update for ActiveX Killbits for Windows Server 2008 R2 x64 Edition (KB2618451)
Security Update for Windows Server 2008 R2 x64 Edition (KB2645640)
Security Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server 2008 R2 SP1 for x64-based Systems (KB2686831)
Security Update for Windows Server 2008 R2 x64 Edition (KB2560656)
Update for Windows Server 2008 R2 x64 Edition (KB2718704)
Security Update for Windows Server 2008 R2 x64 Edition (KB2653956)
Security Update for Windows Server 2008 R2 x64 Edition (KB2659262)
Windows Malicious Software Removal Tool x64 - July 2012 (KB890830)
Security Update for Windows Server 2008 R2 x64 Edition (KB2709715)
Security Update for Windows Server 2008 R2 x64 Edition (KB2507618)
Security Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server 2008 R2 SP1 for x64-based Systems (KB2604115)
Security Update for Windows Server 2008 R2 x64 Edition (KB2691442)
Security Update for Windows Server 2008 R2 x64 Edition (KB2621440)
Security Update for Windows Server 2008 R2 x64 Edition (KB2510531)
Update for Windows Server 2008 R2 x64 Edition (KB2533552)
Security Update for Windows Server 2008 R2 x64 Edition (KB2509553)
Security Update for Windows Server 2008 R2 x64 Edition (KB2631813)
Security Update for Windows Server 2008 R2 x64 Edition (KB2536276)
Security Update for Windows Server 2008 R2 x64 Edition (KB2506212)
Update for Windows Server 2008 R2 x64 Edition (KB2633952)
Security Update for Windows Server 2008 R2 x64 Edition (KB2620712)
Security Update for Windows Server 2008 R2 x64 Edition (KB2676562)
Update for Windows Server 2008 R2 x64 Edition (KB2677070)
Security Update for Windows Server 2008 R2 x64 Edition (KB2718523)
Update for Windows Server 2008 R2 x64 Edition (KB2552343)
Security Update for Windows Server 2008 R2 x64 Edition (KB2567680)
Security Update for Windows Server 2008 R2 x64 Edition (KB2564958)
Security Update for Windows Server 2008 R2 x64 Edition (KB2620704)
Security Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server 2008 R2 SP1 for x64-based Systems (KB2656411)
Security Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server 2008 R2 SP1 for x64-based Systems (KB2656373)
Security Update for Windows Server 2008 R2 x64 Edition (KB2585542)
Security Update for Windows Server 2008 R2 x64 Edition (KB2719985)
Security Update for Windows Server 2008 R2 x64 Edition (KB2644615)
Update Rollup for ActiveX Killbits for Windows Server 2008 R2 x64 Edition (KB2695962)
Update for Windows (KB974405)
Update for Windows (KB2506143)I'm not sure which of these updates did the trick for search, but one or more of them seem to be necessary.
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. -
Tuesday, July 31, 2012 3:35 PM
We are working with the product group to make sure the specific windows updates + hotfixes that are required for Search to work are identified and documented properly. Thanks for raising this issue and sorry for the inconvenience!
-
Wednesday, August 01, 2012 7:21 AM
Hi, All
After some hours of research i found that we need to install update KB2567680. And in test environment each time so interesting spend some hours on configuring gate to internet, downloading and installing all updates. But for me I can find more interesting things for research than doing unnecessary things.
- Proposed As Answer by Roman Levchenko Wednesday, August 01, 2012 7:21 AM
-
Wednesday, August 01, 2012 12:58 PMThanks for the work. I'll give this a try when I get a chance to verify it. Do you just need KB2567680 or all the other Security updates that precede it too?
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. -
Thursday, August 02, 2012 5:23 AM
Hi.
I installed 3 updates previously mentioned, and KB2567680. After that search provision from powershell correctly. I didn't test provision without that 3 updates.
PS interesting: social.technet stop working for reply from mozilla (nothing happens). I need to open IE login on social.technet and copy reply from mozilla...
- Proposed As Answer by Alpesh NAKAR Monday, August 06, 2012 5:37 AM
-
Monday, August 06, 2012 5:40 AM
Can confirm 100 % that 4 updates are all that needed for Search Service to work!
Great work, thanks.
I have a powershell script to provision SP2013Preview Search Service Application - http://alpesh.nakars.com/blog/create-search-service-application-with-powershell/
Big thanks!
Alpesh Nakar's Blog
Alpesh
Just SharePoint
Just SharePoint Updates Online SharePoint Saturday India
June 25 2011 Contributing Author
SharePoint 2010 Unleashed MCTS: SharePoint 2010 Configuration
MCITP: SharePoint 2010 Administrator
- Proposed As Answer by Ed Barnett - MSFT Tuesday, August 07, 2012 11:54 AM
- Unproposed As Answer by Ed Barnett - MSFT Tuesday, August 07, 2012 11:54 AM
-
Tuesday, August 07, 2012 12:03 PM
Hello All
some great individual Work here from the Community
As a colleague has posted earlier we have been working with the Product Group to resolve this issue
Problem Description :
After creating the Search Service Application, the following issues arise:
- The search topology displays the following message: “Unable to retrieve topology component health states. This may be because the admin component is not up and running.”
- The default content source “Local SharePoint Sites” is inconsistent. It doesn’t always appear after creation of Search, sometimes with start addresses of existing web apps listed already, other times not.
- Starting a full crawl results in stuck in ‘starting’.
EVENT:
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)
CAUSE:
a System Issue that prevents the DLL responsible for the ADmin Component to load succesfully
RESOLUTION:
Install KB 2567680
in addition to the three hotfixes
KB 2554876 , KB 2708075 , KB 2472264 recommended in the doc
http://technet.microsoft.com/en-us/library/ee805948(v=office.15)#PrepareServers
We are currently working to update the Prerequistes checker / Preinstaller for this KB update Aswell as
working on a permanent Product update to resolve this .
Again aplogies for the frustrations this has caused and any delays in getting your Sharepoint 2013 Priew builds up and running.
KR
Sharepoint 2013 Preview Beta Search Team
- Proposed As Answer by Paul stork, MVPMVP Tuesday, August 07, 2012 12:17 PM
- Marked As Answer by Sara Windhorst UK Tuesday, August 14, 2012 1:19 PM
-
Sunday, October 07, 2012 9:44 AM
Hi Everyone
Looks like great work by a lot of people here to fix search in Windows 2008 R2, what about those of us with Windows Server 2012 ?
Do we have an equivalent list of hotfixes etc for Windows 2012 ? or is that on a separate forum post ?
Thanks
Nigel
-
Monday, October 08, 2012 10:06 PM
I am now getting this with Windows Server 2012 on both SharePoint 2013 server and SQL 2012 server after a reboot.
Regards
Nigel
-
Thursday, October 25, 2012 10:30 PM
no update left for me to update!
download all those hotfixes as well ... still same issue.
i guess not good idea to go for SPS2013 on beta way too much bugs. personally tons of issues and it keep poping up more...
-
Saturday, October 27, 2012 4:55 PMdid clean install install all those fixes, remove loopback ... and still it keep fail on crawling, it suppose to be easier not weirder than its predecessor SPS 2010
-
Sunday, November 04, 2012 8:12 PM
I am now getting this with Windows Server 2012 on both SharePoint 2013 server and SQL 2012 server after a reboot.
Regards
Nigel
Having same problem: 3 VM's W2K12 (1 DC, 1 SQL 2012, 1 SharePoint). Adding more options to roles and features made it work. can't say which options but at least app server and web server, perhaps also .net35 -
Monday, December 17, 2012 3:47 AM
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
- Edited by directorciaMVP Monday, December 17, 2012 3:52 AM correction
-
Thursday, January 10, 2013 1:45 PMHave some issue on Sharepoint Server 2013, but on Windows 2012 Server
- Edited by yeaster Thursday, January 10, 2013 1:45 PM
-
Friday, January 18, 2013 3:22 PM
Hi,
I was setting up SharePoint 2013 on Windows Server 2012 with SQL 2012.
- SP15 RTM
- 2 WFE Servers
- 2 Application Servers
- All Search Components on both Application Servers
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. :-)
.png)
