Novell GROUPWISE 7 - TROUBLESHOOTING 2 Troubleshooting Manual page 51

appropriate directory queues starting with the newest file to the oldest. This
approach assumes the oldest file caused the lock and allows the Internet Agent
to process the messages that got backed up before dealing with the bad file.
Delete the bad file when you find it. Because the file is encrypted, there is no
way to determine who sent the message.
Action: Check for a bad configuration file. One of the setup files in the
directory might be damaged and therefore causing problems. Before removing
or changing anything, back up your directories. Be sure to back up any files
you want in the 000.prc directory such as the log and accounting files.
Remove all the files in the 000.prc and restart the Internet Agent. If you had
set a screen color or screen saver, you must reset these settings after removing
the SET file.
Action: Remove directories and have the Message Transfer Agent and the Internet
Agent re-create new ones. Be sure to back up the whole GWIA directory and
all subdirectories before deleting anything. Shut down the Internet Agent and
the Message Transfer Agent. Remove the
result, wpcsin, wpcsout, 000.prc
Transfer Agent first to re-create the wpcsin and wpcsout directories, then
restart the Internet Agent to re-create the other directories (empty). This
approach is often effective for solving locking problems, although it is not very
effective for isolating and determining what is causing the problem.
Action: If the Internet Agent continues to lock after removing and re-creating the
directories, you might want to rebuild the domain database for the domain
where the Internet Agent is installed in case there are database structural
problems. If it's a primary domain database, you must rebuild the database
from itself. If it's a secondary domain database, you can rebuild it from the
primary domain database or rebuild it from itself. See
Post Office
Guide.
Action: Run the Internet Agent on a different server that is already set up and running
well (without problems with requestors, network interface cards, and so on). If
the Internet Agent runs well with the same configuration on a different server,
then the hardware is probably causing problems.
Internet Agent Cannot Access the Domain
Problem: The Internet Agent cannot access its input and output queues in the domain.
Explanation: When the domain is located on a remote NetWare server, the Internet Agent
must be started with the /user and /password switches so it can log in to the
remote server.
Action: Make sure these switches have been specified in the Internet Agent .cfg file.
Action: Make sure the user has sufficient rights to access the
\domain\wpgate\gwia
Action: Make sure the password is correct and current.
Databases" in "Databases" in the
directory.
000.prc
send, receive, defer,
directories. Restart the Message
"Rebuilding Domain or
GroupWise 7 Administration
Internet Agent Problems 51