Source
Explanation
Drive or path not found.
Possible Cause(s)
GroupWise cannot find the specified drive or path.
Action(s)
Use Browse to find the correct path.
Possible Cause(s)
The file you are trying to perform an action on does not exist.
Action(s)
Enter a valid filename.
Possible Cause(s)
If this error occurs shortly after starting the GroupWise client, the path to
the archive directory may not be correct.
Action(s)
In the GroupWise client, verify that the path to the archive directory exists
and that you have sufficient rights to create and modify files. Look up
"archive, directory" in GroupWise client Help. You can check user access rights to the
directory using the RIGHTS command.
Action(s)
If the path to the archive directory is valid and this is the first time the
user has tried to archive items, make sure the NGWGUARD.DC file exists in the post office. See Post Office Directory for the location of this file. If it is
missing, the databases required for archiving cannot be created. To restore the
NGWGUARD.DC file if it is missing, copy it from the PO directory in the
software distribution directory to the post office directory. See Software Distribution Directory for the location of the
backup copy of the NGWGUARD.DC file.
Possible Cause(s)
If this error occurs when importing a document into GroupWise, there may be a
problem with the library.
Action(s)
Check and, if necessary, fix the library. Look up "library, database" in
GroupWise Administrator Help, then display Analyze/Fix Databases for Selected
Libraries. Synchronize the library. Look up "synchronizing" in GroupWise
Administrator Help, then display Synchronize GroupWise Objects.
Possible Cause(s)
Some applications, such as Corel WordPerfect 7, MS Word 95, and Excel 95, need
a blank file stored in the C:/WINDOWS/SHELLNEW directory. For example, Corel
WordPerfect 7 needs a file named WORDPFCT.WPD to exist in the SHELLNEW directory
in order to create a new file when called from GroupWise. If this error occurs
when creating a new document in the GroupWise client, the blank template file
for the application may be missing.
Action(s)
Check the SHELLNEW directory for the existence of a blank file for the
application in use from GroupWise. If the blank file is missing, start the application
independently, then save an empty file under the required name in the SHELLNEW
directory. You should then be able to create new documents using that
application from GroupWise.
Possible Cause(s)
A directory required for the normal flow of GroupWise messages could be
missing.
Action(s)
See Directory Structures. Verify the
existence, ownership, and rights of the directories involved with message flow
(domain, post office, and MTA local). You can check access rights to files and
directories using the RIGHTS command. You can check file and directory ownership
using the NDIR command. See Check Network
Access for Mapped Drive Connections.
Possible Cause(s)
A required file or subdirectory could be missing from the directory structure
of the user's post office.
Action(s)
See Post Office Directory. Verify
the existence, ownership, and rights of the files and subdirectories in the
user's post office. You can check user access rights to files and directories
using the RIGHTS command. You can check file and directory ownership using the NDIR
command.
Possible Cause(s)
If this error occurs when trying to add users to a post office or when trying
to rebuild a user database, a required file may be missing from the post office
directory.
Action(s)
Make sure the NGWGUARD.DC file exists in
the post office directory. If it does not, copy it from the PO subdirectory of
your software distribution directory. See Post Office Directory and Software
Distribution Directory for the specific location of this file. New user databases and message databases cannot be created for new users if this file is
missing.
* Novell trademark. ** Third-party trademark. See Trademarks for more information.