Article ID: 305838 - Last Review: November 3, 2003 - Revision: 3.3 PRB: MDAC Installation on Windows Terminal Server May FailThis article was previously published under Q305838 IMPORTANT: This article contains information about modifying the registry.
Before you modify the registry, make sure to back it up and make sure that you
understand how to restore the registry if a problem occurs. For information
about how to back up, restore, and edit the registry, click the following
article number to view the article in the Microsoft Knowledge Base: 256986
(http://support.microsoft.com/kb/256986/EN-US/
)
Description of the Microsoft Windows Registry
SYMPTOMS If you install Microsoft Data Access Components (MDAC)
version 2.1, 2.5, or 2.6 on Windows NT 4.0 Terminal Server or Windows 2000
Terminal Services, sometimes the MDAC installation may fail. This problem may also occur after you use Component Checker to reconfigure the MDAC installation on Terminal Server. CAUSE This problem occurs when a registry setting that points to
the Program Files\Common Files folder is overwritten with the incorrect entry.
RESOLUTIONWARNING: If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system. Microsoft
cannot guarantee that you can solve problems that result from using Registry
Editor incorrectly. Use Registry Editor at your own
risk.
REFERENCESFor additional information about installing MDAC on
Terminal Server, click the article numbers below to view the articles in the
Microsoft Knowledge Base: 216149
(http://support.microsoft.com/kb/216149/EN-US/
)
How to Install ODBC or MDAC on Terminal Server
304332
(http://support.microsoft.com/kb/304332/EN-US/
)
PRB: Installing MDAC on Terminal Server
For general information regarding MDAC
installation, see the following Microsoft Web site: http://msdn.microsoft.com/en-us/data/aa937729.aspx
(http://msdn.microsoft.com/en-us/data/aa937729.aspx)
APPLIES TO
| Article Translations
|
Back to the top
