Timeline for Solr Error When Rebuild xDB Search Index
Current License: CC BY-SA 4.0
8 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Sep 11, 2018 at 14:28 | comment | added | eglasius | @DuanLe glad it helped. Remember to flag the answer as accepted :) | |
Sep 11, 2018 at 9:13 | comment | added | Duan Le | Thanks! I followed the link that you provide and the issue was fixed | |
Sep 10, 2018 at 14:28 | comment | added | eglasius | That registers the rebuild request. If you run it again without the -rr, it will run the indexer in console mode and will start running the rebuild as well. The idea is to make sure to run the indexer in a way you can capture the traffic through fiddler (because it is problematic when running as a service). | |
Sep 10, 2018 at 12:07 | comment | added | Duan Le | sorry but how rebuild xdb search index process can run if you can stop Indexer Windows Service. I tried stop it and run 'XConnectSearchIndexer -rr' in CMD but it didn't work | |
Sep 10, 2018 at 11:14 | comment | added | eglasius | @DuanLe that makes it quite likely the same error. If you want to be extra sure, you can stop the indexer Windows Service and run it from the command line instead while running fiddler i.e. you can see the actual error Solr returns if the details are not making it to the log. | |
Sep 10, 2018 at 11:07 | comment | added | Duan Le | I only saw an unclear error in the indexer log : 2018-09-10 17:48:18.563 +07:00 [Error] An error occured. System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request) :(( | |
Sep 7, 2018 at 14:46 | history | edited | eglasius | CC BY-SA 4.0 |
added 11 characters in body
|
Sep 7, 2018 at 14:20 | history | answered | eglasius | CC BY-SA 4.0 |