Groupwise Error Code D109
Contents |
Favorite Rating: How to recover from a stuck user move with D109 Bad Parameter errorThis document (7008300) is provided subject to the disclaimer at the end of this document. Environment Novell GroupWise 8 Support Pack 2 Hot Patch 2 Situation Problem:User1 from Domain1, Post Office 1 (PO1) is moved to Post Office 2 (PO2), Under Domain2. The move then becomes "stuck" in the Administrative portion of the move and never completes. Symptoms - After the stuck move :1. In ConsoleOne, being connected to the Primary domain - Domain1 ( user source ), in the GroupWise view, the user shows up as a member of the source PO1 under Domain1.2. In ConsoleOne, being connected to the destination domain - http://www.novell.com/documentation/nwec/?page=/documentation/nwec/nwec/data/hj3e0eeg.html Domain2, in the GroupWise view, the user shows up as a member of the destination PO2 under Domain2.3. In the Post Office Address book of PO2, the user shows also as being a member of the destination PO2.4. In the post Office Address book of PO1, the user shows as being a member of the source PO1.5. No moved messages or calendar items make it to the destination Post Office (PO2) mailbox for User1.6. ConsoleOne, "User Move Status" utility http://www.novell.com/support/kb/doc.php?id=7008300 shows the "Last Move Status" is "Move in Progress" and the "Error" is listed as "0xD109 Bad Parameter".Purpose:To know how to best recover from this "stuck" GroupWise user move with the error "D109 Bad Parameter", listed in the User Move Status utility. For the purposes of this document the ultimate goal is to get the user back to the original source Domain and Post Office PO1 mailbox and to access the mail successfully. After this a later attempt to move back to the destination PO2 Post Office can be made, only after first running a “Validate” on the source and destination Post Offices in GroupWise System Operations in ConsoleOne, that likely will help remove the cause for the D109 Bad Parameter error. Resolution Resolution:1. Verify that User1 mailbox (userxxx.db) is still a member of the source PO1 address book by logging to the GroupWise mailbox for User1 (source PO1) and look in the Address book and verify that User1 is still listed as belonging to PO1. Also check if all the mail is still present and assessable as it should be.Also check in the \PO1\ofuser directory and verify that his "full" userxxx.db file is in the directory. An empty userxxx.db is about 87k in size. For this type of failed stuck move in the Administration portion of the move, the user normally is still a member of the source post office from the perspective of
Favorite Rating: MTA reports D109 after Changes to GroupWise users are made in ConsoleOneThis document (7002612) is https://www.novell.com/support/kb/doc.php?id=7002612 provided subject to the disclaimer at the end of this document. Environment Novell GroupWise 8Novell GroupWise 8 Novell GroupWise 7 Novell Identity Manager 3.5 Novell Identity Manager 3.5.1 Novell Identity Manager 3.6 Situation MTAreports"ADM: Error: [D109] Update replica" after changing user informationChanges In ConsoleOne for GroupWise users are not replicating through the GroupWise systemIDM with GroupWise groupwise error Driver is being used.Passwords not changing, user renames not sticking, changes to Internet Addressing Over rides not sticking.Overall Changes in ConsoleOne to GroupWise objects do not replicate properly to other domains and post offices. Resolution This issue is a result of a malfunction found in the GroupWise driver for IDMThe issue has been fixed in the IDM groupwise error code 3.5.3 version 2 or later. This can now be downloaded from Novell.com/Downloads and at the time of this writing was known by IDM 3.6.0/3.5.1 GroupWise Driver Version 3.5.3 Patch 2. (A version by this name or newer should contain the fix.)Once the IDM driver has been updated there are additional steps that need to be taken to correct the sychronization issues in GroupWise which were created as a result of this malfunction.GroupWise Will need to have the primary domain validated and a Top Down rebuild of the entire GroupWise system needs to be preformed.* ConsoleOne snapins dated later then May 29th 2009 will be able to Validate the database and remove the Tags corrupted by the IDM GroupWise driver.Steps to resolve issues:Update IDM driver to IDM 3.5.3 Version 2 or later.Validate the GroupWise Primary domain using ConsoleOne snapins date May 29th or laterPerform a Top Down rebuild on the GroupWise system to insure all GroupWise Databases are in syncTo Validate the GroupWise primary domain do the following:In ConsoleOne Co
be down. Please try the request again. Your cache administrator is webmaster. Generated Mon, 17 Oct 2016 10:00:53 GMT by s_ac15 (squid/3.5.20)