D
David S. Mohler
The following was also posted in the Microsoft Private Partner newsgroups. I
post it here in the event that others are having similar problems with the
Exchange Information Store.
-----
Hello,
Admittedly I don't have all my facts yet, but I am certain that the latest
SP for Entourage, along with Exchange SP1, are somehow causing major
problems with the Information Store in Exchange 2003.
As long as there are no users connecting to Exchange with Entourage, there
are no problems with Exchange. As soon as a user opens Entourage and
attempts to perform any function related to permissions (such as opening a
shared calendar), Exchange generates errors. It frequently shuts down the
Information Store service which usually can be restarted without rebooting
the server. I am concerned, however, that the Information Store will become
corrupted.
I can reproduce this on two different Windows Small Business Server 2003
platforms. If there is a bug, then Information Stores everywhere are
vulnerable. Mind you, this did not start until after the Entourage SP2
update and the associated service packs it requires were installed on
Exchange.
We applied, in the following order, these patches:
Entourage SP2 on MAC OS 10.3
[At this point we had some authentication issues]
Exchange SP1
[Authentication issues went away, and now the IS shuts down randomly]
KB888619 to Exchange Server 2003
[IS shuts down when activity related to permissions is attempted, but not
always - still researching this]
Windows Server 2003 SP1
[No change]
KB843539 to SBS2003 Standard Edition
[No change]
These errors are always reproduced in the following sequence:
Event Type: Warning
Event Source: WinMgmt
Event ID: 5603
User: NT AUTHORITY\SYSTEM
A provider, PerfProv, has been registered in the WMI namespace,
ROOT\CIMV2\MicrosoftHealthMonitor\PerfMon, but did not specify the
HostingModel property. This provider will be run using the LocalSystem
account. This account is privileged and the provider may cause a security
violation if it does not correctly impersonate user requests. Ensure that
provider has been reviewed for security behavior and update the HostingModel
property of the provider registration to an account with the least
privileges possible for the required functionality.
[FOLLOWING ERROR ALWAYS OCCURS A SECOND TIME]
Event Type: Warning
Event Source: WinMgmt
Event ID: 5603
User: NT AUTHORITY\SYSTEM
A provider, PerfProv, has been registered in the WMI namespace,
ROOT\CIMV2\MicrosoftHealthMonitor\PerfMon, but did not specify the
HostingModel property. This provider will be run using the LocalSystem
account. This account is privileged and the provider may cause a security
violation if it does not correctly impersonate user requests. Ensure that
provider has been reviewed for security behavior and update the HostingModel
property of the provider registration to an account with the least
privileges possible for the required functionality.
Event Type: Error
Event Source: POP3SVC
Event ID: 1026
Initialization of the POP3 external interface failed with error 0x80040110.
Event Type: Error
Event Source: MSExchangeIS
Event ID: 9542
Initialization of external interface POP3 failed; Error
ecVersionMismatch-MAPI_E_VERSION.
Event Type: Error
Event Source: IMAP4SVC
Event ID: 1026
Initialization of the IMAP4 external interface failed with error 0x80040110.
Event Type: Error
Event Source: MSExchangeIS
Event ID: 9542
Initialization of external interface IMAP4 failed; Error
ecVersionMismatch-MAPI_E_VERSION.
Event Type: Error
Event Source: MSExchangeIS
Event ID: 9542
Initialization of external interface NNTP failed; Error
ecVersionMismatch-MAPI_E_VERSION.
Event Type: Error
Event Source: EXCDO
Event ID: 8197
Calendaring agent failed to initialize with error 0x80040110.
Event Type: Error
Event Source: MSExchangeIS
Event ID: 9542
Initialization of external interface CDO SERVER failed; Error
ecVersionMismatch-MAPI_E_VERSION.
Microsoft needs to get it together on the Entourage product. The inequality
with Outlook 9 for Mac, and the network connection reliability between
Entourage and Exchange Server 2003, have been awful. The updates are too few
and far between, and the regression testing appears to be lacking.
David
post it here in the event that others are having similar problems with the
Exchange Information Store.
-----
Hello,
Admittedly I don't have all my facts yet, but I am certain that the latest
SP for Entourage, along with Exchange SP1, are somehow causing major
problems with the Information Store in Exchange 2003.
As long as there are no users connecting to Exchange with Entourage, there
are no problems with Exchange. As soon as a user opens Entourage and
attempts to perform any function related to permissions (such as opening a
shared calendar), Exchange generates errors. It frequently shuts down the
Information Store service which usually can be restarted without rebooting
the server. I am concerned, however, that the Information Store will become
corrupted.
I can reproduce this on two different Windows Small Business Server 2003
platforms. If there is a bug, then Information Stores everywhere are
vulnerable. Mind you, this did not start until after the Entourage SP2
update and the associated service packs it requires were installed on
Exchange.
We applied, in the following order, these patches:
Entourage SP2 on MAC OS 10.3
[At this point we had some authentication issues]
Exchange SP1
[Authentication issues went away, and now the IS shuts down randomly]
KB888619 to Exchange Server 2003
[IS shuts down when activity related to permissions is attempted, but not
always - still researching this]
Windows Server 2003 SP1
[No change]
KB843539 to SBS2003 Standard Edition
[No change]
These errors are always reproduced in the following sequence:
Event Type: Warning
Event Source: WinMgmt
Event ID: 5603
User: NT AUTHORITY\SYSTEM
A provider, PerfProv, has been registered in the WMI namespace,
ROOT\CIMV2\MicrosoftHealthMonitor\PerfMon, but did not specify the
HostingModel property. This provider will be run using the LocalSystem
account. This account is privileged and the provider may cause a security
violation if it does not correctly impersonate user requests. Ensure that
provider has been reviewed for security behavior and update the HostingModel
property of the provider registration to an account with the least
privileges possible for the required functionality.
[FOLLOWING ERROR ALWAYS OCCURS A SECOND TIME]
Event Type: Warning
Event Source: WinMgmt
Event ID: 5603
User: NT AUTHORITY\SYSTEM
A provider, PerfProv, has been registered in the WMI namespace,
ROOT\CIMV2\MicrosoftHealthMonitor\PerfMon, but did not specify the
HostingModel property. This provider will be run using the LocalSystem
account. This account is privileged and the provider may cause a security
violation if it does not correctly impersonate user requests. Ensure that
provider has been reviewed for security behavior and update the HostingModel
property of the provider registration to an account with the least
privileges possible for the required functionality.
Event Type: Error
Event Source: POP3SVC
Event ID: 1026
Initialization of the POP3 external interface failed with error 0x80040110.
Event Type: Error
Event Source: MSExchangeIS
Event ID: 9542
Initialization of external interface POP3 failed; Error
ecVersionMismatch-MAPI_E_VERSION.
Event Type: Error
Event Source: IMAP4SVC
Event ID: 1026
Initialization of the IMAP4 external interface failed with error 0x80040110.
Event Type: Error
Event Source: MSExchangeIS
Event ID: 9542
Initialization of external interface IMAP4 failed; Error
ecVersionMismatch-MAPI_E_VERSION.
Event Type: Error
Event Source: MSExchangeIS
Event ID: 9542
Initialization of external interface NNTP failed; Error
ecVersionMismatch-MAPI_E_VERSION.
Event Type: Error
Event Source: EXCDO
Event ID: 8197
Calendaring agent failed to initialize with error 0x80040110.
Event Type: Error
Event Source: MSExchangeIS
Event ID: 9542
Initialization of external interface CDO SERVER failed; Error
ecVersionMismatch-MAPI_E_VERSION.
Microsoft needs to get it together on the Entourage product. The inequality
with Outlook 9 for Mac, and the network connection reliability between
Entourage and Exchange Server 2003, have been awful. The updates are too few
and far between, and the regression testing appears to be lacking.
David