Groupwise Error D107
Contents |
Asset Management ZENworks Configuration Management ZENworks Endpoint Security Management ZENworks Full Disk Encryption ZENworks Patch Management ZENworks Virtual Appliance Learn more about ZENworks File & Networking Services + File Management groupwise error d107 record not found Suite Business Continuity Clustering Dynamic File Services File Reporter Filr Micro Focus iPrint Open
Schoology
Enterprise Server Storage Manager Looking for Linux? See our new home at SUSE.com Services & Support + Services Overview Help Yourself Knowledgebase Support Forums Documentation Product Support Lifecycle Let Us Help Open Service Request Entitlement & Access Premium Support Technical Support Handbook Download Patches Drivers Contribute Participate in Beta Report Bug Report Software Vulnerability Share a Tip, Trick, etc. Cool Solutions Consulting Customer Center My Profile My Products My Support My Training Partners Communities + Communities Blog—Expert Views Blog—Technical Free Tools Support Forums About Us + About Us Contact Us Our Customers Executive Management Job Search Events Media Gallery Industry Analysts Press Releases Subscribe How to Buy + How to Buy Overview Request a Call Find a Partner Shop for Training Volume Licensing & Buying Programs > cool solutions home Solving D107 Errors in GroupWise Novell Cool Solutions: TipBy Brett Walters Digg This - Slashdot This Posted: 18 Jul 2006 Problem You may receive a D107 error when GroupWise starts. It is recommended to look for an item in the whole account that is greater than the auto-archive date, and delete it. If you're using the GW Client, the following method may help. Important: Be sure to back up your mailboxes before trying any of these suggestions. Solution 1. From the GW Client menu choose the Check Mailbox Size tool. 2. For each of the 3 categories of items (don't do Trash, it's redundant), sort by date. 3. Delete those items you believe are older than the Auto-Archive date for that item (this can be found in Tools, Options, Environment, Cleanup). Example An item causing D107 Error can be Received, Sent, or Calendar. "Check Mailbox Size" appears to be better at finding old items still considered in the active mailbox. Also, you will likely have many Trash items after this. I recommend leaving the efficient Auto-Archive Trash function to do the cleanup, as deleting many items from Trash at one time (especially if you are using Cache Mode) will be time-consuming. Note: This solution was tested in an environment with Windows XP and GroupWise Client 6.5.
Like what you see? Sign up for our weeAsset Management ZENworks Configuration Management ZENworks Endpoint Security Management ZENworks Full Disk Encryption ZENworks Patch Management ZENworks Virtual Appliance Learn more about ZENworks File & Networking Services + File Management Suite Business Continuity Clustering Dynamic File Services File Reporter Filr Micro Focus iPrint Open Enterprise Server Storage Manager Looking for Linux? See our new home at SUSE.com Services & Support + Services Overview Help Yourself Knowledgebase Support Forums Documentation Product Support Lifecycle Let Us Help Open Service Request Entitlement & Access Premium Support Technical Support Handbook Download Patches Drivers Contribute Participate in Beta Report Bug Report Software Vulnerability Share a Tip, Trick, etc. Cool https://www.novell.com/coolsolutions/tip/17539.html Solutions Consulting Customer Center My Profile My Products My Support My Training Partners Communities + Communities Blog—Expert Views Blog—Technical Free Tools Support Forums About Us + About Us Contact Us Our Customers Executive Management Job Search Events Media Gallery Industry Analysts Press Releases Subscribe How to Buy + How to Buy Overview Request a Call Find a Partner Shop for Training Volume Licensing & Buying Programs > cool solutions home Fix for D107 error when https://www.novell.com/coolsolutions/tip/10014.html GroupWise starts Novell Cool Solutions: TipBy Shlomo Katz Digg This - Slashdot This Posted: 19 Aug 2004 problem: Upgraded to GroupWise Client 6.0.2 and above. User is now receiving D107 error when GroupWise starts. solution: Auto-Archving is trying to archive a corrupt message. Look for an item in the whole account (received, sent, calendar) that is older then the date archiving is set for and delete it. Chances are this item will have an attachment, when the attachment is opened, will be blank. Restart the client to verify that all corrupt messages have been removed. example: If auto-archiving is set for 30 days, look for any item older then 30 days. submit a tip Here's a chance to share your experiences using GroupWise. Just send us a tip about using (or installing, deploying, troubleshooting, etc.) GroupWise, and if it looks like something we can use, we'll send you a Novell t-shirt, post your tip, and make you famous beyond your tamest dreams. Submit your tip here: http://www.novell.com/coolsolutions/forms/submit_a_tip.html For more tips see: Tips for Administrators Tips for End Users
Like what you see? Sign up for our weekly newsletter. Want to contribute? It could earn you a nano! Learn more. Like Wikis? Join the Cool Solutions Wiki. Interested? Request a sales call Novell Cool Solutions (corporate web communities) are produced by WebWisFavorite Rating: Error D107 http://www.novell.com/support/kb/doc.php?id=10013089&add&title=10013089%3A+Error+D107+in+GroupWise in GroupWise (Last modified: 20Mar2003) This document (10013089) http://www.novell.com/documentation/groupwise2012/gw2012_guide_tsh1/data/b4k4fgh.html is provided subject to the disclaimer at the end of this document. fact Novell GroupWise 5.5 Novell GroupWise 4.1a symptom ErrorD107 in GroupWise Error: An unexpected error has occurred. Any GroupWise changes may not have groupwise error been saved. Error code D107 change Merged the GroupWise 4.1 domain into the GroupWise 5.5 system fix 1) In NWADMIN connect to the 5.5 primary domain.2) Highlight the 5.5 domain.3) Tools - Groupwise Utilities - System Maintenance.4) Run - Validate Database by itself.5) Run groupwise error d107 - Recover Database by itself.6) Run - Rebuild database.7) Remerge the 4.x domain. disclaimer The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information. Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information. Document ID: 10013089 Solution ID: 4.0.2725160.2230978 Creation Date: 20Jul1999 Modified Date: 20Mar2003 NovellGroupware Did this document solve your problem? Provide Feedback © Micro Focus Careers Legal close Feedback Print Full Simple Request a Call Follow Us Facebook YouTube Twitter LinkedIn Newsletter Subscription RSS
parameter D10A Unexpected error D10B Database needs to be repaired D10C Unexpected error D10D Cannot open any more mailboxes 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 issues have been resolved. D101 User not found Source: GroupWise engine; database interface. Explanation: User not found. Possible Cause: The GroupWise user ID is not found in the post office database during login. Action: If using switches, check the /ph switch to make sure the path to the post office is correct. Action: Start the GroupWise client using the /@u or /la startup option to specify the GroupWise user ID. Possible Cause: The user is not yet set up as a GroupWise user. Action: Set the user up as a GroupWise user. See Creating GroupWise Accounts in Users in the GroupWise 2012 Administration Guide. Possible Cause: The user ID provided when the user was set up as a GroupWise user is not correct. Action: Check the GroupWise user information in ConsoleOne. Make sure the common name (CN) of the user is provided. No additional information is needed in the Network ID field. Possible Cause: User information has not replicated from the domain to the post office the user is trying to access. Action: Wait for replication to take place. Make sure the MTA is running. Check the current scan cycles of the MTA. See Adjusting MTA Polling of Input Queues in the Domain, Post Offices, and Gateways in Message Transfer Agent in the GroupWise 2012 Administration Guide. Action: Synchronize the user manually. See Synchronizing Individual Users or Resources in Databases in the GroupWise 2012 Administration Guide. Possible Cause: The user is logging into a specific server, rather than into the tree, causing the network ID information not to match. Action: Log in to the tree rather than to a specific server. Possible Cause: If this error occurs when a user sends a message to a group, the group might contain user IDs that have been deleted from the system. Action: Recreate the group, selecting users from the Address Book to ensure they are valid GroupWise users. Possible Cause: If this error occurs when the user tries to delete user