Problem: The Internet Agent locks up or hangs.
Possible Cause: Bad message file
Possible Cause: Bad configuration file in the 000.prc directory
Possible Cause: Bad domain record
Possible Cause: Bad domain user record
Possible Cause: Software incompatibility
Possible Cause: Hardware failure
Action: Check the dates of the executables and make sure you are using the most current software and patches. Apply the latest versions for the Internet Agent as well as for the TCP/IP kernel. Make sure you meet the minimum version and system requirements for the operating system.
Action: Check for bad message files. Move all files currently in any queues in the send, receive, defer, result, wpcsin, wpcsout, or 000.prc\gwwork directories and let the Internet Agent run idle without processing any messages. If the Internet Agent can run idle without locking, a bad message is probably causing it to lock. Start copying the files back to the 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 000.prc 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 will have to 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 send, receive, defer, result, wpcsin, wpcsout, 000.prc directories. Restart the Message 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'll have to 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.
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.