We recently upgraded our Active Directory from 2000 to 2003R2.  Our schema was previously (in ver 2000) extended to include a handful of custom attributes.  These attributes are still present in the 2003R2 schema, but we are unable to edit them using adsiedit if they contain a STRING value.  Any custom attribute that is a Boolean value we can edit just fine.  

If I try to edit one of the custom attributes, I get an "unspecified error".   The attributes are active, according to SchemaMgr.  No errors show up in my Event logs. I can edit regular/default attributes, like description, display name, etc, so it's only these 'custom STRING' attributes that are misbehaving.  Also it doesn't matter what OU/container an object is in, and it's not a permissions issue as we are using the domain Administrator account to make these changes.

I can modify these attributes if I use LDP.exe, using the same credentials I use when trying adsiedit, and I can clear any value I've put in an attribute by clicking the <Clear> button in adsiedit.  

I can only imagine that something didn't get done during the upgrade process (2000->2003) that should have in order to be able to modify these.  Has anybody encountered this before?  I've done some searching before coming here, and came up pretty much empty-handed.

Thanks in advance for any insight.