Re: Can't access public folder properties

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi,

Thank you for posting here.

In order to get a clear picture on this issue, please let me know the
following questions:

Did you encountered No 80090308 during expand public folder in ESM? Since
different error code indicated various causes. Please verify this info.

After you finished the steps in my previous response, did you perform
"IISRESET" in command prompt? I would like to suggest you reboot your
server and try again.


As the re-injection of the certificate in the IIS does not work for this
issue, I think we actually need to reconfigure the certificate in the CEICW
wizard. This also could let us know if the server could successfully accept
the certificate. As the previous steps, we may still need to remove the
certificate from the IIS console first, then, reinput the correct
certificate.

Additionally, if I understand correctly that your server certificate is
purchased from the third-party authority other than created by the SBS
script in the CEICW. If so, the following steps apply.

1. Open IIS Manager
2. Navigate to Web Sites\Default Web Site
3. Right click Default Web Site and choose Properties.
4. Click on the Directory Security tab.
5. Under Secure Communications, click the Server Certificate button.
6. In the IIS Certificate Wizard, choose the "Remove the current
certificate" option and click Next.
7. Click Next again, then click Finish.
8. Restart the IIS admin service.

Note, you may stop the service [IIS Admin Service] in the services console
and restart it. Also, you may need to make sure the following related
services are restarted afterwards.

World Wide Web Publishing Service
Simple Mail Transfer Protocol (SMTP)
Microsoft Exchange Routing Engine
HTTP SSL

9. Run the Configure Email and Internet Connection wizard. In the Web
Server Certificate section, click the option to "Use a Web server
certificate from a trusted authority" and browse to the location of the
certificate.

10. Complete the Configure Email and Internet Connection wizard.

After that, please test your issue again. If there is any further error
message during processing the above steps, please capture a screenshot of
the error and I will pursue a further research on it.

Also please collect metabase and send it to me for further research. My
email address: v-chacez@xxxxxxxxxxxxx

Use the Metabase Explorer to export the IIS settings:
a. Install .NET Framework Version 1.1:

http://www.microsoft.com/downloads/details.aspx?FamilyID=262d25e3-f589-4842-
8157-034d1e7cf3a3&DisplayLang=en

b. Install MBExplorer by installing IIS 6 Resource Kit Tools:
http://www.microsoft.com/downloads/details.aspx?FamilyId=56FC92EE-A71A-4C73-
B628-ADE629C89499&displaylang=en

c. Once it is installed, access it from Start, Programs, IIS Resources,
Metabase Explorer.
d. In the left pane, right click 'LM' (under your server computer name) to
choose 'Export to file', and then save it as IIS.mbk.
e. Compress this mbk file and send it to me for analysis.

If you have any questions or concerns related to this issue, please let me
know.

I appreciate your time and look forward to hearing from you.

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.

--------------------
| Thread-Topic: Can't access public folder properties
| thread-index: AcbHDFXGKHGjsrtHRnqy/nhNyklwiw==
| X-WBNR-Posting-Host: 64.50.46.226
| From: =?Utf-8?B?RGFycmVuQ0ND?= <DarrenCCC@xxxxxxxxxxxxxxxxxxxxxxxxx>
| References: <E074CB6B-6258-4C98-91A3-45E66191834B@xxxxxxxxxxxxx>
<enBFqeCuGHA.3264@xxxxxxxxxxxxxxxxxxxx>
<B0C47DBD-7C59-453D-8815-5F10C3E985E0@xxxxxxxxxxxxx>
<4a79I#cxGHA.2504@xxxxxxxxxxxxxxxxxxxxx>
| Subject: Re: Can't access public folder properties
| Date: Wed, 23 Aug 2006 16:32:01 -0700
| Lines: 163
| Message-ID: <1B926B9D-0F1E-4DAF-81F0-C0CE863B7AB4@xxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
| Newsgroups: microsoft.public.windows.server.sbs
| Path: TK2MSFTNGXA01.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:292431
| NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| I folled the instructions... Still not working. This is SBS 2003
although
| you referenced exchange 2000. In any case, I deselected the SSL
Requirements
| and tested. didn't work. I then installed the tools and used adsi to
remove
| the 443 things still aren't working.
| Please advise.
|
| "chace zhang" wrote:
|
| > Hi,
| >
| > Thank you for posting here.
| >
| > To keep this thread clean, I recommend you to open a new thread for
further
| > discussion. A support engineer will be assigned (maybe it will be me
again).
| >
| >
| > Also I would like to provide you following info on this issue.
| >
| > According to your description, I understand that you received this
error
| > message "Exchange System Manager. The token supplied to the function is
| > invalid. ID no: 80090308", when trying to access or manage Public
Folders
| > after you installed a third-party certificate on the SBS 2003 Server.
If I
| > have misunderstood the problem, please don??t hesitate to let me know.
| >
| > Based on my experience, please refer to the following information to
| > resolve this issue:
| >
| > I. For SBS 2003, if one has an authorized certificate (in CER
| > extension and FQDN format), please make sure you performed the
following
| > steps to assign the certificate:
| >
| > 1. Open IIS Manager
| > 2. Navigate to Web Sites\Default Web Site
| > 3. Right click Default Web Site and choose Properties.
| > 4. Click on the Directory Security tab.
| > 5. Under Secure Communications, click the Server Certificate button.
| > 6. In the IIS Certificate Wizard, choose the "Remove the current
| > certificate"
| > option and click Next.
| > 7. Click Next again, then click Finish.
| > 8. Restart the IIS admin service.
| > 9. Run the Configure Email and Internet Connection wizard. In the Web
| > Server
| > Certificate section, click the option to "Use a Web server certificate
from
| > a
| > trusted authority" and browse to the location of the certificate.
| > 10. Complete the Configure Email and Internet Connection wizard.
| >
| >
| > II. For SBS 2003, if one does have a CER certificate (but it's
not
| > in FQDN format) from 3rd party authority, and you are willing to use
CEICW
| > self-issue certificate, please re-run CEICW and create a self-issue
FQDN
| > format certificate to the System.
| >
| > III. For SBS 2003, if one does have a CER certificate (but it's
not
| > in FQDN format) from 3rd party authority, and you still want to use
that
| > certificate (instead of the CEICW self-issue certificate):
| >
| > A. To resolve this issue, use one of the following methods:
| >
| > = Publish a new SSL certificate that has the FQDN of the Exchange 2000
| > server to the IIS server.
| >
| > = Remove SSL from the Exadmin virtual root in IIS:
| > 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 Exchange System Manager.
| >
| >
| > 324345 You receive an SSL Certificate error message when you view
public
| > folders in Exchange System Manager c103b404
| > http://support.microsoft.com/?id=324345
| >
| > B. If still doesn't work, use ADSIEDIT to check the
configuration
| > and make corresponding modification:
| >
| > 1. In the properties of the virtual root Exadmin in IIS, go to the
| > "Directory Security" tab.
| >
| > 2. In the "Secure Communications" section select "Edit".
| >
| > 3. Make sure to deselect "Require secure channel (SSL)" and "Require
| > 128-bit encryption."
| >
| > 4. If the "Require 128-bit encryption." is selected and grayed out,
make
| > sure to select "Require secure channel (SSL)" and deselect "Require
128-bit
| > encryption."
| > then deselect "Require secure channel (SSL)" again.
| >
| > 5. Install the Windows 2003 Support Tools from SBS 2003 CD2. Then
launch
| > ADSI Edit.
| >
| > 6. In the left side pane expand the Configuration container.
| >
| > 7. Expand the following: CN=Configuration, then CN=Services,
CN=Microsoft
| > Exchange, CN=<your organization name here>, CN=Administrative Groups,
| > CN=First Administrative
| > Group, CN=Servers, CN=Protocols, CN=HTTP, CN=1, CN=Exadmin
| >
| > 8. Right-click Exadmin and choose Properties.
| >
| > 9. In the Properties dialog box you will see 2 drop-down lists. drop
down
| > the top list and select "Both". Drop down the second list and scroll
down
| > to the attribute
| > "msExchSecureBindings" and double click on it.
| >
| > 10. 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".
| >
| > 11. Close out of ADSI Edit, close and reopen Exchange System Manager
and
| > test Public Folder access again. The connection should now be
successful.
| >
| > Hope this helps. Thank you for your understanding and we look forward
to
| > hearing from you soon.
| >
| > 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.
| >
| >
|

.

Quantcast