Description of the Jet 4.0 Database Engine hotfix package for Windows XP SP2, Windows Server 2003 SP1, Windows Server 2003 SP2, Windows Vista, Windows Vista SP1, and Windows Server 2008: October 23, 2007
This article describes the Microsoft Jet 4.0 Database Engine issues that are fixed in the Jet 4.0 Database Engine hotfix package that is dated October 23, 2007.
This article describes the following items about the hotfix package:
•
The issues that the hotfix package fixes.
•
The prerequisites for installing the hotfix
package.
•
Whether you must restart the computer after you install the
hotfix package.
•
Whether the hotfix package is replaced by any other hotfix
package.
This hotfix package fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:
•
The original release of this hotfix introduced an issue that also affects Windows Vista Service Pack 1 (SP1) and Windows Server 2008. Inserts and updates may fail in C++ Microsoft Jet DAO MFC (CDAO) applications after you install Windows Vista SP1 or Windows Server 2008. You may receive the following error message:
The field is too small to accept the amount of data that you tried to add. Try inserting or pasting less data.
If your application does not capture the exception that is returned by CDAO on the insert or on the update, your database will not have the updates that you intended to make.
When you use an Access database or a Jet database that
contains tables that are linked to an Oracle 10g database server, a query may
return unexpected results. This issue can occur when the query includes a
complex SQL statement that has one or more nested JOIN statements. This issue
can occur if the Oracle server was upgraded from an earlier version and the
Access table links or Jet table links have not been refreshed after the
upgrade.
•
When you use a Microsoft Jet 4.0 database, you may receive
an error message that resembles the following:
ApplicationName has encountered a
problem and needs to close. We are sorry for the inconvenience. If you were in
the middle of something, the information you were working on might be lost.
Please tell Microsoft about this problem. We have created an error report that
you can send to help us improve ApplicationName. We
will treat this report as confidential and anonymous. To see what data this
error report contains, click here.
When you view the data that the
error report contains, you see the following list that contains information
about some common error signatures. This information may vary depending on the
version of Microsoft Office Access or on the application that you use as the
front end for the Jet 4.0 database engine.
Application name
Application
version
Module name
Module version
Offset
Msaccess.exe
10.0.4302.0
Msjet40.dll
4.0.6218.0
00021eb3
Msaccess.exe
10.0.2627.1
Msjet40.dll
4.0.6218.0
00021eb3
Msaccess.exe
10.0.2627.1
Msjet40.dll
4.0.2927.17
00021ac2
Msaccess.exe
11.0.6566.0
Msjet40.dll
4.0.9025.0
00021f23
Msaccess.exe
11.0.6566.0
Msjet40.dll
4.0.8618.0
000221f3
Msaccess.exe
11.0.5614.0
Msjet40.dll
4.0.8618.0
000221f3
Msaccess.exe
11.0.6355.0
Msjet40.dll
4.0.8618.0
000221f3
Msaccess.exe
11.0.6501.0
Msjet40.dll
4.0.8618.0
000221f3
Msaccess.exe
10.0.2627.1
Msjet40.dll
4.0.8618.0
000221f3
•
When you use a Microsoft Jet 4.0 database, you may receive
an error message that resembles the following:
ApplicationName has encountered a
problem and needs to close. We are sorry for the inconvenience. If you were in
the middle of something, the information you were working on might be lost.
Please tell Microsoft about this problem. We have created an error report that
you can send to help us improve ApplicationName. We
will treat this report as confidential and anonymous. To see what data this
error report contains, click here.
When you view the data that the
error report contains, you see the following list that contains information
about some common error signatures. This information may vary depending on the
version of Microsoft Office Access or on the application that you use as the
front end for the Jet 4.0 database engine.
Application name
Application
version
Module name
Module version
Offset
Msaccess.exe
11.0.5614.0
Msjet40.dll
4.0.8618.0
00044d29
Msaccess.exe
11.0.6566.0
Msjet40.dll
4.0.8618.0
00044d29
Msaccess.exe
10.0.6501.0
Msjet40.dll
4.0.8618.0
00044d29
Msaccess.exe
11.0.5614.0
Msjet40.dll
4.0.8618.0
00044d29
Msaccess.exe
11.0.6355.0
Msjet40.dll
4.0.8618.0
00044d29
Msaccess.exe
10.0.2627.1
Msjet40.dll
4.0.8618.0
00044d29
•
When you use a Microsoft Jet 4.0 database, you may receive
an error message that resembles the following:
ApplicationName has encountered a
problem and needs to close. We are sorry for the inconvenience. If you were in
the middle of something, the information you were working on might be lost.
Please tell Microsoft about this problem. We have created an error report that
you can send to help us improve ApplicationName. We
will treat this report as confidential and anonymous. To see what data this
error report contains, click here.
When you view the data that the
error report contains, you see the following list that contains information
about some common error signatures. This information may vary depending on the
version of Microsoft Office Access or on the application that you use as the
front end for the Jet 4.0 database engine.
Application Name
Application
version
Module name
Module version
Offset
Iexplore.exe
6.0.2800.1106
Dao360.dll
3.60.8618.0
00002c5e
Iexplore.exe
6.0.2900.2180
Dao360.dll
3.60.8618.0
00002c5e
Iexplore.exe
6.0.2800.1106
Dao360.dll
3.60.8618.0
00002c0c
Iexplore.exe
6.0.2900.2180
Dao360.dll
3.60.8618.0
00002bc9
Msaccess.exe
11.0.6355.0
hungapp
0.0.0.0
00000000
Msaccess.exe
11.0.6566.0
Dao360.dll
3.60.8618.0
00002c5e
•
When you use a Microsoft Jet 4.0 database, you may receive
an error message that resembles the following:
ApplicationName has encountered a
problem and needs to close. We are sorry for the inconvenience. If you were in
the middle of something, the information you were working on might be lost.
Please tell Microsoft about this problem. We have created an error report that
you can send to help us improve ApplicationName. We
will treat this report as confidential and anonymous. To see what data this
error report contains, click here.
When you view the data that the
error report contains, you see the following list that contains information
about some common error signatures. This information may vary depending on the
version of Microsoft Office Access or on the application that you use as the
front end for the Jet 4.0 database engine.
Application Name
Application
version
Module name
Module version
Offset
Msaccess.exe
11.0.6566.0
Msjet40.dll
4.0.9635.0
0002f736
Msaccess.exe
10.0.4302.0
Msjet40.dll
4.0.6218.0
00041681
Msaccess.exe
10.0.2627.1
Msjet40.dll
4.0.6218.0
00041681
Msaccess.exe
10.0.4302.0
Msjet40.dll
4.0.7328.0
0004234b
Msaccess.exe
11.0.6566.0
Msjet40.dll
4.0.9025.0
40eaec65
Msaccess.exe
10.0.2627.1
Msjet40.dll
4.0.4431.3
000416d1
•
When you use a Microsoft Jet 4.0 database, you may receive
an error message that resembles the following:
ApplicationName has encountered a
problem and needs to close. We are sorry for the inconvenience. If you were in
the middle of something, the information you were working on might be lost.
Please tell Microsoft about this problem. We have created an error report that
you can send to help us improve ApplicationName. We
will treat this report as confidential and anonymous. To see what data this
error report contains, click here.
When you view the data that the
error report contains, you see the following list that contains information
about some common error signatures. This information may vary depending on the
version of Microsoft Office Access or on the application that you use as the
front end for the Jet 4.0 database engine.
Windows Vista, Windows Vista SP1, Windows Server 2008
A supported hotfix is now available from
Microsoft. However, this hotfix is intended to correct only the problem that is
described in this article. Apply this hotfix only to systems that are
experiencing this specific problem. This hotfix might receive additional
testing. Therefore, if you are not severely affected by this problem, we
recommend that you wait for the next service pack that contains this
hotfix.
To resolve this problem, submit a request to Microsoft Online
Customer Services to obtain the hotfix. To submit an online request to obtain
the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or any troubleshooting is required,
you might have to create a separate service request. The usual support costs
will apply to additional support questions and issues that do not qualify for
this specific hotfix. To create a separate service request, visit the following
Microsoft Web site:
If the Jet 4.0 database engine is being used, you must restart
the computer after you apply this hotfix.
Hotfix replacement information
This hotfix replaces the update rollup for Windows Vista that is
documented in Microsoft Knowledge Base article 937248.
For more information, click the following article number to
view the article in the Microsoft Knowledge Base:
937248 (http://support.microsoft.com/kb/937248/)
Description of the Jet 4.0 Database Engine update rollup for the release version of Windows Vista: May 11, 2007
Registry information
You do not have to create or to modify any registry keys to
enable this 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 Vista, 64-bit versions
File name
File version
File
size
Date
Time
Msrd2x40.dll
4.0.9635.0
323,584
22-Oct-2007
21:57
Msrd3x40.dll
4.0.9702.0
344,064
22-Oct-2007
21:57
Msjet40.dll
4.0.9704.0
1,589,248
22-Oct-2007
21:57
Msrepl40.dll
4.0.9702.0
647,168
22-Oct-2007
21:57
Mstext40.dll
4.0.9702.0
282,624
22-Oct-2007
21:57
Msexcl40.dll
4.0.9702.0
344,064
22-Oct-2007
21:57
Msexch40.dll
4.0.9702.0
413,696
22-Oct-2007
21:57
Msltus40.dll
4.0.9702.0
245,760
22-Oct-2007
21:57
Mspbde40.dll
4.0.9702.0
376,832
22-Oct-2007
21:57
Msxbde40.dll
4.0.9702.0
450,560
22-Oct-2007
21:57
Dao360.dll
3.60.9705.0
610,304
22-Oct-2007
21:57
Msjetoledb40.dll
4.0.9702.0
368,640
22-Oct-2007
21:57
Msjtes40.dll
4.0.9702.0
299,008
22-Oct-2007
21:57
Windows Vista SP1, 64-bit versions; Windows Server 2008 (all versions)
File name
File version
File
size
Date
Time
Dao360.dll
3.60.9705.0
610,304
22-Oct-2007
21:57
Windows Vista, x86-based versions
File name
File version
File
size
Date
Time
Msrd2x40.dll
4.0.9635.0
323,584
22-Oct-2007
21:57
Msrd3x40.dll
4.0.9702.0
344,064
22-Oct-2007
21:57
Msjet40.dll
4.0.9704.0
1,589,248
22-Oct-2007
21:57
Msrepl40.dll
4.0.9702.0
647,168
22-Oct-2007
21:57
Mstext40.dll
4.0.9702.0
282,624
22-Oct-2007
21:57
Msexcl40.dll
4.0.9702.0
344,064
22-Oct-2007
21:57
Msexch40.dll
4.0.9702.0
413,696
22-Oct-2007
21:57
Msltus40.dll
4.0.9702.0
245,760
22-Oct-2007
21:57
Mspbde40.dll
4.0.9702.0
376,832
22-Oct-2007
21:57
Msxbde40.dll
4.0.9702.0
450,560
22-Oct-2007
21:57
Dao360.dll
3.60.9704.0
610,304
22-Oct-2007
21:57
Msjetoledb40.dll
4.0.9702.0
368,640
22-Oct-2007
21:57
Msjtes40.dll
4.0.9702.0
299,008
22-Oct-2007
21:57
Windows XP
A supported hotfix is now available
from Microsoft. However, this hotfix is intended to correct only the problem
that is described in this article. Apply this hotfix only to systems that are
experiencing this specific problem. This hotfix might receive additional
testing. Therefore, if you are not severely affected by this problem, we
recommend that you wait for the next Windows XP service pack that contains this
hotfix.
To resolve this problem, submit a request to Microsoft Online
Customer Services to obtain the hotfix. To submit an online request to obtain
the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or any troubleshooting is required,
you might have to create a separate service request. The usual support costs
will apply to additional support questions and issues that do not qualify for
this specific hotfix. To create a separate service request, visit the following
Microsoft Web site:
If the Jet 4.0 database engine is being used, you must restart
the computer after you apply this hotfix.
Hotfix replacement information
This hotfix replaces the update rollups for Windows Vista that
are documented in Microsoft Knowledge Base articles 930620, 918144, and 925051.
For more information, click the following article numbers to view
the articles in the Microsoft Knowledge Base:
930620 (http://support.microsoft.com/kb/930620/)
Description of the Jet 4.0 Database Engine post-Windows XP Service Pack 2 hotfix package: January, 2007
918144 (http://support.microsoft.com/kb/918144/) Description of the Jet 4.0 Database Engine post-837001 hotfix package: May 11, 2006
925051 (http://support.microsoft.com/kb/925051/) An Access program stops responding when it uses the Jet Database Engine and runs a large SQL query that contains double-byte character set data in Windows Server 2003 and in Windows XP
Registry information
You do not have to create or to modify any registry keys to
enable this 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.
A supported hotfix is now
available from Microsoft. However, this hotfix is intended to correct only the
problem that is described in this article. Apply this hotfix only to systems
that are experiencing this specific problem. This hotfix might 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, submit a
request to Microsoft Online Customer Services to obtain the hotfix. To submit
an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or any troubleshooting is required,
you might have to create a separate service request. The usual support costs
will apply to additional support questions and issues that do not qualify for
this specific hotfix. To create a separate service request, visit the following
Microsoft Web site:
If the Jet 4.0 database engine is being used, you must restart
the computer after you apply this hotfix.
Hotfix replacement information
This hotfix replaces the update rollups for Windows Vista that
are documented in Microsoft Knowledge Base articles 933452, 918144, and 925051.
For more information, click the following article numbers to view
the articles in the Microsoft Knowledge Base:
933452 (http://support.microsoft.com/kb/933452/)
Description of the Jet 4.0 Database Engine post-Windows Server 2003, post-Windows Server 2003 Service Pack 1, and post-Windows Server 2003 Service Pack 2 hotfix package: March 5, 2007
918144 (http://support.microsoft.com/kb/918144/) Description of the Jet 4.0 Database Engine post-837001 hotfix package: May 11, 2006
925051 (http://support.microsoft.com/kb/925051/) An Access program stops responding when it uses the Jet Database Engine and runs a large SQL query that contains double-byte character set data in Windows Server 2003 and in Windows XP
Registry information
You do not have to create or to modify any registry keys to
enable this 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 Service Pack 2, Itanium-based versions
File name
File version
File
size
Date
Time
Wdao360.dll
3.60.9512.0
554,008
08-Nov-2007
20:01
Wmsjet40.dll
4.0.9511.0
1,516,568
08-Nov-2007
20:01
Windows Server 2003 Service Pack 1, Itanium-based versions
File name
File version
File
size
Date
Time
Wdao360.dll
3.60.9512.0
554,008
08-Nov-2007
19:57
Wmsexch40.dll
4.0.9502.0
518,944
08-Nov-2007
19:57
Wmsexcl40.dll
4.0.9502.0
326,432
08-Nov-2007
19:57
Wmsjet40.dll
4.0.9511.0
1,516,568
08-Nov-2007
19:57
Wmsjetol1.dll
4.0.9502.0
355,112
08-Nov-2007
19:57
Wmsjint40.dll
4.0.9502.0
151,583
08-Nov-2007
19:57
Wmsjter40.dll
4.0.9502.0
60,192
08-Nov-2007
19:57
Wmsjtes40.dll
4.0.9502.0
248,608
08-Nov-2007
19:57
Wmsltus40.dll
4.0.9502.0
219,936
08-Nov-2007
19:57
Wmspbde40.dll
4.0.9502.0
355,104
08-Nov-2007
19:57
Wmsrd2x40.dll
4.0.9502.0
432,928
08-Nov-2007
19:57
Wmsrd3x40.dll
4.0.9502.0
322,336
08-Nov-2007
19:57
Wmsrepl40.dll
4.0.9502.0
559,904
08-Nov-2007
19:57
Wmstext40.dll
4.0.9502.0
264,992
08-Nov-2007
19:57
Wmswdat10.dll
4.0.9502.0
838,432
08-Nov-2007
19:57
Wmswstr10.dll
4.0.9502.0
621,344
08-Nov-2007
19:57
Wmsxbde40.dll
4.0.9502.0
355,104
08-Nov-2007
19:57
Windows Server 2003 Service Pack 2, x64-based versions
File name
File version
File
size
Date
Time
Wdao360.dll
3.60.9512.0
554,008
08-Nov-2007
20:09
Wmsjet40.dll
4.0.9511.0
1,516,568
08-Nov-2007
20:09
Windows Server 2003 Service Pack 1, x64-based versions
File name
File version
File
size
Date
Time
Wdao360.dll
3.60.9512.0
554,008
08-Nov-2007
19:57
Wmsexch40.dll
4.0.9502.0
518,944
08-Nov-2007
19:57
Wmsexcl40.dll
4.0.9502.0
326,432
08-Nov-2007
19:57
Wmsjet40.dll
4.0.9511.0
1,516,568
08-Nov-2007
19:57
Wmsjetol1.dll
4.0.9502.0
355,112
08-Nov-2007
19:57
Wmsjint40.dll
4.0.9502.0
151,583
08-Nov-2007
19:57
Wmsjter40.dll
4.0.9502.0
60,192
08-Nov-2007
19:57
Wmsjtes40.dll
4.0.9502.0
248,608
08-Nov-2007
19:57
Wmsltus40.dll
4.0.9502.0
219,936
08-Nov-2007
19:57
Wmspbde40.dll
4.0.9502.0
355,104
08-Nov-2007
19:57
Wmsrd2x40.dll
4.0.9502.0
432,928
08-Nov-2007
19:57
Wmsrd3x40.dll
4.0.9502.0
322,336
08-Nov-2007
19:57
Wmsrepl40.dll
4.0.9502.0
559,904
08-Nov-2007
19:57
Wmstext40.dll
4.0.9502.0
264,992
08-Nov-2007
19:57
Wmswdat10.dll
4.0.9502.0
838,432
08-Nov-2007
19:57
Wmswstr10.dll
4.0.9502.0
621,344
08-Nov-2007
19:57
Wmsxbde40.dll
4.0.9502.0
355,104
08-Nov-2007
19:57
Windows Server 2003 Service Pack 2, x86-based versions
File name
File version
File
size
Date
Time
Dao360.dll
3.60.9512.0
554,008
07-Nov-2007
04:52
Msjet40.dll
4.0.9511.0
1,516,568
07-Nov-2007
04:52
Windows Server 2003 Service Pack 1, x86-based versions
The
third-party products that this article discusses are manufactured by companies
that are independent of Microsoft. Microsoft makes no warranty, implied or
otherwise, about the performance or reliability of these
products.
Contact Microsoft Phone Numbers, Support Options and Pricing, Online Help, and more.
Customer Service For non-technical assistance with product purchases, subscriptions, online services, events, training courses, corporate sales, piracy issues, and more.
Newsgroups Pose a question to other users. Discussion groups and Forums about specific Microsoft products, technologies, and services.
Back to the top
