none
Windows Embedded Developer Update [WEDU] - timer exception with background scanning enabled RRS feed

  • Question

  • Anyone else seeing a crash in WEDU with background scanning enabled?

    Seems to happen after being left logged in for a couple of days...

     

     

    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="WEDU" />
      <EventID Qualifiers="0">0</EventID>
      <Level>2</Level>
      <Task>0</Task>
      <Keywords>0x80000000000000</Keywords>
      <TimeCreated SystemTime="2010-07-26T22:32:18.000Z" />
      <EventRecordID>18363</EventRecordID>
      <Channel>Application</Channel>
      <Computer>**elided**</Computer>
      <Security />
      </System>
    - <EventData>
      <Data>System.ArgumentOutOfRangeException: TimeSpan period must be greater than or equal to zero. Parameter name: value at System.Windows.Threading.DispatcherTimer.set_Interval(TimeSpan value) at Microsoft.Wedu.App.SetupNextBackgroundScan() at Microsoft.Wedu.App.ScanCompleted(IAsyncResult ar) at System.Runtime.Remoting.Messaging.AsyncResult.SyncProcessMessage(IMessage msg) at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink) at System.Runtime.Remoting.Proxies.AgileAsyncWorkerItem.DoAsyncCall() at System.Runtime.Remoting.Proxies.AgileAsyncWorkerItem.ThreadPoolCallBack(Object o) at System.Threading._ThreadPoolWaitCallback.WaitCallback_Context(Object state) at System.Threading.ExecutionContext.runTryCode(Object userData) at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack) at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)</Data>
      </EventData>
      </Event>

     

    Tuesday, July 27, 2010 8:57 AM

All replies

  • Hi,

    This sounds like a WEDU bug. Unfortunately it is also one that is near impossible for us to re-produce without more information. By setting WATSON to request more detailed memory dumps etc… the next time it does happen in the field we can get more detailed information about the actual state of WEDU to help diagnose.

    I would recommend opening a support request with Customer Support Services in order to get dedicated resources working with you to reproduce the issue adn obtain more detailed memory dumps etc.

    Lynda

    Tuesday, October 12, 2010 7:05 PM