7/31/2019 _Setup Failed While Installing Sub-component Base DAV
Protocol_ Error Message When You Install Windows Small B
1/31/3upport.microsoft.com/kb/838176
"Setup failed while installing sub-component Base DAV
protocol" error message when you install Windows
Small Business Server 2003 or Exchange Server 2003Article ID:
838176 - View products that this article applies to.
When you do one of the following:
When you upgrade Microsoft Small Business Server 2000 to
Microsoft Windows Small Business Server (SBS)
2003.
When you upgrade Microsoft Windows 2000 Server to Microsoft
Windows Server 2003, and then you try to
install Microsoft Exchange Server 2003 or upgrade from Exchange
2000 to Exchange 2003
You may receive the following error message:
You have the option to click Retry or to click Cancel in
response to the error message. You may receive the following
error message in the Exchange Server Setup Progress.log:
Note This log is located at the root of the drive where you
install SBS 2003 or where you install Exchange Server 2003.
This is a known issue that occurs when you upgrade a computer
with the following configuration:
Windows Server 2000 Microsoft Data Access Components (MDAC)
version 2.7 or 2.7 Service Pack 1 (SP1)
Security Update MS04-003 (KB832483)
When you upgrade a server with this configuration to Windows
Server 2003, the Setup program cannot update the
version of the Oledb32.dll file. Therefore, the Oledb32.dll file
version remains at 2.7.9002.0 (MDAC 2.7 with KB832483)
or 2.71.9031.4 (MDAC 2.7 SP1 with KB832483). For Windows Server
2003, the version of the Oledb32.dll file must be
2.8.1022.0. If you then try to install Small Business Server
2003 or Exchange Server 2003, you receive the error
message that is mentioned in the "Symptoms" section.
To work around this behavior, do the following:
1. Exit the Setup program.
a. If you are in the Windows Small Business Server Setup program
click the Cancel button, to continue the
installation.
b. If you are in the Exchange Server 2003 Setup program, click
OKto quit the Setup program.
2. When the Setup program is complete, or after you have
canceled the Setup program, restart your server .
3. To complete the next steps, you must start your computer in
safe mode. To start your computer in safe mode,
do the following:
a. Press the F8 key during the beginning of the startup process,
before Windows Server 2003 starts to
load.
b. Use the arrow keys to select Safe Mode with Networking, and
then press ENTER.
c. If you have a dual-boot or multiple-boot system, select the
installation that you want to access by using
the arrow keys, and then press ENTER.
4. Click Start, point to All Programs, point to Accessories, and
then click Windows Explorer.
5. Click Tools, click Folder Options, click the View tab, and
then click to clear the Hide protected operating
system files check box.
6. When the warning dialog appears click Yes, and then click
OK.
7. In the Windows Explorer Folders pane locate the Oledb32.dll
file in the following folder:
Symptoms
Setup failed while installing sub-component Base DAV protocol
with error code 0xC103798A (see the installation
logs for a detailed description). You may cancel the
installation or try the failed step again.
The command regsvr32 /s exoledb.dll failed, returning error code
5 (Access is denied.).
Cause
Workaround
7/31/2019 _Setup Failed While Installing Sub-component Base DAV
Protocol_ Error Message When You Install Windows Small B
2/32/3upport.microsoft.com/kb/838176
r ve: rogram es ommon es ys em e
8. Right-click Oledb32.dll, click Properties, and then click the
Version tab.
9. Verify that the version is earlier than 2.80.1022.0.
10. Right-click Oledb32.dll, and then click Rename.
11. Type the file name Oledb32.old, and then press ENTER.
12. On the Windows Explorer Folders pane locate a possible
second instance of the Oledb32.dll file in the
following folder:
Note Windiris the folder where Windows is installed.
Drive:\Windir\System32\Dllcache\Oledb32.dll
13. If the Oledb32.dll file exists, right-click Oledb32.dll,
click Delete, and then click Yes to confirm.
14. With the Windows Small Business Server 2003 installation
disk number 1, or with the Windows Server 2003installation disk in
your CD drive, click Start, click Run, and then in the Open box,
type cmd, and then click OK.
15. At the command prompt type the following where CDdrive is
the drive letter of your CD drive, and then press
ENTER:
CDdrive:
16. Type the following, and then press ENTER:
cd I386
17. Type the following, and then press ENTER:
expand oledb32.dl_ "Drive:\program files\Common files\system\Ole
DB\oledb32.dll"
18. Type the following, and then press ENTER:
expand oledb32.dl_
Drive:\Windir\System32\Dllcache\Oledb32.dll
19. At the command prompt, move to the following folder.
Drive:\Program Files\Common Files\System\Ole DB
20. Type the following, and then press ENTER:regsvr32
oledb32.dll
21. Click OKwhen you receive the following message:
DllRegisterServer in oledb32.dll succeeded.
22. By default, Windows hides protected operating system files.
To hide the protected operating system files,
locate the Windows Explorer program. Click Tools, click Folder
Options, click the View tab, click to select the
Hide protected operating system files check box, and then click
OK.
23. Restart your computer.
24. Start the SBS 2003 Setup program or s tart the Exchange
Server 2003 Setup program to complete the upgrade.
Note If you still experience the behavior, install Microsoft
Data Access Components (MDAC) 2.8.
The following file is available for download from the Microsoft
Download Center:
http://msdn.microsoft.com/en-us/data/aa937730.aspx
(http://msdn.microsoft.com/en-us/data/aa937730.aspx)
This can be caused when the server is running MDAC 2.8. If an
analysis is performed against the selected version of
MDAC 2.8, the Oledb32.dll version is 2.7.9002.0. Windows Server
2003 has Oledb32.dll version 2.8.1022.0. Several
programs, such as Microsoft SQL Server 2000 SP3a, Microsoft
Visual Studio .Net and Microsoft Business Contact
Manager include MDAC 2.7 or 2.71 SP1. If you visit the Windows
Update site on a computer that is running one of
these MDAC versions, the site will offer KB832483 as a critical
update.
The Progress.log file may appear as follows:
Note The information in the following Knowledge Base article
does not resolve this behavior that is described in this
article:
296436 (http://support.microsoft.com/kb/296436/ ) XADM: Setup
cannot register the Exoledb.dll file
If you try the workaround that is suggested in the 296436
Knowledge Base article, you may receive the following error
message:
More information
[03:16:05] Interpreting line
[03:16:05] Process created ... waiting (180000)
[03:16:05] Process has exited with 0x000005
[03:16:05] The command regsvr32 /s exoledb.dll failed, returning
error code 5 (Access is denied.). -- ID:31136 --
ScCreateProcess (drive:\hiddenw1.cxx:1821) Error code 0XC103798A
(31114): An internal component has failed.
[03:16:05] CInsParser::ScProcessLine
(f:\titanium\admin\src\libs\exsetup\hiddenw1.cxx:1225) Error
code
0XC103798A (31114): An internal component has failed.
[03:16:05] Processing file 'e:\setup\i386\exchange\dav.ins', at
or near line 13 (CreateProcess:C:\Program
Files\Exchsrvr\bin;regsvr32 /s exoledb.dll;180000) -- ID:31111
-- CInsParser::ScProcessLine
(f:\titanium\admin\src\libs\exsetup\hiddenw1.cxx:492) Error code
0XC103798A (31114): An internal component has
failed.
LoadLibrary("oledb32.dll") failed - The specified procedure
could not be found.
