locked
NamedProps & ReplidMap Tables RRS feed

  • Question

  • According to KB820 http://support.microsoft.com/kb/820379/en-us Exchange 2007 defaults for quota limits are as follows.

    Named Props Quota – 16K
    NonMAPI Named Props Quota – 8K
    Replids Quota – 8K

    Is there a separate table for each value?

    Permon shows a total of 8290 Rows in NamedProps table and 12 Rows in ReplidMap table, but I can't seem to find a counter for

    NonMAPI Named Props.

    Are named props stored in the same table with NonMAPI Named Props ?

    Thanks

    • Edited by net_tech Friday, November 8, 2013 8:56 PM
    Friday, November 8, 2013 8:55 PM

Answers

  • I would have guessed that, but since the quota for MAPI named props is 16K and the event is reporting you've exceeded the quota of 8K my guess would have been incorrect.

    I'd find the developer and have him thrashed. :-)


    --- Rich Matheisen MCSE&I, Exchange MVP

    • Marked as answer by net_tech Saturday, November 16, 2013 12:31 AM
    Thursday, November 14, 2013 10:18 PM

All replies

  • Yes. There's one set of named MAPI property IDs that spans the range of 1 to 65K. The range is split by the high-order bit of the binary value. It's either a zero or a one, thus the maximum number of properties for either range is 32K.

    The ReplIds are used only for public folders.


    --- Rich Matheisen MCSE&I, Exchange MVP

    Friday, November 8, 2013 10:50 PM
  • I am getting event 9667 for all users in the database that has 8290 rows in  NamedProps table. I am 99% sure MAPI call is being made and I am only at 50% of the default limit for Named Props. Any ideas what would cause it to fail?

    Saturday, November 9, 2013 12:01 AM
  • Doesn't the details section of that event tell you the quota limit?

    --- Rich Matheisen MCSE&I, Exchange MVP

    Saturday, November 9, 2013 2:43 AM
  • Yes, it's saying 8192 in the event ID, but I am already over according to the perfmon
    Saturday, November 9, 2013 2:49 AM
  • According to this, event-id 9667 is logged for both types of named properties.

    The perfmon counter is probably reporting on the total number of named properties, not just the one you're concerned with.

    Have a look at your registry and see if the values have already been increased. If not, increase them for one, or both, of the named property quotas.

    http://technet.microsoft.com/en-us/library/bb851492(v=exchg.80).aspx


    --- Rich Matheisen MCSE&I, Exchange MVP

    Saturday, November 9, 2013 7:12 PM
  • Registry settings for the Mailbox DB Private-GUID in question

    Named Props Quota 16384
    NonMAPI Named Props Quota 8192

     

    Monday, November 11, 2013 7:23 PM
  • MFCMAPI shows the following info:

    Tag: 0x85E2000A
    Type: PT_ERROR
    DASL: http://schemas.microsoft.com/mapi/string/{00020329-0000-0000-C000-000000000046}/BBQ-52e21994429749dfab976c966154e031
    Named Prop Name: sz: "BBQ-52e21994429749dfab976c966154e031"
    Named Prop Guid: {00020329-0000-0000-C000-000000000046} = PS_PUBLIC_STRINGS

    Error Code: (HEX) 0x80070005

    Error Name: MAPI_E_NO_ACCESS



    • Edited by net_tech Monday, November 11, 2013 7:49 PM
    Monday, November 11, 2013 7:48 PM
  • Looks like it's time to increase the NonMAPI Named Props Quota.

    --- Rich Matheisen MCSE&I, Exchange MVP

    Monday, November 11, 2013 10:26 PM
  • All that shows me is that you don't have the necessary permission to access the data.

    What does 0x85e200a represent?

    If the name of the property is BBQ-52..... then what's adding that property?


    --- Rich Matheisen MCSE&I, Exchange MVP

    Monday, November 11, 2013 10:48 PM
  • I am surprised that I have to increase NonMAPI Named Props, because the custom app that's creating the email is adding a random custom header (BBQ-52) to each email generated, however emails are sent from outlook by the user.
    Wednesday, November 13, 2013 5:24 PM
  • Is "BBQ-52" the entire name of the header? Or is there a unique "BBQ-52........" header for each message?

    If there was on a "BBQ-52" header in each message then there would be only one such header added to the property names. If there's a different header for each message then you'll have as many property names as you have messages that have such headers.


    --- Rich Matheisen MCSE&I, Exchange MVP

    Thursday, November 14, 2013 4:07 AM
  • BBQ-52........ is unique for each message, I had over 6000 rows filed with random BBQ-52........ values. Wouldn't they be considered MAPI properties since messages are sent from outlook?
    • Edited by net_tech Thursday, November 14, 2013 5:37 PM
    Thursday, November 14, 2013 5:35 PM
  • I would have guessed that, but since the quota for MAPI named props is 16K and the event is reporting you've exceeded the quota of 8K my guess would have been incorrect.

    I'd find the developer and have him thrashed. :-)


    --- Rich Matheisen MCSE&I, Exchange MVP

    • Marked as answer by net_tech Saturday, November 16, 2013 12:31 AM
    Thursday, November 14, 2013 10:18 PM
  • Found the developer and got some info from him. He was adding a custom header to the message at the time of the message creation (so he could track if the message is discarded prior to being sent).

    Maybe that was the reason why headers didn’t get classified as mapi.

    Anyway, the mailbox database is now trash and all 700 users need to be moved in to a new mailbox database.

    I do realize that custom emails from Sent items need to be hard deleted before I start the move process.

    Friday, November 15, 2013 12:37 AM
  • Your developer can use the Message-ID header to track that information. If he likes to use "BBQ-52...." then have the header look like "Message-ID: BBQ-52-....@the-clients-machine-name".

    Now he can track the message AND the machine that sent it!


    --- Rich Matheisen MCSE&I, Exchange MVP


    Friday, November 15, 2013 10:52 PM