Completed
Last Updated: 26 Sep 2014 06:18 by ADMIN
ADMIN
Cody
Created on: 19 Sep 2014 21:52
Type: Bug Report
0
On a customers machine Scheduling service errors out with Exception Info: System.IO.DirectoryNotFoundException
Ticket 853554

On this customers machine, our scheduling service will start, but after about 60 seconds it shuts back down. Looking at the Windows event log reveals:
Application: Telerik.TestStudio.ExecutionManagerService.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.DirectoryNotFoundException
Stack:

Server stack trace: 
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.Directory.InternalCreateDirectory(String fullPath, String path, Object dirSecurityObj, Boolean checkHost)
   at System.IO.Directory.InternalCreateDirectoryHelper(String path, Boolean checkHost)
   at System.IO.Directory.CreateDirectory(String path)
   at Telerik.TestStudio.Shared.Storage.Local.FileReaderWriterSync.CreateDirectory(String directory)
   at Telerik.TestStudio.Shared.Storage.Local.LocalComplexPathBuilder.CreateCollectionIfNotExists(IDataTransport data)
   at Telerik.TestStudio.Shared.Storage.Local.LocalStorageRepository`2.<Add>d__27.MoveNext()

Exception rethrown at [0]: 
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccess(Task task)
   at Telerik.TestStudio.Shared.Storage.Local.LocalStorageRepository`2.<Add>d__24.MoveNext()

Exception rethrown at [1]: 
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccess(Task task)
   at ArtOfTest.WebAii.Design.Repository.TestListResults.LocalTestListResultDataBus.<UploadTestListResultAsync>d__0.MoveNext()

Exception rethrown at [2]: 
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccess(Task task)
   at Telerik.TestStudio.ExecutionManager.Results.TestListResultTransportManager.<CreateFailedResultAsync>d__0.MoveNext()

Exception rethrown at [3]: 
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccess(Task task)
   at Telerik.TestStudio.ExecutionManager.Jobs.JobRunner.<RunJobAsync>d__c.MoveNext()

Exception rethrown at [4]: 
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccess(Task task)
   at Telerik.TestStudio.ExecutionManager.Jobs.JobBroker.<RunJob>d__b.MoveNext()

Exception rethrown at [5]: 
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccess(Task task)
   at Telerik.TestStudio.ExecutionManager.Jobs.JobBroker.<<.ctor>b__0>d__2.MoveNext()
   at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<ThrowAsync>b__1(System.Object)
   at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()
Attached Files:
1 comment
ADMIN
Daniel Djambov
Posted on: 26 Sep 2014 06:14
Telerik: It turned out there were 5 old queued scheduling jobs left in the folder (C:\Windows\SysWOW64\config\systemprofile\AppData\Roaming\Telerik\TestStudio\Scheduler\ScheduleStorage) that are causing the problem. Even though they show up in the Results view, they would not delete and throw exception in log. Once you delete those old files using Windows Explorer, the scheduling service starts behaving as expected.