ADPREP /FORESTPREP (again)

[Andrew Jones]

Hi, newbie here

I am about to go postal on my schema.

trying to extend the schema for W2k3 and having nothing but problems.

first attempts gave me probs with preferredlanguage and labeleduri

have renamed BOTH of these to COGNOS<respective name>

now getting the following error in ldiff.err.18:
<Begin Error Transcript>
EntryDN: CN=labeledURI,CN=Schema,CN=Configuration,<domain>
Add Error on line 177: Unwilling to Perform
The server side error is "Schema Update failed in recalculating
validation cache."
An error has occured in the program
<End Error Transcript>

have also run schchk.vbs which tells me of lots of duplicate oid's but no
probs in creating things

thought the error may be due to SFU2.0 which was not present but was used
in the past, so reinstalled that then run the hotfix - 0 entries found

run the inetorgpersonfix, that also has 0 entries to modify

I cannot find anything else on the net to help me.

anyone out there able to?

Schema master is forest root, which does nothing, all day to day stuff is
done on a child domain. recently upgraded E2k to E2k3 with no problems.

HELP!!!

 

[Mike Luo [MSFT]]

Hello Andrew,

Thank you for using newsgroup!

From your post, there is COGNOS software in your environment. Base on my
research, this problem may be caused due to COGNOS software makes a schema
change using a non-RFC compliant Object
Identifier (OID). I suggest you refer to the following steps to fix:
1. Open ldp on the Schema FSMO.
2. From the Connection menu option select Bind.
3. Leave all text fields blank and (NTLM/Kerberos) checked. Click OK.
4. From the View Menu option select Tree and leave the field (BaseDN
blank. Click OK
5. On the left pane expand the view until you find CN=labeledURI under the
schema
6. Right click on the labeledURI attribute and select Modify.
7. In the attribute text field add lDAPDisplayName.
8. In the Value field give this to COGNOSlabeledURI.
9. Select the replace radio button.
10. Click Enter to add to the Entry List
11. Click Run to confirm success in left pane.
12. Remove the attribute from the entry list.
13. In the attribute text field add adminDisplayName.
14. In the Value field type COGNOSAdminDisplayName
15. Select the replace radio button.
16. Click Enter to add to the Entry List
17. Click Run to confirm success in left pane.
18. Right click on CN=labeledURI... And select rename.
19. Enter in the old DN field as the current DN of lableledURI.
20. Enter the in the new DN field COGNOSlabeledURI
21. Confirm Delete Old and Synchronous are selected and click Run.
22. Exit from ldp.
23. Force replication to all the domain controllers.

Run adprep /forestprep on domain controller holding schema master role.

Thanks & Regards,

Mike Luo

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Andrew Jones]

Hi Mike, thanks for replying.

I had already done that but it still didn't work.

Here is what I did to fix it:

First, I tried to manually create the labeledURI using the values
specified in sch18.ldf.

Even doing this gave me an error.

I eventually removed that entry from SCH18.ldf (don't panic!)
and ran adprep /forestprep - SUCCESS

it worked

I then went back into adsiedit and renamed my COGNOSlabeledURI back to
URI and manually checked all the attributes (including the OID) against
the one I had taken out of the sch18.ldf file. everything was correct,
and more importantly, everything is working.

 

[Mike Luo [MSFT]]

I am glad to hear you solved the problem yourself. Thank you for sharing
your experience.

Have a nice day!

Mike Luo

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.