Join our community for more solutions or to ask questions. I get these messages all the time for the same user on one postoffice. The caching mailbox has been deleted and recreated (post GWCHECK) but we're still getting the same result. To turn off Live Move, load ConsoleOne with GroupWise snapins, then right click on the Post Office object, then choose Properties, then click on the down arrow on the GroupWise tab,
The POA writes this message in his log-file. Now for the purposes of this document , the Primary was the source domain in the move, but if your move was not involving the Primary domain, use this same procedure After the rebuilds when the system is in sync again, you can use this same procedure to promote the old Primary Domain to again be the current Primary Domain.4. Additional Information 1. see here
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. HelpInfo Want to narrow your search? That concerns us, and has triggered this automated reply.Has your problem been resolved? However, the information provided in this document is for your information only.
However, the problem will re-occur with the next move for this Post Office. Document ID: 10063684 Solution ID: NOVL53616 Creation Date: 20Jul2001 Modified Date: 17May2004 NovellGroupware Did this document solve your problem? We get this error since we updatet to GW2012 latest SP. Document ID:7008300Creation Date:06-APR-11Modified Date:26-APR-12NovellGroupWise Did this document solve your problem?
Microsoft Office has a built-in, main dictionary that is shared by Office apps, including Excel, Outlook, PowerPoint, and Word. Novell makes all reasonable efforts to verify this information. 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. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
At this point to attempt to clear up the cause of the D109 Bad Parameter error , be connected to the Primary Domain in ConsoleOne and in the GroupWise View, hilite The MTA and POA agents must be running to perform this conversion.If this is needed, this is accomplished by being connected to the current Primary domain in the GroupWise view, hilite We've rebuilt the online mailbox, in addition to daily structure and weekly contents checks we've also done standalone GWCheck checks on this individual mailbox, so far as to run a structural Make sure it is posted in thecorrect newsgroup. (http://forums.novell.com)Be sure to read the forum FAQ about what to expect in the way of responses:http://forums.novell.com/faq.phpIf this is a reply to a duplicate
If this is not the case, but at least one GroupWise secondary domain (lets say Domain3) does have the correct information about User1 (lists User1 as member of PO1), it may http://novell.support.groupwise.6x.install-setup.narkive.com/2sHReQ1D/d109-bad-parameter-error MTA and POA on the box. D109 Deerfield Has anybody seen this error and maybe a solution to solve this ? Netware 6.5 sp8 - Groupwise 7.02 Do I need to be concerned?
I used the \ following TIDS to resolve my problem.
The thread number is listed after the time, in the POA log file. Sometimes, it is also seen that mailbox maintenance is needed for resolving various issues of mailbox and other Novell GroupWise database. Corel Lotus Microsoft Access Microsoft Excel Microsoft FrontPage Microsoft InfoPath Microsoft OneNote Microsoft Outlook Microsoft PowerPoint Microsot Project Microsoft Publisher Microsoft Visio Microsoft Word Microsoft Works Novell GroupWise WinZip Media Creation A Live move establishes a Client/Server connection between the source and target POAs.NOTE: The C00F errors occur on the Thread that was being used by the Move.
Select a Product... Consult your product manuals for complete trademark information. Bookmark Email Document Printer Friendly 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 edu [Download message RAW] I don't know if you've had a response on this or not, but I, too, have this error on a user.
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.