This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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(6.4, 98%, 10%)' 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)
I've spent tens of hours searching for a solution to the error message: "We're having a problem opening this location in File Explorer, Add this web site to your Trusted sites list and try again".
I know there are dozens of articles on the Internet that describe this problem and claim that their solution works.
At first I will describe my situation: Productive server is Sharepoint 2010 foundation which is set as farm deployment. SP server runs on OS Windows 2008 R2, Database server is MS SQL 2008 SP2 on OS Windows 2012 R2. When I use in IE11 "Explorer view" for our Sharepoint site, everything works fine, without errors.
I prepared independent environment for Sharepoint 2013 foundation farm (because of it's the last free version) exactly according requirements: Sharepoint 2013 runs on Windows 2012 R2 (of course with Desktop experience feature), database server is MS SQL 2008 SP2 on Windows 2012 R2. I had to solve many error messages regarding of AppFabric Caching service, missing StateServiceDatabase, search serve, error: "Code Blocks Are Not Allowed in This File", etc. I was very surprised how many problems is included in new instalation of Sharepoint 2013 against 2010 version. But now is server fully hotfixed, without any error messages.
I did copy of productive content database of our Sharepoint site and than I attached this copy as new content database in Sharepoint 2013 environment. Than I did conversion from Form authentication to Claim authentication.
Now I have one productive site under Sharepoint 2010 and copy of the same site as test site under Sharepoint 2013. This test site works correctly in IE11 except of function: Open in Explorer program. Every my attempt ends with error message mentioned on the top of topic. When I open the productive site from Sharepoint 2010 on the same IE11, on the same computer, function Works properly. I tested it on several computer, of course.
Trust me, I tried all the recommendations and advice I found, nothing helped me:
I found that this problem still exist also in the newer versions of Sharepoint, include of Sharepoint online. So please do not send me recommendation in the meaning, forget about Sharepoint or move to newer version.
We need Open in Explorer function, do you know any other advices to solve this issue?
@Artas ,
Would you tell me whether your issue has been resolved or have any update ?
I am looking forward to your reply.
Hi Allen Xu,
no I stucked on this issue, I am thinking, I will delete whole web application and create new with classic windows authentication.
For everyone who might be interested, finally I found solution. Microsoft, every your newer version of SP has more complications as older.
My solution:
And after two months from start of my torture a miracle happened, function Open in Explorer started to work without problems.
Hi @Artas ,
I suggest you to reboot your server firstly and try agian.
If this error still exists, you could check your ULS Logs to trace more information:
You can find Log path in Central Administration -> Monitoring -> Configure diagnostic logging:
I hope this information has been useful, please let me know if you still need assistance.
If an 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.
Hi AllenXu, this server was restarted many times, because I am trying to solve this problem last two weeks. I am checking the trace log you mentioned. I only found these log records immediately after my attempt to use Open Explorer in library "Nvody":
a5fb2
11/02/2020 16:29:03.21 w3wp.exe (0x1A74) 0x1EEC SharePoint Foundation Monitoring nasq Medium Entering monitored scope (Request (OPTIONShttp://sgsrv20:80/weby/sgportal/Nvody)). Parent No
11/02/2020 16:29:03.21 w3wp.exe (0x1A74) 0x1EEC SharePoint Foundation Logging Correlation Data xmnv Medium Name=Request (OPTIONS:http://sgsrv20:80/weby/sgportal/Nvody) 04bc899f-fdae-50c4-d7eb-023b452686a9
11/02/2020 16:29:03.23 w3wp.exe (0x1A74) 0x1EEC SharePoint Foundation Authentication Authorization agb9s Medium Non-OAuth request. IsAuthenticated=False, UserIdentityName=, ClaimsCount=0 04bc899f-fdae-50c4-d7eb-023b452686a9
11/02/2020 16:29:03.23 w3wp.exe (0x1A74) 0x1EEC SharePoint Foundation Micro Trace uls4 Medium Micro Trace Tags: 0 nasq,3 agb9s 04bc899f-fdae-50c4-d7eb-023b452686a9
11/02/2020 16:29:03.23 w3wp.exe (0x1A74) 0x1EEC SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Request (OPTIONS:http://sgsrv20:80/weby/sgportal/Nvody)). Čas spuštění=5,23714828141992 04bc899f-fdae-50c4-d7eb-023b452686a9
11/02/2020 16:29:03.30 w3wp.exe (0x1A74) 0x2694 SharePoint Foundation Monitoring nasq Medium Entering monitored scope (Request (OPTIONS:http://sgsrv20:80/weby/sgportal/Nvody)). Parent No
11/02/2020 16:29:03.30 w3wp.exe (0x1A74) 0x2694 SharePoint Foundation Logging Correlation Data xmnv Medium Name=Request (OPTIONS:http://sgsrv20:80/weby/sgportal/Nvody) 04bc899f-ddb4-50c4-d7eb-0ab74380f3bd
11/02/2020 16:29:03.30 w3wp.exe (0x1A74) 0x2694 SharePoint Foundation Authentication Authorization agb9s Medium Non-OAuth request. IsAuthenticated=True, UserIdentityName=0#.w|<my user name and domain>, ClaimsCount=44 04bc899f-ddb4-50c4-d7eb-0ab74380f3bd
11/02/2020 16:29:03.30 w3wp.exe (0x1A74) 0x2210 SharePoint Foundation General af71 Medium HTTP Request method: OPTIONS 04bc899f-ddb4-50c4-d7eb-0ab74380f3bd
11/02/2020 16:29:03.30 w3wp.exe (0x1A74) 0x2210 SharePoint Foundation General af75 Medium Overridden HTTP request method: OPTIONS 04bc899f-ddb4-50c4-d7eb-0ab74380f3bd
11/02/2020 16:29:03.30 w3wp.exe (0x1A74) 0x2210 SharePoint Foundation General af74 Medium HTTP request URL: /weby/sgportal/Nvody 04bc899f-ddb4-50c4-d7eb-0ab74380f3bd
11/02/2020 16:29:03.30 w3wp.exe (0x1A74) 0x2210 SharePoint Foundation General af76 Medium HTTP request translate header: f 04bc899f-ddb4-50c4-d7eb-0ab74380f3bd
11/02/2020 16:29:03.30 w3wp.exe (0x1A74) 0x0C04 SharePoint Foundation Micro Trace uls4 Medium Micro Trace Tags: 0 nasq,4 agb9s 04bc899f-ddb4-50c4-d7eb-0ab74380f3bd
11/02/2020 16:29:03.32 w3wp.exe (0x1A74) 0x0C04 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Request (OPTIONS:http://sgsrv20:80/weby/sgportal/Nvody)). Čas spuštění=9,55884009412613 04bc899f-ddb4-50c4-d7eb-0ab74380f3bd
11/02/2020 16:29:03.68 OWSTIMER.EXE (0x27CC) 0x1FD4 SharePoint Foundation Monitoring aeh57 Medium Sql Ring buffer status eventsPerSec = 0,processingTime=0,totalEventsProcessed=0,eventCount=0,droppedCount=0,memoryUsed=0
But it is not clear information for me.
@Artas ,
Thank for sharing your log.
The messages in your log are all normal.
Make sure to clear the cache and cookies in your IE, best is to completely delete your IE history and restart the browser and check if issue exist.
If your issue still exists, I suggest you to open a ticket from Microsoft for further help :-)
Hi AllenXu,
You were my last hope of solving the problem. I did that steps a few times during my attempts to solve this issue. I am afraid that I can expect from Microsoft only one answer: "Sharepoint 2013 is no longer supported, we recommend to migrate to Sharepoint online. IE11 is no longer supported, ActiveX is obsolete technology and we recommend to use modern browser MS Edge and Synchronize option."
Such type of answers will not help me.
Not only are those not helpful, they're false. Are you using Premier support or where did you open your case at?
Hi @allen ,
I changed level of trace log to verbose and I found another information:
Verbose Trace level override is turned off. 55678a9f-8db4-50c4-d7eb-0577038803d5
11/04/2020 18:23:01.57 w3wp.exe (0x2648) 0x21E4 SharePoint Foundation Monitoring nasq Verbose Entering monitored scope (SPFederationAuthenticationModule.OnEndRequest). Parent No 55678a9f-8db4-50c4-d7eb-0577038803d5
11/04/2020 18:23:01.57 w3wp.exe (0x2648) 0x21E4 SharePoint Foundation Claims Authentication amge4 Verbose SPFederationAuthenticationModule.IsRedirectToLogOnPage: This is a 302 redirect to /_login/default.aspx?ReturnUrl=%2fweby%2fsgportal%2fNvody 55678a9f-8db4-50c4-d7eb-0577038803d5
11/04/2020 18:23:01.57 w3wp.exe (0x2648) 0x21E4 SharePoint Foundation Claims Authentication amge6 Verbose SPFederationAuthenticationModule.IsRedirectToLogOnPage: Redirect to known signin page: /_login/default.aspx?ReturnUrl=%2fweby%2fsgportal%2fNvody 55678a9f-8db4-50c4-d7eb-0577038803d5
11/04/2020 18:23:01.57 w3wp.exe (0x2648) 0x21E4 SharePoint Foundation Claims Authentication aip7c Verbose SPFederationAuthenticationModule.OnEndRequest: User was being redirected to authenticate. 55678a9f-8db4-50c4-d7eb-0577038803d5
11/04/2020 18:23:01.57 w3wp.exe (0x2648) 0x21E4 SharePoint Foundation Claims Authentication af32v Verbose Claims Windows Sign-In: Sending 401 for request 'http://sgsrv20/weby/sgportal/Nvody' because the user is not authenticated and resource requires authentication. 55678a9f-8db4-50c4-d7eb-0577038803d5
11/04/2020 18:23:01.57 w3wp.exe (0x2648) 0x21E4 SharePoint Foundation Monitoring b4ly Verbose Leaving Monitored Scope (SPFederationAuthenticationModule.OnEndRequest).
Maybe the problem is with authentication