UPDATE: We have now released the hotfix that corrects this issue for Exchange 2003 SP2. The article is: 930241 The Exchange 2003 database does not mount, and event IDs 9518 and 9519 are logge...
Updated Jul 01, 2019
Version 2.0
Blog Post
I have been assigned to handle the issue with the revised DST where I work. First I'll say what we run, then what has happened so far.
We have a Windows 2000 AD domain running four DCs, and an Exchange 2000 Server that I recently updated to Enterprise Edition.
I have done the following to address DST 2007:
- Created a registry file as per KB 914387 and imported into the registry of all Windows 2000 servers and workstations.
- XP clients received the DST 2007 update through WSUS.
- For the Exchange server, it was a multi-step process. First, I ran the Msextmzcfg.exe tool as per KB 930879 in extraction mode. This wrote all existing email accounts in the private store into an export file, then it allowed to select a timezone to be applied to all the discovered mailboxes. I excluded recurring appointments at the time that I ran it pending the outcome of the regular appointments on all the accounts.
I granted myself "Send on Behalf of" permission for everyone using that GrandMailboxPermission script.
After this finished, I used the Msextmzcfg.exe again in update mode. After modifying the INI file a bit so it knew where to look for what, it went through every single mailbox specified in the export file. It first tried to find a timezone file for each mailbox, and when it didn't find it, it proceeded to set the timezone I specified previously.
I did encounter this error on every mailbox:
HrProcessInputFile:Processing Mailbox:/O=ISABELLA/OU=NYC01/CN=RECIPIENTS/CN=LEHMAEL1
HrProcessMailbox:Timezone set to EASTERN STANDARD TIME.
HrSpawnOLTool:Spawned worker process as pid - 1680.
HrScanEventLogForSuccess:Success Event not found in Application log, treating as failure.
HrProcessMailbox:Unable to process mailbox /O=ISABELLA/OU=NYC01/CN=RECIPIENTS/CN=LEHMAEL1 - 0x80004005
HrProcessInputFile:Error Processing Mailbox:/O=ISABELLA/OU=NYC01/CN=RECIPIENTS/CN=LEHMAEL1 - 0x80004005
However, after the utility finished running, users did encounter changes to their mailboxes. Some reported recurring all-day events changed to a specific time, resulting in calendar events spawning two days instead of one.
Due to focusing on the mailboxes, I forgot to address the public store, and there are several items affected by DST 2007. Unfortunately, I can't seem to find a way or a tool to effect the appropriate changes in it.
So I guess I have several questions...
Is there a way to run the update tool on the public store? Anyone figure this out?
Why do I get failure messages when running the update tool on the mailboxes, or is this merely a false negative?
TIA
Omar
We have a Windows 2000 AD domain running four DCs, and an Exchange 2000 Server that I recently updated to Enterprise Edition.
I have done the following to address DST 2007:
- Created a registry file as per KB 914387 and imported into the registry of all Windows 2000 servers and workstations.
- XP clients received the DST 2007 update through WSUS.
- For the Exchange server, it was a multi-step process. First, I ran the Msextmzcfg.exe tool as per KB 930879 in extraction mode. This wrote all existing email accounts in the private store into an export file, then it allowed to select a timezone to be applied to all the discovered mailboxes. I excluded recurring appointments at the time that I ran it pending the outcome of the regular appointments on all the accounts.
I granted myself "Send on Behalf of" permission for everyone using that GrandMailboxPermission script.
After this finished, I used the Msextmzcfg.exe again in update mode. After modifying the INI file a bit so it knew where to look for what, it went through every single mailbox specified in the export file. It first tried to find a timezone file for each mailbox, and when it didn't find it, it proceeded to set the timezone I specified previously.
I did encounter this error on every mailbox:
HrProcessInputFile:Processing Mailbox:/O=ISABELLA/OU=NYC01/CN=RECIPIENTS/CN=LEHMAEL1
HrProcessMailbox:Timezone set to EASTERN STANDARD TIME.
HrSpawnOLTool:Spawned worker process as pid - 1680.
HrScanEventLogForSuccess:Success Event not found in Application log, treating as failure.
HrProcessMailbox:Unable to process mailbox /O=ISABELLA/OU=NYC01/CN=RECIPIENTS/CN=LEHMAEL1 - 0x80004005
HrProcessInputFile:Error Processing Mailbox:/O=ISABELLA/OU=NYC01/CN=RECIPIENTS/CN=LEHMAEL1 - 0x80004005
However, after the utility finished running, users did encounter changes to their mailboxes. Some reported recurring all-day events changed to a specific time, resulting in calendar events spawning two days instead of one.
Due to focusing on the mailboxes, I forgot to address the public store, and there are several items affected by DST 2007. Unfortunately, I can't seem to find a way or a tool to effect the appropriate changes in it.
So I guess I have several questions...
Is there a way to run the update tool on the public store? Anyone figure this out?
Why do I get failure messages when running the update tool on the mailboxes, or is this merely a false negative?
TIA
Omar