|
|
|
date: Sun, 11 May 2008 16:11:44 -0700 (PDT),
group: microsoft.public.exchange.admin
back
Error with IMAP access
Hi
On Friday, the imap access to our exchange 2007 server stopped
working.
In the log I get:
An unexpected exception
Microsoft.Exchange.Data.Storage.StoragePermanentException occurred
while processing a command for user Jean-Yves Avenard.
Microsoft.Exchange.Data.Storage.StoragePermanentException: Cannot get
ID from name. --->
Microsoft.Mapi.MapiExceptionNamedPropsQuotaExceeded:
MapiExceptionNamedPropsQuotaExceeded: Unable to get IDs from property
names. (hr=0x80040900, ec=-2147219200)
Diagnostic context:
Lid: 18969 EcDoRpcExt2 called [length=174]
Lid: 27161 EcDoRpcExt2 returned [ec=0x0][length=140][latency=0]
Lid: 23226 --- ROP Parse Start ---
Lid: 27962 ROP: ropGetIDsFromNames [86]
Lid: 17082 ROP Error: 0x80040900
Lid: 16993
Lid: 21921 StoreEc: 0x80040900
Lid: 27962 ROP: ropExtendedError [250]
Lid: 1494 ---- Remote Context Beg ----
Lid: 26426 ROP: ropGetIDsFromNames [86]
Lid: 6363 StoreEc: 0x8004010F
Lid: 6363 StoreEc: 0x8004010F
Lid: 31229 Error: 0x0
Lid: 6363 StoreEc: 0x8004010F
Lid: 7867 StoreEc: 0x80040900
Lid: 4475 StoreEc: 0x80040900
Lid: 4603 StoreEc: 0x80040900
Lid: 5323 StoreEc: 0x80040900
Lid: 1750 ---- Remote Context End ----
Lid: 26849
Lid: 21817 ROP Failure: 0x80040900
Lid: 24529
Lid: 18385 StoreEc: 0x80040900
at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message,
Int32 hresult, Object objLastErrorInfo)
at Microsoft.Mapi.MapiProp.GetIDsFromNames(Boolean
fCreateIfNotExists, NamedProp[] np)
at
Microsoft.Exchange.Data.Storage.InternalSchema.ResolveNames(MapiProp
mapiProp, NamedProp[] namedProperties, Boolean
allowUnresolvedInternetHeaders, MapiExceptionNamedPropsQuotaExceeded
originalException)
--- End of inner exception stack trace ---
at
Microsoft.Exchange.Data.Storage.InternalSchema.ResolveNames(MapiProp
mapiProp, NamedProp[] namedProperties, Boolean
allowUnresolvedInternetHeaders, MapiExceptionNamedPropsQuotaExceeded
originalException)
at
Microsoft.Exchange.Data.Storage.InternalSchema.PropTagsFromPropertyDefinitions(MapiProp
mapiProp, StoreSession storeSession, Boolean
allowUnresolvedInternetHeaders, MapiExceptionNamedPropsQuotaExceeded
originalException, NativeStorePropertyDefinition[]
propertyDefinitions)
at
Microsoft.Exchange.Data.Storage.InternalSchema.PropTagsFromPropertyDefinitions(MapiProp
mapiProp, StoreSession storeSession, Boolean
allowUnresolvedInternetHeaders, IList`1 propertyDefinitions)
at
Microsoft.Exchange.Data.Storage.MapiPropertyBag.GetProperties(IList`1
propertyDefinitions)
at
Microsoft.Exchange.Data.Storage.StoreObjectPropertyBag.InternalLoad(PropertyDefinition[]
properties, Boolean forceReload)
at
Microsoft.Exchange.Data.Storage.StoreObjectPropertyBag.Load(PropertyDefinition[]
properties)
at Microsoft.Exchange.Imap4.Imap4RequestAppend.Process()
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
The error reported by the mail client is:
Server Unavailable. 15
Any ideas?
I have already upgraded the mapi properties to 65535 a while back
Thanks
JY
date: Sun, 11 May 2008 16:11:44 -0700 (PDT)
author: JYA
Re: Error with IMAP access
On Sun, 11 May 2008 16:11:44 -0700 (PDT), JYA
wrote:
>Hi
>
>On Friday, the imap access to our exchange 2007 server stopped
>working.
>
>In the log I get:
Roh -roh.
You must have other errors in the app log as well, yes?
Looks like you exceed the named properties again.
>
>An unexpected exception
>Microsoft.Exchange.Data.Storage.StoragePermanentException occurred
>while processing a command for user Jean-Yves Avenard.
>Microsoft.Exchange.Data.Storage.StoragePermanentException: Cannot get
>ID from name. --->
>Microsoft.Mapi.MapiExceptionNamedPropsQuotaExceeded:
>MapiExceptionNamedPropsQuotaExceeded: Unable to get IDs from property
>names. (hr=0x80040900, ec=-2147219200)
>Diagnostic context:
> Lid: 18969 EcDoRpcExt2 called [length=174]
> Lid: 27161 EcDoRpcExt2 returned [ec=0x0][length=140][latency=0]
> Lid: 23226 --- ROP Parse Start ---
> Lid: 27962 ROP: ropGetIDsFromNames [86]
> Lid: 17082 ROP Error: 0x80040900
> Lid: 16993
> Lid: 21921 StoreEc: 0x80040900
> Lid: 27962 ROP: ropExtendedError [250]
> Lid: 1494 ---- Remote Context Beg ----
> Lid: 26426 ROP: ropGetIDsFromNames [86]
> Lid: 6363 StoreEc: 0x8004010F
> Lid: 6363 StoreEc: 0x8004010F
> Lid: 31229 Error: 0x0
> Lid: 6363 StoreEc: 0x8004010F
> Lid: 7867 StoreEc: 0x80040900
> Lid: 4475 StoreEc: 0x80040900
> Lid: 4603 StoreEc: 0x80040900
> Lid: 5323 StoreEc: 0x80040900
> Lid: 1750 ---- Remote Context End ----
> Lid: 26849
> Lid: 21817 ROP Failure: 0x80040900
> Lid: 24529
> Lid: 18385 StoreEc: 0x80040900
> at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message,
>Int32 hresult, Object objLastErrorInfo)
> at Microsoft.Mapi.MapiProp.GetIDsFromNames(Boolean
>fCreateIfNotExists, NamedProp[] np)
> at
>Microsoft.Exchange.Data.Storage.InternalSchema.ResolveNames(MapiProp
>mapiProp, NamedProp[] namedProperties, Boolean
>allowUnresolvedInternetHeaders, MapiExceptionNamedPropsQuotaExceeded
>originalException)
> --- End of inner exception stack trace ---
> at
>Microsoft.Exchange.Data.Storage.InternalSchema.ResolveNames(MapiProp
>mapiProp, NamedProp[] namedProperties, Boolean
>allowUnresolvedInternetHeaders, MapiExceptionNamedPropsQuotaExceeded
>originalException)
> at
>Microsoft.Exchange.Data.Storage.InternalSchema.PropTagsFromPropertyDefinitions(MapiProp
>mapiProp, StoreSession storeSession, Boolean
>allowUnresolvedInternetHeaders, MapiExceptionNamedPropsQuotaExceeded
>originalException, NativeStorePropertyDefinition[]
>propertyDefinitions)
> at
>Microsoft.Exchange.Data.Storage.InternalSchema.PropTagsFromPropertyDefinitions(MapiProp
>mapiProp, StoreSession storeSession, Boolean
>allowUnresolvedInternetHeaders, IList`1 propertyDefinitions)
> at
>Microsoft.Exchange.Data.Storage.MapiPropertyBag.GetProperties(IList`1
>propertyDefinitions)
> at
>Microsoft.Exchange.Data.Storage.StoreObjectPropertyBag.InternalLoad(PropertyDefinition[]
>properties, Boolean forceReload)
> at
>Microsoft.Exchange.Data.Storage.StoreObjectPropertyBag.Load(PropertyDefinition[]
>properties)
> at Microsoft.Exchange.Imap4.Imap4RequestAppend.Process()
>
>For more information, see Help and Support Center at
>http://go.microsoft.com/fwlink/events.asp.
>
>The error reported by the mail client is:
>Server Unavailable. 15
>
>Any ideas?
>I have already upgraded the mapi properties to 65535 a while back
>Thanks
>JY
date: Sun, 11 May 2008 19:43:48 -0400
author: Andy David {MVP}
Re: Error with IMAP access
On Sun, 11 May 2008 17:36:41 -0700 (PDT), JYA
wrote:
>On May 12, 9:43 am, Andy David {MVP}
> wrote:
>> Roh -roh.
>>
>> You must have other errors in the app log as well, yes?
>>
>> Looks like you exceed the named properties again.
>>
>
>Actually, no ...
>The only other error is that the Microsoft Forefront security license
>has expired.
>
>Yep, I think this is what happened. over time it has received more
>than 65,535 different properties...
>
>Any ideas what I could do ? other than deleting all emails, re-
>creating a new storage group?
probably your only option, yes. Delete messages with offending
xheaders and the move mailboxes to a new store.
>
>That limitation on exchange is so lame ....
>i could disable a windows exchange server just by sending 65500 email
>all with a unique property ID .... sounds insane
Yep. Its defintely not a good thing. I feel your pain.
date: Sun, 11 May 2008 20:56:27 -0400
author: Andy David {MVP}
Re: Error with IMAP access
JYA wrote:
>Hi
>
>On May 12, 1:05 pm, "Rich Matheisen [MVP]"
> wrote:
>> MAPI hasn't been changed in years. The number of bits used by the
>> hardware isn't the problem.
>
>it is indirectly related.
But it isn't. It hasn't changed at all, it was the same size value
when the code ran on 16-bit machines. To change the size of the
property from 32 to 64 bits would break every MAPI application there
is. Now, if you want to dump all your old desktop and laptop machines,
switch to 64-bit versions of XP and Vista, pay MS some exorbitant sum
of money to change MAPI (and all their dependant applications) and
possibly rewrite any MAPI apps you have, well then, go for it!
>To have such limitation in these days and age is just plain stupid.
>And outright dangerous, as looking at it, you can *crash* any exchange
>server in only a few minutes (just send a lot of email, all with a
>unique x-header)
A point that's been made several times to MS (by me) and probably many
more times by many others.
FYI, this same problem exists with public folders.
--
Rich Matheisen
MCSE+I, Exchange MVP
MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
Don't send mail to this address mailto:h.pott@getronics.com
Or to these, either: mailto:h.pott@pinkroccade.com mailto:melvin.mcphucknuckle@getronics.com mailto:melvin.mcphucknuckle@pinkroccade.com
date: Mon, 12 May 2008 22:52:07 -0400
author: Rich Matheisen [MVP]
|
|
