Forum Discussion
Karl-WE
Oct 15, 2022MVP
ISSUE: b20348.887 "Not enough quota is available to process this command" when copying bigger files
I am trying to copy bigger files via SMB from Windows 11 22622.575 to Windows Server 2022 b20348.887
No matter if use Windows Explorer OR any other application like Macrium Backup, after some gigabytes of file transfer the transfer will stop and break with error 0x80070718.
the target SMB share configuration:
- ReFS 3.7
- SMB encryption: no
- SMB compression: yes (tried with disabled, but no effect)
- volume is hosted on a mirrored Storage Spaces volume
- offline files / caching: not enabled
general configuration:
both source and target have Hyper-V enabed using a simple SET switch in Hyper-V mode (2x 1 Gbit)
Error:
Error 0x80070718: Not enough quota is available to process this command
- reproducible: yes, always. Smaller files are unaffected. Cannot specify the exact file size that result in to the error
- Quotas (via FSRM): not implemented
unaffected files:
Windows_InsiderPreview_ADK_en-us_25217.iso, 1.7 GB
Windows_InsiderPreview_Server_vNext_en-us_25151.iso, 4,8 GB
affected files:
en-us_windows_server_2022_updated_april_2022_x64_dvd_d428acee.iso, 4.9 GB
AzureMigrateAppliance.zip, 10,8 GB (see error message)
Thanks for your help and feedback!
5 Replies
Sort By
- I don't feel it is really explained or solved, but after stopping + starting the Lanmanerver service all works fine now. Weird.
Interesting enough restarting the service or restarting the server or shutdown / power up, did not solve it before for days.- MegaCloudianaCopper ContributorI was about to say to restart the LanManServer service , but I found that already solved for you , that's great and as you said , it is not Macrium issue as issues like that happens with tools that supports SMB on windows 11 and windows server 2022 like Goodsync and Gs Richcopy 360 and the solution always solved by restarting this service
Good luck- Great you can second this. I have not seen this issue again.
- NedPyleFormer EmployeeHave you lost the repro? If yes, when it happens again, please run T.cmd in an elevated CMD prompt on the server and the client. https://1drv.ms/u/s!Aj_tsbbaXqQqgYaMQPlcLuoQ2I13ZG4?e=Pg0ySe
On server:
t.cmd SRVON
(reproduce the issue)
t.cmd SRVOFF
On client:
t.cmd CLION
(reproduce the issue)
t.cmd CLIOFFThank you Ned, when I am seeing it again I will definitely follow up on this. Have a good time!