MSDSS Reverse Sync Problem

I am attempting to create a 2 way sync relationship between AD and our NDS
tree, but I am running into an error whenever MSDSS tries to run the reverse
sync in my test environment.
Test setup:
In AD I created an OU named "DCTEST1" under the root of my AD tree for the
NDS objects to sync into.
In NDS I created an OU named "DCTEST1", and created a user object in the
container.
In MSDSS I created a new two-way synchronization session between the two OU
objects.
Forward sync works fine.
Reverse sync errors with the following error: Error code (0x800704b8): An
extended error has occured (0xfffffda5).

This is what the error log shows:

================================================== ===========
(Session 1)Start Reverse Sync Incremental 7/31/2008 9:30:43
================================================== ===========
NDSREAD: IgnoreDeletesFromNDS = No
NDSREAD: UseMemberAttribute = No
Successfully binded to vm-jce-w2k3-1.ad.wiwd.circ7.dcn as local system
The updateUSN from the last forward ssync is 41383
Write Provider Initialized Successfully
Guid not available for
NDS://WIW_TREE/O=WIW/OU=MSN/OU=DC/OU=DCTEST1/CN=jcetest (new object)
Getting column ACL
Getting column CN
Getting column Object Class
Fixing object class attribute (Object Class) on object ((null))
Getting column Public Key
Getting column Surname
Getting column Language
Getting column Revision
Getting column GUID
Getting column uniqueID
Getting column creatorsName
Getting column modifiersName
Getting column sasDefaultLoginSequence
Getting column ADsPath
ADsPath = NDS://WIW_TREE/O=WIW/OU=MSN/OU=DC/OU=DCTEST1/CN=jcetest
[Guid] Failed setting guid for object
(O=WIW/OU=MSN/OU=DC/OU=DCTEST1/CN=jcetest): 0x800704b8
DirSync(736): read.cpp(1985): The NDS extended error is 0xfffffda5
DirSync(736): read.cpp(1996): Error setting guid: 0x800704b8
Bailed from: read.cpp(1996) with error 0x800704b8(-2147023688)
An extended error has occurred.
Write Provider Terminated Successfully
Session thread 736 ending for Session 1
================================================== ===========
(Session 1)Finish Reverse Sync 7/31/2008 9:30:43
================================================== ===========

Oddly enough, if I create a migration session instead of a two way sync, the
reverse sync works fine.
I've been beating my head against this for a couple days, and have tried
every permutation of options I could think of before coming here.

Can anyone here help?

Thank you.

Dear Customer,

Thank you for using newsgroup.

We mainly focus on Windows server migration related issues here in this
newsgroup

microsoft.public.windows.server.migration

To ensure that you are best served, I would like to suggest that you open a
new thread in our Netware queue.

microsoft.public.win2000.netware

The engineers and newsgroup members there are more experienced on related
issues, and should be able to provide you with suggestions on this kind of
issue.

I'd like to share some knowledge with you.

Since MSDSS reads a static list of attributes from the Novell Directory and
then passes those attributes into Active Directory in order to create the
user account in Active Directory. The valid user with static value will be
migrated. Normally, if an attribute in NDS has no value, MSDSS will not
attempt to write that attribute to Active Directory. However, if the object
in the Novell directory has become corrupted, a whitespace value may be
read for one or more of the attributes. MSDSS will then attempt to import
the attribute with a null value, which will fail with the error 0x8007200b.

Reference:
===========

How to Migrate or Deploy a Novell NetWare Environment to Windows
http://support.microsoft.com/kb/274279/en-us

Hope the issue will be resolved soon.

David Shen
Microsoft Online Partner Support

I had the same problem and resolved it by manually extending the NDS schema
with ndsext.exe.

"jcegg" wrote:

> I am attempting to create a 2 way sync relationship between AD and our NDS
> tree, but I am running into an error whenever MSDSS tries to run the reverse
> sync in my test environment.
> Test setup:
> In AD I created an OU named "DCTEST1" under the root of my AD tree for the
> NDS objects to sync into.
> In NDS I created an OU named "DCTEST1", and created a user object in the
> container.
> In MSDSS I created a new two-way synchronization session between the two OU
> objects.
> Forward sync works fine.
> Reverse sync errors with the following error: Error code (0x800704b8): An
> extended error has occured (0xfffffda5).
>
> This is what the error log shows:
>
> ================================================== ===========
> (Session 1)Start Reverse Sync Incremental 7/31/2008 9:30:43
> ================================================== ===========
> NDSREAD: IgnoreDeletesFromNDS = No
> NDSREAD: UseMemberAttribute = No
> Successfully binded to vm-jce-w2k3-1.ad.wiwd.circ7.dcn as local system
> The updateUSN from the last forward ssync is 41383
> Write Provider Initialized Successfully
> Guid not available for
> NDS://WIW_TREE/O=WIW/OU=MSN/OU=DC/OU=DCTEST1/CN=jcetest (new object)
> Getting column ACL
> Getting column CN
> Getting column Object Class
> Fixing object class attribute (Object Class) on object ((null))
> Getting column Public Key
> Getting column Surname
> Getting column Language
> Getting column Revision
> Getting column GUID
> Getting column uniqueID
> Getting column creatorsName
> Getting column modifiersName
> Getting column sasDefaultLoginSequence
> Getting column ADsPath
> ADsPath = NDS://WIW_TREE/O=WIW/OU=MSN/OU=DC/OU=DCTEST1/CN=jcetest
> [Guid] Failed setting guid for object
> (O=WIW/OU=MSN/OU=DC/OU=DCTEST1/CN=jcetest): 0x800704b8
> DirSync(736): read.cpp(1985): The NDS extended error is 0xfffffda5
> DirSync(736): read.cpp(1996): Error setting guid: 0x800704b8
> Bailed from: read.cpp(1996) with error 0x800704b8(-2147023688)
> An extended error has occurred.
> Write Provider Terminated Successfully
> Session thread 736 ending for Session 1
> ================================================== ===========
> (Session 1)Finish Reverse Sync 7/31/2008 9:30:43
> ================================================== ===========
>
> Oddly enough, if I create a migration session instead of a two way sync, the
> reverse sync works fine.
> I've been beating my head against this for a couple days, and have tried
> every permutation of options I could think of before coming here.
>
> Can anyone here help?
>
> Thank you.

Hi jose,

Thanks for the knowledge sharing.

David Shen
Microsoft Online Partner Support