I have an extranet solution in SharePoint 2013 running on Windows Server 2012 r2. When I try to use the "Open in Explorer" command in a SharePoint document library, I get the following message:
"We have a problem opening this location in File Explorer and add this site to your list of trusted sites and try again."
First some more detailed information about my setup:
-This is a development server, so everything runs on the same machine.
-I am logged into the development server with an account that has all permissions under the sun.
– May be related – I also can not reach any of my sites through mapping network drives ("Add Network Location" via Explorer).
Below is a complete list of things I've already tried after over a week of research, trial and error:
-Using 32-bit Internet Explorer (I understand that Chrome, Firefox, Edge, and 64-bit IE can not use the "Open with Explorer" option).
-All my sites have been added to the Trusted Sites list in 32-bit IE.
– You also tried to add them to the intranet zone with identical settings.
-Activates all commonly recommended ActiveX controls / add-ons / etc in IE.
-Use the Emulation tab in the IE11 developer tools to emulate the IE10.
-All sites have been added to the Compatibility View in IE11.
Between each attempt, the cache was flushed in IE (ie after I changed something, including those listed below).
-Checked alternative access mappings according to (https://goo.gl/kkbyXb).
-Checked managed paths according to (https://goo.gl/1TErTM).
The website application in question uses Integrated Windows Authentication (NTLM). Basic authentication is also enabled.
Client integration is enabled for this web application.
-The account I use has full access to all the resources in question.
-WebDAV is installed / running.
The WebClient will be installed / run (including Desktop Experience).
Registry changes (WebClient parameter – BasicAuthLevel to "2", AuthForwardServerList, which includes all my sites).
– User Account Control set to low, then disabled.
– Installs any recommended updates / hotfixes that are remotely applicable to the problem.
Other potentially useful information
Until I enabled the "Automatically log in with current user credentials" option in IE, the "Open with explorer" button prompted for credentials before the above error message was displayed.
I used Fiddler to see what happened when I clicked Open with Explorer. That probably only confused me. When attempting to open the library in the Explorer view, the error message "401 UNAUTHORIZED" is displayed. This is almost useful if the button for entering credentials has been requested. However, the question arises: If my credentials do not exist, what is being searched for?
I've tried every solution I could get my hands on after I've dealt extensively with the subject. I divide them up logically, not chronologically, but meanwhile I've tried every possible variant of the above solutions that I can imagine to make any difference.
The goal here is actually to retrieve the path of a document within the library and pass it to an Excel connection manager in an SSIS package. I mention that because at this point I'm ready to try a workaround, if any.