Link to home
Start Free TrialLog in
Avatar of Seedubya
Seedubya

asked on

Exchange 2007 problems post-migration

Hi
I was last month in the middle of an SBS2003 to SBS2008 migration, using the Swing Migration method, when a family issue forced me to hand over the job in progress to another individual for completion. Now I am back in the saddle and the customer is having problems with Exchange 2007 SP1 (rollup 10 installed). Specifically, they are having problems both sending and receiving emails *sometimes*, some of the Exchange services will not start after an update, and there are quite a few Exchange errors in the event logs.  I had hoped to revert to the point in the migration where I'd left it but the indiviual in quesiton overwrote the backups I'd made AND formatted the TempDC I was using so I have no fallback.  The TempDC is still listed in the AD and is also the routing group master. Using ADSIEdit I see may references to it but haven't changed any of them for fear of doing further damage.  It's such a mess I'm tempted to start from scratch but the client doesn't want that!

I am hoping someone here can help me with this.  The very first error I see in the Applicaiton Event Log is

CertificationAuthority    91   "Could not connect to the Active Directory. Active directory Certificate Services will retry when processing requres Active Directory access."
THEN
MSExchange ADAccess    2114    "Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1552). Topology discovery failed, error 0x80040952 (LDAP_LOCAL_ERROR (Client-side internal error or bad LDAP message)). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185, "Microsoft LDAP Error Codes." Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers."

There are quite a few more if you want them.
Cheers
CW

SOLUTION
Avatar of RobertParten
RobertParten
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Seedubya
Seedubya

ASKER

Thanks for the VERY swift reply.
It's still listed alright. What are the potential pitfalls in deleting it?
I had the same issue with mine, except that the DC no longer existed and I got those MSEXCHANGETOPOLOGY messages. I deleted the DC from it and ensured that the other DC was in tehre...in your case that should list itself.
Ok, here goes....
Let me know how it works out for you.
No improvement - I don't think the CA role is installed properly - which might be why I'm getting Error 91
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Good job on that! I generally don't use self-signed certs though and I wonder why you have to delay start the topology service...sounds like the migration was a little botched because you weren't there. I will keep your solution in my books in the event I run into this as well.
We use pop connectors and an ISP smarthost so no need for a proper cert. Although as I'm finding this may not be as clearcut as I thought in SBS2008.  See my other open question for the details on that.  Thanks again Robert.
The answer did not directly help me. However it got me investigating other avenues which did help me so it was a catalyst.