locked
WDS alternates between events 266 and 267. RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote


    I'm having some strange behavior with Windows Deployment Services --- in particular, some strange event log entries for the WDSIMGSRV source. Every half-hour WDSIMGSRV 'refreshes' its settings. However, every *other* refresh consistently fails. In other words, for each 267 event ("The Windows Deployment Services image server refreshed settings successfully.) there is consistently a 266 event 30 minutes later ("An error occurred while refreshing settings. Error Information 0x6BE.") I've turned on WDE log monitoring (http://support.microsoft.com/kb/936625 ) and here are the results:

    Here is the log that corresponds to the same time in the event log that I have a succesful configuration update:

    [2480] 11:26:10: Updating Server Configuration...
[2480] 11:26:10: [9060014][WdsImgSrv] -> ServiceControl
[2480] 11:26:10: [9060014][WdsImgSrv] -> pWdsImgSrvRefreshSettings
[2480] 11:26:10: [9060046][WdsImgSrv] <- pWdsImgSrvRefreshSettings=0
[2480] 11:26:10: [9060046][WdsImgSrv] <- ServiceControl=0
[2480] 11:26:10: [9060046][WDSPXE] Bind Policy: Exclude Registered
[2480] 11:26:10: [9060046][WDSPXE] Rogue Detection: Auth Recheck Time=3600
[2480] 11:26:10: [9060046][WDSPXE] Rogue Detection: Auth Failure Retry Time=30
[2480] 11:26:10: [9060046][WDSPXE] Rogue Detection: Disable Rogue Detection=Yes
[2480] 11:26:10: [9060046][WDSPXE] -> CBannedGuids::Initialize
[2480] 11:26:10: [9060046][WDSPXE] -> CBannedGuids::Shutdown
[2480] 11:26:10: [9060046][WDSPXE] <- CBannedGuids::Shutdown=0
[2480] 11:26:10: [9060046][WDSPXE] <- CBannedGuids::Initialize=0
[2704] 11:26:10: [9060046][WDSPXE] Rogue Detection: Wait=3600
[2480] 11:26:11: [9060155][WDSPXE] -> CBannedGuids::Initialize
[2480] 11:26:11: [9060155][WDSPXE] -> CBannedGuids::Shutdown
[2480] 11:26:11: [9060155][WDSPXE] <- CBannedGuids::Shutdown=0
[2480] 11:26:11: [9060155][WDSPXE] <- CBannedGuids::Initialize=0
[2480] 11:26:11: Dynamic Update Timer: 900000 ms
[2480] 11:26:11: Service Configuration Updated.


    Here is the log that corresponds to the same time in the event log that I have a failed configuration update:

    [1236] 12:11:11: Updating Server Configuration...
[1236] 12:11:11: [11760679][WdsImgSrv] -> ServiceControl
[1236] 12:11:11: [11760679][WdsImgSrv] -> pWdsImgSrvRefreshSettings
[1236] 12:11:30: [11779820][WdsImgSrv] <- pWdsImgSrvRefreshSettings=6be
[1236] 12:11:30: [11779820][WdsImgSrv] <- ServiceControl=6be
[1236] 12:11:30: [11779820][WDSPXE] Bind Policy: Exclude Registered

[1236] 12:11:30: [11779820][WDSPXE] Rogue Detection: Auth Recheck Time=3600
[1236] 12:11:30: [11779820][WDSPXE] Rogue Detection: Auth Failure Retry Time=30
[1236] 12:11:30: [11779820][WDSPXE] Rogue Detection: Disable Rogue Detection=Yes
[1236] 12:11:30: [11779820][WDSPXE] -> CBannedGuids::Initialize
[1236] 12:11:30: [11779820][WDSPXE] -> CBannedGuids::Shutdown
[1236] 12:11:30: [11779820][WDSPXE] <- CBannedGuids::Shutdown=0
[1236] 12:11:30: [11779820][WDSPXE] <- CBannedGuids::Initialize=0
[2704] 12:11:30: [11779820][WDSPXE] Rogue Detection: Wait=3600
[1236] 12:11:30: [11779914][WDSPXE] -> CBannedGuids::Initialize
[1236] 12:11:30: [11779914][WDSPXE] -> CBannedGuids::Shutdown
[1236] 12:11:30: [11779914][WDSPXE] <- CBannedGuids::Shutdown=0
[1236] 12:11:30: [11779914][WDSPXE] <- CBannedGuids::Initialize=0
[1236] 12:11:30: Dynamic Update Timer: 900000 ms
[1236] 12:11:30: Service Configuration Updateded.



    Has anyone else seen this, and found a workaround to stop these errors?

    P.S. I am only using WDS in conjunction with MDT 2010 RC --- I am letting MDT do all of the 'heavy lifting.'

    P.P.S. I have two domain controllers, but DCDiag shows all tests passed on both domain controllers. (We check our domain controllers daily with DCDiag.)

    Wednesday, September 2, 2009 1:05 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

     

    You can refer to this article:

     

    http://technet.microsoft.com/en-us/library/cc726554(WS.10).aspx

     

    Hope it helps.

     

    Tim Quan - MSFT

     

    Thursday, September 3, 2009 2:21 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Here is something that could be related. Before each failure in the log file, there is a line:

    [NetMon] Network Interface(s) Change Notification

    Each of those lines occurs at the exact same timestamp as a Time-Service Event 37 ("The time provider NtpClient is currently receiving valid time data..."). Is it possible that the NtpClient is causing the 'Network Interface(s) Change Notification" which in turn is causing the WDS failures? Turning off the Windows Time service did not stop the 266 Events --- but something is periodically causing that "Network Interface(s) Change Notification." ...
    • Edited by RJMPhD Thursday, September 3, 2009 7:02 PM Added additional information.
    Thursday, September 3, 2009 6:09 PM