Networks

Ask something
Discussion Locked

NDS & Groupwise

0 helpful
7 replies

by rauguste

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am having problem synchronizing a NDS account with a Groupwise Account. I moved a user account from one to another, but now I am getting an error message stating "The groupwise information for this object does not exist. A possible cause is that replication is still in progress." I've been getting this error message for about a week now on this user object. I also can't move anything to that container where this object is located. Can anyone possibly give me any insights on how to fix this problem.

Thanks

7 replies

by rbgnr111

try running dsrepair to see if there are any errors in nds.
also maybe after the dsrepair go into groupwise view and in the options for the domain tell it to synch with nds.

by jimbb

Try enabling Groupwise Diagnostics in NW Administrator. This will give you additional tools to fix these kinds of problems, like linking and disconnecting a groupwise mailbox to and from an NDS account, to make a move easier. You do this by creating a blank file in the c:\-root of the PC on which you run NWADMN32.EXE, called "C:\GWSUPP.FIL". The restart NWADMN32.EXE, and you'll see "Groupwise Diagnostics" in the "Tools" menu.

You may have to combine that with some rebuilding on mailboxes and/or postoffices, also via NWAdmin.

Jim

by jereg

I'm not sure how or where you were moving this user, but it's happened to me. It ususally takes a lot of work but here are some things you can try. Move the user back to their orginal container. The mailbox may work at that point. If not, run GWcheck on the mailbox. If that doesn't work, find the user FID. Go to your tape backup before this happened and get a copy of the userxxx.db, and put it in the message store. They should see some mail at that point. Run GWcheck again. This should bring back most of the mail. Make a copy of the userxxx.db, (for the next cheat). Try moving the user again. If it fails this time, delete that user mail account. Create the user in the new post office. Find out the new FID. Replace the userxxx.db(new FID) with userxxx.db(old FID). Rename the userxxx.db with the new FID. All the mail will be there.
If you need any help, contact me at:
augustwest@altavista.com
hope that helps.

This discussion is closed to new replies.