Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/924940

From BetaArchive Wiki

Article ID: 924940

Article Last Modified on 10/11/2007



APPLIES TO

  • Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise Edition
  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft Windows Server 2003, Web Edition
  • Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
  • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
  • Microsoft Windows Server 2003, Datacenter x64 Edition
  • Microsoft Windows Server 2003, Enterprise x64 Edition
  • Microsoft Windows Server 2003, Standard x64 Edition
  • Microsoft Windows XP Professional x64 Edition



SYMPTOMS

When you use Microsoft Collaboration Data Objects for Windows (CDOSYS) in Microsoft Windows Server 2003 to send an e-mail message that has an attachment, the e-mail program stops responding.

CAUSE

This problem may occur if the HKEY_CLASSES_ROOT registry subtree contains a registry subkey that is longer than 133 characters.

CDOSYS uses the RegEnumKeyEx API to enumerate the HKEY_CLASSES_ROOT registry subtree to find all the different file name extensions. CDOSYS does this so that it can stamp the correct MIME type for the attachment. If CDOSYS encounters a registry subkey that is longer than 133 characters, CDOSYS may stop responding.

Program IDs (ProgIDs) for .NET assemblies sometimes use very long registry keys.

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

Prerequisites

To apply this hotfix, your computer must be running one of the following operating systems:

  • A 32-bit version of Windows Server 2003 with Service Pack 1 (SP1)
  • An Itanium-based version of Windows Server 2003 with SP1
  • An x64-based version of Windows

Restart requirement

You must restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

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 item in Control Panel.

Windows Server 2003, x86-based versions
File name File version File size Date Time Platform SP requirement Service branch
Advapi32.dll 5.2.3790.2859 620,032 10-Jan-2007 12:54 x86 SP1 Not Applicable
Advapi32.dll 5.2.3790.4003 618,496 10-Jan-2007 12:08 x86 SP2 SP2QFE
Updspapi.dll 6.3.4.1 379,184 27-Dec-2006 07:40 x86 SP1 Not Applicable
Windows Server 2003, x64-based versions
File name File version File size Date Time Platform SP requirement Service branch
Advapi32.dll 5.2.3790.2860 1,051,136 12-Jan-2007 12:07 x64 SP1 Not Applicable
Advapi32.dll 5.2.3790.4004 1,051,648 12-Jan-2007 13:45 x64 SP2 SP2QFE
Wadvapi32.dll 5.2.3790.4004 618,496 12-Jan-2007 13:45 x86 SP2 WOW
Updspapi.dll 6.3.4.1 462,128 12-Jan-2007 13:46 x64 SP1 Not Applicable
Wadvapi32.dll 5.2.3790.2860 620,032 12-Jan-2007 12:07 x86 SP1 WOW
Windows Server 2003, Itanium-based versions
File name File version File size Date Time Platform SP requirement Service branch
Advapi32.dll 5.2.3790.2859 1,480,704 10-Jan-2007 14:03 IA-64 SP1 Not Applicable
Advapi32.dll 5.2.3790.4003 1,481,216 10-Jan-2007 16:08 IA-64 SP2 SP2QFE
Wadvapi32.dll 5.2.3790.4003 618,496 10-Jan-2007 16:08 x86 SP2 WOW
Updspapi.dll 6.3.4.1 655,152 10-Jan-2007 18:38 IA-64 SP1 Not Applicable
Wadvapi32.dll 5.2.3790.2859 620,032 10-Jan-2007 14:03 x86 SP1 WOW


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

MORE INFORMATION

For more information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:

816915 New file naming schema for Microsoft Windows software update packages


For more information, 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




Technical support for x64-based versions of Microsoft Windows

If your hardware came with a Microsoft Windows x64 edition already installed, your hardware manufacturer provides technical support and assistance for the Windows x64 edition. In this case, your hardware manufacturer provides support because a Windows x64 edition was included with your hardware. Your hardware manufacturer might have customized the Windows x64 edition installation by using unique components. Unique components might include specific device drivers or might include optional settings to maximize the performance of the hardware. Microsoft will provide reasonable-effort assistance if you need technical help with a Windows x64 edition. However, you might have to contact your manufacturer directly. Your manufacturer is best qualified to support the software that your manufacturer installed on the hardware. If you purchased a Windows x64 edition such as a Microsoft Windows Server 2003 x64 edition separately, contact Microsoft for technical support.

For product information about Microsoft Windows XP Professional x64 Edition, visit the following Microsoft Web site:

For product information about x64-based versions of Microsoft Windows Server 2003, visit the following Microsoft Web site:


Additional query words: Winx64 Windowsx64 64bit 64-bit

Keywords: kbfix kbqfe kbprb kbexpertiseinter kbhotfixserver kbwinserv2003sp2fix KB924940