I recently had a number of users report that they were unable to connect to a mapped network drive to a WebDAV resource folder. On investigation, the mapped network drive was disconnected from Windows Explorer and the following error events had been reported in the application log:
Faulting application name: svchost.exe_WebClient, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1 Faulting module name: webclnt.dll, version: 6.1.7600.20967, time stamp: 0x4dce2f92 Exception code: 0xc0000005 Fault offset: 0x0000000000027bac Faulting process id: 0x17b4 Faulting application start time: 0x01cebaa35e44cc71 Faulting application path: C:\Windows\system32\svchost.exe Faulting module path: c:\windows\system32\webclnt.dll Report Id: 9bf15756-2696-11e3-b9b6-005056a561e1 Faulting application name: svchost.exe_WebClient, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1 Faulting module name: webclnt.dll, version: 6.1.7600.20967, time stamp: 0x4dce2f92 Exception code: 0xc0000005 Fault offset: 0x000000000000502b Faulting process id: 0x1188 Faulting application start time: 0x01cebaa319128423 Faulting application path: C:\Windows\system32\svchost.exe Faulting module path: c:\windows\system32\webclnt.dll Report Id: 5cb189bc-2696-11e3-b9b6-005056a561e1 Faulting application name: svchost.exe_WebClient, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1 Faulting module name: webclnt.dll, version: 6.1.7600.20967, time stamp: 0x4dce2f92 Exception code: 0xc0000005 Fault offset: 0x0000000000027bac Faulting process id: 0x318 Faulting application start time: 0x01ceb9f521176cd8 Faulting application path: C:\Windows\system32\svchost.exe Faulting module path: c:\windows\system32\webclnt.dll Report Id: 54600b6d-2696-11e3-b9b6-005056a561e1
This issue appears to be caused by an access violation issue in the the WebClient service which causes the service to crash intermittently and to impact clients running on Windows 7 and Windows Server 2008 R2.
This is a known issue and there is a support hotifx available from Microsoft to resolve this issue and is available from http://support.microsoft.com/kb/2548470.
Once installed, the issue now seems to have been resolved.
Deans Blog 