I have built a SharePoint 2013 environment and everything was successfully setup. Then I had to disconnect the SharePoint 2013 server from the Farm, then I reconnected it to the farm again using the SharePoint 2013 products configuration wizard, then I re-run the AutoSPInstaller script I used to install SharePoint 2013 originally and this time the search service application was not successfully provisioned (already provisioned during initial install via AutoSPInstaller).
In search service application search administration page, I get the following message under "Search Application Topology":
"Unable to retrieve topology component health states. This may be because the admin component is not up and running"
Has anyone come across this issue before? how was it resolved?
I have installed the required/additional hotfixes: KB2472264, KB2554876, KB2708075, KB2765317...
Would deleting the Search Service Application and the database (data) associated with it via central admin, then running the AutoSPInstaller script again fix this issue? has anybody tries this method?
Any suggestions would be greatly appreciated... I am tearing my hair out at this minute...
Thanks in advance
After much researching on the internet, the one thing that resolved this issue was to delete the search service application via central admin altogether and then re-provisioning it again. In my occasion this was provisioned via "AutoSPInstaller" which did the trick and resolved the message:
"Unable to retrieve topology component health states. This may be because the admin component is not up and running"
1.Remove corrupt search service applications:
http://pointsforsharing.com/Lists/Posts/Post.aspx?ID=5
2.Run powershell script:
$hostA = Get-SPEnterpriseSearchServiceInstance -Identity "YourServerName"
Start-SPEnterpriseSearchServiceInstance -Identity $hostA
$UP = Get-SPServiceApplicationProxy | where {$_.TypeName -like "Usage*"}
$UP.Provision()
Get-SPEnterpriseSearchServiceInstance –Identity $hostA
$hostA
I've gotten this working by installing these updates BEFORE INSTALLING SHAREPOINT. If I install these updates after installing SharePoint, I don't have much luck with this..
Related
i am approaching the development of Restful web services for the first time. I tried to follow this guide for Netbeans . I am stuck at the testing of the web service.
When i open the
http://localhost:8080/WebServicesTest/test-resbeans.html
page, none of the root resources appears in the left menu. (there should be entities.customer and entities.discountcode)
I really can't find a solution.
Thanks in advance to anyone who likes to give me a hint.
--------------- Edit
If i click on CustomerDB --> Deploy i get an error
In-place deployment at C:\Users\utente\Documents\NetBeansProjects\CustomerDB\build\web
GlassFish Server 4, deploy, null, false
C:\Users\utente\Documents\NetBeansProjects\CustomerDB\nbproject\build-impl.xml:1071:
The module has not been deployed.
See the server log for details.
The line 1071 of build-impl.xml is
<nbdeploy clientUrlPart="${client.urlPart}" debugmode="false" forceRedeploy="${forceRedeploy}"/>
I checked out the referenced tutorial.
Which exact path did you follow? Did you change anything?
Most likely your CustomerDB application is not deployed correctly (see GlassFish Server output in NetBeans) and thus is not able to expose the web service and thus is not displayed in the test page (nothing visible in the side bar).
I tried the tutorial myself and had that phenomenon when using another database ("test" instead of the sample db, which was not connectable in my installed environment), resulting in a message that "test__pm" resource was not found. I then created a conection pool and a jdbc reosurce for test and then it worked.
I have looked in quite a few places but all the information I have seen does not address my scenario. Please note that I can probably just make a new server for my SharePoint 2013 installation but I think this might be one of those gems for people who do not have that luxury and facing the same problem.
SCENARIO:
I uninstalled a functional SharePoint 2013 setup by
uninstalling SharePoint 2013 on the SharePoint Server and
manually deleting the databases on the remote SQL Server.
When I tried to reinstall SharePoint 2013 though I kept getting a 503 Error on the Central Administration page which appears to be due to the Central Administration AppPool stopping.
SUGGESTIONS I HAVE TRIED:
Check the password of the account running the AppPool service.
I did that and the account have Domain Administrator privileges and is capable of logging into the SQL Server without issue using the same password.
Try uninstalling IIS.
I uninstalled and reinstalled IIS and it made still gave the 503 error.
I read on a blog post (let me know if I can send the link) that "[he] need[ed] to clean up the content db, virtual directory and app pool properly next time."
I believe I did this but I may be missing something and that bit of stuck information is probably what is causing the issue.
Any thoughts?
Summary:
I have an Office 365 E3 account where I'm trying to deploy a Word task pane app that will read some SharePoint list data. Right now, I'm just trying to get the task pane app to load, however, it shows the Office 365 login page (in the pane) but does not do anything after clicking Login.
Details:
I went through the instructions provided here:
http://msdn.microsoft.com/en-us/library/office/fp179815.aspx
Basically, I create an App for SharePoint configured as SharePoint-hosted, then in the same project, added an App for Office (Task Pane App for Word only). The SharePoint app also has a custom document library.
I am able to install the app to my App Catalog, and it correctly shows up in Site Contents where I see it being provisioned to the app web. I can also launch Word 2013 with the Trusted App Catalog configured correctly, and I am able to see my Task Pane App and insert it. When I click Insert, it loads it but prompts for credentials.
I am using the same credentials all throughout this exercise so by virtue of being able to install and deploy the SharePoint app, you can trust that I'm providing the right credentials.
It also appears the custom document library is never created - I wonder if both suffer from the same underlying issue.
I encountered the same problem and the solution provided in the answer below did not help.
After some desparation i created a taskpane app using the Napa Cloud App, opened the application in Visual Studio and went looking for differences.
In the Taskpane app manifest.xml file i found the following entries which were missing in my own application manifest:
<AppDomains>
<AppDomain>https://login.microsoftonline-int.com</AppDomain>
<AppDomain>https://login.microsoftonline.com</AppDomain>
</AppDomains>
This solved my problem and cured one horrible friday.
I was able to get this to work. It turns out doing a Deploy from Visual Studio (whether you right-clicked Deploy or F5-debug), the installation of the app isn't enough.
To make it work, I skipped doing a Deploy all together, but instead published my app. I then took the .app file and loaded it in my App Packages folder, and then deployed it from there.
Unfortunately, I don't know the difference between the two, but I'm assuming it has something to do with provisioning the app web for the Office App.
I'm trying to create a Solr collection in ColdFusion 9. I have never used Solr before, but I am following the directions in Forta's Web Application Construction Kit.
Every time I go to create the collection, I get the following error:
Unable to create collection usaf.
Unable to create Solr collection usaf.
An error occurred while creating the collection: org.apache.solr.common.SolrException. Check the Solr logs for more detail.
Anyone have a clue what's wrong? I have read that the update to CF 9.0.1 causes some issues with Solr -- I tried installing that update and it failed several times. Could that be the problem?
If so, how to solve it? This is on a production Windows Server 2008 and a previous attempt to uninstall and reinstall forced us to restore the server from an image because it was such a disaster.
I know this is a bit old but here is what I did to fix the same problem. Solr service in CF Administrator wasnt showing the core collection and it wouldnt let me create a new collection (as per above).
Using Win7, CF9.0.1
Stopped the Search service and the Solr service via the windows service manager.
Edited the file ColdFusion9\solr\multicore\solr.xml and removed the entries for the collections I was working on at the time it all stopped working. This is the step that seems to have made the difference. Backup the file first!!!
For the entries I removed from solr.xml I also removed the collection folders and files completely from the file system using windows file manager.
Restarted the Search service and Solr service. Core collection now appears in CF Administrator. My CF pages now create and index collections as they should. Phew!
Cheers,
Murray
You can check CFAdmin under Data & Services > ColdFusion Collections to make Solr is running. Should be a default collection listed. If not, search runs as seperate services on Windows. Check that ColdFusion 9 Search Server and Solr Service are there and started.
Adobe has a standalone Solr install. http://www.adobe.com/support/coldfusion/downloads.html
Updating to 9.0.1 and hotfixes corrupted my Solr install. Had to reinstall CF from scratch.
It's also possible for the ColdFusion Solr Search Service to be running even though Solr is not. This can happen, for example, when there are errors in a collection's schema.xml file. I imagine there are other conditions under which this can happen. At any rate, as the poster above explained, if you look on CF Admin under "ColdFusion Collections" you should see at least the default Solr collection (core0). If you don't see that collection then Solr isn't running properly even if Windows tells you that the service is running.
Also, you may want to see if you can reach the Solr web service (port 8983 by default): http://localhost:8983/solr/
There could be 3 reasons for this:
1. Solr is not running.
2. Solr is running and if you are on Unix, Solr/CF is running as a non privileged user.
3. Solr is installed after CF. In that case go to CF Admin Data& Services->Solr Server(CF10) and provide solr home path.
It seems like solr service is timing out or not working properly for some reason.
First make sure that you can go to the Solr Admin UI on one host. Try http://hostname:8983/solr/ or http://localhost:8983/solr/ from RDP. If it is not working, then you will get the exact error or reason for why you are getting an error while adding CF collection. Most probably there should be CF collection which is not configured properly and you may remove those from 'ColdFusion9\solr\multicore\solr.xml'.
"TAKE A BACKUP IF YOU ARE TRYING TO MODIFY ANYTHING"
I had created a Team Project Collection and added a team project on TFS 2010 which was a created on a VMWare space. Of late my system administrator copied the image of the server and recreated it on to a new VMWare server due to space shortage.
Not sure if the given issue is occuring due to that but post the movement I am getting this error when trying to create a Team Project on TFS 2010
Error TF24023:
Team Foundation Server Configuration Failure. The New
Team Project Wizard work item component could not connect to the Team
Foundation Server \
Explanation
Contact the administrator for the Team Foundation Server
\ to confirm that the
server is available on the network. Also, you might find additional
helpful information in the project creation log. The log shows each
action taken by the wizard at the time of the failure and may include
additional details about the error.
User Action
The Project Creation Wizard was not able to connect to
the Team Foundation Server \. The reason for the failed connection cannot be
determined at this time.
The server is accessible and am able to work with my earlier created Team Project, but not able to create a new one as it tries to look at the servername\projectcollectionname instance as the server name. Can someone help to resolve this.
Tried searching the error number and the log related solutions and other forums but could not get any specifics related to my issue.
What is in the log files? Do you have SharePoint or SSRS configured? And are those configurations still valid?