You are currently offline, waiting for your internet to reconnect

Exception 0E in Vredir.vxd during CoCreateInstanceEx() on remote DCOM server

This article was previously published under Q271754
This article has been archived. It is offered "as is" and will no longer be updated.
If this article does not describe the error message that you are receiving, view the following Microsoft Knowledge Base article to view more articles that describe error messages:
315854 Windows 98 and Windows Me Error Message Resource Center
If your network is set up as a workgroup, you have a drive mapped to a Microsoft Windows NT-based server, and you run a Distributed Component Object Model (DCOM) program that attempts to start a remote server component on the Windows NT-based server, you may receive one of the following error messages on a blue screen.

Windows 95, Windows 98, Windows 98 Second Edition:

A fatal exception 0E has occurred at 0028:???????? in VXD VREDIR(??)+ ????????. The current application will be terminated.

* Press any key to terminate the current application.
* Press CTRL+ALT+DEL again to restart your computer. You will lose any unsaved information on all applications.

Press any key to continue.
Windows Millennium Edition (Me):

An error has occurred. To continue:

Press Enter to return to Windows, or Press CTRL+ALT+DEL to restart your computer. If you do this, you will lose any unsaved information in all open applications.

File Name: VREDIR(06) + 00006C54 Error: 0E : 0028 : C02D2770

Press any key to continue.
If you press ENTER, CoCreateInstanceEx returns RPC_S_CALL_FAILED (0x800706BE). The program may display the following error message:
The remote procedure call failed.
See the "More Information" section of this article for the error message values for various versions of the Vredir.vxd file.
The redirector (Vredir.vxd) incorrectly references internal resource data for the mapped drive connection while setting up the connection that the DCOM Remote Procedure Call (RPC) traffic will use.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, 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.

The English version of this fix should have the following file attributes or later:
   Date        Time    Version    Size     File name   Operating system   --------------------------------------------------------------------      09/28/2000  09:23p  4.10.2152  165,461  Vredir.vxd  Windows 98   09/20/2000  04:06a  4.10.2228  165,461  Vredir.vxd  Windows 98                                                        Second Edition   09/19/2000  08:24p  4.90.3002  161,849  Vredir.vxd  Windows Me				

To work around this problem, you can map the drive to the server by using Windows Explorer, or by right-clicking Network Neighborhood, and then clicking Map Network Drive.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More information
The following list contains the error message values for the error condition. Note that on Windows 95 with the indicated Vredir.vxd update installed, the exception may not occur. Instead, CoCreateInstanceEx may return 0x80070005 ERROR_ACCESS_DENIED ("Access is denied").
  Error message details                      Vredir.vxd  Operating system  -----------------------------------------------------------------------  0028:C0291111 in VXD VREDIR(04)+ 00005A79  4.00.955    Windows 95 SP1  0028:C029FEA8 in VXD VREDIR(06)+ 000066A4  4.00.1111   Windows 95 OSR2  0028:C02CFBC2 in VXD VREDIR(06)+ 00006C4A  4.00.1122   Windows 95 (all                                                         versions) *  0028:C02CFB16 in VXD VREDIR(06)+ 00006B4A  4.10.1998   Windows 98  0028:C02CFC16 in VXD VREDIR(06)+ 00006C4A  4.10.2150   Windows 98 *  0028:C02D1A7A in VXD VREDIR(06)+ 00006B3A  4.10.2222   Windows 98                                                          Second Edition  0028:C02D1CA4 in VXD VREDIR(06)+ 00006E44  4.10.2226   Windows 98                                                          Second Edition *  0028:C02CFBC2 in VXD VREDIR(06)+ 00006C54  4.90.3000   Windows Me				
* Indicates the previous Vredir.vxd update.

For additional information about the previous update to Vredir.vxd, click the following article number to view the article in the Microsoft Knowledge Base:
238853 Cannot browse network neighborhood if PDC is on separate subnet
For additional information about Windows Me hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:
295413 General information about Windows Millennium Edition hotfixes
For additional information about Windows 98 and Windows 98 Second Edition hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:
206071 General Information About Windows 98 and Windows 98 Second Edition Hotfixes
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Article ID: 271754 - Last Review: 10/26/2013 00:53:00 - Revision: 1.0

Microsoft Windows 95

  • kbnosurvey kbarchive kbhotfixserver kbqfe kberrmsg kbfatalexerr0e kbfix kbprb KB271754