Exchange 2007 distribution group creation
in [Microsoft Exchange]
|
Prev: Updates to recurring meeting does not update in user's calendar (Outlook 2007)
Next: Changing Exchange 2007 message size doesn't work
From: Michael Dragone on 25 Sep 2008 11:21 Glad you got it resolved; are we going with the school software changing the schema as the root cause? "gerrycurtis" <gerrycurtis(a)discussions.microsoft.com> wrote in message news:59D3EA22-453B-4ADE-AE14-9CB1D86BC5A3(a)microsoft.com... > > "gerrycurtis" wrote: > >> A peculiar problem has arisen whereby I am no longer able to create a >> universal distribution group in exchange management console (or shell). >> I have previously had no problem with this. >> The error message that comes up is as follows after trying to create a >> distribution group called Extended Services. Saturn.falmouth.local is one >> of >> our domain controllers: >> >> Active Directory operation failed on saturn.falmouth.local. This error is >> not retriable. Additional information: An attempt was made to modify an >> object to include an attribute that is not legal for its class. >> Active directory response: 0000207D: UpdErr: DSID-03150F9C, problem 6002 >> (OBJ_CLASS_VIOLATION), data 0 >> >> >> An object class violation occurred. >> >> Exchange Management Shell command attempted: >> new-DistributionGroup -Name 'Extended Services' -Type 'Distribution' >> -OrganizationalUnit 'falmouth.local/Users' -SamAccountName 'Extended >> Services' -Alias 'ExtendedServices' >> >> I have also tried creating a universal distribution group in AD then >> selecting in management console. I get the same error. >> Any help would be most appreciated. >> > > > I finally solved the problem by running the following in Exchange > powershell > window: > E: > cd \setup\data > dir schema* | foreach {ldifde -i -f $_.name -c "<SchemaContainerDN>" > "CN=Schema,CN=Configuration,DC=falmouth,DC=local" -v } > > E: is the DVD drive containing the Exchange installation package > Change The CN and DC to your own. > This uses the ldifde utility to reinstall all the AD schema for exchange, > correcting errors. > NOTE - this is a low level fix not recommended by MS unless all else > fails. > > Thanks to all who helped > Gerry
From: gerrycurtis on 25 Sep 2008 15:49
They ran tests on another school and claim their software was not to blame. I think I will never know the true reason! Gerry "Michael Dragone" wrote: > Glad you got it resolved; are we going with the school software changing the > schema as the root cause? > > "gerrycurtis" <gerrycurtis(a)discussions.microsoft.com> wrote in message > news:59D3EA22-453B-4ADE-AE14-9CB1D86BC5A3(a)microsoft.com... > > > > "gerrycurtis" wrote: > > > >> A peculiar problem has arisen whereby I am no longer able to create a > >> universal distribution group in exchange management console (or shell). > >> I have previously had no problem with this. > >> The error message that comes up is as follows after trying to create a > >> distribution group called Extended Services. Saturn.falmouth.local is one > >> of > >> our domain controllers: > >> > >> Active Directory operation failed on saturn.falmouth.local. This error is > >> not retriable. Additional information: An attempt was made to modify an > >> object to include an attribute that is not legal for its class. > >> Active directory response: 0000207D: UpdErr: DSID-03150F9C, problem 6002 > >> (OBJ_CLASS_VIOLATION), data 0 > >> > >> > >> An object class violation occurred. > >> > >> Exchange Management Shell command attempted: > >> new-DistributionGroup -Name 'Extended Services' -Type 'Distribution' > >> -OrganizationalUnit 'falmouth.local/Users' -SamAccountName 'Extended > >> Services' -Alias 'ExtendedServices' > >> > >> I have also tried creating a universal distribution group in AD then > >> selecting in management console. I get the same error. > >> Any help would be most appreciated. > >> > > > > > > I finally solved the problem by running the following in Exchange > > powershell > > window: > > E: > > cd \setup\data > > dir schema* | foreach {ldifde -i -f $_.name -c "<SchemaContainerDN>" > > "CN=Schema,CN=Configuration,DC=falmouth,DC=local" -v } > > > > E: is the DVD drive containing the Exchange installation package > > Change The CN and DC to your own. > > This uses the ldifde utility to reinstall all the AD schema for exchange, > > correcting errors. > > NOTE - this is a low level fix not recommended by MS unless all else > > fails. > > > > Thanks to all who helped > > Gerry > > |