Hi Adam,I ran into similar situation with Windows Box and TS 6.7.1. I believe if you update the branches.cfg at time, you will not run into the issue.Second and I do not have stuff handy right now, but this will require some trials. Did you try deleting idex for this specific branch, remove entry of this branch from branches.cfg and then try and run the index service.
How does one remove an index for a specific branch (without using an iwndx* CLT - which won't work because the index server won't run)?
Adam - As I remember there is a command for this.. I am totally off hook on Idexing right now so please forgive me if its incorrect information..But something like "Purge" clt is there..`basically destroys the previously created index of a branch.....If purge is not the option then I would go ahead a manually delete the branch index file ..Again - i am off hook.. so this may be completely a failure experiment..
what about recreating "/default/main/test_branch" as an empty branch.. restarting the indexer and then running the CLT.. seems odd that you would have to do that.. but just a thought..
That's a reasonable work-around (annoying, but reasonable) - I'll try to remember to test that out on Monday.
hi Adam,Another thing, you can try is as follows.. Add the previous branch entry back to branches.cfg... Add the branch to Teamsite again. Run your index service and see if it comes up then..If it does, you can run the iw clts then to remove the branch from the index..
The only way that I was able to get around this was to stop all services and delete the search index and start the services. The index was recreated. Luckily I had a small store so it was not that painful. Lesson learned is that you should not just delete branches that are indexed and should purge them from index first.
