Re: Routing engine failed to initialize
- From: "Ed Crowley [MVP]" <curspice@xxxxxxxxxxxxxx>
- Date: Sat, 11 Mar 2006 12:37:00 -0800
#2 is:
2- Verify that if any Exchange Server Site was removed, it no longer shows
up in Active Directory.
You say it shows up. That is a problem.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"
"KUMAIL" <KUMAIL@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3A47626D-2F3E-4828-9A30-63626A004C0E@xxxxxxxxxxxxxxxx
dear friend,
I believe there is some misunderstanding regarding number (2) :)
In my last post I said: "2- Using the ADSIedit tool, I can see that the
server is Listed there."
Yes, I CAN see the server LISTED :) it is not removed :)
thanks in advance for any help :)
"Ed Crowley [MVP]" wrote:
1. I would agree.
2. Then this is your problem, IF the Exchange server was removed.
3. This appears not to apply since #2 appears to be your problem.
Search the KB for "manually remove exchange" all words. One of the
articles
should help you remove this ghost server from your organization.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"
"KUMAIL" <KUMAIL@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:122F1C28-72B8-43D7-B2C6-5B994028FBBF@xxxxxxxxxxxxxxxx
thanks for your reply Ed,
1- I have checked the recipient policies, there is only one policy
(Default
policy) and its periority is set to "Low". So, I guess this shouldn't
be
the
problem..right ?
2- Using the ADSIedit tool, I can see that the server is Listed there.
3- I couldn't figure out where to look to check for the various values
on
the Network Address attribute for the Server object. would you please
point
them out for me.
thanks so much for your help..
"Ed Crowley [MVP]" wrote:
1. Look at the list of recipient policies, and you'll see the
priority
listed.
2. Use ADSI Edit and connect to the Configuration node. Then drill
down
into Services > Microsoft Exchange Server and so on until you get to
the
Servers container, and see if it's listed there.
3. Numbers 2 and 3 are exclusive. Number 3 applies only if the
condition
stated for number 2 are not met and therefore it doesn't apply.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"
"KUMAIL" <KUMAIL@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C8ACECB6-312E-4C1F-B332-F39465EBBC69@xxxxxxxxxxxxxxxx
I am running Exchange 2003 SP2.
The Information store fails to start and I am getting the following
error
in
the event viewer:
-----------------------------------------------------------
Error 0xc0040391 calling StrInitialize in REAPI.DLL.
Source: MSExchangeIS
Event ID: 9538
Routing engine failed to initialize and as a result the store would
not
start.
---------------------------------------------------------------------------
and there is some more info about the error I got from microsoft:
Explanation:
This event can be accompanied by an inability to start the Microsoft
Exchange Information Store service. The actual error code in the
description
section could vary, depending on the underlying cause of the
problem.
This problem occurs because a server name that is not valid is
passed
into
the routing engine. When the Microsoft Exchange Information Store
service
starts, it makes a call to the routing engine (through Reapi.dll) to
build
the routing table. If a server name that is not valid is passed into
Reapi.dll, the service does not start, and this and several related
events
are logged in the application log.
There could be varied causes for this event, but the following are
the
most
common:
Multiple recipient policies are displayed with the same priority.
A Microsoft Exchange Server 5.5 site was removed from the
organization,
but
it is still partially listed in the Exchange System Manager.
Some values are missing on the Server object's Network Address
attribute
in
Active Directory.
The Exchange Domain Servers group does not have the appropriate
permissions
in Active Directory.
User Action
1- Check to ensure that the recipient policies do not all have the
same
priority.
2- Verify that if any Exchange Server Site was removed, it no longer
shows
up in Active Directory.
3- Verify that the various values on the Network Address attribute
for
the
Server object are present in Active Directory. Compare with a
working
server,
if possible.
my questions are regarding this last paragraph directly above this
line,
(the User Action paragraph)
1- How do I check to ensure that the recipient policies do not all
have
the
same priority ?
2- How do I Verify that if any Exchange Server Site was removed, it
no
longer shows up in Active Directory ??
3- How do I Verify that the various values on the Network Address
attribute
for the Server object are present in Active Directory ??
thanks for any help in advance..
.
- Follow-Ups:
- Re: Routing engine failed to initialize
- From: KUMAIL
- Re: Routing engine failed to initialize
- References:
- Routing engine failed to initialize
- From: KUMAIL
- Re: Routing engine failed to initialize
- From: Ed Crowley [MVP]
- Re: Routing engine failed to initialize
- From: KUMAIL
- Re: Routing engine failed to initialize
- From: Ed Crowley [MVP]
- Re: Routing engine failed to initialize
- From: KUMAIL
- Routing engine failed to initialize
- Prev by Date: Re: Public Folder Age limit not taking effect
- Next by Date: Re: Exchange 2003 mail slow from SQL, ASP, and ASP.net - fine otherwise
- Previous by thread: Re: Routing engine failed to initialize
- Next by thread: Re: Routing engine failed to initialize
- Index(es):