On a server 2016 machine, a drive mapping in a batch file stops working with an error 8, not enough storage available to process the command. The mapping is to a netapp file server, and I think the problem started when the netapp was either upgraded or installed as a replacement for something else. Rebooting the 2016 server fixes it for a week.
Googling turns up two main ideas. One seems to be smb server related, to increase the registry setting for IRPSTACKSIZE. But there is a lot of ambiguity on what to set it to.
But since the 2016 machine is acting as an smb client to read from the share on the netapp, the ones related to the desktop heap seem more plausible. But there again, it seems to be a tricky operation to figure out what to increase desktop heap to.
Any advice? Thanks! My theory is something changed on the netapp that is consuming the server 2016 resources, similar to a memory leak or something. Nothing changed in the 2016 machine.
Googling turns up two main ideas. One seems to be smb server related, to increase the registry setting for IRPSTACKSIZE. But there is a lot of ambiguity on what to set it to.
But since the 2016 machine is acting as an smb client to read from the share on the netapp, the ones related to the desktop heap seem more plausible. But there again, it seems to be a tricky operation to figure out what to increase desktop heap to.
Any advice? Thanks! My theory is something changed on the netapp that is consuming the server 2016 resources, similar to a memory leak or something. Nothing changed in the 2016 machine.
Facebook
Twitter