Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
Exchange
2000.active.directory
2000.admin
2000.announcements
2000.app.conversion
2000.applications
2000.clients
2000.clustering
2000.connectivity
2000.development
2000.documentation
2000.general
2000.information.store
2000.interop
2000.kms
2000.misc
2000.protocols
2000.realtime.collabo.
2000.setup
2000.transport
2000.win2000
admin
application.conversion
applications
clients
clustering
connectivity
design
development
misc
mobility
setup
tools
  
 
date: Fri, 10 Mar 2006 14:34:23 -0800,    group: microsoft.public.exchange2000.information.store        back       


Routing engine failed to initialize and as a result the store woul   
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..
date: Fri, 10 Mar 2006 14:34:23 -0800   author:   KUMAIL

RE: Routing engine failed to initialize and as a result the store woul   
I forgot to mention that I am running Exchange 2003 SP2

"KUMAIL" wrote:

> 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.. 
>
date: Fri, 10 Mar 2006 14:37:21 -0800   author:   KUMAIL

RE: HELP! WE HAVE THE SAME ISSUE! DID YOU RESOLVE?   
Were you able to resolve this, and if so, how?  The same issue you had 
occurred on our Exchange server this morning and we are still fighting it.  
Seems to be some sort of SMTP error??  Any info would be VERY much 
appreciated. (We are running Exchange 2003 SP2 also)
date: Wed, 29 Mar 2006 14:11:38 -0600   author:   Amy N Downey

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us