Re: public folders snap-in is hanging mmc.exe

Hi Steve,

Thanks for your update.

Based on my knowledge, the behavior you encountered is expected. Let me
have a further explanation.

Basically, there are the following Exchange related Virtual Directories
(VD) created in IIS.

1. Exchange: Contains the private mailbox stores.
2. Public: Contains the default public folders tree.
3. OMA: special for Outlook Mobile Access
4. Microsoft-Server-ActiveSync: special for ActiveSync access
5. Exchweb: Stores graphics and other ancillary files used by Outlook Web
Access.
6. Exadmin: Used by Exchange System Manager to administer public folders.

Among them, Exchange, Microsoft-Server-ActiveSync, OMA and Public VDs are
used for customer direct access by inputting http://ExchangeServer/ in
Internet browser. Exchange VD contains the private mailbox stores. Public
VD contains the default public folders tree. Microsoft-Server-ActiveSync VD
and OMA VD are used for Mobile Device ActiveSync and OMA Access. We call
them direct access VD and open for customers.

However, ExchWeb and Exadmin VDs are not directly accessed by customer from
Internet Explorer. ExchWeb VD stores graphics and other ancillary files
used by Outlook Web Access; and Exadmin VD is used by Exchange System
Manager to administer public folders. We call them indirect access VD..

So let's focus on EXadmin virtual directory. Please double check by the
steps below:


1. Click Start, point to Programs, click Administrative Tools, and then
click Internet Services Manager.
2. Click your server, and then expand the Web site that contains the
Exadmin virtual root (the default Web site is "Default Web Site").
3. Right-click Exadmin, and then click Properties.
4. Click the Directory Security tab.
5. Under Secure Communications, click Edit.
6. Click to clear the Require secure channel (SSL) check box. If Require
128-bit encryption is shaded, click to select Require secure channel (SSL),
click to clear Require 128-bit encryption, and then click to clear the
Require secure channel (SSL) check box again.
7. Click OK two times.
8. Restart IIS Admin Service (services.msc).
9. Restart Exchange System Manager.

Please verify whether the issue disappears when you open Public Folder in
ESM

1. Launch ADSIEdit utility integrated in Windows Support Tools, in the left
side pane expand the Configuration container.

2. Expand the following: CN=Configuration, then CN=Services, CN=Microsoft
Exchange, CN=<your organization name here>, CN=Administrative Groups,
CN=First Administrative Group <or it may be your original Exchange 5.5 site
name>, CN=Servers, CN=Protocols, CN=HTTP, CN=1, CN=Exadmin

3. Right-click Exadmin and choose Properties.

4. In the Properties dialog box, drop down the Attributes list and scroll
down to the attribute "msExchSecureBindings" and double click on it.

5. The value of this attribute may be 443 (this is the SSL Port value). If
it is, click the 443 value to select it and click the "Remove" button. Then
click "Apply" and then "OK".

6. Close out of ADSI Edit.

7. Restart Exchange System Attendant Service (Services.msc) and then
restart Exchange System Manager.


If the issue persists, please recreate the virtual directory of Default Web
Site.
To do so:
a. Download and 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

If you do not want to install all the IIS 6.0 Resource Kit Tools, click the
Custom installation option to install only Metabase Explorer 1.6.
b. Start IIS Manager.
c. Back up the metabase. To do this, right-click Default Web Site, click
All Tasks, and then click Save Configuration to a File. Type a filename for
the file and click OK.
d. Expand Default Web Site, and then delete the following virtual
directories:
o Microsoft-Server-ActiveSync
o OMA
o Exadmin
o Exchange
o Public
o ExchWeb

e. Start Metabase Explorer. To do this, click Start, point to All
Programs, point to IIS Resources, point to Metabase Explorer, and then
click Metabase Explorer.
f. Expand the LM key, right-click the DS2MB key, and then click Delete.
g. Close Metabase Explorer.
h. Restart the Microsoft Exchange System Attendant service to re-create
the virtual directories in IIS.

Note If the virtual directories are not re-created after 15 minutes,
restart the server.

Note If the virtual directories are not re-created after 15 minutes,
restart the server.

Then verify the settings of Exadmin Virtual Directory.

If the issue persists after the steps above, in order to have a more
concrete idea about the issue, please let me know the following
information.

1. Please collect the IIS metabase on Exchange Server and send to me:
v-leeli@xxxxxxxxxxxxx for further analysis:

1). Install .NET Framework Version 1.1:
http://www.microsoft.com/downloads/details.aspx?FamilyID=262d25e3-f589-4842-
8157-034d1e7cf3a3&DisplayLang=en.
2). Install MBExplorer by installing IIS 6 Resource Kit Tools:
http://www.microsoft.com/downloads/details.aspx?FamilyId=56FC92EE-A71A-4C73-
B628-ADE629C89499&displaylang=en.
3). Once it is installed, access it from Start, Programs, IIS Resources,
Metabase Explorer.
4). In the left pane, right click ''LM'' (under your server computer name)
to choose ''Export to file'', and then save it as IIS.mbk.
5). Compress this mbk file and send it to me for analysis:
v-chacez@xxxxxxxxxxxxxx Please let me know if there is any password on the
file.


2. Please collect the IIS log on Exchange Server for further analysis:

1). Open IIS MMC on Exchange Server, right click Default Web Site and then
click Properties.
2). Click Website tab and then check Enable logging.
3). With ''W3C Extended Log File Format'', click ''Properties''.
4). Switch to the ''Extended Properties'', and then select to enable All
the logging Options.
5). Stop the Default Website and RENAME the existing IIS log files under
C:\WINDOWS\system32\LogFiles.
6). Restart the Default Website and reproduce the error c103b404 in
Exchange System Manager, which will makes the new IIS log generation with
the error.
7). Go to the following folder: C:\WINDOWS\system32\LogFiles.

Please send me the log file to my working email address:
v-chacez@xxxxxxxxxxxxx



Hope this helps. And I look forward to your update.

Have a nice day!


Best Regards,

Chace Zhang (MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.

=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

.

Loading