Renaming a resource object will cause D101 errors if the new name contains underscores

Renaming a GroupWise Resource that contains an underscore returns the following error:
ERROR: D101 User not found

Workaround:
Since the problem only seems to be with underscores, dashes can be used instead to avoid the problem.
The problem has been corrected in GroupWise 8.0.1.

Resources can be created with underscores in their names and they work fine. However, if an existing resource is renamed and the new name contains underscores then d101 errors occur when accepting appointments as the resource.