[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 479
  • Last Modified:

Exhange Transport Service not starting

I cant seem to get my transport service running. It had been running fine and then stopped on me. I was using the local account when it stopped. So i switched to the NT AUTHORITY account and it started working for a few hours. Now neither account works. The only error i see is the event ID 1016  the worker process craches continously on startup. The only change was that we stood up another exchange server and added the transport role as well.

Thanks
0
mendozar
Asked:
mendozar
  • 5
  • 3
1 Solution
 
jayasankerCommented:
have you disabled ipv6 in the tcp/ip properties??
0
 
mendozarAuthor Commented:
thanks
0
 
mendozarAuthor Commented:
yes i dont have that running on my server..............
0
[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

 
mendozarAuthor Commented:
i  have 64 bit 2003 Windows server wtih Exchange 2007 SVC Pack 3
0
 
jayasankerCommented:
Hi
Download exchange best practice analyzer (http://www.microsoft.com/downloads/en/details.aspx?FamilyID=dbab201f-4bee-4943-ac22-e2ddbd258df3&displaylang=en) and look for any errors

when did this error start??
Thx
0
 
jayasankerCommented:
Also i believe it relates to IIS configuration, have you changed anything??

check this as well

http://technet.microsoft.com/en-us/library/bb676685%28EXCHG.80%29.aspx

Thx
0
 
Roshan_cCommented:
Hi,

Check for all the dependency service are running related to transport service (MS Exchange Active Directory Topology Service). then start the transport service and try.

chech microsoft exchange information store service status.
0
 
mendozarAuthor Commented:
Turns out that teh second exchange server created two instances of the name that almost looked like an IPV6 name.  EX. Exchangeserver1
                               Exchangeserver1[]0:FB:)9:Fb  (almost like the IPV6 naming convention.)

I had to go into the ADSIEDIT.MSC to see the second naming instance and remove it. That fixed the issue.
0
 
mendozarAuthor Commented:
Got solution from Microsoft.
0

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now