RE: Exchange 2000 ent management setup.

Jude,

1. I did find a few related errors on the web, but they are refering to a
different .dll file and none of them is a sollution to my issue. Such as

http://support.microsoft.com/kb/281383/en-us
http://support.microsoft.com/kb/296436/en-us
http://www.exchange2exchange.org/group-3294-1901.html

2. No, I don't have cluster installed in our network.

3. No, I'm not installing the Exchange Manager on the existing exchange
server. I'm just trying to install the management on a new Windows 2000
member server.

4. After I install the exchange manangement successfully (?) I will move the
FSMO roles from exisitng AD to this new server. The new server will replace
a 4 year old server.

Sam


"jude" wrote:

Sam,

I checked and there are several article that are referring to this error
message.

Do you have a cluster installed at this location?

When you install the Exchange snap-in are you doing this on the exchange
server it self?

The other question I have is why do you want to move the FSMO roles to
another server? Preformance reasons, server crashed?


"Sam" wrote:

Everytime I try to install the Exchange System Management on a new Windows
2000 Member server I get an error when it's trying to configure reistry
entries for Exchange Snap-ins.

Current Network Configuration:
# 1 Server - Windows 2000 Server Sp4 Active Directory Domain
# 2 Server - Windows 2000 Server Sp4 w/ Microsoft Exchange 2000 Enterprise Sp3
Process:
#3 Server – New HP ML350 Server and New install of Windows 2000 Server Sp4
w/ all MS Updates

(Login as Domain & Exchange Administrator)
1.Added to the server to the domain as a member.
2.Installed IIS and NNTP
3.Install Microsoft Exchange System Management. During the last process of
the
Install “Configuring registry entries for Exchange System Management
Snap-ins”. I
received an error

Error:
Microsoft Exchange 2000 Installation Wizard

Setup failed while installing sub-component Exchange System Management
Snap-ins with error code 0xC103798A (please contact the installation logs for
a detailed description).You may cancel the installation or try the failed
step again.

Error Installation Log:
regsvr32.exe -s exadmin.dll
failed, returning error code 3 (The system cannot find the path specified.).
ScCreateProcess (K:\admin\src\libs\exsetup\hiddenw1.cxx:1763)
Error code 0XC103798A (31114): An internal component has failed.

Note:
Plan to Move FSMO roles from AD server #1 to AD server #3 and Setup an
Exchange 2003 Ent. Server #4 and migrate from existing Exchange 2K server #2

Thank You,
Sam


.

Relevant Pages

  • Re: REDIR.ASP file in use - access denied when installing Exchange 2003 SP1
    ... To resolve the problem i gave the 'Server Operators' group Full Control ... As soon as this was done the install worked fine. ... > Installation Instructions for Service Pack 1 for Windows Small Business ... What's the exact error message when you are installing the Exchange ...
    (microsoft.public.windows.server.sbs)
  • Re: Blackberry and MS Exchange Administrator
    ... I understand that you want to install the Exchange ... System Manager components onto a server other than the SBS box. ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange 2003 and NT4 trusted domain
    ... > If you run Exchange 2003, you will need to install AD on at least on ... > use the server for Exchange. ... There would be no need to have a server at the remote ... There is a Linux box at each site ...
    (microsoft.public.exchange.connectivity)
  • Re: Exchange 2003 and NT4 trusted domain
    ... > If you run Exchange 2003, you will need to install AD on at least on ... > use the server for Exchange. ... There would be no need to have a server at the remote ... There is a Linux box at each site ...
    (microsoft.public.exchange.setup)
  • Re: Exchange 2003 and NT4 trusted domain
    ... > If you run Exchange 2003, you will need to install AD on at least on ... > use the server for Exchange. ... There would be no need to have a server at the remote ... There is a Linux box at each site ...
    (microsoft.public.exchange.admin)