Microsoft KB Archive/937956

= A call to the DeleteMailbox method of the Hosted Exchange namespace is not successful in a hosted environment that has Microsoft Solution for Hosted Messaging and Collaboration 3.5 Feature Pack 1 installed =

Article ID: 937956

Article Last Modified on 1/2/2008

-

APPLIES TO


 * Microsoft Solution for Hosted Messaging and Collaboration 3.5

-



SYMPTOMS
In a hosted environment that has Microsoft Solution for Hosted Messaging and Collaboration 3.5 Feature Pack 1 installed, a call to the DeleteMailbox method of the Hosted Exchange namespace is not successful. In this hosted environment, the Live Communications Server (LCS) component is not deployed or is not configured. Or, the user whose mailbox is being deleted is not enabled for the LCS component. Additionally, the DeleteMailbox method returns the following error message:



















CAUSE
This problem occurs because of an issue in the Hosted Exchange namespace code in Hosted Messaging and Collaboration 3.5 Feature Pack 1.



Hotfix information
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Hosted Messaging and Collaboration service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites
To apply this hotfix, you must have Hosted Messaging and Collaboration 3.5 Feature Pack 1 installed.

Restart requirement
You do not have to restart the computer after you apply this hotfix. However, you have to stop and then restart the Microsoft Provisioning Server (MPS) Provisioning Engine service.

Hotfix replacement information
This hotfix does not replace a previously released hotfix.

File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Steps to apply the hotfix
Important Before you apply the hotfix, make sure that you remove any workaround for this problem.

Use the MPS Deployment Tool
Important If you have more than 50,000 users in the environment, do not use the Deployment Tool. Instead, you must apply the hotfix manually. To do this, follow the steps that are described in the &quot;Manually apply the hotfix&quot; section in this article.

To use the Deployment Tool to apply the hotfix in Hosted Messaging and Collaboration Solution 3.5 environments and in Hosted Messaging and Collaboration Solution 3.0 environments, follow these steps:
 * 1) Log on to the MPS01 server by using an account that is a member of the Domain Admins group.
 * 2) Start the Microsoft Provisioning System (MPS) Deployment Tool.
 * 3) In the Requirements Status pane, expand Windows-based Hosting, right-click MPSImport, and then click Force State.
 * 4) Under States, click Not Installed, and then click OK.
 * 5) In the Requirements Status pane, expand Exchange Hosting, right-click Hosted Exchange, and then click Uninstall.
 * 6) Click Start Deployment. Wait for the Deployment Complete dialog box to appear.
 * 7) Open Windows Explorer, and then locate the C:\MSIShare folder.
 * 8) Back up the HostedExchangeNS.msi file to another location.
 * 9) Copy the HostedExchangeNS.msi file from the hotfix distribution to the C:\MSIShare folder. Overwrite the existing file.
 * 10) In the MPS Deployment Tool, expand Exchange Hosting, right-click Hosted Exchange, and then click Install.
 * 11) Click Start Deployment. Wait for the Deployment Complete dialog box to appear.

Note The Deployment Tool automatically runs the InitializeHostedExchange procedure as part of this deployment. When the deployment finishes, Hosted Exchange is fully installed and configured.
 * 1) Expand Windows-based Hosting, right-click MPSImport, and then click Force State.
 * 2) Under States, click Verified, and then click OK.

Manually apply the hotfix
To apply the hotfix manually in Hosted Messaging and Collaboration Solution 3.5 environments or in Hosted Messaging and Collaboration Solution 3.0 environments, follow these steps:  Log on to the MPS01 server by using an account that is a member of the Domain Admins group. Remove the existing version of the Hosted Exchange namespace. To do this follow these steps:  Run the following command at a command prompt:

msiexec /x \\MPS01\Msishare\HostedExchangeNS.msi ENABLEUI=YES

</li> Follow the wizard to remove the existing Hosted Exchange Namespace.

Note If you have multiple MPS Engine Servers, you must repeat step 2 for each server.</li></ol> </li> On the MPS01 server, open Windows Explorer.</li> Locate the C:\MSIShare folder, and then back up the HostedExchangeNS.msi file to another location.</li> Copy the HostedExchangeNS.msi file from the hotfix distribution to the C:\MSIShare folder. Overwrite the existing file.</li> On the MPS01 server, follow these steps: <ol style="list-style-type: lower-alpha;"> Run the following command at the command prompt to install the new version of the Hosted Exchange namespace:

msiexec /i \\MPS01\Msishare\HostedExchangeNS.msi ENABLEUI=YES

</li> Follow the wizard to install the new version of the Hosted Exchange namespace.

Note If you have multiple MPS Engine Servers, you must repeat step 6 for each server.</li></ol> </li> On the MPS01 server, run the following command at the command prompt:

c:\program files\microsoft provisioning\tools\provtest.exe %SYSTEMDRIVE%:\Program Files\Microsoft Hosting\Provisioning\Sample\Hosted Exchange\InitializeNamespaceSecurity.xml /x2

Note This command initializes the namespace security for the Hosted Exchange namespace without completing the data upgrade process.</li></ol>

<div class="workaround_section">

WORKAROUND
To work around this problem, follow these steps:
 * 1) In the Microsoft Hosting\Provisioning\MPF Namespace\ManagedHelpers_ns.xml file, use the Managed Helpers::LCSDisableUser_ procedure in provisioning manager to add   at the beginning of the first   section.
 * 2) Add the following lines before   in Managed Helpers::LCSDisableUser_.

<execute namespace=”Managed Active Directory” procedure=”RethrowError”> <executeData> </executeData> After you make these changes, restart the Microsoft Provisioning Engine COM+ component in component services.

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

<div class="moreinformation_section">

MORE INFORMATION
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

817903 New naming schema for Exchange Server software update packages

Additional query words: DeleteMailbox HMC FP1 LCS

Keywords: kbexpertiseinter kbhotfixserver kbqfe KB937956

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.