Novell Cool Solutions

Update – Solving “Find” Problems in GroupWise Accounts



April 24, 2007 2:54 am






You are unable to search for content in a given account.

CASE 1: Finding an item in a problem account for User A …

User A attempts to use Tools > Find in the GroupWise client to locate an appointment with the subject “Find-Me” – but the result is “No items were found”. However, the appointment can be clearly seen in Mailbox list. Also, User C has proxy access to User A and can successfully find known appointments as a proxy to user A.

CASE 2: Finding items in the account for User B …

User A has proxy access to User B. The Find operation for a known appointment as proxy to User B results in “No items were found”. However, User B can find known appointments successfully, and User C has proxy access to User B and can find known appointments successfully.


  • No filtering issues
  • Not client-specific: this is demonstrated on GroupWise Windows client version 7.0.1 build 524 and 7.0.2 build 558
  • Not machine-specific: repeatable on 5 different Windows XP machines
  • Not Post-Office-specific: user C performed the test on the host post office and with an account on another Post Office in the same domain
  • Performed GWCheck utilities, but it did not correct the problem
  • Performed structural rebuild, but it did not correct the problem


Note: The Account management functions described below are completed in ConsoleOne.

1. Archive the contents of the account to a workstation.

2. Record the following user settings: FID, rules, signature, folder structure, address book contents, address book shares, folder shares, proxy list, Junk Mail Handling, etc.

3. Some items may need to be saved using screen capture. Use “Print Screen” key and Microsoft Paint with “Edit, Paste” to capture and save screen shots; or use a screen capture utility if available.

4. Delete and empty all contents of the account as the user.

5. Log out of the account from all locations.

From ConsoleOne …

6. Locate the “user{FID}.db” file on the Post Office and rename it to “user{FID}.db-old”

7. Delete and recreate the account.

8. Reset the FID before accessing the account for the first time.

9. Log in to the account, which should be clean of all old content. If it’s not clean, stop and recheck the creation process. You may need to stop the Post Office Agent to unlock the “user{fid}.db” file.

10. Retest the Find operation by creating an appointment with the subject “Find-Me2″. If the Find works, then the problem is resolved. If not, recheck steps 4-6 above.

11. Restore the contents to the account at a workstation, and other settings as the user. Proxy and shared resources must be manually restored.

Note: It was deemed important to restore the user FID to its original setting because of other system requirements.

Tommy Mikkelsen

Archiving and deleting the complete account can be a problem, as most often the issue is that the user simply saved a new Find Result template.

Here’s how to recover from this issue:

1. Right-click on any folder in the Windows Client and select Properties > Display.

2. In the Combo box named “Setting Name”, select Find Results.

3. Click Delete and then Cancel.

4. Now try the search again.

The “Find Results” setting is used as a template when doing a find, but it can be overwritten by the user. If it’s deleted, the GroupWise Client will recreate it with the defaults.

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.

Categories: Uncategorized


Disclaimer: This content is not supported by Novell. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.