REPOST: Cannot remove class from schema with Win2k SP3

[Bert Roos]

Hi,

Our product uses a directory schema extension. We used to work on Windows
2000 SP2 and everything worked fine. Now we've upgraded to SP4 and since
then, we can't remove our schema extensions anymore. I've installed a test
machine with Windows 2000 SP2 and verified that I can extend the schema and
remove the extensions (both programmatically and through ADSIEdit). Next, I
upgraded the machine to SP3. After the upgrade, I couldn't remove the schema
extension anymore.

ADSIEdit shows a message box saying 'The requested delete operation could
not be performed'. The API error says 'The server is unwilling to process
the request'.

I'm doing this on a standalone domain controller that is operations master
and allows the schema to be modified on this domain controller, where the
current user (who is a schema admin) has the right to delete all child
objects from the schema. The class that I'm deleting is not used at all, so
there can't be any dependency problems.

Is this a bug or am I doing something wrong.

 

[Brian Desmond [MVP]]

When you add something to your schema, note the warning that the change
cannot be reversed. It can be disabled, but not removed.

--
--
Brian Desmond
Windows Server MVP
(e-mail address removed)12.il.us

Http://www.briandesmond.com

 

[Bert Roos]

Hi Brian,

Thanks for replying. Where do I find the warning you're talking about?

Regards, Bert

 

[Brian Desmond [MVP]]

You get it everytime you go to create a new item in the schema, I believe. I
don't remember what exactly the scenario is to get it, but i think creating
any extension will yield it.

--
--
Brian Desmond
Windows Server MVP
(e-mail address removed)12.il.us

Http://www.briandesmond.com

 

[Bert Roos]

Hi Brian,

It's indeed clearly documented. It's interesting to see that one of my
former colleagues based his design on the abillity to remove schema
extensions at will (even when objects of these types already exist), despite
the extensive documentation that says you shouldn't do that. It's also
interesting to see that the documented restriction is only inforced from SP3
and up, unfortunately without clear error messages.

Thanks again!
Bert Roos