Hi everybody, I'm trying to evaluate Exchange 2007 for my company. Unfortunately I've run into problems right after installation. Let me describe environment first. My test lab setup is (both servers are virtual machines): - one W2K3 R2 Ent SP1 server with Active Directory domain - clean install, no GPOs or other settings. - one W2K3 R2 Ent SP2 server dedicated to Exchange - also clean install. Mailbox role and Hub transport roles installed. - there's no problem with any kind of firewalls, I've opened all ports between these two servers. Installation day stituation: I installed all required packages (i've downloaded what setup advised). Everything in setup seemed to be OK, except warning about no Client Access server available (which is indeed not available). Installation was successfull. Everything was fine and working. So i started to check what this product is capable of and how it works. During this i created one send connector, i run few of tools (BPA, perf mon) and i installed one windows XP VM to provide me a Outlook client. I sent from there one mail from this client (loopback test, so i sent that email to the same account it was send from). Nothing else. Next day situation: I have full event logs of warnings / errors. MS Exchange Transport service is not started and it can't start, just fills event logs with few errors. Now, I've spent like 6 hours to find some answer / fix to my problems but everything i found wasn't exactly for my situation and/or there was nothing to do for me, because suggested settings were already there. So here are events which started to pop up in event log: Event Type: Warning Event Source: MSExchange Assistants Event Category: Assistants Event ID: 9039 Date: 9/15/2009 Time: 5:35:52 PM User: N/A Computer: BCPH-EXCH-WT1 Description: Service MSExchangeMailSubmission. Unable to process anything for over 30 minutes. Diagnostic info: Governor: Governor for DatabaseManagerEvent, Last run time: 9/15/2009 5:04:37 PM, Next retry interval: 00:05:00. Current exception: Microsoft.Exchange.Assistants.TransientServerException at Microsoft.Exchange.Assistants.Util.CatchMeIfYouCan(CatchMe function) at Microsoft.Exchange.Assistants.Base.CatchMeIfYouCan(CatchMe function) at Microsoft.Exchange.Assistants.EventDispatcherPrivate.DangerousProcessItem(EmergencyKit kit, InterestingEvent interestingEvent) For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type: Warning Event Source: MSExchangeSA Event Category: OAL Generator Event ID: 9390 Date: 9/15/2009 Time: 5:12:29 PM User: N/A Computer: BCPH-EXCH-WT1 Description: OALGen failed to find the OAB version 4 manifest file '\\BCPH-EXCH-WT1\ExchangeOAB\c266907c-7a25-4197-b3ed-6b365a1fd960\oab.xml'. This is normal if it is the first time this offline address list has been published to the file system. Check other logged events to see if this is a serious error. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Later on, event log is filled just with these events: Event Type: Warning Event Source: MSExchangeMailSubmission Event Category: MSExchangeMailSubmission Event ID: 1009 Date: 9/15/2009 Time: 5:55:52 PM User: N/A Computer: BCPH-EXCH-WT1 Description: The Microsoft Exchange Mail Submission Service is currently unable to contact any Hub Transport servers in the local Active Directory site. The servers may be too busy to accept new connections at this time. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type: Error Event Source: MSExchange Common Event Category: General Event ID: 4999 Date: 9/16/2009 Time: 9:39:15 AM User: N/A Computer: BCPH-EXCH-WT1 Description: Watson report about to be sent to dw20.exe for process id: 1972, with parameters: E12, c-RTL-AMD64, 08.01.0240.006, edgetransport, M.E.E.Internal, M.E.D.T.I.M.FactoryTable.CreateAgentFactory, System.ArgumentNullException, 277a, 08.01.0240.005. ErrorReportingEnabled: False For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type: Error Event Source: MSExchange TransportService Event Category: ProcessManager Event ID: 1016 Date: 9/16/2009 Time: 9:39:22 AM User: N/A Computer: BCPH-EXCH-WT1 Description: The worker process crashes continuously on startup: D:\#Exchange\Bin\edgetransport.exe. The service will be stopped. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. - plus warnings from before. Later on i restarted server, everything seemed to be ok for 20-30 minutes, then it all started to happening again. Just few more event popped additionaly. Event Type: Warning Event Source: MSExchange Assistants Event Category: Assistants Event ID: 9039 Date: 9/16/2009 Time: 10:41:17 AM User: N/A Computer: BCPH-EXCH-WT1 Description: Service MSExchangeMailSubmission. Unable to process anything for over 30 minutes. Diagnostic info: Governor: Governor for DatabaseManagerEvent, Last run time: 9/16/2009 10:10:07 AM, Next retry interval: 00:05:00. Current exception: Microsoft.Exchange.Assistants.TransientServerException at Microsoft.Exchange.Assistants.Util.CatchMeIfYouCan(CatchMe function) at Microsoft.Exchange.Assistants.Base.CatchMeIfYouCan(CatchMe function) at Microsoft.Exchange.Assistants.EventDispatcherPrivate.DangerousProcessItem(EmergencyKit kit, InterestingEvent interestingEvent) For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type: Error Event Source: MSExchangeTransport Event Category: Storage Event ID: 17002 Date: 9/16/2009 Time: 2:22:47 PM User: N/A Computer: BCPH-EXCH-WT1 Description: The non-nullable column Version on the Extensible Storage Engine (ESE) table VersionTable from database D:\#Exchange\TransportRoles\data\Queue\mail.que is part of the database schema but cannot be found in the actual database table. The module containing the database schema may have been updated and could be attempting to open an older database. The old database must be removed before starting the Exchange Server Transport service in Microsoft Exchange Server 2007. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. These are all I can see in event log. I still can't start the service and now I have no idea what might happen during the night. Does anyone have idea what is wrong with this Exchange i have here? Best regards, Petr

Hi,Please try torename the Queue folder under c:\program files\Microsoft\Exchange server\TransportRoles\data to Queue.bak, then start Microsoft Exchange Transport service to check this issue.ThanksAllen

Thats A good option , or see what is the size of the queue.bak database, If u feel this is more than Normal then defragment it and check . Renaming the queue will also do for u .

Sumanthk, Can you please help me understand whatdefragmenting the renamed queue have to do with anything?