Solved

Exhange Transport Service not starting

Posted on 2011-02-21
9
467 Views
Last Modified: 2012-05-11
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
Comment
Question by:mendozar
  • 5
  • 3
9 Comments
 
LVL 10

Expert Comment

by:jayasanker
ID: 34948314
have you disabled ipv6 in the tcp/ip properties??
0
 

Author Comment

by:mendozar
ID: 34948324
thanks
0
 

Author Comment

by:mendozar
ID: 34948326
yes i dont have that running on my server..............
0
NAS Cloud Backup Strategies

This article explains backup scenarios when using network storage. We review the so-called “3-2-1 strategy” and summarize the methods you can use to send NAS data to the cloud

 

Author Comment

by:mendozar
ID: 34948329
i  have 64 bit 2003 Windows server wtih Exchange 2007 SVC Pack 3
0
 
LVL 10

Expert Comment

by:jayasanker
ID: 34948347
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
 
LVL 10

Expert Comment

by:jayasanker
ID: 34948353
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
 
LVL 3

Expert Comment

by:Roshan_c
ID: 34948977
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
 

Accepted Solution

by:
mendozar earned 0 total points
ID: 34970140
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
 

Author Closing Comment

by:mendozar
ID: 35005111
Got solution from Microsoft.
0

Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Today, still in the boom of Apple, PC's and products, nearly 50% of the computer users use Windows as graphical operating systems. If you are among those users who love windows, but are grappling to keep the system's hard drive optimized, then you s…
Learn how to PXE Boot both BIOS & UEFI machines with DHCP Policies and Custom Vendor Classes
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…
The Task Scheduler is a powerful tool that is built into Windows. It allows you to schedule tasks (actions) on a recurring basis, such as hourly, daily, weekly, monthly, at log on, at startup, on idle, etc. This video Micro Tutorial is a brief intro…

821 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question