Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Friday, September 25, 2015 9:22 PM | 1 vote
Hi All.
Windows 10 computers with a mapped network drive for a file share hosted on Server 2012. When we try copying and renaming a file on the shared drive, it freezes and spits out *Error 0x8007003B: An unexpected network error occurred. *It only gives this message when you try renaming the file, though. It copies without any problem. If you try renaming a file immediately after copying, the operation will hang for a few minutes. A few minutes later it will give you this error message, and then it will complete renaming the file. No problems copying and renaming when working directly on the server; only when accessing the fileshare from a network location. This is happening on every computer on the network; all machines are Windows 10. The server and the client machines all have current Windows updates, but if this is caused by an update I don't know how to determine which one, in this case.
The server is barely a year old, and we have had no other major issues with it, but occasionally a file saved there by one machine will take a while to show up on another machine - slow performance for reasons I'm not sure of. Not sure if the two are connected.
I tried using Microsoft Message Analyzer and I'll be honest, I'm not 100% sure what to do with it, but I tried tracing something and similar to the technet thread below, it looks like there are duplicate TCP packets when I try renaming and it freeze:
https://social.technet.microsoft.com/Forums/en-US/1208ca4a-47aa-451c-8aa7-04599527484c/windows-81-network-share-0x8007003b-error-copying-files?forum=w8itpronetworking%20Cheers,%20Zak
Also per the recommendations in the above thread (the only thing I've found so far that resembles what I'm seeing):
-I tried the following commands:
netsh int tcp set global chimney=disabled
netsh int tcp set global rss=disabled
netsh int ip set global taskoffload=disabled
netsh int tcp set global autotuninglevel=disabled
netsh int tcp set global congestionprovider=none
netsh int tcp set global ecncapability=disabled
netsh int tcp set global timestamps=disabled
-Disabled the firewall on client machine to see if that had any effect
-Disabled SMBv2 and SMBv3 as well
==
All to no avail. It is still happening.
I vaguely remember reading something at some point saying that these kinds of performance bugs could be due to problems with the network switches. We have had some problems with our router lately. This seems to be a network issue and not a problem with the server itself. But I am not a networking professional and I have no idea how to proceed to diagnose it any further than this.
Can anyone help me nail down a firm diagnosis of what's going on?
Thanks,
Ivan
All replies (11)
Tuesday, September 29, 2015 6:01 AM | 1 vote
Hi imd567,
Same issue could be caused by various reasons.
After a deep research, I found one of the possible reason is related to the router. According to your description, you have mentioned the router, too.
To test whether this issue is related to the router, we could try to connect the machine (Windows 10) and the shared host machine(Server 12) with a cable. It will help us to troubleshoot whether this issue is related to the router. If it is proved to be caused by the router, we should update the router firmware and contact the router for support.
If it is proved not to be caused by the router, we could try to disable the third party antivirus software and the firewall temporarily to have a check if it has been installed. We should ensure all the packages are not blocked.
One of the another possible reason is related to the offline files not being synced correctly. We could check the sync center for the sync information. We could disable the offline feature to have a troubleshoot.
To troubleshoot whether this issue only occurred with the Windows Server 12, we could try to create the shared folder on other machines to have check.
Please also try to check the Event Viewer for related information to troubleshoot this issue.
Event Viewer\Windows Logs\Application, System
Best regards
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Wednesday, September 30, 2015 11:01 PM
-Offline syncing was already disabled, so I don't think that could be it.
-I tried disabling the firewall and all third party antivirus software, and it was still happening. I'm not sure how to ensure that all the packages are not blocked, but.
It's a very intermittent problem and has stopped happening the last few days... Which is good, but is making it harder for me to diagnose when I can't reproduce it again. Perhaps it has fixed itself? Otherwise, I will just try to sort it out when it starts happening again.
Anyway, after reading your explanation, the router seems like the most obvious source of the problem. I will look into it and keep an eye on Event viewer. Thanks!
Wednesday, April 6, 2016 4:34 PM
I'm having this same issue, but it is intermittent, I can copy folders just fine but the moment I go to rename them it freezes, same behavior you're describing, but not on all machines and not every time either, sometimes it works without any lag or freezing. Were you ever able to find a solution to this? This just started happening on my network and is a real pain for many users.
Wednesday, April 6, 2016 4:50 PM
Got any Win 7 machine you can hook up? According to numerous post on the internet it seems like Win 10 has network trouble.
With a Win 7 machine you can get a baseline and also get it working. Try it!
Best regards, George
If you got help to solve your problem, then please give credentials to the answerer
Thursday, April 7, 2016 6:36 PM
I do have one machine with Win 7, this is a brand new issue, and most of my machines have had Win 10 for almost a year now, which makes me think it was a update that may have caused this.
Monday, August 15, 2016 12:16 AM | 1 vote
Hi all,
Check out thread:
I just posted a possible solution at the bottom if you happen to want to give it a try. The same thing is happening with renaming files over in this thread. Could be something to do with "Windows Search". Try turning it off on the host PC and see if makes a different. Be interesting if it works for you....
Mr O 76
Tuesday, August 30, 2016 9:14 AM
Hi all,
Check out thread:
I just posted a possible solution at the bottom if you happen to want to give it a try. The same thing is happening with renaming files over in this thread. Could be something to do with "Windows Search". Try turning it off on the host PC and see if makes a different. Be interesting if it works for you....
Mr O 76
Hello MR O 76, yes, turning Search indexing off on the server works. But, we have business applications that rely and use the file index, so we can't turn it off. Also, we have like 100 000 files. If we have file indexing turnd off, it takes minutes or more to find a file. But it definately has something to do with the new File Explorer in windows 10 anniversary update and the windows search indexing service on Windows Server.
Monday, September 12, 2016 9:44 AM
Microsoft need to fix this and fast!!! Its bulls&^t!
Thursday, October 6, 2016 11:37 PM
Checking now to see if this has been fixed, hang tight.
Thursday, October 20, 2016 10:05 AM
Well Im still experiencing this problem so no fix here what it seems.
Tuesday, January 9, 2018 7:49 AM | 1 vote
Windows search is the issue for my case. Also good to know the DB file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" always grow up too fast. 32Gb currently.