Solved

SBS2008 Exchange System Attendant Will not run after migration completed

Posted on 2009-05-11
12
761 Views
Last Modified: 2012-06-21
We have completed a migration from SBS2003 to SBS 2008.
During the transtition period we saw a couple of times that the system attendant wasn't running.
A restart seemed to fix the issue.
Now that the migration is completed, including the removal of the old SBS2003 server we now can not get the System attendant to start.  SNtLmSspo we can't create new address's etc.
Dependency failure is on NtLmSsp

The System Event log shows the following error:
Log Name:      System
Source:        Service Control Manager
Date:          5/11/2009 9:31:36 AM
Event ID:      7003
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SBSV.cov.nsp
Description:
The Microsoft Exchange System Attendant service depends the following service: NtLmSsp. This service might not be installed.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Service Control Manager" Guid="{555908D1-A6D7-4695-8E1E-26931D2012F4}" EventSourceName="Service Control Manager" />
    <EventID Qualifiers="49152">7003</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2009-05-11T14:31:36.000Z" />
    <EventRecordID>75315</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>SBSV.cov.nsp</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">Microsoft Exchange System Attendant</Data>
    <Data Name="param2">NtLmSsp</Data>
  </EventData>
</Event>

Most of the hits on this are related to delaying the startup or restarting the service which is a known issue.
In this case the service will just not run!

0
Comment
Question by:BobPrinceExpert
  • 9
  • 3
12 Comments
 
LVL 52

Expert Comment

by:Manpreet SIngh Khatra
ID: 24355746
Ohk.
Check if the remote registry and NTLM and Netlogon services are running.
Also would like to ask if the IPv6 is enabled?

If not go to regedit
HKLM\System\CCS\Services\MSExchangeSA
and see the "Depend on Service and Depend on Group" DWORD value the "Depend on Service might have NTLMSsl" so you can try removing it from the list and see.
0
 
LVL 1

Author Comment

by:BobPrinceExpert
ID: 24356102
Here is what I find:
IP6 is enabled.
Remote REgistry  and Netlogon are both running.
Not sure what service name is responsible for NTLM - so unable to verify that.
Can you provide that detail for me?

Tried removing NTLMSsl from DependOnService list but that did not change the startup issue.
Did not find a DependOnGroup key.
Error is still the same.
Restart required for that?
Thanks for your assistance.
0
 
LVL 52

Expert Comment

by:Manpreet SIngh Khatra
ID: 24361606
Yeah you can once try restarting as at times registry takes effect only after reboot.
0
Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

 
LVL 52

Expert Comment

by:Manpreet SIngh Khatra
ID: 24361613
Also would like to as to whether the service does not start or you can start it manually but it does not come up automatically when you reboot?
0
 
LVL 1

Author Comment

by:BobPrinceExpert
ID: 24364940
I will have the client try a reboot first.
The problem is that it will not start.
That is event after the boot finishes - successive tries continue to fail.
0
 
LVL 52

Expert Comment

by:Manpreet SIngh Khatra
ID: 24372305
Cool would wait for your update
0
 
LVL 52

Expert Comment

by:Manpreet SIngh Khatra
ID: 24440993
If the issue is resolved can close the issue and distribute the points...... :-)
0
 
LVL 52

Expert Comment

by:Manpreet SIngh Khatra
ID: 24448330
Any updates ?
0
 
LVL 52

Expert Comment

by:Manpreet SIngh Khatra
ID: 24465202
Any updates on the issue ?
0
 
LVL 1

Author Comment

by:BobPrinceExpert
ID: 24472903
Issue is resolved. I believe that removing the dependnency corrected the problem.
I believe an onter engineer had perhaps entered the dependency manually.
So it made sense to remove it. Since it probobably didn't belong there it fixed the issue.
0
 
LVL 52

Expert Comment

by:Manpreet SIngh Khatra
ID: 24480427
As the issue is resolved can close the issue and distribute the points...... :-)
0
 
LVL 52

Accepted Solution

by:
Manpreet SIngh Khatra earned 500 total points
ID: 24482245
As the issue is resolved can close the issue and distribute the points...... :-)
0

Featured Post

Are your AD admin tools letting you down?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

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

This article explains in simple steps how to renew expiring Exchange Server Internal Transport Certificate.
Read this checklist to learn more about the 15 things you should never include in an email signature.
In this video we show how to create a mailbox database in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Servers >> Data‚Ķ
how to add IIS SMTP to handle application/Scanner relays into office 365.

825 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