Groupwise Error 8201 Sending Email
Favorite Rating: 8201 error: The agent could not read this message from the message transport on GWIAThis document (7008629) is provided subject to the disclaimer at the end of this document. Environment Microsoft Windows 2008 Novell GroupWise 8 Support Pack 2 GroupWise Internet Agent (GWIA) Situation Unable to send email from GroupWise to the internet.GWIA logs show 8201 error: "The agent could not read this message from the message transport.".Attempt to rename wpcsin and wpcsout in the GWIA's wpgate directory does not work as the MTA is unable to recreate them.Gave the gwia.exe and gwmta.exe the ability to run with Administrator Privilege, by going into the properties of the object, compatibility tab, then selecting the last check box.Running the service as admin local account. Resolution Even with the additional Administrator Privilege enabled for the exe, and running as a admin local account, the Agents still did not have enough permissions. Right clicking the exe, and selecting the "Run as Administrator" was enough to get the agent up and running and processing mail without error. Running as Administrator also gave the Agents the ability to recreate the folder structure. To make this change permanent, on the Windows box, go into the properties of the individual GroupWise Agent service in the Services panel, select the "Log On" tab, change the account from Local System Account to "This Account" by clicking the second radio button. It is best to browse, to insure the right account is selected, then plug in the password. Additional Information Sometimes installing the agent with something other then the Local System Account may cause problems with completing the install. It is best to install with the Local System Account then switch to the "This account" option and choose the administrator to run the services. DisclaimerThis Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND. Document ID:7008629Creation Date:23-MAY-11Modified Date:26-APR-12NovellGroupWise Did this document solve your problem? Provide Feedback © Micro Focus Careers Legal close Feedback Print Full Simple
Path not found 820B Path too long 820E Cannot lock file 8210 Cannot create path 8211 Cannot rename file 8212 Password incorrect 8214 Unsupported encryption level 8215 Path root error 8219 Cannot connect to remote network resource 821A Access to a critical file denied NOTE:This guide does not include a comprehensive list of all possible GroupWise error codes. It lists error codes for which solutions are readily available from GroupWise engineers and testers. You can search the Novell Support Knowledgebase to locate additional solutions documented by Novell Support as specific customer http://www.novell.com/support/kb/doc.php?id=7008629 issues have been resolved. 8200 File I/O error Source: GroupWise engine; file input/output. Explanation: Generic file I/O error. Any file I/O error that cannot be mapped to a more specific file I/O error message. Possible Cause: A GroupWise database has been damaged so it is unrecognizable as a GroupWise database, for example, having a size of 0 KB or 2 GB. Action: Restore the damaged databases http://www.novell.com/documentation/groupwise2012/gw2012_guide_tsh1/data/b4k0tb1.html from backup. For the locations of GroupWise databases in domains and post offices, see Domain Directory and Post Office Directory in Directory Structure Diagrams in GroupWise 2012 Troubleshooting 3: Message Flow and Directory Structure. Possible Cause: One or more of the GroupWise databases might have an invalid owner or no owner. Action: Check the ownership of the GroupWise databases. If necessary, change the ownership to a valid user such as the system administrator. Possible Cause: If this error occurs when users are trying to log in to GroupWise through the GWIA from a POP3 mail client, the post office link information needed by the GWIA might be incorrect. Action: Check the post office link set up for the GWIA. In ConsoleOne, browse to and select the Domain object where the GWIA is installed. Right-click the GWIA object, then click Properties. Click Post Office Links, select the post office, then click Edit Link. Make sure the IP address and TCP port for the POA are specified correctly in the Client/Server Access box. See Internet Agent in the GroupWise 2012 Administration Guide. 8201 Access to file denied Source: GroupWise engine; file input/output. Explanation: Access denied. The program tried to access or open
amongst my new client shops. Pages Home About Me BrainShare Tips & Tricks Monday, January 10, 2011 8201 Error on Archive location in GroupWise 8.x If you've used GroupWise long at all you've probably seen this error pop up from time http://wmnug-mary.blogspot.com/2011/01/8201-error-on-archive-location-in.html to time and you know it has multiple possible causes. However, none of the TIDs that I've https://www.suse.com/support/kb/doc?id=7001971 come across seem to have the particular issue I've been running into noted. Good news is I have a work around. First though, you'll need some background info. All of our archive locations are locked by default. Default archive locations for this environment are to the users home drives. GroupWise version on the backend is 8.01 HP2, client is at 7.03 or higher up to 8.0.2. groupwise error Home drives are on an OES2 SP2 - Linux server The server is virtualized on VMWare's VSphere (was ESXi to begin with) The symptoms are usually experienced by a new archive user, but not always. What happens is the user goes to Open Archive within the GroupWise client and they immediately get an 8201 error. For some users it moves from an 8201 error to an 8209 error after several unsuccessful attempts to get at the archive. This occurs for PC users groupwise error 8201 only, our Mac users don't get to archive unless it's to their local drive and they have to agree to be responsible for the backup of the archive. Here's the workaround: Unlock the archive location for the given user (use ConsoelOne, right click on the user, select Client Options, pick the File Locations tab) If there is an existing archive, copy that folder to the user's local drive. I generally use c:\grpwise\archive to keep within the 8.3 file format. Close the GroupWise client. Open the GroupWise client and change the File Location (Tools | Options) to the new spot on the local drive. Have the user select Open Archive. Go back to the mailbox. Archive a message that is "ok" to potentially lose (only had this happen once, but it's a caveat you'll want to be aware of) Open Archive and verify the message is there. Close the GroupWise client. Copy the archive from the local drive back up to the server, and lock the archive location again (if you want). Open the GroupWise client, verify that the File Location is pointing back to the original location. Open Archive, verify that they can see at least the message that was just archived. This has worked for everyone reporting the issue here. Hopefully it will work for everyone else as well. Posted by "The" Mary at 2:01 PM No comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Search This Blog Loadin
and issues × × Sorry for the inconvenience Our new site design is only available in English right now. Go to the previous site to read in my language Stay here and read in English × Give Us Feedback Got some feedback about the website? Let us know so we can fix it. For support information, please visit Support. Sales:1-800-796-3700 Support:1-800-858-4000 Connect with us Feedback Form We adapt, you succeed. Read Privacy Policy Required Fields* X SUSE Support My Favorites Close Please login to see your favorites. Bookmark Email Document Printer Friendly Favorite Rating: GroupWise 8 current information and issuesThis document (7001971) is provided subject to the disclaimer at the end of this document. Environment Novell GroupWise 8Novell GroupWise 8 Hot Patch 1Novell GroupWise 8 Hot Patch 2Novell GroupWise 8 Support Pack Situation Here is a current list of known issues with, and information for,GroupWise 8: Resolution 3347260 - Doing a Top Down Rebuild on GroupWise 5, 6, 6.5, 7, or 8 3519110 - Mail sent to personal group is not being delivered to nested system distribution lists This has been resolved in GroupWise 8 Hot Patch 1 3540444 - Blank Web Page after logging in to GroupWise WebAccess 3607973 - Error: "C022" when starting MTA 3611803 - Caller is not allowed access to a file when rebuilding GroupWise Domain 3788883 - How to rebuild a domain database. 7000192 - GroupWise gwdva process causing 100% CPU utilization on virtualized Linux server 7000208 - Attachments keep on increasing in the draft mail if File | Print is clicked This has been resolved in GroupWise 8 Hot Patch 1 7000388 - GroupWise Agents Status on Linux is unused 7000578 - WebAccess webconsole shows HTTP over SSL disabled even though WebAccess configured for SSL 7000586 - Message Conversion Slow for Outbound GWIA 7000590 - Error: File store not a view description file, using Group