-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Alphaleonis.Win32.Filesystem.DeviceNotReadyException bug #531
Comments
I just came here for the same reason, I use the latest version and get the same error. here is excerpt from my log 2023-09-12 09:28:27 PATH1: D:_ARGOSY_PROD\EXEDIR\Argosy_2023_08_21__12_12_12\DevExpress.XtraGrid.v22.1.dll PATH2: \homer.du.laus.hr\ARGOSY\EXEDIR\Argosy_2023_08_21__12_12_12 MSG:Transaction not active. 2023-09-12 09:28:27 PATH1: D:_ARGOSY_PROD\EXEDIR\Argosy_2023_08_21__12_12_12\DevExpress.XtraGrid.v22.1.xml PATH2: \homer.du.laus.hr\ARGOSY\EXEDIR\Argosy_2023_08_21__12_12_12 MSG:(21) The device is not ready: [D:] I cant move further with this, I tried this and that to no avail. |
Hello everyone, we are using version of the library AlphaFS 2.2.5 and we are facing this exception. Is there any fix for this bug? Or can someone describes, how they solved this bug?
According on the StackTrace, it seems like the bug is inside Alphaleonis.Win32.Filesystem.Directory.ExistsDriveOrFolderOrFile function.
Thank you
Type:
Alphaleonis.Win32.Filesystem.DeviceNotReadyException
Message:
(21) The device is not ready: [PATH]
Data:
HResult=80070015 -2147024875 [2147942421]
ErrorCode=00000015 21 [ERROR_NOT_READY]
StackTrace:
at Alphaleonis.Win32.Filesystem.Directory.ExistsDriveOrFolderOrFile(KernelTransaction transaction, String path, Boolean isFolder, Int32 lastError, Boolean throwIfDriveNotExists, Boolean throwIfFolderOrFileNotExists)
at Alphaleonis.Win32.Filesystem.FindFileSystemEntryInfo.FindFirstFile(String pathLp, WIN32_FIND_DATA& win32FindData, Boolean suppressException)
at Alphaleonis.Win32.Filesystem.FindFileSystemEntryInfo.d__88`1.MoveNext()
The text was updated successfully, but these errors were encountered: