XWEB: Troubleshooting Active Server Components

Last reviewed: March 5, 1998
Article ID: Q167003

The information in this article applies to:

Microsoft Exchange Active Server components, version 5.0
Microsoft Internet Information Server, version 3.0

SUMMARY

The Microsoft Exchange Active Server Components interact with multiple applications, including Windows NT, Internet Information Server (IIS), Microsoft Exchange, and a browser (for example, Internet Explorer) The first objective in troubleshooting problems with Active Server Components is to determine what is causing problems.

This article assumes the following setup:

   Computer running Microsoft Exchange Server and IIS with a
   Server Name = "XServer" (this can be two different computers)
   Domain = "XDom"
   Client Computer (Windows 95) = "client1"
   Microsoft Exchange mailbox name = "test1"
   Primary Windows NT Account = "NTTest1"
   Password= "Pass1"

MORE INFORMATION

Remember the following throughout troubleshooting:

When prompted with the authentication (logon) dialog box, enter the information in the following manner:
```
      Username:     <DomainName>\<DomainUsername>
```

NOTE: This must be a backslash, NOT a forward slash.

      Password:     <DomainPassword>

NOTE: The Password field is case-sensitive.

   Only entering the username will work in some cases (for instance, if you
   have already logged on to the Microsoft Exchange domain from the
   operating system).

In the logon.asp page, you must enter the mailbox name (alias name) exactly as it appears from the Microsoft Exchange Server Administrator program. Display names are not accepted.

Whenever ANY changes are made on the computer running IIS or Microsoft Exchange Server, stop and restart the World Wide Web Publishing Service on the server and completely close the browser and restart it on the client computer before testing again. Some information may be cached and this can lead to inconsistent results.

Review the following Microsoft Knowledge Base article prior to troubleshooting:

ARTICLE-ID: Q167002

   TITLE     : XWEB: Limitations of the Active Server Components

Troubleshooting

The following questions will help you troubleshoot the Active Server Components:

Can the "test1" mailbox be accessed from any non web-based Microsoft Exchange clients running on this computer? To determine this:

    - From "client1," attempt to log on to "mailbox1" using Microsoft
      Exchange Client 4.0 or 5.0, a POP3 client (if Microsoft Exchange 5.0)
      or Outlook).

If the answer is no, troubleshoot this as a normal client/server issue.

Try creating a brand new Microsoft Exchange mailbox and Windows NT account, set up a new Microsoft Exchange profile on the client computer, and attempt to connect.
If you can connect, continue.

Can this browser attach to ANY other web sites?

    - If the answer is no, this is likely a browser-specific issue; contact
      the manufacturer of the browser for assistance.

    - If the answer is yes, continue.

Can the browser access the IIS default Web page at http://Nserver (where Nserver is the IIS computer with the Exchange Active Server

    Components installed)?

    - If the answer is no, this is an IIS issue. Contact Microsoft
      Technical Support for assistance.

    - If the answer is yes, continue.

Can the browser access the ASP Sample Pages at http://Nserver/aspsamp (where Nserver is the IIS computer with the Microsoft Exchange Active Server Components installed)?
- If the answer is no, this is an IIS issue. Contact Microsoft Technical
```
     Support for assistance.
```
```
    - If the answer is yes, continue.
```

Are the Sample Active Server scripts that ship with Microsoft Exchange Server being used?

    - If the answer is yes, contact Microsoft Technical Support for
      assistance.

    - If the answer is no, contact Developer support for assistance with
      custom ASPs. Test the sample active server scripts that ship with
      Microsoft Exchange Server. If necessary, rename the current Webdata
      directory and copy a new one from the Microsoft Exchange Server
      compact disc to test).

Set up IIS to use "Clear Text" Only in Internet Service Manager (Service Properties for WWW service). Disable "Windows NT Challenge/Response" if enabled.
Stop and restart the "World Wide Web Publishing Service" after making any changes
Attempt to connect to another computer running IIS and Microsoft Exchange Server

There is a test server normally available on Microsoft's Web site. See http://www.exchangeserver.com/testdrive/instruct.htm for instructions The location for the test-drive server is http://exchinet.exchangeserver.com/exchange.

Create a brand new mailbox and brand new Windows NT account for testing.
Clear the browser cache for Internet Explorer:
a. On the View menu, click Options.
b. On the Advanced tab, click Emtpy Folder.
If using a proxy server and attempting to use NTLM, you MUST select the option Do Not Use Proxy Server For Local (Intranet) Addresses (this is located on the Properties for IE Connection tab).

REFERENCE

For additional information, please see the following article(s) in the Microsoft Knowledge Base:

   ARTICLE-ID: Q147532
   TITLE     : Access Denied and Login Failed on Internet Information
               Server

   ARTICLE-ID: Q142868
   TITLE     : IIS: Authentication & Security Features

Additional query words: kluane tshoot
Keywords : XCLN kbusage kbfaq
Version : 5.0
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 5, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.