You may receive a "The name could not be resolved" error message and Outlook 2003 unexpectedly quits after you log on to a network over the Internet in Windows Server 2003 (895104)



The information in this article applies to:

  • Microsoft Windows Server 2003, Standard Edition
  • Microsoft Windows Server 2003, Web Edition
  • Microsoft Windows Server 2003, Enterprise Edition
  • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
  • Microsoft Office Outlook 2003

SYMPTOMS

When you try to verify your account name in Microsoft Office Outlook 2003, you may receive the following error message:
The name could not be resolved. Operation failed.
After you close the error message window, Outlook 2003 unexpectedly quits. The error code is 0x8004011c.

This problem occurs when the following conditions are true:
  • The computer is running Microsoft Windows Server 2003.
  • You log on to a network over the Internet by using your user principal name (UPN).

    Note A UPN uses the following format:

    user_name@domain.com

  • You log on to the network by using one of the following connections:
    • A virtual private network (VPN) connection
    • A remote procedure call/Hypertext Transfer Protocol (RPC/HTTP) connection
  • You then start Microsoft Office Outlook 2003.
  • One or both of the following conditions is true:
    • Outlook 2003 automatically checks for new e-mail messages.
    • You click Send/Receive.
In this scenario, you are prompted to reenter the Microsoft Exchange server name and your user account name. When you then click Check Name, you receive the error message.

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

889100 How to obtain the latest service pack for Windows Server 2003

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it 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 Windows Server 2003 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: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

No prerequisites are required.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

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 tool in Control Panel.Microsoft Windows Server 2003, 32-bit versions
   Date         Time   Version            Size  File name
   ----------------------------------------------------------------
   14-Jan-2005  08:57  5.2.3790.250  1,191,936  Ole32.dll
   16-Mar-2004  03:17  5.2.3790.141     26,112  Rpcproxy.dll
   22-Mar-2005  22:39  5.2.3790.293    659,968  Rpcrt4.dll
   14-Jan-2005  08:57  5.2.3790.250    294,912  Rpcss.dll
Microsoft Windows Server 2003, Itanium-based versions
   Date         Time   Version            Size  File name  Platform
   ----------------------------------------------------------------
   13-Jan-2005  16:48  5.2.3790.250  3,576,832  Ole32.dll     IA-64
   30-Mar-2004  11:25  5.2.3790.141     73,216  Rpcproxy.dll  IA-64
   22-Mar-2005  06:39  5.2.3790.293  2,151,424  Rpcrt4.dll    IA-64
   13-Jan-2005  16:48  5.2.3790.250    688,640  Rpcss.dll     IA-64
   13-Jan-2005  16:57  5.2.3790.250  1,191,936  Wole32.dll      x86
   30-Mar-2004  11:26  5.2.3790.141     26,112  Wrpcproxy.dll   x86
   22-Mar-2005  06:39  5.2.3790.293    544,256  Wrpcrt4.dll     x86

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 1.

MORE INFORMATION

For more information about a similar problem that occurs in Microsoft Windows XP, click the following article number to view the article in the Microsoft Knowledge Base:

830355 You cannot use Outlook 2003 over the Internet by using your user principal name (UPN)

For more information about the terminology that is used in this article, 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


Modification Type:MinorLast Reviewed:7/26/2006
Keywords:kbBug kbfix kbWinServ2003preSP1fix kbHotfixServer kbQFE kbpubtypekc KB895104 kbAudITPRO