Windows 2003 Upgrade and inetorgperson

[Guest]

I recently installed Exchange 2003 in my Windows 2000 domain. It went off
perfectly - no problems at all from an AD standpoint. Now I am beginning the
process of upgrading my domains to Windows 2003. I ran adprep /forestprep
this morning, and it failed with the following error in the ldif.log:

24: CN=inetOrgPerson,CN=Schema,CN=Configuration,DC=MYDOMAIN,DC=LOCAL
Entry DN: CN=inetOrgPerson,CN=Schema,CN=Configuration,DC=MYDOMAIN,DC=LOCAL
Add error on line 333: Unwilling To Perform
The server side error is "Schema update failed: attribute in may-contain
does not exist."
23 entries modified successfully.

Additionally, the adprep.log tells me this:

Adprep was unable to update forest-wide information.

[Status/Consequence]

Adprep requires access to existing forest-wide information from the schema
master in order to complete this operation.

This happens even though I am logged onto the schema naming master (it's the
same machine I was on when I did forestprep for Exchange) and logged in as
the Enterprise Admin account.

Any ideas on what may be causing this or how to resolve it?

Thanks in advance for any suggestions.

Dave B

 

[Chris Malone]

Dave,

You need to run InetOrgPersonFix as per:

http://support.microsoft.com/?kbid=314649

Chris Malone

 

[Guest]

We are having the same problem/error and have run the InetOrgPersonFix but
that did not resolve the problem.

 

[Guest]

There are 5 different 3rd-party applications that cause this problem - Cisco
Call
Manager, Cognos, SAP, Trinity, Apple.
They all add a non-RFC compliant OID to the schema. However each application
does it for a different object.

In our case it was Cisco Call Manager.