|
OK -> Unknown SMTP Issue/Transport Service not running -RESOLVED (26.Jun.2007 7:12:26 PM)
|
EDIT:
For future reference I will post my solution towards my problem here, so that anyone else that stubles into the same nightmare can have a swift and hopefully seccessful solution.
My initial problem was that the Microsoft Exchange Transport Service did not start after a ordinary reboot of my MS Exchange 2007 STD EDT Server, running on a Windows 2003 R2 64-bit STD.EDT. OS.
When starting the service manually, it would run for 5-10 seconds, and then shutdown again by itself. The event Id logged in the Application log was:
Event Type: Information
Event Source: MSExchangeTransport
Event Category: (6)
Event ID: 7001
Date: 27.06.2007
Time: 14:19:06
User: N/A
Computer: MX
Description:
The description for Event ID ( 7001 ) in Source ( MSExchangeTransport ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: 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 'TransportSettingsConfigLoader' failed. ---> Microsoft.Exchange.Transport.TransportComponentLoadFailedException: The Transport Settings configuration couldn't be found.
at Microsoft.Exchange.Transport.GlobalConfigurationBase`2.Start()
at Microsoft.Exchange.Transport.SequentialTransportComponent.<>c__DisplayClass2.<Load>b__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.<OnLoadChild>b__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.<Load>b__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().
Followed by Event ID's
Event Type: Information
Event Source: MSExchange TransportService
Event Category: ProcessManager
Event ID: 1022
Date: 27.06.2007
Time: 14:19:06
User: N/A
Computer: MX
Description:
Worker process with process ID 5332 requested the service to be stopped.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
And
Event Type: Information
Event Source: MSExchange TransportService
Event Category: ProcessManager
Event ID: 1002
Date: 27.06.2007
Time: 14:19:06
User: N/A
Computer: MX
Description:
The service is trying to stop.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Initially this did not make any sence at all, and I am now pretty sure that there can be possibly more than one reason for this issue to occour, but in my case here's what was wrong.
Using the Powershell I ran the command get-TransportConfig.
This resulted in the following errormsg's:
[PS] C:\>get-transportconfig
ClearCategories : True
GenerateCopyOfDSNFor : {5.4.8, 5.4.6, 5.4.4, 5.2.4, 5.2.0, 5.1.4}
InternalSMTPServers : {}
JournalingReportNdrTo : <>
MaxDumpsterSizePerStorageGroup : 600MB
MaxDumpsterTime : 7.00:00:00
MaxReceiveSize : unlimited
MaxRecipientEnvelopeLimit : unlimited
MaxSendSize : unlimited
TLSReceiveDomainSecureList : {}
TLSSendDomainSecureList : {}
VerifySecureSubmitEnabled : False
VoicemailJournalingEnabled : True
Xexch50Enabled : True
WARNING: Object Transport Settings has been corrupted and it is in an
inconsistent state. The following validation errors have been encountered:
WARNING: MaxSendSize(50GB) is out of range: [0KB,2097151KB].
WARNING: MaxReceiveSize(50GB) is out of range: [0KB,2097151KB].
As you can see, theese values is quite enormous, and I asure you that I have not set theese myself. Initially i had Max Send and MaxReceive set to 30MB for my organization, and nothing has been changed to couse this value to change, other than a reboot after a Windows Update.
So, how to resolve the issue?
i have spent several hours on the phone with a very nice representative of Microsoft Support, and we have tried so many things that you wouldnt believe it.
Short summary of nonworking solution for our case:
We followed: http://technet.microsoft.com/en-us/library/aa998836.aspx to configure the send and receive connectors back to 20Mb
Set-SendConnector "Connection to Contoso.com" -MaxMessageSize 20MB
Did the same for the receive connector(s)
Checked with: Get-receiveconnector | fl *size
Then we still had the same error when typing in Exchange management Shell: Get-TransportConfig
I tought the value had to come from a higher level in the AD structure.
So while waiting for the elevation technitian to call me back I went to ADSIEdit and changed the following values:
1.…Services\Microsoft Exchange\CN=Organization\CN=Transport Settings->properties->Attribute:SubmissionContentLength
This value is not set by default, I changed it to 20MB (20480).
2….services\Microsoft Exchange\CN=Organization->properties->Attribute:DelivContLength
This value is not set by default, I changed it to 20MB (20480)
And what do you know.
I had a running Transport service again. [:D]
Now how this value og 50GB came into AD, I dont know.
But if you should encounter similar problems, I hope this might resolve it for you.
My thanks go out to Mr. Dronkers @ MS for his valuable support in resolving this issue.
Regards
OK
|
|
|
|