• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 582
  • Last Modified:

Install Exchange 2003 Server Error - Urgent!

Hi experts! Please Helpe-me! I need to put working my New E-mail Server but I can´t!

I´m installing a new Exchange Server 2003 in a Windows 2003 Server Std with SP2.

The problem is:
About 80% through the installation in the "Microsoft Exchange Messaging and Collaboration Services" phase, I received an error message that stated the following:
"Setup failed while installing sub-component Base DAV protocol with error code 0xC103798A (please consult the installation logs for a detailed description). You may cancel the installation or try the failed setup again."  The only options were to "Retry" or "Cancel."
If i continue the installation after click "Cancel", i have troubles with the Information Store.
I´ve been searching in MS TechNet, Foruns and also in Experts-exchanges similar cases, but  couldnt find a soluction to solve this problem.

Here is the "Exchange Server Setup Progress.log"<, which has been trimmed by -red>:
-------------------------------------------------------------------------------------------------------
[17:15:40]  ************** Beginning Setup run **************
[17:15:40] Starting Exchange 6944 setup on Windows 5.2.3790.Service Pack 2 at 17:15:40 03/29/2007
*****
      regsvr32 /s exoledb.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.
[17:47:46]  CInsParser::ScProcessLine (f:\titanium\admin\src\libs\exsetup\hiddenw1.cxx:1225)
           Error code 0XC103798A (31114): An internal component has failed.
[17:47:46] Processing file 'e:\setup\i386\exchange\dav.ins', at or near line 13 (CreateProcess:D:\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.
[17:47:46] Registry file name: 'e:\setup\i386\exchange\dav.ins' CRegistryManager::ScProcessFile (f:\titanium\admin\src\udog\setupbase\tools\regmgr.cxx:125)
           Error code 0XC103798A (31114): An internal component has failed.
[17:47:46] Filename = 'e:\setup\i386\exchange\dav' CBaseAtom::ScAddRegistryKeys (f:\titanium\admin\src\udog\setupbase\basecomp\baseatom.cxx:1408)
           Error code 0XC103798A (31114): An internal component has failed.
[17:47:46]  CBaseAtom::ScForklift (f:\titanium\admin\src\udog\setupbase\basecomp\baseatom.cxx:1004)
           Error code 0XC103798A (31114): An internal component has failed.
[17:47:46] Service = '' CBaseServiceAtom::ScForklift (f:\titanium\admin\src\udog\setupbase\basecomp\basesvcatom.cxx:290)
           Error code 0XC103798A (31114): An internal component has failed.
[17:47:46] mode = 'Disaster Recovery' (61959) CBaseAtom::ScSetup (f:\titanium\admin\src\udog\setupbase\basecomp\baseatom.cxx:842)
           Error code 0XC103798A (31114): An internal component has failed.
--------------------------------------------------------------------------------------------------
Could you give-me any help?
0
flavio2000
Asked:
flavio2000
  • 14
  • 9
1 Solution
 
redseatechnologiesCommented:
Have you seen this KB Article?

http://support.microsoft.com/kb/838176

-red
0
 
flavio2000Author Commented:
Yes, i executed this KB, including i ran the MDAC 2.8, but didn´t work.

-Flavio
0
 
redseatechnologiesCommented:
Can you manually run this? >> regsvr32 /s exoledb.dll

you may have to run that as regsvr32 /s d:\whereverthatfileis\exoledb.dll

-red
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
flavio2000Author Commented:
Yes, i executed at this time, i didn´t get an error message but didn´t work yet.

- flavio
0
 
redseatechnologiesCommented:
try to reinstall exchange again
0
 
flavio2000Author Commented:
I tried so many time...
now,  at this time, i´m installing using  /disasterRecovery parameter, but give me the same error.

-flavio
0
 
redseatechnologiesCommented:
This is a new exchange 2003 server, on a new windows 2003 server, right?

Do you have any other exchange 2003 servers in the organization?  Exchange 2000?

I would be inclined to just format that box and start again...

-red
0
 
flavio2000Author Commented:
Yes, i have another Exchange Server 2000 in my network.
But I formated my server yesterday and installed Windows 2003 Server, the SP2.
After that, I started the Exchange Server 2003 installation, so the error occurred.

I can format it again, but is it realy necessary?

- Flavio
0
 
redseatechnologiesCommented:
Something has gone wrong there, whether it is something you have done or something else that was installed.

Either way, on new builds, if they don't play the game they get wiped.
0
 
flavio2000Author Commented:
Ok. I´ll format it again!

Just a question.
In the actual instalation, in the hard disk (160 GB), i separeted in 2 partions. The ideia is install Windows and SPs in partition "C", and install applications like Exchange Server 2003 in partition "D".
Is it possible, or maybe this is causing troubles in my installation?

-Flavio
0
 
redseatechnologiesCommented:
That should not cause any problems at all, and is how I normall do it
0
 
flavio2000Author Commented:
Ok, i´ll format now.
0
 
flavio2000Author Commented:
Red,

Please, how are the steps that you usually run?

-Install Windows 2003 Server
-Install Windows Update
-Add the server in an AD
-Install Exchange Server 2003 (running before /forestPrep and DomainPrep)

Are correct these step?

-Flavio
0
 
redseatechnologiesCommented:
looks ok, assuming you have already prepped the domain for WINDOWS 2003, and you have to prep it for exchange 2003 before you actually install it (only once though)
0
 
flavio2000Author Commented:
Ok..
I installed Windows 2003 Server Std Edition;
I ran Windows UpDate :
Service pack 2 32-bit x86
Windows Malicious SW Removal Tool (KB890830)  
0
 
flavio2000Author Commented:
Sorry..

I installed Windows 2003 Server Std Edition;
I ran Windows UpDate :
- Service pack 2 32-bit x86
- Windows Malicious SW Removal Tool (KB890830)
- Windows Internet Explorer For Windows Server 2003
- Update for Windows Service Pack 2 (KB931836)
Using "Configure Your Server Wizard", I installed Domain Controller (AD) selecting “Additional DC for an existing domain”
Everything is OK, without errors at this time. Now I´ll start to install MS Exchange Server 2003...
Good Lock to me!
0
 
flavio2000Author Commented:
:) Locked I am!
Good Luck to me!
0
 
flavio2000Author Commented:
Wonderful!!!
Belive or not but the installation was successfully!

To me, the problem was the right sequence to execute the steps. In the tries before, i installed the Windows 2003 server, put it in the domain, add it like a DC, ran the Updates and after that i installed the Exchange Server 2003. The point is, after to run the Update, i had trobles with the COM+ and Network Connections Services. To solve this troubles, i found a procedure in KB313222, but i thougt that was normal had this troubles.
Today, i executed these sequences and worked fine:
1)Install Windows Server 2003 Std Edition …OK
2)Restart server…OK
3)Run Windows UpDate (service pack 2 32-bit x86) …OK
4)Restart server…OK
5)Run again Windows UpDates (03 actualizations found):
   Windows Malicious SW Removal Tool (KB890830) …OK
   Windows Internet Explorer For Windows Server 2003…OK
   Update for Windows Service Pack 2 (KB931836) …OK
6)Restart server…OK
7)Change the Server name for the appropriated name before insert it in a DC…OK
8)Restart server…OK
9)Using Configure Your Server Wizard, install Domain Controller (AD).Select “Additional DC for an existing domain” (user administrator) …OK
10)Restart server…OK
11)Install MS Exchange Server 2003, select Exchange Deployment Tools, Deploy the first Exchange 2003 Server, New Exchange 2003 installation
  a)Follow All steps (1 to 8), don’t skip any.
  b)In step 6, when I ran ForestPrep, I received this message: Exchange Server 2003 has a Known compatibility issue with this version of Windows. For more information, refer to http:go.microsoft.com/fwlink/?LinkId=37488.
  c)I ignore this message an clicked “Continue”
  d)In step 8, Run Setup Now, in Component Selection, when I change the Action to Typical, I received this message: The component “Microsoft Exchange Messaging and collaborations Services” cannot be assigned the action Install because: A Server object for this server (“MYSERVERNAME”) already exists in the administrative Group “First Administrative Group”. If you are attempting to recover this server please run setup with the DisasterRecovery switch otherwise you must first remove this server object from the Active Directory by using the Exchange System Manager. (this error occurred because I used the same server name that I was using before to had format the machine, and I forgot to check this before to start the installation).
  e)I removed this server object from the Active Directory by using the Exchange System Manager like suggested and restarted the server.
  f)I started the installation again by step 8 and the message didn’t appear.

The installation was successfully!

Thanks Red for stimulated me to format the server again! Thank you so much.
0
 
flavio2000Author Commented:
Now i have a final doubts...

At this time i have myold exchange server named EXCHSERVE1, and the new server named EXCHSERVE2.
To avoid problems with the clients... about 100 clients, i would like to "rename" the EXCHSERVE2 to EXCHSERVE1, and change the IP address too.

Is it possible, without troubles in my AD structure?
0
 
flavio2000Author Commented:
I opened a new ASK to the doubts about rename Exchange Servers.

tks!
0
 
redseatechnologiesCommented:
Renaming Exchange Servers is not possible - you will need to uninstall exchange, rename it and then reinstall exchange.

Is the old Exchange server online?  If so, when you move mailboxes to this new server, the clients will not need any more configuration.

Sorry I wasn't around to answer some of your latest questions, we are in opposite time zones

-red
0
 
flavio2000Author Commented:
Red, don´t worry! After i posted this msg, i discovered that the AD points where the mail box is.

Now, is everything working perfectly.

Thanks for your replay... and your help yesterday!

-flavio
0
 
redseatechnologiesCommented:
You are most welcome.

-red
0

Featured Post

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

  • 14
  • 9
Tackle projects and never again get stuck behind a technical roadblock.
Join Now