Article ID: 970644 - Last Review: July 2, 2009 - Revision: 3.0 Error message when you try to use the DateDiff function in VBScript on a Windows Server 2003-based, Windows Vista-based, or Windows Server 2008-based computer that uses an RTL language: "Microsoft VBScript runtime error" "Type mismatch"
On This PageSYMPTOMSConsider the following scenario on a Windows Server 2003-based, Windows Vista-based, or Windows Server 2008-based computer:
In this scenario, you receive the following error message: Microsoft VBScript runtime error Type mismatch CAUSEThis problem occurs because the DateDiff function cannot handle RTL-formatted strings. Note There are other functions that cannot handle RTL-formatted strings. The following other functions are also fixed in the hotfix that is mentioned in the "Resolution" section:
RESOLUTIONHotfix information for Windows Server 2003A supported hotfix is 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 the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.PrerequisitesTo apply this hotfix, you must have a Windows Server 2003 Service Pack 1 (SP1)-based or Windows Server 2003 Service Pack 2 (SP2)-based computer.For more information, click the following article number to view the article in the Microsoft Knowledge Base: 889100
(http://support.microsoft.com/kb/889100/
)
How to obtain the latest service pack for Windows Server 2003
Restart requirementYou do not have to restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other hotfixes.File informationThe 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.For all supported x86-based versions of Windows Server 2003 SP1Collapse this table
For all supported x86-based versions of Windows Server 2003 SP2Collapse this table
For all supported Itanium-based versions of Windows Server 2003 SP1Collapse this table
For all supported Itanium-based versions of Windows Server 2003 SP2Collapse this table
For all supported x64-based versions of Windows Server 2003 SP1Collapse this table
For all supported x64-based versions of Windows Server 2003 SP2Collapse this table
Hotfix information for Windows Vista and for Windows Server 2008A supported hotfix is 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 the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page. PrerequisitesTo apply this hotfix on a Windows Vista-based computer, you must have Windows Vista SP1 or Windows Vista SP2 installed.To apply this hotfix on a Windows Server 2008-based computer, you must have Windows Server 2008 SP1 or Windows Server 2008 SP2 installed. Restart requirementYou do not have to restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other hotfixes.File informationThe 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 and Windows Server 2008 file information notesThe MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature. For all supported x86-based versions of Windows Server 2008 and of Windows VistaCollapse this table
For all supported x64-based versions of Windows Server 2008 and of Windows VistaCollapse this table
For all supported Itanium-64-based versions of Windows Server 2008Collapse this table
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONFor more information about the FormatDateTime function, visit the following Microsoft Web site: http://msdn.microsoft.com/en-us/library/8aebkz6s(VS.85).aspx
(http://msdn.microsoft.com/en-us/library/8aebkz6s(VS.85).aspx)
For more information about the DateDiff function, visit the following Microsoft Web site:http://msdn.microsoft.com/en-us/library/xhtyw595(VS.85).aspx
(http://msdn.microsoft.com/en-us/library/xhtyw595(VS.85).aspx)
Additional file information for Windows Server 2008 and for Windows VistaAdditional files for all supported x86-based versions of Windows Server 2008 and of Windows VistaCollapse this table
Additional files for all supported x64-based versions of Windows Server 2008 and of Windows VistaCollapse this table
Additional files for all supported Itanium-64-based versions of Windows Server 2008Collapse this table
APPLIES TO
| Article Translations
|
| United States | Change | | | All Microsoft Sites |
Back to the top
|
