Action(s)
Make sure the IPX address change is completed. One way to do this is run DSREPAIR
select Advanced Options select Servers Known to this Database select the server name select Repair Selected Server's Network Address.
Source
Explanation
Access denied.
Possible Cause(s)
A user tried accessing/opening a file that did not have or allow sharing. A
user tried to create a file that already exists.
Action(s)
Open the file with correct sharing flags.
Possible Cause(s)
If this error occurs when the user sends a message to multiple users or to
users in a different post office, the user may not have sufficient rights to write
files into the WPCSIN directory for the MTA to pick up.
Action(s)
See Post Office Directory. Make
sure the directory exists and that the user has sufficient rights to write files
into the 0-7 priority subdirectories in WPCSIN. Also check the rights on the OFUSER and OFMSG directories. If access is being handled with a group rather than on an
individual basis, make sure the user is a member of the group that has the
required access. See Check Network Access for
Mapped Drive Connections.
Possible Cause(s)
The user may have a user space limit on the volume where the post office
resides. If that limit is exceeded, the user cannot write files into the WPCSIN directory.
Action(s)
If the user has reached a space limit, increase the maximum space allowed for
that user.
Possible Cause(s)
The GroupWise databases may be owned by an invalid user.
Action(s)
See Domain Directory and Post Office Directory for the locations of
GroupWise databases in domains and post offices. Check the ownership of the
GroupWise databases. If necessary, change the ownership to a valid user such as the
system administrator. You can check file ownership using the NDIR command. You
can reset ownership if needed using the FILER command.
Possible Cause(s)
Another program may already have the required file open with exclusive
access.
Action(s)
On Novell NetWare, you can use Monitor to check the open/lock activity on
GroupWise databases and other files. You might find that a backup program is
holding the file open.
Possible Cause(s)
The GroupWise client has been installed on the local drive, so the program can
still run, but the network connection to the post office has been
lost.
Action(s)
When the network connection to the post office is reestablished the GroupWise
client will function normally again. Reboot the workstation. If the post office
still cannot be accessed, resolve those network problems.
Possible Cause(s)
If this error occurs when using the 16-bit GroupWise client, the user's
private BIF file may be damaged. Look up "BIF files" in GroupWise Administrator
Help.
Action(s)
Rename the user's private BIF file, then try the action again. If this solves
the problem, there was a problem with the BIF file and a new one has been
created automatically.
Possible Cause(s)
If this error occurs when exiting the GroupWise client, the user database may be damaged.
Action(s)
Check and, if necessary, repair the user database. Look up "maintain
GroupWise, mailbox and library databases" in GroupWise Administrator Help, then display
Mailbox/Library Maintenance.
Possible Cause(s)
If the IPX address for the server where the post office resides has been
changed recently, the change may not yet have propagated throughout the
network.
Action(s)
Make sure the IPX address change is completed. One way to do this is run
DSREPAIR select Advanced Options select Servers Known to this Database select the server name select Repair Selected Server's Network Address.
Action(s)
If using the UNIX** MTA, check
the UMASK of the owner of that process. For example, if root owns the process,
a root UMASK of 022 would work, but 077 would not.
* Novell trademark. ** Third-party trademark. See Trademarks for more information.