Outlook Web Access could not find a mailbox for DOMAIN\IUSR_EXCHANGE.
Restoring the Metabase with History Files (IIS 6.0)
The metabase consists of the following elements:
• MetaBase.xml file. This file stores IIS configuration information that is specific to an installation of IIS.
• MBSchema.xml file. This file contains the metabase schema. The MBSchema.xmlfileis a master configuration file that defines default attributes for all metabase properties and enforces rules for constructing and placing metabase entries within the metabase.
Notice that the dialog box (refer back to ) displays both metabase backups stored in %SystemRoot%\System32\inetsrv\MetaBack and history files stored in %SystemRoot%\System32\inetsrv\History in one combined list. You can tell the difference between a history file and a backup file in this list by looking at the filenames: all history files are named Automatic Backup and are distinguished in the GUI only by their timestamp, while backup files you create are named whatever you decide to call them.
IIS periodically creates history files consisting of copies of the metabase configuration file (MetaBase.xml) and the matching metabase schema file (MBSchema.xml). Restoring the metabase from history files is similar to restoring the metabase from backup files.
You must be a member of the Administrators group on the local computer to run scripts and executables. As a security best practice, log on to your computer by using an account that is not in the Administrators group, and then use the runas command to run your script or executable as an administrator. At a command prompt, type runas /profile /user:MyComputer\Administrator cmd to open a command window with administrator rights and then type cscript.exeScriptName (include the script’s full path and any parameters).
Procedures
To restore the metabase using IIS Manager
1.In IIS Manager, right-click the local computer, point to All Tasks, and click Backup/Restore Configuration.
2.In the Backups list, click the Automatic Backup you want to restore, and then click Restore.
3.Read the message that appears and click Yes if you want to continue.
4.Click OK.
To manually restore the metabase
1.From the Start menu, click Run.
2.In the Open box, type cmd, and then click OK.
3.Stop the IIS services by typing iisreset /stop at the command prompt, and then press ENTER. The command prompt displays the following:
Attempting stop…
Internet services successfully stopped
If the IIS services do not stop, and it is possible to restart the computer, type iisreset /stop /rebootonerror, and then press ENTER.
4. Make copies of your current metabase files. At the command prompt, type cd %systemroot%\System32\Inetsrv, and then press ENTER to navigate to the folder where the files are. Next, type copy MBSchema.xml MBSchema.old, and then press ENTER to copy the schema file. Finally, type copy MetaBase.xml Metabase.old, and then press ENTER to copy the metabase configuration file.
5.
Locate the metabase history files. At the command prompt, type cd %systemroot%\System32\Inetsrv\History, and then press ENTER.
6.
Select the version of history files that you want. At the command prompt, type dir, and then press ENTER. All of the files appear in the following format:
<date> <time> <file size> MBSchema_<identifying number>_0000000000.xml
<date> <time> <file size> MetaBase_<identifying number>_0000000000.xml
When you restore the IIS metabase to a previous version, you will need matching metabase schema and configuration files. Select matching files by their identifying number.
7.
Copy the chosen history schema file over the existing metabase schema. At the command prompt, type copy /y MBSchema_<identifying number>_0000000000.xml %systemroot%\System32\Inetsrv\MBSchema.xml, and then press ENTER. With this command, you copy the file and rename it at the same time.
8.
Copy the matching history configuration file over the existing metabase configuration. At the command prompt, type copy /y Metabase_<identifying number>_0000000000.xml %systemroot%\System32\Inetsrv\MetaBase.xml, and then press ENTER. Again, this command copies the file and renames it at the same time.
Important
If you mix up the names or copy a schema and configuration file that do not match, the metabase restoration will fail when you start the IIS services.
9.
Restart IIS. At the command prompt, type iisreset /start, and then press ENTER. The command prompt displays the following:
Attempting start…
Internet services successfully started
If the IIS services do not restart, repeat these steps beginning at step 4, and copy a different set of history files over the current metabase files.
Restore the Metabase
Notice that the dialog box (refer back to ) displays both metabase backups stored in %SystemRoot%\System32\inetsrv\MetaBack and history files stored in %SystemRoot%\System32\inetsrv\History in one combined list. You can tell the difference between a history file and a backup file in this list by looking at the filenames: all history files are named Automatic Backup and are distinguished in the GUI only by their timestamp, while backup files you create are named whatever you decide to call them.
First, stop all IIS services by typing net stop iisadmin /y at the command prompt (or use iisreset /stop if you prefer). Then, find the metabase.bin file in %Systemroot%\System32\inetsrv and rename it metabase.bad (keep it in case you need it later). Copy your backup file (it probably has the extension .MD0) from %Systemroot%\System32\inetsrv\MetaBack to %Systemroot%\System32\inetsrv and rename it metabase.bin. Now, restart the computer. You should once again have a working IIS configuration and be able to start Internet Services Manager.
How to reset the default virtual directories that are required to provide Outlook Web Access, Exchange ActiveSync, and Outlook Mobile Access services in Exchange Server 2003
In this scenario, you must use one of the following methods to remove and then re-create the virtual directories in IIS:
•Method 1. Use Metabase Explorer from the IIS 6.0 Resource Kit Tools
•Method 2. Use Adsutil.vbs
•Method 3: Edit the Metabase.xml file
Method 1: Use Metabase Explorer from the IIS 6.0 Resource Kit Tools
1.
Install the IIS 6.0 Resource Kit Tools. To obtain the IIS 6.0 Resource Kit Tools, visit the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?FamilyID=56FC92EE-A71A-4C73-B628-ADE629C89499&displaylang=en (http://www.microsoft.com/downloads/details.aspx?FamilyID=56FC92EE-A71A-4C73-B628-ADE629C89499&displaylang=en)
Note If you do not want to install all the IIS tools on your computer, you can install only the Metabase Explorer 1.6 component. To do this, follow these steps:
a.
Double-click iis60rkt.exe, and then follow the instructions that are on your screen until you reach the Setup Type page of the IIS 6.0 Resource Kit Tools Setup Wizard.
b.
On the Setup Type page, click Custom, and the click Next.
c.
Click to clear all the IIS Resource Kit Tools and components check boxes except the Metabase Explorer 1.6 check box.
d.
Click Next, and then click Finish.
2.
Back up your IIS metabase. To do this, follow these steps:
a.
Start IIS Manager.
b.
Right-click Default Web Site, point to All Tasks, and then click Save Configuration to a File.
c.
In the Save Configuration to a File dialog box, type a configuration name in the File name input box, and then click OK.
3.
Delete the virtual directories for Outlook Web Access. To do this, expand the Default Web Site in the left pane of IIS Manager, right-click Exadmin, and then click Delete. Click Yes when you are prompted with the question of whether you want to delete this item.
Repeat this step for the following virtual directories:
•
Exchange
•
ExchWeb
•
Microsoft-Server-ActiveSync
•
OMA
•
Public
4.
Quit IIS Manager.
5.
Click Start, point to All Programs, point to IIS Resources, point to Metabase Explorer, and then click Metabase Explorer.
6.
Expand LM, right-click DS2MB, and then click Delete. Click Yes when you are prompted with the question of whether you want to delete this key and all subkeys.
7.
Quit IIS Metabase Explorer.
8.
Click Start, point to All Programs, point to Administrative Tools, and then click Services.
9.
To restart the Microsoft Exchange System Attendant service, follow these steps:
a.
Click Start, click Run, type services.msc, and then click OK.
b.
Right-click Microsoft Exchange System Attendant, and then click Restart.
c.
When you are prompted to restart the dependant Exchange Server services, click Yes.
Note When you restart the Microsoft Exchange System Attendant service, the Microsoft Exchange Information Store service is also restarted. In this scenario, your Exchange Server users lose connectivity to their Exchange Server mailboxes.
The virtual directories are re-created. To verify that the virtual directories are re-created, start IIS Manager, and then view the Default Web site folder.
Important If the virtual directories are not re-created after 15 minutes, restart your computer.
10.
Reset the access permissions to Anonymous. To do this, follow these steps:
a.
Start IIS Manager, right-click ExchWeb, click Properties, and then click the Directory Security tab.
b.
Under Authentication and access control click Edit, and then verify that the Enable anonymous access check box is turned on.
c.
Click to select the Integrated Windows authentication check box, click OK, and then click Apply.
d.
If you an Inheritance Overrides dialog box appears, click Select All, and then click OK.
e.
Under Authentication and access control, click Edit, and then click to clear the Integrated Windows authentication check box.
f.
Click OK two times, and then quit IIS Manager.
Use a Web browser to verify that you can connect to your Outlook Web Access server. If you are also running other mobility services, verify that you can connect to these services by using an appropriate client.
Method 2: Use Adsutil.vbs
1.
Back up your IIS Metabase. To do this, follow these steps:
a.
Start IIS Manager.
b.
Right-click Default Web Site, point to All Tasks, and then click Save Configuration to a File.
2.
Delete the virtual directories for Outlook Web Access. To do this, right-click Exadmin in the left pane of IIS Manager, and then click Delete. Click Yes when you are prompted with the question of whether you want to delete this item.
Repeat this step for the following virtual directories:
•
Exchange
•
ExchWeb
•
Microsoft-Server-ActiveSync
•
OMA
•
Public
3.
Quit IIS Manager.
4.
Click Start, click Run, type cmd, and then press ENTER.
5.
Change to the following folder. In this example, Drive is the hard disk drive where Windows is installed:
Drive:\inetpub\adminscripts
6.
Type adsutil, and then press ENTER.
Important By default, CScript is not the default scripting host for Windows Server 2003. To run the adsutil command, CScript must be configured as the default scripting host. To do this, click Yes if you are prompted to register CScript as you default host for VBscript, and then click OK.
Note If you receive a list of adsutil command options, CScript is already configured as the default scripting host for VBscript.
7.
Type adsutil delete ds2mb, and then press ENTER.
Note To set the default scripting host to WScript, type WScript //H:WScript at the command prompt, press ENTER, and then click OK.
8.
Click Start, point to All Programs, point to Administrative Tools, and then click Services.
9.
To restart the Microsoft Exchange System Attendant service, follow these steps:
a.
Click Start, click Run, type services.msc, and then click OK.
b.
Right-click Microsoft Exchange System Attendant, and then click Restart.
c.
When you are prompted to restart the dependant Exchange Server services, click Yes.
Note When you restart the Microsoft Exchange System Attendant service, the Microsoft Exchange Information Store service is also restarted. In this scenario, your Exchange Server users lose connectivity to their Exchange Server mailboxes.
The virtual directories are re-created. To verify that the virtual directories are re-created, start IIS Manager, and then view the Default Web site folder.
Important If the virtual directories are not re-created after 15 minutes, restart the computer.
10.
Reset the access permissions to Anonymous. To do this, follow these steps:
a.
Start IIS Manager, right-click ExchWeb, click Properties, and then click the Directory Security tab.
b.
Under Authentication and access control click Edit, and then verify that the Enable anonymous access check box is turned on.
c.
Click to select the Integrated Windows authentication check box, click OK, and then click Apply.
d.
If an Inheritance Overrides dialog box appears, click Select All, and then click OK.
e.
Under Authentication and access control, click Edit, and then click to clear the Integrated Windows authentication check box.
f.
Click OK two times, and then quit IIS Manager.
Use a Web browser to verify that you can connect to your Outlook Web Access server. If you are also running other mobility services, verify that you can connect to these services by using an appropriate client.
Method 3: Edit the Metabase.xml file
To resolve this issue, you must modify the Metabase.xml file. The modified Metabase.xml file causes the Exchange Server-related virtual directories to be re-created when the Microsoft Exchange System Attendant service is restarted. To do this, follow these steps.
Warning If you edit the metabase incorrectly, you can cause serious problems that may require you to reinstall any product that uses the metabase. Microsoft cannot guarantee that problems that result if you incorrectly edit the metabase can be solved. Edit the metabase at your own risk.
Note Always back up the metabase before you edit it.
1.
Configure IIS to enable real-time editing of the metabase. To do this, follow these steps:
a.
Click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
b.
Right-click ServerName (local computer) , and then click Properties.
Note Replace ServerName with the name of the computer that is running IIS.
c.
Click to select the Enable Direct Metabase Edit check box, and then click OK.
2.
Modify the Metabase.xml file. The metabase is a database that resides in memory on the computer that is running IIS. When the computer shuts down, all the metabase settings are written to a file that is named Metabase.bin. You can modify the Metabase.xml file to cause the Exchange Server-related virtual directories to be re-created in IIS when the Microsoft Exchange System Attendant service restarts. To do this, follow these steps:
a.
Open the Metabase.xml by using a text editor such as Notepad. By default, the Metabase.xml file is located in the following folder:
%windir%\System32\Inetsrv
b.
On the Edit menu, click Find.
c.
In the Find what box, type 61472, and then click Find Next to locate the following area in this file:
<IIsConfigObject Location=”/LM/DS2MB/HighWaterMarks/{79F81D41-A652-4375-85F0-41A16037CC85}”>
<Custom
Name=”UnknownName_61472″
ID=”61472″
Value=”207778″
Type=”STRING”
UserType=”IIS_MD_UT_SERVER”
Attributes=”NO_ATTRIBUTES”
/>
d.
In this area of the Metabase.xml file, replace the Value entry with 0. For example, modify this area of the Metabase.xml file so that it appears similar to the following:
<IIsConfigObject Location=”/LM/DS2MB/HighWaterMarks/{79F81D41-A652-4375-85F0-41A16037CC85}”
>
<Custom
Name=”UnknownName_61472″
ID=”61472″
Value=”0″
Type=”STRING”
UserType=”IIS_MD_UT_SERVER”
Attributes=”NO_ATTRIBUTES”
/>
e.
Save your changes to the Metabase.xml file. Then, quit Notepad.
Note You can also use the Metabase Editor tool (MetaEdit.exe) to modify this value in the metabase. For more information about how to obtain MetaEdit, click the following article number to view the article in the Microsoft Knowledge Base:
232068 (http://support.microsoft.com/kb/232068/) How to download, install, and remove the IIS MetaEdit 2.2 utility
3.
To restart the Microsoft Exchange System Attendant service, follow these steps:
a.
Click Start, click Run, type services.msc, and then click OK.
b.
Right-click Microsoft Exchange System Attendant, and then click Restart.
c.
When you are prompted to restart the dependant Exchange Server services, click Yes.
NoteWhen you restart the Microsoft Exchange System Attendant service, the Microsoft Exchange Information Store service is also restarted. In this scenario, your Exchange Server users lose connectivity to their Exchange Server mailboxes.
4.
Restore the default IIS setting to disable real-time editing of the metabase. To do this, follow these steps:
a.
Click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
b.
Right-click ServerName (local computer) , and then click Properties.
c.
Click to clear the Enable Direct Metabase Edit check box, and then click OK.
The virtual directories are re-created. To verify that the virtual directories are re-created, start IIS Manager, and then view the Default Web site folder.
Important If the virtual directories are not re-created after 15 minutes, restart the computer.
Use a Web browser to verify that you can connect to your Outlook Web Access server. If you are also running other mobility services, verify that you can connect to these services by using an appropriate client.
Commands Erros Message:
Outlook Web Access could not find a mailbox for IUSR_EXCHANGE
HTTP 401 or 404 error messages when you access OWA implicitly or explicitly
Event ID 64 is logged in the Application log on the Exchange 2007 server, and you receive the following error message when you try to access Outlook Web Access: “Outlook Web Access did not initialize”
To resolve this error, follow one of these steps:
-
Rename the Web site back to its original name.
-
Restore Internet Information Services (IIS) metabase configuration settings from backup.
http://www.msexchange.org/tutorials/Resetting-OWA-Folder-IIS-security-permissions-Exchange-2003.html
http://www.msexchange.org/tutorials/Securing-Exchange-Server-2003-Outlook-Web-Access-Chapter5.html
One Response to “Outlook Web Access could not find a mailbox for DOMAIN\IUSR_EXCHANGE.”
Leave a Reply
You must be logged in to post a comment.