Unable to install Mailbox Role Error 3238230410
Hi I am unable to install the Mailbox Role for Exchange 2007 And get the error: An error occurred. error code was 3238230410 message was An internal component has failed.." How to solve this? Thanks in advance Ruben
July 4th, 2007 2:37pm

Hi, Look in the exchange setup log located in a folder on the c drive and see if that helps. Leif
Free Windows Admin Tool Kit Click here and download it now
July 7th, 2007 10:03pm

I am getting the same error. All I can see is "access is denied" when registering exoledb.dll in the Exchange log. have you figured this out yet? I will let you know if I do.... Michael
July 10th, 2007 12:12am

Hi Leif I hope this can help. I Found this, also included in the last CutNpaste below, what does it mean, why would I get an access denied? regsvr32 /s exoledb.dll failed, returning error code 5 (Access is denied.). -- ID:31136 -- ScCreateProcess (f:\08.00.0685\sources\dev\admin\src\libs\exsetup\hiddenw1.cxx:1784) A few CutnPastes from ExchangeSetup.log: --- WRN: Assembly binding logging is turned OFF.To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.Note: There is some performance penalty associated with assembly bind failure logging.To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].while resolving 0xa000af5 - Microsoft.Exchange.Clients.Strings.get_None.Warning: System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Exchange.Clients.Strings, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.File name: 'Microsoft.Exchange.Clients.Strings, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'WRN: Assembly binding logging is turned OFF.To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.Note: There is some performance penalty associated with assembly bind failure logging.To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].while resolving 0xa000b0d - Microsoft.Exchange.Clients.Strings.get_QuotaUsage.Could not load file or assembly 'Microsoft.Exchange.Clients.Strings, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. while scanning method 0x600011d - Microsoft.Exchange.Clients.Owa.Basic.Controls.ContactsListViewContents.get_PropertyAltMapCould not load file or assembly 'Microsoft.Exchange.Clients.Strings, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. (Exception from HRESULT: 0x80070002) while scanning method 0x60003b2 - Microsoft.Exchange.Clients.Owa.Basic.Controls.ToolbarButton..ctorCould not load file or assembly 'Microsoft.Exchange.Clients.Strings, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. (Exception from HRESULT: 0x80070002) while scanning method 0x60003b3 - Microsoft.Exchange.Clients.Owa.Basic.Controls.ToolbarButton..ctorCould not load file or assembly 'Microsoft.Exchange.Clients.Strings, Version=8.0.0.0, Culture=neutral, ---- ---- [04-07-2007 12:53:31] [2] Beginning processing.[04-07-2007 12:53:31] [2] Starting: unlodctr arguments: ESE[04-07-2007 12:53:31] [2] Process standard output: Counters for ESE have not been installed yet [04-07-2007 12:53:31] [2] Process standard error: [04-07-2007 12:53:31] [2] [ERROR] Unexpected Error[04-07-2007 12:53:31] [2] [ERROR] Process execution failed with exit code 1010.[04-07-2007 12:53:31] [2] Ending processing.[04-07-2007 12:53:31] [1] The following 1 error(s) occurred during task execution:[04-07-2007 12:53:31] [1] 0. ErrorRecord: Process execution failed with exit code 1010.[04-07-2007 12:53:31] [1] The previous errors were generated by a non-critical task and will be ignored.[04-07-2007 12:53:31] [1] Setup will continue processing component tasks...[04-07-2007 12:53:31] [1] Executing '$proc = [System.Environment]::GetEnvironmentVariable("PROCESSOR_ARCHITECTURE"); $p = [System.IO.Path]::Combine("$RoleInstallPath", "bin"); $p = [System.IO.Path]::Combine("$p", "perf"); $p = [System.IO.Path]::Combine("$p", "$proc"); $p = [System.IO.Path]::Combine("$p", "eseperf.ini"); start-SetupProcess -Name:"lodctr" -Args:"`"$p`"" -Timeout:600000;', handleError = True[04-07-2007 12:53:31] [2] Launching sub-task '$error.Clear(); $proc = [System.Environment]::GetEnvironmentVariable("PROCESSOR_ARCHITECTURE"); $p = [System.IO.Path]::Combine("$RoleInstallPath", "bin"); $p = [System.IO.Path]::Combine("$p", "perf"); $p = [System.IO.Path]::Combine("$p", "$proc"); $p = [System.IO.Path]::Combine("$p", "eseperf.ini"); start-SetupProcess -Name:"lodctr" -Args:"`"$p`"" -Timeout:600000;'.[04-07-2007 12:53:31] [2] Beginning processing.[04-07-2007 12:53:31] [2] Starting: lodctr arguments: "C:\Program Files\Microsoft\Exchange Server\bin\perf\AMD64\eseperf.ini"[04-07-2007 12:54:09] [2] Process standard output: [04-07-2007 12:54:09] [2] Process standard error: [04-07-2007 12:54:09] [2] Ending processing.[04-07-2007 12:54:09] [1] Executing 'start-SetupProcess -Name:"unlodctr" -Args:"MSExchangeIS" -Timeout:180000;', handleError = True[04-07-2007 12:54:09] [2] Launching sub-task '$error.Clear(); start-SetupProcess -Name:"unlodctr" -Args:"MSExchangeIS" -Timeout:180000;'.[04-07-2007 12:54:09] [2] Beginning processing.[04-07-2007 12:54:09] [2] Starting: unlodctr arguments: MSExchangeIS[04-07-2007 12:54:09] [2] Process standard output: Counters for MSExchangeIS have not been installed yet ---- --- regsvr32 /s exoledb.dll failed, returning error code 5 (Access is denied.). -- ID:31136 -- ScCreateProcess (f:\08.00.0685\sources\dev\admin\src\libs\exsetup\hiddenw1.cxx:1784) Error code 0XC103798A (31114): An internal component has failed.[04-07-2007 13:06:47] [2] CInsParser:cProcessLine (f:\08.00.0685\sources\dev\admin\src\libs\exsetup\hiddenw1.cxx:1199) Error code 0XC103798A (31114): An internal component has failed.[04-07-2007 13:06:47] [2] Processing file 'C:\Program Files\Microsoft\Exchange Server\Setup\data\dav.ins', at or near line 13 (CreateProcess:C:\Program Files\Microsoft\Exchange Server\bin;regsvr32 /s exoledb.dll;180000) -- ID:31111 -- CInsParser:cProcessLine (f:\08.00.0685\sources\dev\admin\src\libs\exsetup\hiddenw1.cxx:488) Error code 0XC103798A (31114): An internal component has failed.[04-07-2007 13:06:47] [2] Registry file name: 'C:\Program Files\Microsoft\Exchange Server\Setup\data\dav.ins' CRegistryManager:cProcessFile (f:\08.00.0685\sources\dev\admin\src\udog\setupbase\tools\regmgr.cxx:125) Error code 0XC103798A (31114): An internal component has failed.[04-07-2007 13:06:47] [2] Filename = 'C:\Program Files\Microsoft\Exchange Server\Setup\data\dav' CBaseAtom:cRunRegistryFile (f:\08.00.0685\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:1379) Error code 0XC103798A (31114): An internal component has failed.[04-07-2007 13:06:47] [2] Leaving CBaseAtom(Base DAV protocol):cRunRegistryFile[04-07-2007 13:06:47] [2] Filename = 'C:\Program Files\Microsoft\Exchange Server\Setup\data\dav' CBaseAtom:cAddRegistryKeys (f:\08.00.0685\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:1249) Error code 0XC103798A (31114): An internal component has failed.[04-07-2007 13:06:47] [2] Leaving CBaseAtom(Base DAV protocol):cAddRegistryKeys[04-07-2007 13:06:47] [2] CBaseAtom:cAdd (f:\08.00.0685\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:639) Error code 0XC103798A (31114): An internal component has failed.[04-07-2007 13:06:47] [2] Leaving CBaseAtom(Base DAV protocol):cAdd[04-07-2007 13:06:47] [2] Service = '' CBaseServiceAtom:cAdd (f:\08.00.0685\sources\dev\admin\src\udog\setupbase\basecomp\basesvcatom.cxx:203) Error code 0XC103798A (31114): An internal component has failed.[04-07-2007 13:06:47] [2] Leaving CBaseServiceAtom(Base DAV protocol):cAdd[04-07-2007 13:06:47] [2] mode = 'Install' (61953) CBaseAtom:cSetup (f:\08.00.0685\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:535) Error code 0XC103798A (31114): An internal component has failed.[04-07-2007 13:06:47] [2] ScSetupAtom (f:\08.00.0685\sources\dev\admin\src\udog\exsetdata\exsetds.cxx:889) Error code 0XC103798A (31114): An internal component has failed.[04-07-2007 13:06:47] [2] Leaving ScSetupAtom[04-07-2007 13:06:47] [2] [ERROR] An error occurred. error code was 3238230410 message was An internal component has failed.."[04-07-2007 13:06:48] [1] The following 1 error(s) occurred during task execution:[04-07-2007 13:06:48] [1] 0. ErrorRecord: An error occurred. error code was 3238230410 message was An internal component has failed.."[04-07-2007 13:06:48] [1] 0. ErrorRecord: Microsoft.Exchange.Management.Deployment.ExsetdataException: An error occurred. error code was 3238230410 message was An internal component has failed.."[04-07-2007 13:06:48] [1] [ERROR] An error occurred. error code was 3238230410 message was An internal component has failed.."[04-07-2007 13:06:48] [1] Setup is halting task execution because of one or more errors in a critical task.[04-07-2007 13:06:48] [1] Finished executing component tasks.[04-07-2007 13:06:48] [1] Ending processing.[04-07-2007 13:08:06] [0] End of Setup--------
Free Windows Admin Tool Kit Click here and download it now
July 10th, 2007 10:47am

As this error is going around. We have just Bought Exchange 2007 and I am trying to install it on a HP DL360 with Dual Xeon Dual Core Processors and 8GB of RAM, with 250GB SATA RAID. I too get this in the log. [12/07/2007 09:40:35] [2] Interpreting line <CreateProcess:\Program Files\Exchange Server\bin;regsvr32 /s exoledb.dll;180000> -- ID:31259 --[12/07/2007 09:40:35] [2] Process created ... waiting (180000)[12/07/2007 09:40:36] [2] Process has exited with 0x000005[12/07/2007 09:40:36] [2] The command regsvr32 /s exoledb.dll failed, returning error code 5 (Access is denied.). -- ID:31136 -- ScCreateProcess (f:\e12rtmhot\sources\dev\admin\src\libs\exsetup\hiddenw1.cxx:1784) Error code 0XC103798A (31114): An internal component has failed.[12/07/2007 09:40:36] [2] CInsParser:cProcessLine (f:\e12rtmhot\sources\dev\admin\src\libs\exsetup\hiddenw1.cxx:1199) Error code 0XC103798A (31114): An internal component has failed.[12/07/2007 09:40:36] [2] Processing file 'D:\Program Files\Exchange Server\Setup\data\dav.ins', at or near line 13 (CreateProcess:\Program Files\Exchange Server\bin;regsvr32 /s exoledb.dll;180000) -- ID:31111 -- CInsParser:cProcessLine (f:\e12rtmhot\sources\dev\admin\src\libs\exsetup\hiddenw1.cxx:488) Error code 0XC103798A (31114): An internal component has failed.[12/07/2007 09:40:36] [2] Registry file name: 'D:\Program Files\Exchange Server\Setup\data\dav.ins' CRegistryManager:cProcessFile (f:\e12rtmhot\sources\dev\admin\src\udog\setupbase\tools\regmgr.cxx:125) Error code 0XC103798A (31114): An internal component has failed.[12/07/2007 09:40:36] [2] Filename = 'D:\Program Files\Exchange Server\Setup\data\dav' CBaseAtom:cRunRegistryFile (f:\e12rtmhot\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:1379) Error code 0XC103798A (31114): An internal component has failed.[12/07/2007 09:40:36] [2] Leaving CBaseAtom(Base DAV protocol):cRunRegistryFile[12/07/2007 09:40:36] [2] Filename = 'D:\Program Files\Exchange Server\Setup\data\dav' CBaseAtom:cAddRegistryKeys (f:\e12rtmhot\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:1249) Error code 0XC103798A (31114): An internal component has failed.[12/07/2007 09:40:36] [2] Leaving CBaseAtom(Base DAV protocol):cAddRegistryKeys[12/07/2007 09:40:36] [2] CBaseAtom:cAdd (f:\e12rtmhot\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:639) Error code 0XC103798A (31114): An internal component has failed.[12/07/2007 09:40:36] [2] Leaving CBaseAtom(Base DAV protocol):cAdd[12/07/2007 09:40:36] [2] Service = '' CBaseServiceAtom:cAdd (f:\e12rtmhot\sources\dev\admin\src\udog\setupbase\basecomp\basesvcatom.cxx:203) Error code 0XC103798A (31114): An internal component has failed.[12/07/2007 09:40:36] [2] Leaving CBaseServiceAtom(Base DAV protocol):cAdd[12/07/2007 09:40:36] [2] mode = 'Install' (61953) CBaseAtom:cSetup (f:\e12rtmhot\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:535) Error code 0XC103798A (31114): An internal component has failed.[12/07/2007 09:40:36] [2] ScSetupAtom (f:\e12rtmhot\sources\dev\admin\src\udog\exsetdata\exsetds.cxx:889) Error code 0XC103798A (31114): An internal component has failed.[12/07/2007 09:40:36] [2] Leaving ScSetupAtom[12/07/2007 09:40:36] [2] [ERROR] An error occurred. error code was 3238230410 message was An internal component has failed.."[12/07/2007 09:40:36] [1] The following 1 error(s) occurred during task execution:[12/07/2007 09:40:36] [1] 0. ErrorRecord: An error occurred. error code was 3238230410 message was An internal component has failed.."[12/07/2007 09:40:36] [1] 0. ErrorRecord: Microsoft.Exchange.Management.Deployment.ExsetdataException: An error occurred. error code was 3238230410 message was An internal component has failed.."[12/07/2007 09:40:36] [1] [ERROR] An error occurred. error code was 3238230410 message was An internal component has failed.."[12/07/2007 09:40:36] [1] Setup is halting task execution because of one or more errors in a critical task.[12/07/2007 09:40:36] [1] Finished executing component tasks.[12/07/2007 09:40:36] [1] Ending processing. Running regsvr32 /s exoledb.dll from the E:\Program Files\Exchange Server\Bin directory MANUALLY exit's without an error. BUT the install still wont go past this point.. It wopuld be nice to be able to install this 1,500 piece of software, before we take the Open Source route and move to Linux and Open Exchange...!
July 12th, 2007 11:54am

Forgot to mention. 1st install went the same way. So, removed Exchange 2007, Server would then not load in normal mode only Safe Mode. So, I rebuilt the server and the AD system. Tried loading JUST the Mailbox on the first install, this failed. Now I don't want to have to try and remove Exchange 2007 AGAIN, as (as stated) the server refused to work. So. Fix needed..? BTW. Server OS = Windows 2003 Server x64 R2 Services loaded AD DNS DHCP FILE Server PRINT Server IIS (Exchange wanted it) PowerShell All Hotfixes Latest Service Packs..
Free Windows Admin Tool Kit Click here and download it now
July 12th, 2007 12:06pm

Seems this was an issue in Exchange 2000 too, but the help for that mentioned 3 dll's in the common ODB system. http://support.microsoft.com/kb/296436/ One of which is not installed on this server with the new system Msdaipp.dll, So. Does the exoledb.dll need the same DLL's as exchange 2000 to register, if so where can one get the Msdaipp.dll from??? P.S. My mistake, I was using regsvr32 /s (silent) i've now set it up so that regsvr is allocated as the default .dll tool so I can simply click a dll and register it.. (saves alot of time )
July 12th, 2007 1:39pm

Microsoft Case Reference = SRQ070712600788 1 hr in. It COULD be a DLL issue. As the server used to have the 32 bit version installed, and then the 64 bit wnet over the top (not an upgrade, but leaving traces of the 32 bit system in place) MS state that this could be the issue. So, OS install number 4, this time doing a format too.
Free Windows Admin Tool Kit Click here and download it now
July 12th, 2007 3:04pm

I CAN CONFIRM, this IS a DLL issue caused by upgrading a 32 bit install to 64 bit. The 64 bit installation seems to see the 32 bit version of the OLE DB dll's and simply uses them (as they are the same version) BUT these dll's don't load under the x64 system. Therefore. DO NOT UPGRADE from 32 bit to 64 bit Server 2003. You must format the drive and do a full install, totally fresh.. i.e. Build a new server.. 2 weeks it's taken and ALOT of reading.. But should you follow this rule, you'll be fine.. After the OS Install, I simply did all the usual:- Installed DNS, DHCP, File and Print services, IIS and then AD(made it a PDC (yes I know, I'm and old NT / Linux person)) , installed all the required software (PowerShell, .NET v2 + Patches) and then Exchange 2007 (tipical set-up) Now i'm off to do the Unified Messaging smailbox, and see if I can get this to talk to our phone system.. Microsoft Phone Support ROCKS..!
July 12th, 2007 7:46pm

i was trying to installl a beta version myself got the same error This is a dll issue for sure Istarted to match the dll versions ---all version matched Used 838176 Found out that oledb.dll was causing the issue So i renamed both the file as indicated by the KB i expanded the file from the media and now the mailbox role is installed Hope this helps cheers
Free Windows Admin Tool Kit Click here and download it now
July 14th, 2007 11:49am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics