Recently my Exchange 2003 SP2 BE server has started having these errors occur in the Applications Log. I have read all three of the articles below and I am still a bit confused about the solution. I am hoping that someone can shed some light on the subject and help me resolve this. The first link
describes modifying the registry to increase the default quota. This solution seems like a temporary fix to the issue at hand. I would hate to just keep increasing this quota until it hits the hard limit and opens a whole new can of worms.
The second article mentioned a hotfix from MS and description of how to modify the registry to prevent the generation of new named properties. This seems like a more solid fix but my concerns are the side effects of disabling this feature. If it wasn't necessary, it wouldn't be be there, so by disabling it, what features or functionality would I be losing?
On a side note, the only two accounts listed in the description for this error are the "SYSTEM" and "BES" accounts. Also, the "SYSTEM" account has only started showing up since I enabled OMA in ESM because I am trying to configure a Droid device to connect to our exchange server. As I mentioned earlier, I am a bit confused by all of this so I decided to ask for some help. Thanks in advance,