SBS2008 Exchange System Attendant Will not run after migration completed
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-
<EventID Qualifiers="49152">7003</E
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000
<TimeCreated SystemTime="2009-05-11T14:
<EventRecordID>75315</Even
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>SBSV.cov.nsp</Co
<Security />
</System>
<EventData>
<Data Name="param1">Microsoft Exchange System Attendant</Data>
<Data Name="param2">NtLmSsp</Dat
</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!
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-
<EventID Qualifiers="49152">7003</E
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000
<TimeCreated SystemTime="2009-05-11T14:
<EventRecordID>75315</Even
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>SBSV.cov.nsp</Co
<Security />
</System>
<EventData>
<Data Name="param1">Microsoft Exchange System Attendant</Data>
<Data Name="param2">NtLmSsp</Dat
</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!
ASKER
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.
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.
Yeah you can once try restarting as at times registry takes effect only after reboot.
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?
ASKER
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.
The problem is that it will not start.
That is event after the boot finishes - successive tries continue to fail.
Cool would wait for your update
If the issue is resolved can close the issue and distribute the points...... :-)
Any updates ?
Any updates on the issue ?
ASKER
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.
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.
As the issue is resolved can close the issue and distribute the points...... :-)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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\M
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.