As a Portal Search User, have you ever encountered such an error message while trying to search in PTC Knowledgebase?
Based on previous occurrences, some other things aside from browser type and cache can cause this issue. Recently, uBlock Origin was the most frequent cause of this Search malfunction.
We are suggesting below steps to self-diagnose first:
Step 1: Clear the browser cache and restart the browser.
Step 2: Try with another browser and see whether the issue still exists.
Step 3: Check the browser setting and configuration and see whether there is any adblocker blocking Search from functioning, for example, uBlock Origin.
Most of the time the above steps should be able to solve the issue. If not, continue with the following steps...
Step 5: Check if there is any network security restrictions or proxy issue in the local network. If possible, try from a different network.
Currently when searching for any reference documentation is returning zero results. See attached... a simple search for Creo Parametric 7 reference documents returns zero results. There should be a ton of results.
Responding quickly to acknowledge that the problem is on our side. At first look it seems like the index for Reference Documents is either disconnected or corrupted. I've pulled in the Enterprise Search team to investigate and resolve on highest urgency. We'll keep you updated as we make progress.
Thanks for letting us know,
Looks like they're working again. One question - is it normal to see other language articles mixed in with the results? I guess I would have thought the search would only return articles in the preferred language.
Our Search should only show English results for all Content Types if your eSupport language is set to English. If it's set to a language other than English, it attempts to find hits for the string / facets you've entered first of all in your chosen language, then queries the English indexes for the same.
So, in your case, it shouldn't show these Br-PT items.
I've let the Search team know and we'll aim to have this fixed as soon as possible.
Many thanks again,