Prev: SBS Monitoring 4GB (2008) Now what? Help needed
Next: SBS 2008 and eSATA
From: Hmmm on 24 Feb 2010 15:16
I'm currently experiencing the following issue on two SBS 2008
servers. Both servers have identical hardware (HP ML350 G6). One was a
swing migration from SBS 2003, the other a swing migration from SBS
2000.

When booting into Windows and before the logon prompt, there is a long
delay at the "Applying computer settings" stage.

The following events are logged:-

Log Name: Application
Source: Microsoft-Windows-Winlogon
Date: 23/02/2010 3:36:37 p.m.
Event ID: 6005
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: myserver.mydomain.local
Description:
The winlogon notification subscriber <GPClient> is taking long time to
handle the notification event (CreateSession).

Log Name: Application
Source: Microsoft-Windows-Winlogon
Date: 23/02/2010 3:45:05 p.m.
Event ID: 6006
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: myserver.mydomain.local
Description:
The winlogon notification subscriber <GPClient> took 567 second(s) to
handle the notification event (CreateSession).

The first event logged after the long delay is the following. I
suspect this may be the cause of the problem (I also realise it could
be a symptom rather than the cause):-

Log Name: System
Source: Service Control Manager
Date: 23/02/2010 3:45:01 p.m.
Event ID: 7022
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: myserver.mydomain.local
Description:
The Windows SBS Manager service hung on starting.

Can anyone tell me how I'd go about troubleshooting this problem?

--
Simon
From: Larry Struckmeyer[SBS-MVP] on 24 Feb 2010 18:19
Before I do so, have you run these events through www.eventid.net?

Usually some clues there.

Also, run the sbs bpa: www.sbsbpa.com
and fix anything it finds.

dcdiag (native to Windows 2K8) and netdiag (from 2K3 server tools) is also
a good place to start.

-
Larry
Please post the resolution to your
issue so others may benefit
-
Get Your SBS Health Check at
www.sbsbpa.com


> I'm currently experiencing the following issue on two SBS 2008
> servers. Both servers have identical hardware (HP ML350 G6). One was a
> swing migration from SBS 2003, the other a swing migration from SBS
> 2000.
>
> When booting into Windows and before the logon prompt, there is a long
> delay at the "Applying computer settings" stage.
>
> The following events are logged:-
>
> Log Name: Application
> Source: Microsoft-Windows-Winlogon
> Date: 23/02/2010 3:36:37 p.m.
> Event ID: 6005
> Task Category: None
> Level: Warning
> Keywords: Classic
> User: N/A
> Computer: myserver.mydomain.local
> Description:
> The winlogon notification subscriber <GPClient> is taking long time to
> handle the notification event (CreateSession).
> Log Name: Application
> Source: Microsoft-Windows-Winlogon
> Date: 23/02/2010 3:45:05 p.m.
> Event ID: 6006
> Task Category: None
> Level: Warning
> Keywords: Classic
> User: N/A
> Computer: myserver.mydomain.local
> Description:
> The winlogon notification subscriber <GPClient> took 567 second(s) to
> handle the notification event (CreateSession).
> The first event logged after the long delay is the following. I
> suspect this may be the cause of the problem (I also realise it could
> be a symptom rather than the cause):-
>
> Log Name: System
> Source: Service Control Manager
> Date: 23/02/2010 3:45:01 p.m.
> Event ID: 7022
> Task Category: None
> Level: Error
> Keywords: Classic
> User: N/A
> Computer: myserver.mydomain.local
> Description:
> The Windows SBS Manager service hung on starting.
> Can anyone tell me how I'd go about troubleshooting this problem?
>
> --
> Simon


From: Hmmm on 24 Feb 2010 21:39
There's nothing on eventid.net.

All is well as far as the SBS BPA is concerned.

One of the servers was missing SQL Server 2005 SP3. After installing
this service pack and rebooting, the start-up delay dropped to 120
seconds and the Windows SBS Manager service didn't hang on starting.
Interesting.

The other server is already fully patched.

When I run dcdiag, everything passes except for the SystemLog test,
which has a long list of errors that all look the same.

Starting test: SystemLog

An Error Event occurred. EventID: 0xC0002719

Time Generated: 02/25/2010 14:31:41

EvtFormatMessage failed, error 15100 Win32 Error 15100.
(Event String (event log = System) could not be retrieved,
error
0x3afc)


On Feb 25, 12:19 pm, Larry Struckmeyer[SBS-MVP] <lstruckme...(a)mis-
wizards.com> wrote:
> Before I do so, have you run these events throughwww.eventid.net?
>
> Usually some clues there.
>
> Also, run the sbs bpa:  www.sbsbpa.com
> and fix anything it finds.
>
> dcdiag (native to Windows 2K8) and netdiag (from 2K3 server tools) is also
> a good place to start.
>
> -
> Larry
> Please post the resolution to your
> issue so others may benefit
> -
> Get Your SBS Health Check atwww.sbsbpa.com
>
> > I'm currently experiencing the following issue on two SBS 2008
> > servers. Both servers have identical hardware (HP ML350 G6). One was a
> > swing migration from SBS 2003, the other a swing migration from SBS
> > 2000.
>
> > When booting into Windows and before the logon prompt, there is a long
> > delay at the "Applying computer settings" stage.
>
> > The following events are logged:-
>
> > Log Name:      Application
> > Source:        Microsoft-Windows-Winlogon
> > Date:          23/02/2010 3:36:37 p.m.
> > Event ID:      6005
> > Task Category: None
> > Level:         Warning
> > Keywords:      Classic
> > User:          N/A
> > Computer:      myserver.mydomain.local
> > Description:
> > The winlogon notification subscriber <GPClient> is taking long time to
> > handle the notification event (CreateSession).
> > Log Name:      Application
> > Source:        Microsoft-Windows-Winlogon
> > Date:          23/02/2010 3:45:05 p.m.
> > Event ID:      6006
> > Task Category: None
> > Level:         Warning
> > Keywords:      Classic
> > User:          N/A
> > Computer:      myserver.mydomain.local
> > Description:
> > The winlogon notification subscriber <GPClient> took 567 second(s) to
> > handle the notification event (CreateSession).
> > The first event logged after the long delay is the following. I
> > suspect this may be the cause of the problem (I also realise it could
> > be a symptom rather than the cause):-
>
> > Log Name:      System
> > Source:        Service Control Manager
> > Date:          23/02/2010 3:45:01 p.m.
> > Event ID:      7022
> > Task Category: None
> > Level:         Error
> > Keywords:      Classic
> > User:          N/A
> > Computer:      myserver.mydomain.local
> > Description:
> > The Windows SBS Manager service hung on starting.
> > Can anyone tell me how I'd go about troubleshooting this problem?
>
> > --
> > Simon
From: Larry Struckmeyer[SBS-MVP] on 25 Feb 2010 08:10
Is the SBS the source for DHCP and DNS?

One of the usual causes for slow startups is DNS. In the case of SBS every
NIC in the SBS network should point to the SBS for DNS, and there should
be no public or router DNS settings anywhere. The Wizards take care of setting
the forwarders.

If you are in doubt, post up the results of "ipconfig /all > c:\iptest.txt".

"An Error Event occurred. EventID: 0xC0002719"

That one has lots of references in an internet search. Too many for me to
run through, but you might want to take a look.

Does the BPA suggest updating the NIC drivers, or are there any updates available?

-
Larry
Please post the resolution to your
issue so others may benefit
-
Get Your SBS Health Check at
www.sbsbpa.com


> There's nothing on eventid.net.
>
> All is well as far as the SBS BPA is concerned.
>
> One of the servers was missing SQL Server 2005 SP3. After installing
> this service pack and rebooting, the start-up delay dropped to 120
> seconds and the Windows SBS Manager service didn't hang on starting.
> Interesting.
>
> The other server is already fully patched.
>
> When I run dcdiag, everything passes except for the SystemLog test,
> which has a long list of errors that all look the same.
>
> Starting test: SystemLog
>
> An Error Event occurred. EventID: 0xC0002719
>
> Time Generated: 02/25/2010 14:31:41
>
> EvtFormatMessage failed, error 15100 Win32 Error 15100.
> (Event String (event log = System) could not be retrieved,
> error
> 0x3afc)
> On Feb 25, 12:19 pm, Larry Struckmeyer[SBS-MVP] <lstruckme...(a)mis-
> wizards.com> wrote:
>
>> Before I do so, have you run these events throughwww.eventid.net?
>>
>> Usually some clues there.
>>
>> Also, run the sbs bpa: www.sbsbpa.com
>> and fix anything it finds.
>> dcdiag (native to Windows 2K8) and netdiag (from 2K3 server tools) is
>> also a good place to start.
>>
>> -
>> Larry
>> Please post the resolution to your
>> issue so others may benefit
>> -
>> Get Your SBS Health Check atwww.sbsbpa.com
>>> I'm currently experiencing the following issue on two SBS 2008
>>> servers. Both servers have identical hardware (HP ML350 G6). One was
>>> a swing migration from SBS 2003, the other a swing migration from
>>> SBS 2000.
>>>
>>> When booting into Windows and before the logon prompt, there is a
>>> long delay at the "Applying computer settings" stage.
>>>
>>> The following events are logged:-
>>>
>>> Log Name: Application
>>> Source: Microsoft-Windows-Winlogon
>>> Date: 23/02/2010 3:36:37 p.m.
>>> Event ID: 6005
>>> Task Category: None
>>> Level: Warning
>>> Keywords: Classic
>>> User: N/A
>>> Computer: myserver.mydomain.local
>>> Description:
>>> The winlogon notification subscriber <GPClient> is taking long time
>>> to
>>> handle the notification event (CreateSession).
>>> Log Name: Application
>>> Source: Microsoft-Windows-Winlogon
>>> Date: 23/02/2010 3:45:05 p.m.
>>> Event ID: 6006
>>> Task Category: None
>>> Level: Warning
>>> Keywords: Classic
>>> User: N/A
>>> Computer: myserver.mydomain.local
>>> Description:
>>> The winlogon notification subscriber <GPClient> took 567 second(s)
>>> to
>>> handle the notification event (CreateSession).
>>> The first event logged after the long delay is the following. I
>>> suspect this may be the cause of the problem (I also realise it
>>> could
>>> be a symptom rather than the cause):-
>>> Log Name: System
>>> Source: Service Control Manager
>>> Date: 23/02/2010 3:45:01 p.m.
>>> Event ID: 7022
>>> Task Category: None
>>> Level: Error
>>> Keywords: Classic
>>> User: N/A
>>> Computer: myserver.mydomain.local
>>> Description:
>>> The Windows SBS Manager service hung on starting.
>>> Can anyone tell me how I'd go about troubleshooting this problem?
>>> --
>>> Simon


From: Hmmm on 25 Feb 2010 15:29
Yes, the SBS server is the DHCP and DNS server.

All the drivers are up to date, as the server was only built three
weeks ago with the latest HP ProLiant Support Pack.

Here are the results of ipconfig/all

Windows IP Configuration

Host Name . . . . . . . . . . . . : LODGE
Primary Dns Suffix . . . . . . . : beva.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : beva.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC326i PCIe Dual Port
Gigabit Server Adapter
Physical Address. . . . . . . . . : 18-A9-05-6F-78-86
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . :
fe80::69f6:86bf:de35:d612%10(Preferred)
Link-local IPv6 Address . . . . . :
fe80::c824:1f8:cb7:ee91%10(Preferred)
IPv4 Address. . . . . . . . . . . : 10.10.0.2(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.10.0.1
DHCPv6 IAID . . . . . . . . . . . : 253274373
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-FB-D1-7A-18-
A9-05-6F-78-86
DNS Servers . . . . . . . . . . . : fe80::69f6:86bf:de35:d612%10
10.10.0.2
NetBIOS over Tcpip. . . . . . . . : Enabled

PPP adapter RAS (Dial In) Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : RAS (Dial In) Interface
Physical Address. . . . . . . . . :
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.10.0.43(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 8:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.
{9B2CC134-1D56-40C7-98A6-5FEB13E96AFE}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 9:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes


On Feb 26, 2:10 am, Larry Struckmeyer[SBS-MVP] <lstruckme...(a)mis-
wizards.com> wrote:
> Is the SBS the source for DHCP and DNS?
>
> One of the usual causes for slow startups is DNS.  In the case of SBS every
> NIC in the SBS network should point to the SBS for DNS, and there should
> be no public or router DNS settings anywhere.  The Wizards take care of setting
> the forwarders.
>
> If you are in doubt, post up the results of "ipconfig /all > c:\iptest.txt".
>
> "An Error Event occurred.  EventID: 0xC0002719"
>
> That one has lots of references in an internet search.  Too many for me to
> run through, but you might want to take a look.
>
> Does the BPA suggest updating the NIC drivers, or are there any updates available?
>
> -
> Larry
> Please post the resolution to your
> issue so others may benefit
> -
> Get Your SBS Health Check atwww.sbsbpa.com
>
> > There's nothing on eventid.net.
>
> > All is well as far as the SBS BPA is concerned.
>
> > One of the servers was missing SQL Server 2005 SP3. After installing
> > this service pack and rebooting, the start-up delay dropped to 120
> > seconds and the Windows SBS Manager service didn't hang on starting.
> > Interesting.
>
> > The other server is already fully patched.
>
> > When I run dcdiag, everything passes except for the SystemLog test,
> > which has a long list of errors that all look the same.
>
> > Starting test: SystemLog
>
> > An Error Event occurred.  EventID: 0xC0002719
>
> > Time Generated: 02/25/2010   14:31:41
>
> > EvtFormatMessage failed, error 15100 Win32 Error 15100.
> > (Event String (event log = System) could not be retrieved,
> > error
> > 0x3afc)
> > On Feb 25, 12:19 pm, Larry Struckmeyer[SBS-MVP] <lstruckme...(a)mis-
> > wizards.com> wrote:
>
> >> Before I do so, have you run these events throughwww.eventid.net?
>
> >> Usually some clues there.
>
> >> Also, run the sbs bpa:  www.sbsbpa.com
> >> and fix anything it finds.
> >> dcdiag (native to Windows 2K8) and netdiag (from 2K3 server tools) is
> >> also a good place to start.
>
> >> -
> >> Larry
> >> Please post the resolution to your
> >> issue so others may benefit
> >> -
> >> Get Your SBS Health Check atwww.sbsbpa.com
> >>> I'm currently experiencing the following issue on two SBS 2008
> >>> servers. Both servers have identical hardware (HP ML350 G6). One was
> >>> a swing migration from SBS 2003, the other a swing migration from
> >>> SBS 2000.
>
> >>> When booting into Windows and before the logon prompt, there is a
> >>> long delay at the "Applying computer settings" stage.
>
> >>> The following events are logged:-
>
> >>> Log Name:      Application
> >>> Source:        Microsoft-Windows-Winlogon
> >>> Date:          23/02/2010 3:36:37 p.m.
> >>> Event ID:      6005
> >>> Task Category: None
> >>> Level:         Warning
> >>> Keywords:      Classic
> >>> User:          N/A
> >>> Computer:      myserver.mydomain.local
> >>> Description:
> >>> The winlogon notification subscriber <GPClient> is taking long time
> >>> to
> >>> handle the notification event (CreateSession).
> >>> Log Name:      Application
> >>> Source:        Microsoft-Windows-Winlogon
> >>> Date:          23/02/2010 3:45:05 p.m.
> >>> Event ID:      6006
> >>> Task Category: None
> >>> Level:         Warning
> >>> Keywords:      Classic
> >>> User:          N/A
> >>> Computer:      myserver.mydomain.local
> >>> Description:
> >>> The winlogon notification subscriber <GPClient> took 567 second(s)
> >>> to
> >>> handle the notification event (CreateSession).
> >>> The first event logged after the long delay is the following. I
> >>> suspect this may be the cause of the problem (I also realise it
> >>> could
> >>> be a symptom rather than the cause):-
> >>> Log Name:      System
> >>> Source:        Service Control Manager
> >>> Date:          23/02/2010 3:45:01 p.m.
> >>> Event ID:      7022
> >>> Task Category: None
> >>> Level:         Error
> >>> Keywords:      Classic
> >>> User:          N/A
> >>> Computer:      myserver.mydomain.local
> >>> Description:
> >>> The Windows SBS Manager service hung on starting.
> >>> Can anyone tell me how I'd go about troubleshooting this problem?
> >>> --
> >>> Simon
 |  Next  |  Last
Pages: 1 2
Prev: SBS Monitoring 4GB (2008) Now what? Help needed
Next: SBS 2008 and eSATA