Networks

Ask something
Discussion Locked

GW C05F Error on Search

0 helpful
5 replies

by chris.riley 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have recently upgraded a GroupWise system from 5.2.3 to 5.5.4 which went very smoothly. I have a couple of users that have a recurring problem when using the search facility (they are now using the 5.5.4 client). They get a C05F error when doing asearch. I found TID 10056457 which fixes the problem but then error comes back again a few days later (it appears that something is getting corrupted). I found another TID which suggested a fix was to access the Post Office in direct mode rather than client/server - this did not seem to make a difference. Has anyone seen this problem before and any ideas on how to solve?

5 replies

by wcraigmiles

I much prefer client/server mode to keep problems like this from happening.

Check the POA setting and ensure that the indexing interval is NOT/NOT set to zero. Zero means to index continuously. ALso you want indexing to stop while your backups are running. You can set this in NWAdmin with the GW snap-in. Tell it to stop the POA agent from xx time to xx time. Check the backup logs to see how long back ups are taking. If after this you see the speed of the backups increase, I'm pretty sure you've found the problem. Also set your maintenance to occur on a weekly interval. Also stop the POA while the weekly maintenance is running.

by estebandelatorre

Disable the indexing function from the POA startup command line arguments and let the users perform the search.
Although this made the search up to 2 times longer, it won?t corrupt databases as the main indexer do.
Also: Be sure to be working in client/server mode, otherwise, the C05F may came from broken connection and when the indexer browse the database, it arrise with the error, but he did not produce the error.

hope it helps!!!

This discussion is closed to new replies.