Forum Discussion
What causes SMB server error STATUS_INSUFFICIENT_RESOURCES (0xc000009a) ?
I’m looking for advice on understanding this SMB error: STATUS_INSUFFICIENT_RESOURCES (0xc000009a). I have also posted this to https://www.reddit.com/r/WindowsServer/comments/16zc6pa/windows_file_se...
Hi DanDan320,
this can be caused by a lot of things, like too many open folders, too many connections, or not enough CPU, memory, or disk space...
Here are a few more things you can do to troubleshoot the problem:
- Check your server resources. Make sure your server isn't overloaded with CPU, memory, or disk usage. You can use tools like Windows Performance Monitor to check this.
- Check your SMB connections. See how many connections your server is handling at once. You can use the netstat command to check this. If you're seeing a lot of connections, it could be maxing out your server's resources.
- Check your server settings. There might be limits on how many connections or open files your server can handle. If these limits are too low, you may need to raise them. You can usually find these settings in the server's management console.
- Check your network. Make sure there are no problems with your network, like slow connections or lost data. This can mess up your file sharing. You can use tools like Ping and Tracert to test your network connection.
- Monitor your resources. Use tools to keep an eye on how your server uses resources over time. Watch for any big spikes before the problem happens again. This can help you identify the source of the problem.
- Review your file sharing settings. Check things like how long sessions last and how files are locked. You may need to adjust these settings to reduce the load on your server.
Please click Mark as Best Response & Like if my post helped you to solve your issue.
This will help others to find the correct solution easily. It also closes the item.
If the post was useful in other ways, please consider giving it Like.
Kindest regards,
Leon Pavesic
(LinkedIn)
- Check your server resources - as already mentioned in original post, issue is not CPU, RAM or disk. Of course I checked Task Manager, Resource manager, monitoring server, etc. as the first step.
- Check your SMB connections - netstat shows about 20 active connections including just 1x from the problematic machine. Get-SmbSession lists about 10 sessions, most with just a few files open, but the problematic client has 9011 files open in read mode, due to monitoring all those paths for changes, but as I said before, plenty CPU, RAM, disk, so I don't see this as a problem, unless there's some configured limit.
- Check your server settings - This very obvious advice doesn't help without specifics. I did post the output of Get-SmbServerConfiguration above. Is there some other server settings I should check?
- Check your network. - My 10GbE connection is perfectly fine, no packet drops, etc.
- Monitor your resources. - again fine.
- Review your file sharing settings. - yeah, again, any specifics? Where, which command or tool how?