Is this using verity? There used to be a problem if you used login policy = all. Best to stick to integratedonly or expliciton
Or if you are using encrytpted passwords, KB has an issue. Ask about problem 4770 with your local support provider
thanks for the suggestion but we are on 7.3.2 using Lucene for Knowledge.
Since I posted my original question I have logged it with LANDesk Support.
You say you are on 7.3.2 but do you know if the Patch 4770 has also been applied to your installation as well?
If so i think (had it myself) that the problem is that even though you've installed the patch, you still have an unencrypted password in your config file and why you get the wrong password message as it's thinking it is encrypted.
You need to run the "Touchpaper.Tools.KnowledgePassword.exe" utility to create the config password in encrypted form. Then start your service.
thanks for your suggestion. I have been waiting on feedback from a third-party who has been dealing with this issue.
However, I do not think this username / password is the problem since I have found that when I run the Console
on the server which hosts the application the Knowledge Search works OK.
This suggests that the problem is with access / permissions.
Presume you have the following setup in your tps.config files?
<add key="FreeTextSearchIndexPath" value="...unc path to KB share...." />
I have a real strange one on our environments where in my tps.configs on remote servers (to KB server) i use UNC path in the above strings BUT on the KB server itself this doesnt work and I need to instead use localhost for it to work.
Just throwing this out there...!