SBS Exchange 2007 can't send/recv
Hi folks. Our Exchange is down. I've been troubleshooting since yesterday. Its SBS 2008 running Exchange 2007 on one server. All Exchange roles and DC/GC are on the same physical box. Currently, the Transport service starts and then stops. I am running a local nt backup to try and have a recovery point plus free or clear any transaction logs. A little background: Users started complaining yesterday about email access - they could send out, and send/recv internally, but no incoming mail was getting through. I tried to use telnet from a remote computer to test smtp on the server. When I connected via telnet, and did the helo, mail from:drkuhl...@yahoo.com I was getting the insufficient resources 4.3.2 message I did a shutdown and restart on the server No luck. So I started googling and found some blurbs about modifying the edgetransport.exe.config file and setting EnableResourceMonitoring value=false to see if things got better while working to free up resources and stop what I think is a back pressure situation. Since that didn't help, I put the backup copy of the edgetransport.exe.config file back in place. Now getting connection refused with the transport service not being able to stay started. And we can't send/recv internally or externally now. I don't know if the service issues is currently because of the backup running but wanted to get some feelers out to try and work on later after it finishes if I still can't get the service to run. The event attached below seems to indicate that a file is locked or in use, maybe because of the backup running? Any help or pointers would be appreciated. Thanks Don K Here is a snip of one event relating to the transport service failure. Log Name: Application Source: MSExchangeTransport Date: 6/7/2012 2:36:17 PM Event ID: 7001 Task Category: Components Level: Information Keywords: Classic User: N/A Computer: SMISBS010.corp.abtrex.com Description: The service will be stopped. Reason: Microsoft.Exchange.Transport.TransportComponentLoadFailedException: Loading of component 'AD Configuration Readers' failed. --- Microsoft.Exchange.Transport.TransportComponentLoadFailedException: The transport component 'SequentialTransportComponent' couldn't be loaded successfully. --- Microsoft.Exchange.Transport.TransportComponentLoadFailedException: Loading of component 'Database' failed. --- Microsoft.Exchange.Transport.TransportComponentLoadFailedException: The following database is in use: Queuing Database. --- Microsoft.Exchange.Isam.IsamFileAccessDeniedException: Cannot access file, the file is locked or in use (-1032) at Microsoft.Exchange.Isam.?A0xf73de38c.HandleError(Int32 err) at Microsoft.Exchange.Isam.Interop.MJetInit(MJET_INSTANCE instance) at Microsoft.Exchange.Transport.Storage.DataSource.InitInstance() at Microsoft.Exchange.Transport.Storage.DataSource.OpenDatabase() at Microsoft.Exchange.Transport.Storage.Messaging.Database.AttachInternal(String path, Boolean wipe) at Microsoft.Exchange.Transport.Storage.Messaging.Database.Attach() --- End of inner exception stack trace --- at Microsoft.Exchange.Transport.Storage.Messaging.Database.Attach() at Microsoft.Exchange.Transport.SequentialTransportComponent.c__DisplayClass2.Loadb__0() at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.RunADOperation(ADOperation adOperation, Int32 retryCount) at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.TryRunADOperation(ADOperation adOperation, Int32 retryCount) at Microsoft.Exchange.Transport.SequentialTransportComponent.Load() --- End of inner exception stack trace --- at Microsoft.Exchange.Transport.SequentialTransportComponent.Load() at Microsoft.Exchange.Transport.ParallelTransportComponent.c__DisplayClass2.OnLoadChildb__0() at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.RunADOperation(ADOperation adOperation, Int32 retryCount) at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.TryRunADOperation(ADOperation adOperation, Int32 retryCount) at Microsoft.Exchange.Transport.ParallelTransportComponent.OnLoadChild(Object state) --- End of inner exception stack trace --- at Microsoft.Exchange.Transport.ParallelTransportComponent.Load() at Microsoft.Exchange.Transport.SequentialTransportComponent.c__DisplayClass2.Loadb__0() at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.RunADOperation(ADOperation adOperation, Int32 retryCount) at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.TryRunADOperation(ADOperation adOperation, Int32 retryCount) at Microsoft.Exchange.Transport.SequentialTransportComponent.Load() --- End of inner exception stack trace --- at Microsoft.Exchange.Transport.SequentialTransportComponent.Load() at Microsoft.Exchange.Transport.Components.Activate() Event Xml: Event xmlns=http://schemas.microsoft.com/win/2004/08/events/event;
Re: SBS Exchange 2007 can't send/recv
hi Don Have you tried running the ExBPA? Steve On Thu, Jun 7, 2012 at 3:15 PM, Don Kuhlman drkuhl...@yahoo.com wrote: Hi folks. Our Exchange is down. I've been troubleshooting since yesterday. Its SBS 2008 running Exchange 2007 on one server. All Exchange roles and DC/GC are on the same physical box. Currently, the Transport service starts and then stops. I am running a local nt backup to try and have a recovery point plus free or clear any transaction logs. A little background: Users started complaining yesterday about email access - they could send out, and send/recv internally, but no incoming mail was getting through. I tried to use telnet from a remote computer to test smtp on the server. When I connected via telnet, and did the helo, mail from:drkuhl...@yahoo.com I was getting the insufficient resources 4.3.2 message I did a shutdown and restart on the server No luck. So I started googling and found some blurbs about modifying the edgetransport.exe.config file and setting EnableResourceMonitoring value=false to see if things got better while working to free up resources and stop what I think is a back pressure situation. Since that didn't help, I put the backup copy of the edgetransport.exe.config file back in place. Now getting connection refused with the transport service not being able to stay started. And we can't send/recv internally or externally now. I don't know if the service issues is currently because of the backup running but wanted to get some feelers out to try and work on later after it finishes if I still can't get the service to run. The event attached below seems to indicate that a file is locked or in use, maybe because of the backup running? Any help or pointers would be appreciated. Thanks Don K Here is a snip of one event relating to the transport service failure. Log Name: Application Source:MSExchangeTransport Date: 6/7/2012 2:36:17 PM Event ID: 7001 Task Category: Components Level: Information Keywords: Classic User: N/A Computer: SMISBS010.corp.abtrex.com Description: The service will be stopped. Reason: Microsoft.Exchange.Transport.TransportComponentLoadFailedException: Loading of component 'AD Configuration Readers' failed. --- Microsoft.Exchange.Transport.TransportComponentLoadFailedException: The transport component 'SequentialTransportComponent' couldn't be loaded successfully. --- Microsoft.Exchange.Transport.TransportComponentLoadFailedException: Loading of component 'Database' failed. --- Microsoft.Exchange.Transport.TransportComponentLoadFailedException: The following database is in use: Queuing Database. --- Microsoft.Exchange.Isam.IsamFileAccessDeniedException: Cannot access file, the file is locked or in use (-1032) at Microsoft.Exchange.Isam.?A0xf73de38c.HandleError(Int32 err) at Microsoft.Exchange.Isam.Interop.MJetInit(MJET_INSTANCE instance) at Microsoft.Exchange.Transport.Storage.DataSource.InitInstance() at Microsoft.Exchange.Transport.Storage.DataSource.OpenDatabase() at Microsoft.Exchange.Transport.Storage.Messaging.Database.AttachInternal(String path, Boolean wipe) at Microsoft.Exchange.Transport.Storage.Messaging.Database.Attach() --- End of inner exception stack trace --- at Microsoft.Exchange.Transport.Storage.Messaging.Database.Attach() at Microsoft.Exchange.Transport.SequentialTransportComponent.c__DisplayClass2.Loadb__0() at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.RunADOperation(ADOperation adOperation, Int32 retryCount) at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.TryRunADOperation(ADOperation adOperation, Int32 retryCount) at Microsoft.Exchange.Transport.SequentialTransportComponent.Load() --- End of inner exception stack trace --- at Microsoft.Exchange.Transport.SequentialTransportComponent.Load() at Microsoft.Exchange.Transport.ParallelTransportComponent.c__DisplayClass2.OnLoadChildb__0() at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.RunADOperation(ADOperation adOperation, Int32 retryCount) at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.TryRunADOperation(ADOperation adOperation, Int32 retryCount) at Microsoft.Exchange.Transport.ParallelTransportComponent.OnLoadChild(Object state) --- End of inner exception stack trace --- at Microsoft.Exchange.Transport.ParallelTransportComponent.Load() at Microsoft.Exchange.Transport.SequentialTransportComponent.c__DisplayClass2.Loadb__0() at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.RunADOperation(ADOperation adOperation, Int32 retryCount) at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.TryRunADOperation(ADOperation adOperation, Int32 retryCount) at Microsoft.Exchange.Transport.SequentialTransportComponent.Load() --- End of inner exception stack trace --- at
