You receive an "IDS_INSTALLFAILED" error message and an access violation occurs if you configure an Outlook Express account profile on your Windows XP-based, Windows 2000-based or Windows Server 2003-based computer (893605)



The information in this article applies to:

  • Microsoft Windows XP Home Edition SP1
  • Microsoft Windows XP Home Edition SP2
  • Microsoft Windows XP Professional SP1
  • Microsoft Windows XP Professional SP2
  • Microsoft Windows XP Professional 64-Bit Edition (Itanium)
  • Microsoft Windows XP Professional x64 Edition
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Professional
  • Microsoft Windows 2000 Server
  • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
  • Microsoft Windows Server 2003, Enterprise x64 Edition
  • Microsoft Windows Server 2003, Standard x64 Edition
  • Microsoft Windows Server 2003 SP1
  • Microsoft Windows Server 2003, Enterprise Edition
  • Microsoft Windows Server 2003, Standard Edition

SYMPTOMS

If you try to create a Microsoft Outlook Express account profile for a broadband connection by using an Internet Signup (.ins) file, you may experience the following symptoms:
  • You cannot create the Outlook Express account profile.
  • You receive an access violation error message, and the access violation occurs in the Isign32.exe process.
  • You receive an error message that is similar to the following error message:
    IDS_INSTALLFAILED

CAUSE

This problem may occur if the following conditions are true:
  • The Multilingual User Interface (MUI) installed on your computer.
  • The MUI language is set to Portuguese.
  • The MUI tries to translate n error message that is larger than the default buffer allocation of 256 bytes.
In this scenario, the error message causes a buffer overflow, which causes the account profile creation process to fail.

RESOLUTION

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 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

  • Windows 2000
  • Windows XP Service Pack 1 (SP1)
  • Windows XP Service Pack 1 (SP2)
  • Windows Server 2003

Restart requirement

You do not have to restart your 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.Windows Server 2003 (no SP), 32-bit versions
   Date         Time   Version            Size    File name
   --------------------------------------------------------------
   19-Apr-2005  20:30  6.0.3790.312       77,824  Isign32.dll     
Windows Server 2003 SP1, 32-bit versions
   Date         Time   Version            Size    File name
   --------------------------------------------------------------
   19-Apr-2005  21:02  6.0.3790.2424      81,920  Isign32.dll  
Windows Server 2003 , 64-bit (ia64)
   Date         Time   Version            Size    File name
   --------------------------------------------------------------
   19-Apr-2005  23:52  6.0.3790.312      161,792  Isign32.dll      IA64
   19-Apr-2005  23:52  6.0.3790.312       77,824  Wisign32.dll     X86
   19-Apr-2005  23:52  6.0.3790.2424     176,640  Isign32.dll      IA64
   19-Apr-2005  23:52  6.0.3790.2424      81,920  Wisign32.dll     X86
   19-Apr-2005  23:52  6.1.22.4          639,712  Updspapi.dll     IA64
   
Windows Server 2003 , 64-bit (x64)
   Date         Time   Version            Size    File name
   --------------------------------------------------------------
   19-Apr-2005  23:52  6.0.3790.2424      98,816  Isign32.dll      
   19-Apr-2005  23:52  6.0.3790.2424      81,920  Wisign32.dll     
   19-Apr-2005  23:52  6.1.22.4          462,560  Updspapi.dll       
Windows XP SP1, 32-bit versions
   Date         Time   Version            Size    File name
   --------------------------------------------------------------
   04-Mar-2005  21:01  6.0.2800.1636      77,824  Isign32.dll         
Windows XP SP2, 32-bit versions
   Date         Time   Version            Size    File name
   --------------------------------------------------------------      
   04-Mar-2005  21:00  6.0.2900.2624      81,920  Isign32.dll    
Windows XP SP1, 64-bit versions
   Date         Time   Version           Size     File name     Platform
   -----------------------------------------------------------------------
   24-Feb-2005  14:20  6.1.22.4          639,712  Updspapi.dll  IA-64
   04-Mar-2005  07:31  6.0.2800.1636     166,400  Isign32.dll   IA-64
   04-Mar-2005  07:31  6.0.2800.1636      77,824  Wisign32.dll  x86
Windows 2000
   Date         Time   Version            Size    File name
   --------------------------------------------------------------
   19-Apr-2005  07:12  5.0.3900.7039      72,464  Isign32.dll      
   25-Feb-2005  17:43  6.1.22.4          371,936  Updspapi.dll   

WORKAROUND

To work around this problem, set the MUI language to English, and then use the .ins file. After the account profile is created, change the MUI language according to your preference.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information about the standard terminology that is used to describe Microsoft software updates, 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:6/1/2006
Keywords:kbQFE kbHotfixServer kbWinXPpreSP2fix kbWin2000preSP5fix kbWinXPpreSP3fix kbWinXPsp3fix kbfix kbbug KB893605 kbAudITPRO