4 comments

• 

  Michael Belmont

  1 year ago

  Don't you think you should tell readers that Event ID 1216 should be fixed? If you leave it as is readers may think that the Exchange Store database periodic dismount is expected.
  
  It seems like a strange way to leave a "Fix It"
  
  No Add-Click for you.
  
  MRB
  reply
• 

  hightechdad

  1 year ago

  @ Michael,
  
  Thanks for the comment. However, I'm not sure I understand your comment. Event 1216 is an Informational message, meaning that it doesn't need to be fixed. I used Event 1216 to let people know how to check to make sure that the registry hack worked and was taking the new value. My article subject does discuss Event 1216 either.
  Sorry that you found it confusing. Hopefully by reading through the article and your and my comments, users will understand the issue and fixes.
  -HTD
  reply
• 

  Mark

  4 months ago

  Your steps don't clearly explain the new entry names. Below are the steps reocmeended by MS...
  Install Exchange 2003 Service Pack 2. This is essential!
  Launch regedit
  Navigate to HKLM/System/CurrentControlSet/Services/MSExchangeIS/<yourservername>
  Under the server name there will be two folders, one called 'private', the other 'public'. Both names are followed by a long string of alphanumerics.
  Highlight the private one.
  Right-click it and choose NEW -> DWORD VALUE
  Call it 'Database Size Limit in Gb' without the quotes. This is case sensitive and you must get it absolutely spot on or it will not work.
  Double-click this new value, change the type to 'decimal' and give it any number up to 75. This is the size in Gb that you want it to be.
  Repeat steps 6 to 8 for the public entry.
  Restart the Exchange Information Store Service.
  reply
• 

  hightechdad

  4 months ago

  Thanks Mark for the details. I wrote this post quite a while ago so it probably has some tips that are stale. I appreciate you bringing it up to speed.
  -HTD
  reply