Microsoft KB Archive/822583

= Exchange Server 2003 Setup fails with error code 0xC103798A while installing Active Directory schema update =

Article ID: 822583

Article Last Modified on 11/14/2007

-

APPLIES TO


 * Microsoft Exchange Server 2003 Enterprise Edition
 * Microsoft Exchange Server 2003 Standard Edition
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Service Pack 3
 * Microsoft Windows 2000 Service Pack 4

-





SYMPTOMS
When you try to install Microsoft Exchange Server 2003 on a server that is running Microsoft Windows 2000 Server, you may receive the following error message:

Setup failed while installing sub-component &quot;Microsoft Windows Active Directory schema update &quot; with error code 0xC103798A (please consult the installation logs for a detailed description). You may cancel the installation or try the failed step again.

When you view the Exchange Server Setup Progress.log installation log file, the file contains the following information: [00:58:15]    Entering CRegistryManager::ScProcessFile [00:58:15] ++++ Starting interpreter on file \\servername\prop\6867\server\enterprise\ent\rtl\usa\setup\i386\exchange\schema.ins ++++ -- ID:31258 -- [00:58:15] Interpreting line 8 -- ID:31259 -- [00:58:15] Process created ... waiting (-1) [00:59:17] Process has exited with 0x000005 [00:59:17] The command regsvr32.exe /i /n /s maildsmx.dll failed, returning error code 5 (Access is denied.). -- ID:31136 -- ScCreateProcess (f:\titanium\admin\src\libs\exsetup\hiddenw1.cxx:1821) Error code 0XC103798A (31114): An internal component has failed. [00:59:17]     CInsParser::ScProcessLine (f:\titanium\admin\src\libs\exsetup\hiddenw1.cxx:1225) Error code 0XC103798A (31114): An internal component has failed. [00:59:17] Processing file '\\servername\prop\6867\server\enterprise\ent\rtl\usa\setup\i386\exchange\schema.ins', at or near line (CreateProcess:\\servername\prop\6867\server\enterprise\ent\rtl\usa\setup\i386\exchange\bin;regsvr32.exe /i /n /s        maildsmx.dll;4294967295)8 -- ID:31111 -- CInsParser::ScProcessLine (f:\titanium\admin\src\libs\exsetup\hiddenw1.cxx:492) Error code 0XC103798A (31114): An internal component has failed. [00:59:17] Registry file name: '\\servername\prop\6867\server\enterprise\ent\rtl\usa\setup\i386\exchange\schema.ins' CRegistryManager::ScProcessFile (f:\titanium\admin\src\udog\setupbase\tools\regmgr.cxx:125) Error code 0XC103798A (31114): An internal component has failed. [00:59:17] Filename = '\\servername\prop\6867\server\enterprise\ent\rtl\usa\setup\i386\exchange\schema' CBaseAtom::ScAddRegistryKeys (f:\titanium\admin\src\udog\setupbase\basecomp\baseatom.cxx:1408) Error code 0XC103798A (31114): An internal component has failed. [00:59:17]     CAtomSchema::ScAddRegistryKeys (f:\titanium\admin\src\udog\exsetdata\components\root\a_schema.cxx:318) Error code 0XC103798A (31114): An internal component has failed. [00:59:17] Leaving CAtomSchema::ScAddRegistryKeys [00:59:17]     CAtomSchema::ScAdd (f:\titanium\admin\src\udog\exsetdata\components\root\a_schema.cxx:150) Error code 0XC103798A (31114): An internal component has failed. [00:59:17] Leaving CAtomSchema::ScAdd [00:59:17] mode = 'Install' (61953) CBaseAtom::ScSetup (f:\titanium\admin\src\udog\setupbase\basecomp\baseatom.cxx:842) Error code 0XC103798A (31114): An internal component has failed.



CAUSE
This problem may occur if your Domain Name System (DNS) configuration does not have service location records (SRV records) configured. The problem may occur if all the following conditions exist:
 * Your DNS configuration does not permit dynamic updates.
 * You install a global catalog server in the domain, and select the No, I will install and configure DNS myself option during the Dcpromo procedure.
 * You do not manually configure the service location records (SRV records) in DNS.
 * You install Exchange Server 2003.

Exchange Server 2003 Setup does not warn you that the DNS configuration is not valid before it continues with the Exchange installation.



WORKAROUND
To resolve this problem, configure DNS to permit automatic updates, and then re-register the server or servers in DNS. To do so:  Start the DNS utility on the Windows 2000-based server. Expand Forward Lookup Zones, right-click the appropriate forward lookup zone, and then click Properties. In the Allow dynamic updates? list, click Yes or Only secure updates.

Note The Only secure updates option is only available if the zone type is set to Active Directory-integrated. Click Apply, and then click OK. On a domain controller, do one of the following: <ul> Restart the Net Logon service to force the domain controller to re-register SRV records. To do this, enter the following commands from a command prompt and press ENTER after each command:

net stop netlogon

net start netlogon

</li> Run the netdiag /fix command to verify SRV records. To do this, enter the following command from a command prompt, and then press ENTER:

netdiag /fix

</li></ul> </li> Re-register other servers in DNS. To do so, enter the following commands from a command prompt on the server that you want to re-register, and then press ENTER after each command.

ipconfig /flushdns

ipconfig /registerdns

</li></ol>

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

<div class="moreinformation_section">

MORE INFORMATION
For additional information about how to troubleshoot missing SRV records in DNS, click the following article number to view the article in the Microsoft Knowledge Base:

241505 SRV records missing after implementing Active Directory and Domain Name System

For additional information about managing resource records in DNS, visit the following Web site:

http://technet.microsoft.com/en-us/windowsserver/2000/default.aspx

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

255913 Integrating Windows 2000 DNS into an existing BIND or Windows NT 4.0-based DNS namespace

Additional query words: C103798A

Keywords: kbnofix kbbug KB822583

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.