Error 0x57 importing AD schema export into ADAM

[George]

I'm having a problem importing the AD schema into a new ADAM store.
I exported the AD schema with:
c:\windows\adam\ldifde -m
-o whenCreated,whenChanged,objectGUID,uSNChanged,uSNcreated
-r "(|(objectCategory=classSchema)(objectCategory=attributeSchema))"
-f <filename>
-d "cn=schema,cn=configuration,<domain root>"

I try to import into the ADAM store with:
c:\windows\adam\ldifde -i -k -s <servername>
-f <filename>
-c "CN=schema,cn=configuration,<domain root>"
"CN=Schema,CN=Configuration,CN=<ADAM store GUID>"

I get the following error:
Connecting to "<servername>"
Logging in as current user using SSPI
Importing directory from file "<filename>"
Loading entries.......
Add error on line 147: No Such Attribute
The server side error is: 0x57 The parameter is incorrect.
The extended server error is:
00000057: LdapErr: DSID-0C090AB7, comment: Error in attribute
conversion operation, data 0, vece
0 entries modified successfully.
An error has occurred in the program
No log files were written. In order to generate a log file, please
specify the log file path via the -j option.

I am logged into the domain as Adminstrator, who is a member of
Enterprise Admins, which has Full Control on the AD. Server runs
Windows 2003 Enterprise Edition.

The import file has on lines 147-171:
dn: CN=See-Also,CN=Schema,CN=Configuration,<domain root>
changetype: add
adminDescription: See-Also
adminDisplayName: See-Also
attributeID: 2.5.4.34
attributeSyntax: 2.5.5.1
cn: See-Also
distinguishedName:
CN=See-Also,CN=Schema,CN=Configuration,<domain root>
instanceType: 4
isSingleValued: FALSE
lDAPDisplayName: seeAlso
mAPIID: 33071
name: See-Also
objectCategory:
CN=Attribute-Schema,CN=Schema,CN=Configuration,<domain root>
objectClass: top
objectClass: attributeSchema
oMObjectClass:: KwwCh3McAIVK
oMSyntax: 127
schemaIDGUID:: MXqWv+YN0BGihQCqADBJ4g==
searchFlags: 0
showInAdvancedViewOnly: TRUE
systemFlags: 16
systemOnly: FALSE

What is wrong here?
How can I import the AD schema into the ADAM store?

 

[Joe Richards [MVP]]

Your status as an Enterprise Admin has no bearing on ADAM at all. ADAM doesn't
care. You need admin roles inside of ADAM and nothing you have indicated
indicates you do have that access. However, it would appear you have the access
as I assume the import would have failed sooner.

As for the place where it did fail, is every attribute defined for that class
already defined in your ADAM Instance? For instance, MAPIID isn't defined in any
of my ADAM instances...

 

[Dmitri Gavrilov [MSFT]]

Joe's correct -- you should exclude mAPIID, which is not a part of ADAM
schema. Everything else seems ok.

--
Dmitri Gavrilov
SDE, DS Admin eXperience

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm