Re: Intelligent Message Filtering - Error when changing SCL ratings.



Ok, thats interesting. You shouldn't have created that yourself. Best thing
is for you to delete that container and re-apply SP2.

Unfortunately that paragraph is misleading many. All it really means is that
the installation will need to create the container and thus the person
running the install should have the necessary rights.

cheers,

Alexander Zammit
Software Development Consultant
ExchangeInbox.com MS Exchange resource site
http://www.exchangeinbox.com/



"Jaycee" <jaycee131973@xxxxxxxxxxx> wrote in message
news:%23bVfsIr6FHA.3752@xxxxxxxxxxxxxxxxxxxxxxx
> Yes. SP2 was installed with my account and I have administrative rights.
>
> In the release notes for SP2 it states:
> Because Intelligent Message Filter is included in Exchange Server 2003
> SP2, it is no longer an add-on and, therefore, a container must be created
> within Active Directory® directory service as follows:
>
> Cn=UCE Content Filter,cn=Message Delivery,cn=Global Settings,cn=<ORG
> NAME>cn=Microsoft Exchange,cn=Services,cn=configuration,dc=<root domain>
>
> You must have elevated rights to create this container - either Exchange
> Full Administrator or Exchange Administrator role at the organization
> level. The first time that you try to upgrade to a released or SP1 version
> of Exchange Server 2003, your permissions will be checked and a warning
> displayed if you do not have the correct rights level.
>
> I created this container with ADSI Edit under my account. I haven't done
> anything else.
>
> Any more ideas?
>
>
> "Alexander Zammit" <alex@nospamplease> wrote in message
> news:eoOf70i6FHA.744@xxxxxxxxxxxxxxxxxxxxxxx
>> That error comes from Active Directory. That error typically indicates
>> access rights poblem. Was SP2 installed by yourself under the same
>> credentials you are using now?
>>
>> cheers,
>>
>> Alexander Zammit
>> Software Development Consultant
>> ExchangeInbox.com MS Exchange resource site
>> http://www.exchangeinbox.com/
>>
>>
>>
>>
>> "Jaycee" <jaycee131973@xxxxxxxxxxx> wrote in message
>> news:uqBR8lh6FHA.2600@xxxxxxxxxxxxxxxxxxxxxxx
>>>I recently installed SP2 on my Exchange 2003 servers. IMF was not
>>>installed previously. Now that SP2 is installed I'm trying to configure
>>>the SCL ratings. However, when I make any changes and then click Apply I
>>>get the following error:
>>>
>>> The requested operation did not satisfy one or more constraints
>>> associated with the class of the object.
>>>
>>> Facility: LDAP Provider
>>> ID no: 80072014
>>> Microsoft Intelligent Message Filter
>>>
>>> Any ideas?
>>>
>>>
>>>
>>
>>
>
>


.



Relevant Pages

  • Re: Enabling IMF on Exchange 2003 SP2
    ... create the container, but SP2 should create it for you, assuming that you ... have the right pems (Exchange Full Admin, or Exchange Administrator at the ... As far as where it goes, you'd find it under the Configuration container ...
    (microsoft.public.exchange.admin)
  • Re: Deploying SP2 to MS Exchange Server 2003
    ... >portion of the installation procedures. ... >Because Intelligent Message Filter is included in Exchange Server 2003 SP2, ... >procedures as to how and where I need to create this new container. ...
    (microsoft.public.exchange.admin)
  • Re: SP2 for SBS 2003 Question
    ... Just checked Exchange version and SP2 is already on there (did this last ... installation notes ... >>> like to soon start using Windows Search on the server and this runs ...
    (microsoft.public.windows.server.sbs)
  • RE: sbs 2003 SP2
    ... I installed Exchange SP2 (Single Server) with no problems noted ... You would like to know if it is proper to install Exchange 2003 Service ... Generally, as Dave indicated, we don't have to first install SP1 before SP2 ... please perform a fully SBS backup before your installation. ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange Information Store Help
    ... getting Exchange to go beyond 16gb using SP2. ... I removed the Exchange Agent and the store ... During installation, I recieved and error ...
    (microsoft.public.exchange.admin)