Workbench Error on last run: The directory is not empty.
I'm not sure what this error indicates, looking at the log it's not really clear what to do to resolve the issue any one had this and resolved it? The message I'm getting is "The directory is not empty." And here's the log info:
[ERROR] [16416:25] 2019-12-26 11:05:29,954 - Error executing DataSet Job
System.IO.IOException: The directory is not empty.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.Directory.DeleteHelper(String fullPath, String userPath, Boolean recursive, Boolean throwOnTopLevelDirectoryNotFound, WIN32_FIND_DATA& data)
at System.IO.Directory.Delete(String fullPath, String userPath, Boolean recursive, Boolean checkHost)
at WorkbenchSDK.Data.WorkbenchDataFile.CleanupDataPath(String path) in C:\jenkins\workspace\Workbench\WorkbenchBuild\WorkbenchSDK\Data\WorkbenchDataFile.cs:line 445
at WorkbenchSDK.Execution.Pipeline.DefaultJobExecution.<ExecuteAsync>d__0.MoveNext() in C:\jenkins\workspace\Workbench\WorkbenchBuild\WorkbenchSDK\Execution\Pipeline\DefaultJobExecution.cs:line 315
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at WorkbenchSDK.Execution.Pipeline.DefaultJobExecution.<ExecuteAsync>d__0.MoveNext() in C:\jenkins\workspace\Workbench\WorkbenchBuild\WorkbenchSDK\Execution\Pipeline\DefaultJobExecution.cs:line 332
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at WorkbenchSDK.Execution.WorkbenchJobExecutor.<ExecuteJobAsync>d__3.MoveNext() in C:\jenkins\workspace\Workbench\WorkbenchBuild\WorkbenchSDK\Execution\WorkbenchJobExecutor.cs:line 72
Comments
-
Hi Njt,
I've seen this before when files have been corrupted or permissions are causing problems. Is it just workbench that is having issues connecting to the information?
One thing that may resolve this is to run the "chkdsk" command on the location that is reporting the error. Before doing this I would check with your admins on how to do this or have them arrange for this to happen.
Jarvis
Jarvis
0
Categories
- All Categories
- 1.2K Product Ideas
- 1.2K Ideas Exchange
- 1.3K Connect
- 1.1K Connectors
- 273 Workbench
- 2 Cloud Amplifier
- 3 Federated
- 2.7K Transform
- 78 SQL DataFlows
- 525 Datasets
- 2.1K Magic ETL
- 2.9K Visualize
- 2.2K Charting
- 435 Beast Mode
- 22 Variables
- 513 Automate
- 115 Apps
- 390 APIs & Domo Developer
- 8 Workflows
- 26 Predict
- 10 Jupyter Workspaces
- 16 R & Python Tiles
- 332 Distribute
- 77 Domo Everywhere
- 255 Scheduled Reports
- 66 Manage
- 66 Governance & Security
- 1 Product Release Questions
- Community Forums
- 40 Getting Started
- 26 Community Member Introductions
- 68 Community Announcements
- 4.8K Archive