2020028-windows-10-loses-connections-to-server-shares-on-2008-r2-and-2012-r2
2019 File Server Stops Responding to SMB Connections, server service cannot be restarted
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(48, 8%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKF%3C/text%3E%3C/svg%3E)
kajzica foler
96
Reputation points
hi
I have nightmare in company. New server 2019 with all patches. SMB server service hang several times per day, no any event log. Windows 10 clients cant access shares. Only solution is to restart server. Can even restart server service, which stuck in stopping state.
Exactly symptoms like in this big topic:
https://social.technet.microsoft.com/Forums/windowsserver/ja-JP/e9567167-22db-4b8c-9f96-a08b97d507f9/server-2012-r2-file-server-stops-responding-to-smb-connections?forum=winserverfiles
Any help?
Windows for business | Windows Server | User experience | Other
Answer accepted by question author
3 additional answers
Sort by: Most helpful
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous2020-11-06T19:50:47.493+00:00 Something fundamental must be broken if automatic start services crash and nothing written to event logs. If you cannot rebuild I'd suggest starting a case here with product support.
https://support.serviceshub.microsoft.com/supportforbusiness--please don't forget to Accept as answer if the reply is helpful--
-
kajzica foler 96 Reputation points
2020-11-08T20:50:43.59+00:00 i see event 1020, but nowhere solution. this is problem from 2008 server up to 2019. shame
SMB Server event ID 1020
File system operation has taken longer than expected.
Guidance:
The underlying file system has taken too long to respond to an operation. This typically indicates a problem with the storage and not SMB.
Sign in to comment -
-
kajzica foler 96 Reputation points
2020-11-09T12:32:26.437+00:00 All of this is in working condition. Windows have problem.
Before 2 days I start robocopy job from folder on server 1 (2019) to folder on server 2 (2012 R2). Several seconds from job start, server service on server 2 stopped working and cant access server anymore!!! Even cant to restart server 2. Server 2 work for long time without any problems. I use robocopy for years without problems. Something in past months in updates make problems.-
Joy Qiao 5,812 Reputation points Moderator2020-11-18T09:04:27.473+00:00 Hi,
I would apologize for my late reply.
Would you feedback your actions result to us in my previous reply.Bests,
Sign in to comment -
-
Joy Qiao 5,812 Reputation points Moderator
2020-11-09T07:27:47.487+00:00 Hi @kajzica foler ,
If you encounter Event ID 1020 warnings from SMB-Server in the Microsoft-Windows-SMBServer/Operational event log, we need to check the following:
Performance issues on clients working with this file server.
Connectivity issues for clients working with this file server.
Performance issues for applications or other components that run locally on this file server.
The file server appears to stop responding.According to Microsoft official article: Troubleshoot event ID 1020 warnings on a file server, we need to troubleshoot if it is caused by the following possible reasons:
overload of the physical disks
prolonged disk freeze operations such as the ones performed by VSS or other backup solutions
the network/storage stack of an underlaying hypervisor
the network connections to the storage
the SAN/NAS/Storage-Appliance itselfAs StorPortPacman trace log analysis and kernel dump log analysis is out of our Forum support scope. We recommend to create a ticket if you need further assistance.
If the issue could be resolved by restart SMB server service, as a workaround we could try to create a task scheduler to restart SMB service once it stopped.
Here is a similar thread for script creation reference.
How do I restart a Windows service from a script?During create task scheduler, please change the trigger to specific event ID such as Event ID 1020.
Please note: Information posted in the given link is hosted by a third party. Microsoft does not guarantee the accuracy and effectiveness of information.
Bests,
============================================
If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.