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

From BetaArchive Wiki

Article ID: 924748

Article Last Modified on 10/25/2007



APPLIES TO

  • Microsoft Exchange Server 2003 Service Pack 2, when used with:
    • Microsoft Exchange Server 2003 Standard Edition
    • Microsoft Exchange Server 2003 Enterprise Edition




SYMPTOMS

Consider the following scenario. In Microsoft Exchange Server 2003 Service Pack 2 (SP2), you set up the Microsoft Exchange Server 2003 Connector for Lotus Notes to connect to a Lotus Notes Domino server. Then, an Exchange Server 2003 user sends a meeting request to a Lotus Notes user. The Lotus Notes user accepts the request by using the Respond option.

In this scenario, you notice that the Lotus Notes Connector generates an acceptance message that may contain an incorrect date format in the message body. For example, you expect the date to use the "dd/mm/yyyy" format. This is the format this is used when you set the English (Australia) language setting on the computer. However, the date in the acceptance message body uses the "mm/dd/yyyy" format.

CAUSE

This problem occurs because the Lotus Notes Connector cannot recognize the language settings that are set in the Regional and Language Options Control Panel program in Microsoft Windows. Therefore, the Lotus Notes Connector uses the date format for the default language setting. The default language setting is English (United States).

RESOLUTION

To resolve this problem, install the latest version of the Microsoft Exchange Server 2003 Connector for Lotus Notes. To obtain the latest version of the Lotus Notes Connector, visit the following Microsoft Web site:

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

You must have Exchange Server 2003 Service Pack 2 (SP2) and Lotus Notes Client 6.x installed to apply this hotfix.

For more information about Exchange Server 2003 SP2, click the following article number to view the article in the Microsoft Knowledge Base:

836993 How to obtain the latest service packs for Exchange Server 2003


Restart requirement

You do not have to restart the computer after you apply this software update.

Hotfix replacement information

This hotfix does not replace any other software updates.

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.

File name File version File size Date Time Platform
Exchmem.dll 6.5.7869.0 160,256 21-Oct-2006 10:51 x86
Notescondata.dll 6.5.7869.0 1,320,448 21-Oct-2006 12:20 x86
Pttrace.dll 6.5.7869.0 16,384 20-Oct-2006 13:35 x86
Exchmem.dll 6.5.7869.0 160,256 21-Oct-2006 10:51 x86
Notescup.dll 6.5.7869.0 5,632 20-Oct-2006 13:34 x86
Ntscupwp.dll 6.5.7869.0 39,424 20-Oct-2006 13:34 x86
Addxa.dll 6.5.7869.0 565,760 20-Oct-2006 13:31 x86
Aqadmcon.dll 6.5.7869.0 44,544 20-Oct-2006 13:34 x86
Ctreestd.dll 6.5.7869.0 203,776 20-Oct-2006 13:31 x86
Devcon.dll 6.5.7869.0 6,144 20-Oct-2006 13:32 x86
Dispatch.exe 6.5.7869.0 37,888 20-Oct-2006 13:32 x86
Dxamex.dll 6.5.7869.0 36,864 20-Oct-2006 13:33 x86
Dxanotes.dll 6.5.7869.0 58,368 20-Oct-2006 13:33 x86
Lscmd.exe 6.5.7869.0 23,040 20-Oct-2006 13:32 x86
Lscms.dll 6.5.7869.0 157,184 20-Oct-2006 13:31 x86
Lscntrl.exe 6.5.7869.0 50,176 20-Oct-2006 13:32 x86
Lscps.dll 6.5.7869.0 339,456 21-Oct-2006 11:27 x86
Lsctrl.exe 6.5.7869.0 7,168 20-Oct-2006 13:32 x86
Lsdevlog.dll 6.5.7869.0 8,192 20-Oct-2006 13:33 x86
Lsdevnt.dll 6.5.7869.0 10,240 20-Oct-2006 13:33 x86
Lsdevui.dll 6.5.7869.0 7,680 20-Oct-2006 13:31 x86
Lsdxa.exe 6.5.7869.0 27,648 20-Oct-2006 13:33 x86
Lsinst.dll 6.5.7869.0 8,704 20-Oct-2006 13:33 x86
Lslde.dll 6.5.7869.0 66,048 20-Oct-2006 13:31 x86
Lsldew.dll 6.5.7869.0 16,896 20-Oct-2006 13:31 x86
Lsmain.exe 6.5.7869.0 41,472 20-Oct-2006 13:33 x86
Lsmexhc.dll 6.5.7869.0 128,000 20-Oct-2006 13:31 x86
Lsmexif.dll 6.5.7869.0 233,984 20-Oct-2006 13:31 x86
Lsmexin.exe 6.5.7869.0 11,776 20-Oct-2006 13:33 x86
Lsmexnts.exe 6.5.7869.0 34,816 20-Oct-2006 13:33 x86
Lsmexout.exe 6.5.7869.0 11,776 20-Oct-2006 13:33 x86
Lsntshc.dll 6.5.7869.0 215,040 20-Oct-2006 13:31 x86
Lsntsmex.exe 6.5.7869.0 44,544 20-Oct-2006 13:34 x86
Lspa.exe 6.5.7869.0 13,312 20-Oct-2006 13:34 x86
Lspcta.dll 6.5.7869.0 27,648 20-Oct-2006 13:31 x86
Lsrcc.dll 6.5.7869.0 7,168 20-Oct-2006 13:31 x86
Lsrcs.dll 6.5.7869.0 19,456 20-Oct-2006 13:31 x86
Lsxfm.dll 6.5.7869.0 43,008 20-Oct-2006 13:34 x86
Mlmig32.dll 6.5.7869.0 4,469,760 21-Oct-2006 11:25 x86
Ntsperf.dll 6.5.7869.0 19,968 21-Oct-2006 11:27 x86
Adclog.dll 6.5.7869.0 1,184,256 21-Oct-2006 11:14 x86
Calconmsg.dll 6.5.7869.0 262,656 21-Oct-2006 11:30 x86
Exconmsg.dll 6.5.7869.0 4,523,008 21-Oct-2006 11:27 x86


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


For more information, click the following article number to view the article in the Microsoft Knowledge Base:

817903 New naming schema for Exchange Server software update packages


Keywords: kbbug kbfix kbqfe kbpubtypekc kbexpertiseinter kbhotfixserver KB924748