Toon posts:

Win2003/Exchange 2003 installatie met foutmelding 0xC130798A

Pagina: 1
Acties:

Verwijderd

Topicstarter
Ik krijg steeds een foutmelding die ik niet direct kan thuisbrengen.
Excange weigert de installie voort te zetten na de foutmelding:
- 'setup failed while installing sub-component Excange messaging and collaboration services with error code 0xC130798A (please.....)....' en foutmelding
- 'setup failed while installing sub-component Exchange System Management Snap-ins with error code 0xC130798A (please.....)....'

Ik heb alle voorbereidingen voor de installatie voltooid: installatie iis componenten zoals aangegeven, dcdiag, netdiag, forestprep, domainprep

Wat zie ik over het hoofd?
Het is een nieuw-installatie op een Win 2003 server

  • Rolfie
  • Registratie: Oktober 2003
  • Laatst online: 08:47
MIjn glazen bol geeft aan dat je op de verkeerde toets drukt B) .

Wat kunnen we hier nu mee?

Je geeft alleen een error melding. Wat heb je zelf al gevonden, wat heb je zelf al probeert om het probleem op te lossen?

Je plaatst het wel in PNS, en daar verwachten we wat meer zelf in initiatief . Iets wat we in jouw posting.

  • _Arthur
  • Registratie: Juli 2001
  • Laatst online: 19-02 21:16

_Arthur

blub

Wat zijn de eventlog meldingen? Graag met de event-id's er bij.

  • Brahiewahiewa
  • Registratie: Oktober 2001
  • Laatst online: 30-09-2022

Brahiewahiewa

boelkloedig

_Arthur schreef op vrijdag 25 november 2005 @ 17:02:
Wat zijn de eventlog meldingen? Graag met de event-id's er bij.
Denk nie dat er veel zinnigs in z'n eventlog komt te staan. Voor problemen met Exchange setup, moet je in de Exchange Setup.log file kijken, in de root van je C:\ schijf

QnJhaGlld2FoaWV3YQ==


Verwijderd

Topicstarter
Wat heb ik zelf al gedaan?

Na Exchange er handmatig af te hebben gehaald en iis verwijderd te hebben is met dcdiag de domeincontroller nagelopen maar daar staan geen foutmeldingen in. Dat was voor de installatie ook al niet 't geval
Daarnaast is de DNS-configuratie nagelopen omdat MS aangeeft dat hierdoor de installatie spaak kan lopen. Echter dit functioneert normaal.
Heb inmiddels al een tijd lopen te zoeken op technet van MS, daar staat naar mijn weten maar een artikel dat de foutcode 0xC103798A omschrijft: Exchange Server 2003 Setup fails with error code while installing Active Directory schema update (http://support.microsoft....aspx?scid=kb;en-us;822583).

Het netwerk met dez Win2003 Server functioneert al bijna 2 jaar normaal. We wilden af van de combinatie Mercury4 en outlook omdat we onze agenda's willen delen in onze kleine instelling, vandaar de nieuwe installatie van Exchange 2003.

Hieronder een uitdraai van de 'Exchange Server Setup Progress' logfile.

[15:52:00] Interpreting line <CloseKey:> -- ID:31259 --
[15:52:00] Interpreting line <CreateProcessSafe:C:\Program Files\Exchsrvr\bin;regsvr32.exe -s -u excluadm.dll;180000> -- ID:31259 --
[15:52:00] Process created ... waiting (180000)
[15:52:01] Ignoring exit code 00000000
[15:52:01] Interpreting line <CreateProcessSafe:C:\Program Files\Exchsrvr\bin;regsvr32.exe -s -u cdoexm.dll;180000> -- ID:31259 --
[15:52:01] Process created ... waiting (180000)
[15:52:02] Ignoring exit code 00000000
[15:52:02] Interpreting line <CreateProcessSafe:C:\Program Files\Exchsrvr\bin;regsvr32.exe -s -u pop3mgr.dll;180000> -- ID:31259 --
[15:52:02] Process created ... waiting (180000)
[15:52:02] Ignoring exit code 0x000005
[15:52:02] Interpreting line <CreateProcessSafe:C:\Program Files\Exchsrvr\bin;regsvr32.exe -s -u pop3adm.dll;180000> -- ID:31259 --
[15:52:02] Process created ... waiting (180000)
[15:52:03] Ignoring exit code 00000000
[15:52:03] Interpreting line <CreateProcessSafe:C:\Program Files\Exchsrvr\bin;regsvr32.exe -s -u imapmgr.dll;180000> -- ID:31259 --
[15:52:03] Process created ... waiting (180000)
[15:52:03] Ignoring exit code 0x000005
[15:52:03] Interpreting line <CreateProcessSafe:C:\Program Files\Exchsrvr\bin;regsvr32.exe -s -u imapadm.dll;180000> -- ID:31259 --
[15:52:03] Process created ... waiting (180000)
[15:52:03] Ignoring exit code 00000000
[15:52:03] Interpreting line <CreateProcessSafe:C:\Program Files\Exchsrvr\bin;regsvr32.exe -s -u nntpmgr.dll;180000> -- ID:31259 --
[15:52:03] Process created ... waiting (180000)
[15:52:03] Ignoring exit code 0x000005
[15:52:03] Interpreting line <CreateProcessSafe:C:\Program Files\Exchsrvr\bin;regsvr32.exe -s -u smtpmgr.dll;180000> -- ID:31259 --
[15:52:03] Process created ... waiting (180000)
[15:52:03] Ignoring exit code 0x000005
[15:52:03] Interpreting line <CreateProcessSafe:C:\Program Files\Exchsrvr\bin;regsvr32.exe -s -u exadmin.dll;180000> -- ID:31259 --
[15:52:03] Process created ... waiting (180000)
[15:52:04] Ignoring exit code 0x000005
[15:52:04] Interpreting line <CreateProcessSafe:C:\Program Files\Exchsrvr\bin;regsvr32.exe -s -u maqadmin.dll;180000> -- ID:31259 --
[15:52:04] Process created ... waiting (180000)
[15:52:04] Ignoring exit code 00000000
[15:52:04] Interpreting line <CreateProcessSafe:C:\Program Files\Exchsrvr\bin;regsvr32.exe -s -u aqadmcon.dll;180000> -- ID:31259 --
[15:52:04] Process created ... waiting (180000)
[15:52:04] Ignoring exit code 00000000
[15:52:04] Interpreting line <CreateProcessSafe:C:\Program Files\Exchsrvr\bin;regsvr32.exe -s -u phatqadm.dll;180000> -- ID:31259 --
[15:52:04] Process created ... waiting (180000)
[15:52:04] Ignoring exit code 00000000
[15:52:04] Interpreting line <OpenMachineKey:SYSTEM\CurrentControlSet\Control\BackupRestore> -- ID:31259 --
[15:52:04] Interpreting line <DeleteValue:DLLPaths\esebcli2> -- ID:31259 --
[15:52:04] Interpreting line <CloseKey:> -- ID:31259 --
[15:52:04] Interpreting line <OpenMachineKey:SYSTEM\CurrentControlSet\Services\EventLog\Application> -- ID:31259 --
[15:52:04] Interpreting line <DeleteKey:ESE> -- ID:31259 --
[15:52:04] Interpreting line <CloseKey:> -- ID:31259 --
[15:52:05] Leaving CRegistryManager::ScProcessFile
[15:52:05] Leaving CBaseAtom(Exchange System Management Snap-ins)::ScRemoveRegistryKeys
[15:52:05] Entering CAtomAdmin::ScRegisterAdcDSMIfAppropriate
[15:52:05] Leaving CAtomAdmin::ScRegisterAdcDSMIfAppropriate
[15:52:05] Leaving CAtomAdmin::ScAddRegistryKeys
[15:52:05] Removing Active Directory objects for Exchange System Management Snap-ins
[15:52:05] Entering CBaseAtom(Exchange System Management Snap-ins)::ScRemoveShortcuts
[15:52:05] Removing start menu shortcuts for Exchange System Management Snap-ins
[15:52:05] Failed to delete shortcut 'Exchange Technical Library'.
[15:52:05] Failed to delete shortcut 'Exchange Tools and Updates'.
[15:52:05] Failed to delete shortcut 'Exchange Web Site'.
[15:52:05] Removing start menu shortcuts for Exchange System Management Snap-ins
[15:52:05] Leaving CBaseAtom(Exchange System Management Snap-ins)::ScRemoveShortcuts
[15:52:05] Removing IIS Metabase objects for Exchange System Management Snap-ins
[15:52:05] Leaving CBaseAtom(Exchange System Management Snap-ins)::ScRemove
[15:52:05] Entering CBaseServiceAtom(Exchange System Management Snap-ins)::ScDeleteAtomServices
[15:52:05] Leaving CBaseServiceAtom(Exchange System Management Snap-ins)::ScDeleteAtomServices
[15:52:05] Leaving CBaseServiceAtom(Exchange System Management Snap-ins)::ScRemove
[15:52:05] Entering CBaseServiceAtom(Exchange System Management Snap-ins)::ScAdd
[15:52:05] Entering CBaseServiceAtom(Exchange System Management Snap-ins)::ScCreateAtomServices
[15:52:05] Leaving CBaseServiceAtom(Exchange System Management Snap-ins)::ScCreateAtomServices
[15:52:05] Entering CBaseAtom(Exchange System Management Snap-ins)::ScAdd
[15:52:05] Entering CAtomAdmin::ScAddRegistryKeys
[15:52:05] Entering CBaseExchangeAtom::ScRemove55ExchmemDLL
[15:52:05] Attempting to remove file C:\WINDOWS\system32\exchmem.dll (if it exists)
[15:52:05] C:\WINDOWS\system32\exchmem.dll did not exist
[15:52:05] Leaving CBaseExchangeAtom::ScRemove55ExchmemDLL
[15:52:05] Entering CBaseAtom(Exchange System Management Snap-ins)::ScAddRegistryKeys
[15:52:05] Configuring registry entries for Exchange System Management Snap-ins
[15:52:05] Entering CRegistryManager::ScProcessFile
[15:52:05] ++++ Starting interpreter on file r:\setup\i386\exchange\admin.ins ++++ -- ID:31258 --
[15:52:05] Interpreting line <OpenMachineKey:SYSTEM\CurrentControlSet\Services\EventLog\Application> -- ID:31259 --
[15:52:05] Interpreting line <CreateKey:MSExchangeAdmin> -- ID:31259 --
[15:52:05] Interpreting line <CreateKey:CDOEXM> -- ID:31259 --
[15:52:05] Interpreting line <CreateKey:MSExchangeMGMT> -- ID:31259 --
[15:52:05] Interpreting line <CreateKey:MSExchangeMig> -- ID:31259 --
[15:52:05] Interpreting line <CreateKey:MSExchangeMigDS> -- ID:31259 --
[15:52:05] Interpreting line <CloseKey:> -- ID:31259 --
[15:52:05] Interpreting line <OpenMachineKey:SYSTEM\CurrentControlSet\Services\EventLog\Application\MSExchangeAdmin> -- ID:31259 --
[15:52:05] Interpreting line <ReplaceDword:CategoryCount;0x11> -- ID:31259 --
[15:52:05] Interpreting line <ReplaceExpandString:CategoryMessageFile;C:\Program Files\Exchsrvr\res\madmsg.dll> -- ID:31259 --
[15:52:05] Interpreting line <ReplaceExpandString:EventMessageFile;C:\Program Files\Exchsrvr\res\madmsg.dll> -- ID:31259 --
[15:52:05] Interpreting line <ReplaceDword:TypesSupported;7> -- ID:31259 --
[15:52:05] Interpreting line <CloseKey:> -- ID:31259 --
[15:52:05] Interpreting line <OpenMachineKey:SYSTEM\CurrentControlSet\Services\EventLog\Application\CDOEXM> -- ID:31259 --
[15:52:05] Interpreting line <ReplaceDword:CategoryCount;0x10> -- ID:31259 --
[15:52:05] Interpreting line <ReplaceExpandString:CategoryMessageFile;C:\Program Files\Exchsrvr\res\madmsg.dll> -- ID:31259 --
[15:52:05] Interpreting line <ReplaceExpandString:EventMessageFile;C:\Program Files\Exchsrvr\res\madmsg.dll> -- ID:31259 --
[15:52:05] Interpreting line <ReplaceDword:TypesSupported;7> -- ID:31259 --
[15:52:05] Interpreting line <CloseKey:> -- ID:31259 --
[15:52:06] Interpreting line <OpenMachineKey:SYSTEM\CurrentControlSet\Services\EventLog\Application\MSExchangeMGMT> -- ID:31259 --
[15:52:06] Interpreting line <ReplaceDword:CategoryCount;0x1> -- ID:31259 --
[15:52:06] Interpreting line <ReplaceExpandString:CategoryMessageFile;C:\Program Files\Exchsrvr\bin\exmgmt.exe> -- ID:31259 --
[15:52:06] Interpreting line <ReplaceExpandString:EventMessageFile;C:\Program Files\Exchsrvr\bin\exmgmt.exe> -- ID:31259 --
[15:52:06] Interpreting line <ReplaceDword:TypesSupported;7> -- ID:31259 --
[15:52:06] Interpreting line <CloseKey:> -- ID:31259 --
[15:52:06] Interpreting line <OpenMachineKey:SYSTEM\CurrentControlSet\Services\EventLog\Application\MSExchangeMig> -- ID:31259 --
[15:52:06] Interpreting line <ReplaceExpandString:EventMessageFile;C:\Program Files\Exchsrvr\bin\mlmig32.dll> -- ID:31259 --
[15:52:06] Interpreting line <ReplaceExpandString:ParameterMessageFile;C:\Program Files\Exchsrvr\bin\mlmig32.dll> -- ID:31259 --
[15:52:06] Interpreting line <ReplaceExpandString:CategoryMessageFile;C:\Program Files\Exchsrvr\bin\mlmig32.dll> -- ID:31259 --
[15:52:06] Interpreting line <ReplaceDword:TypesSupported;7> -- ID:31259 --
[15:52:06] Interpreting line <CloseKey:> -- ID:31259 --
[15:52:06] Interpreting line <OpenMachineKey:SYSTEM\CurrentControlSet\Services\EventLog\Application\MSExchangeMigDS> -- ID:31259 --
[15:52:06] Interpreting line <ReplaceExpandStringSystem:EventMessageFile;dapi.dll> -- ID:31259 --
[15:52:06] Interpreting line <ReplaceDword:TypesSupported;7> -- ID:31259 --
[15:52:06] Interpreting line <CloseKey:> -- ID:31259 --
[15:52:07] Interpreting line <OpenUserKey:Software\Microsoft> -- ID:31259 --
[15:52:07] Interpreting line <CreateKey:Exchange\MSExchangeAdmin> -- ID:31259 --
[15:52:07] Interpreting line <CloseKey:> -- ID:31259 --
[15:52:07] Interpreting line <OpenUserKey:Software\Microsoft\Exchange\MSExchangeAdmin> -- ID:31259 --
[15:52:07] Interpreting line <SetDword:KMPasswordRemember(flag);0> -- ID:31259 --
[15:52:07] Interpreting line <SetDword:KMPasswordRemember(mSec);0x493E0> -- ID:31259 --
[15:52:07] Interpreting line <CloseKey:> -- ID:31259 --
[15:52:08] Interpreting line <CreateProcess:C:\Program Files\Exchsrvr\bin;regsvr32.exe -s maildsmx.dll;4294967295> -- ID:31259 --
[15:52:08] Process created ... waiting (-1)
[15:52:10] Process has exited with 0x000005
[15:52:10] The command

regsvr32.exe -s maildsmx.dll

failed, returning error code 5 (Toegang geweigerd.). -- ID:31136 -- ScCreateProcess (f:\titanium\admin\src\libs\exsetup\hiddenw1.cxx:1821)
Error code 0XC103798A (31114): An internal component has failed.
[15:52:10] CInsParser::ScProcessLine (f:\titanium\admin\src\libs\exsetup\hiddenw1.cxx:1225)
Error code 0XC103798A (31114): An internal component has failed.
[15:52:10] Processing file 'r:\setup\i386\exchange\admin.ins', at or near line 73 (CreateProcess:C:\Program Files\Exchsrvr\bin;regsvr32.exe -s maildsmx.dll;4294967295) -- ID:31111 -- CInsParser::ScProcessLine (f:\titanium\admin\src\libs\exsetup\hiddenw1.cxx:492)
Error code 0XC103798A (31114): An internal component has failed.
[15:52:10] Registry file name: 'r:\setup\i386\exchange\admin.ins' CRegistryManager::ScProcessFile (f:\titanium\admin\src\udog\setupbase\tools\regmgr.cxx:125)
Error code 0XC103798A (31114): An internal component has failed.
[15:52:10] Filename = 'r:\setup\i386\exchange\admin' CBaseAtom::ScAddRegistryKeys (f:\titanium\admin\src\udog\setupbase\basecomp\baseatom.cxx:1408)
Error code 0XC103798A (31114): An internal component has failed.
[15:52:10] CAtomAdmin::ScAddRegistryKeys (f:\titanium\admin\src\udog\exsetdata\components\admin\a_admin.cxx:189)
Error code 0XC103798A (31114): An internal component has failed.
[15:52:10] Leaving CAtomAdmin::ScAddRegistryKeys
[15:52:10] CBaseAtom::ScAdd (f:\titanium\admin\src\udog\setupbase\basecomp\baseatom.cxx:939)
Error code 0XC103798A (31114): An internal component has failed.
[15:52:10] Service = '' CBaseServiceAtom::ScAdd (f:\titanium\admin\src\udog\setupbase\basecomp\basesvcatom.cxx:210)
Error code 0XC103798A (31114): An internal component has failed.
[15:52:10] Leaving CBaseServiceAtom(Exchange System Management Snap-ins)::ScAdd
[15:52:10] mode = 'Install' (61953) CBaseAtom::ScSetup (f:\titanium\admin\src\udog\setupbase\basecomp\baseatom.cxx:842)
Error code 0XC103798A (31114): An internal component has failed.
[15:58:38] ***** RETRYING THE FAILED OPERATION *****

  • Brahiewahiewa
  • Registratie: Oktober 2001
  • Laatst online: 30-09-2022

Brahiewahiewa

boelkloedig

QnJhaGlld2FoaWV3YQ==


  • StevenK
  • Registratie: Februari 2001
  • Laatst online: 08:40
Verwijderd schreef op vrijdag 25 november 2005 @ 22:14:
[15:52:10] The command

regsvr32.exe -s maildsmx.dll

failed, returning error code 5 (Toegang geweigerd.). -- ID:31136 -- ScCreateProcess
Lijkt me duidelijk ?

Was advocaat maar vindt het juridische nog steeds leuk. Doet tegenwoordig iets in de metaal.


Verwijderd

Move PNS > SA

  • paella
  • Registratie: Juni 2001
  • Laatst online: 20-02 20:20
Ben je wel de juiste Administrators? (Schema/Enterprise/etc)

No production networks were harmed during this posting


  • sanfranjake
  • Registratie: April 2003
  • Niet online

sanfranjake

Computers can do that?

(overleden)
Dan had je bij de forestprep ook al rare errors moeten krijgen lijkt me. Die doet afaik ook een schema update.

Mijn spoorwegfotografie
Somda - Voor en door treinenspotters


  • StevenK
  • Registratie: Februari 2001
  • Laatst online: 08:40
paella schreef op zaterdag 26 november 2005 @ 11:29:
Ben je wel de juiste Administrators? (Schema/Enterprise/etc)
Die regsvr32 foutmelding heeft iets te maken met rechten lokaal op die bak, niet met AD rechten.

Was advocaat maar vindt het juridische nog steeds leuk. Doet tegenwoordig iets in de metaal.


  • paella
  • Registratie: Juni 2001
  • Laatst online: 20-02 20:20
StevenK schreef op zaterdag 26 november 2005 @ 12:33:
[...]

Die regsvr32 foutmelding heeft iets te maken met rechten lokaal op die bak, niet met AD rechten.
juiste admin kan dus ook lokale admin zijn... :P
(valt onder "etc...").

[ Voor 5% gewijzigd door paella op 26-11-2005 12:45 ]

No production networks were harmed during this posting


  • StevenK
  • Registratie: Februari 2001
  • Laatst online: 08:40
paella schreef op zaterdag 26 november 2005 @ 12:36:
[...]


juiste admin kan dus ook lokale admin zijn... :P
Ja, wie heeft 't nu over Schema/Enterprise admins ?

Ik vermoed trouwens dat er eerder een NTFS of registry ACL probleempje is, maar dat moet TS met regmon en/of filemon toch wel kunnen achterhalen ?

Was advocaat maar vindt het juridische nog steeds leuk. Doet tegenwoordig iets in de metaal.

Pagina: 1