Sharepoint Revision History in Explorer View - Is it possible?

Hello, thank you in advance for any help. We are beginning our deployment of SharePoint and many of our "hard converts" have love the ability to use "explorer view" to manage documents. On question has arose though. When in explorer view they are unable to view revision history for a document. I know you can open office documents and view the history there but this is not available to non office documents.
Is there a way to have this information be displayed in a right click context or on some other manner from explorer view or when the repository is mapped as a network drive? In the box functionality a custom solution or a commercial pay add-on are all acceptable options to me.

Technically it's possible, but not feasible at all.
You need to write you own Explorer Extension to add the context menu to mange Web Folders. That extension will work on the top of existing WebDav extension (http://chestofbooks.com/computers/revision-control/subversion-svn/Microsoft-Web-Folders-Webdav-Clients-File-explorer-extension.html) to match the Web Folder items with the SharePoint lists and items to get the item history.
You can add the Explorer panel and render the History Info there for each selected element.
So it's doable, but not an easy stuff.
I would estimate it for couple of weeks of work for senior Web/WinForms developer (you not only need to query SharePoint data, but know how to write explorer extension and show info inside the Explorer info)
SharePoint 2007 - 2010 Tips & Tricks Portal | Microsoft MVP |
My Blog about Information Management |
My twitter

Similar Messages

SharePoint 2013 Open with Explorer View Requirement of Permissions for copy / paste

Hi,
I have a scenario, where I have a document library and it resides in the top level site of the site collection. I have another document library in one of the subsites. What I am trying to do is:
Use Explorer View in the top-level site's document library to copy / paste into Explorer View of the document library in the subsite.
I can't seem to do it. Does it require owner permissions to do so?
Can anyone list the limitations of using explorer view for copy/paste?
techie

Hi,
SharePoint maintain the same access restriction in windows explorer view as it is in web UI. That means if user has contributor permission the he/she will be able to contribute in windows explorer view as well. By default windows explorer view is available
to every users in SharePoint.
Are you getting error message while opening windows explorer view for any document library? Windows explorer view only works in Internet Explorer currently other browsers doesn't support Windows Explorer view.
Here are couple of article on troubleshooting windows explorer view:
Office 365: https://support.microsoft.com/en-us/kb/2629108?wa=wsignin1.0
There are multiple fix available for different Windows OS and version of IE you are using.
.Net Devoloper

Error while creating folder named "bin" using explorer view in sharepoint 2010

I am getting error when I create a folder in a library named "bin" using explorer view in sharepoint 2010.
When I create folders with other names I don't get any errors.
Please suggest.

Hi,
According to your description, my understanding is that you got an
error when you create a folder named “bin” in a SharePoint library with explorer view.
There are any Microsoft.NET Framework assemblies that have controls or parts that the SharePoint site uses, which are stored in the bin folder. You can remove “bin” from hidden segments, then you can create a folder named “bin”
in the SharePoint library with explorer view.
1.Opened IIS Manager and selected Server name -> Request Filtering -> Hidden Segments tab -> Removed "bin" from there:
2.Perform IISRESET:
Thanks,
Dean Wang

Sharepoint 2013 explorer view error - problem opening this location in file explorer (HTTPS + Win7 Enterprise 64 bit + IE9 32 bit + Office 2007 32 bit)

Hi,
We have a problem using Sharepoint 2013 explorer view. (Error - We're having a problem opening this location in file explorer. Add this web site to your trusted sites list and try again).
I'm using Windows 7 Enterprise 64 bit, Office 2007 32 bit and IE9 32 bit. And the sharepoint site is a https site.
Some people in my organization are able to browse and some users getting the above error. (with the same client machine configuration)
If I clear my browser cache, closes the browser and open it then the explorer view is working. But after a minute if I try again I'm getting the above mentioned error. This 1 minute expiration happens is since the first time I have used explorer
view, not since I opened the browser.
I have tried the following on my machine:
1. Modified the web client service to run automatically.
2. Verified the sharepoint site is part of trusted sites (https://*.spsite.com/)
3. Compatibility mode is turned on.
4. Tried adding
AuthForwardServerList in the webclient registry settings under parameters. (restarted the web client)
5. Verified the BasicAuthLevel set to 1 (since we are using SSL). Tried setting the BasicAuthLevel to 2 as well. (restarted the web client)
6. Tried installing software update for web folders (KB907306).
Verified the below on the production server:
1. The web application has the root site collection.
2. It has WebDav Publishing disabled under IIS Web Server feature.
Could some one please help me in resolving this issue?
Thanks.

Hi Deepak,
According to your post, my understanding is that you failed to use "Open with Explorer" in a document library.
For your issue, please verify the following:
ActiveX controls must be enabled in IE.
As you are using Windows 7 Server as the client computer, you must install the Desktop Experience feature from Server Manager.
Make sure there is a working Root site collection.
Install this hotfix for windows 7 work with sharepoint 2013 :hotfixv4.microsoft.com/.../463266_intl_x64_zip.exe
Best Regards,
Eric
Eric Tao
TechNet Community Support

Computer crashes on SharePoint explorer view

One of our customers has connected a SharePoint document library as network drive to manage his documents. since a while his computer crashes nearly every time he uses this view.
We tried everything descriped in the Whitepaper "Understanding and Troubleshouting SharePoint Explorer View but nothing helped.
Our onsite support made a complete new installation to his computer, but nothing changed. He uses Windows XP (SP3) and Office 2007 (no SP). The same problem occurenced by using Office 2003.
I have no ideas any more...please help.
Thank you very much
cibyl-a

This issue can be a difficult one to troubleshoot via the forums. One suggestion I would have is if the user has no business need for office 2003 since he has office 2007 is to remove Office 2003. Also apply SP2 for office 2007. Verify if the user can get to explorer view through the SharePoint Site.
-Aseem
This posting is provided "AS IS" with no warranties, and confers no rights

SharePoint 2013 Service Pack 1 broke Explorer View (WebDAV)?

We recently installed SharePoint 2013 Service Pack 1 and have since been troubled by Explorer View. Very often Explorer View doesn't work. This error often appears:
"We're having a problem opening this location in File Explorer. Add this web site to your Trusted Sites list and try again."
The weird thing is that sometimes the Explorer View works just fine, but more often it doesn't. There's are a lot of blogs / topics about this on the internet, but they all didn't help resolve this issue. We use persistent cookies for our STS (AllowSessionCookies
== false), we've added the site to Trusted Sites, made sure WebClient service is running on the clients, cleared cookie caches, etc., etc.
Explorer View works fine when we connect to Office 365 instances. But our local farm has these problems. We use ADFS auth.
Our problems actually resemble the problems this guy had:
http://blog.skadefro.dk/2011/09/sharepoint-2010-and-webdav.html
But his fix doesn't seem to apply to us.
This all started after installing Service Pack 1, so could this be a Service Pack 1 issue?

Hi LZandman,
There is a KB article, it provides that:
Issue 2
Assume that you access the date in a SharePoint Document Library. Then, you click Open with Explorer View when you view a SharePoint Document Library in Internet Explorer 10. In this situation, the operation fails, and you receive one of the following error
messages.
Error message 2
We're having a problem opening this location in File Explorer. Add this web site to your Trusted Sites list and try again.
Notes
These issues occur only when the SharePoint server is configured for cookie-based authentication, such as SharePoint Online.
You may encounter a similar issue when you use other Web Distributed Authoring and Versioning (WebDAV) servers that are configured for cookie-based authentication.
Please take a look at :
http://support.microsoft.com/kb/2846960/en-us , and download and install the hotfix, compare the result.
I hope this helps.
Thanks,
Wendy
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Wendy Li
TechNet Community Support

Differentiate file uploaded from explorer view in SharePoint

Hello,
I am working on event receiver which on item adding updates few fields of document in library if those are not empty. The code is working fine in new file, drag and drop but in explorer view, I am not getting afterproperties values except two default field
values (vti_parserversion and vti_filesize). But in updating event we are getting those values.
Is there any way to differentiate file uploaded using explorer view in event receiver? So that I can work on updating in case of explorer view.
Thanks.

Hi,
According to your post, my understanding is that you want to differentiate file uploaded from explorer view in SharePoint 2013.
I made a test in my environment, both the two ways(“new document” or “Open with explorer” ) to upload document, the AfterProperties only contains two default field values(vti_parserversion and vti_filesize) in
ItemAdding method in event receiver.
There are two steps occur when uploading a file to document library, the file is uploaded in the first step, then the list item properties will be modified in the second step.
So, it is recommended to update the fields of document in ItemUpdating
method in event receiver.
Best Regards
Dennis Guo
TechNet Community Support

Explorer View SharePoint 2013

I migrated a SharePoint 2007 web application to SharePoint 2013 and ran into a strange situation. Clicking on the
Explorer View does not work. But clicking the Open With Explorer in the ribbon works great.
Here are things I have done so far:
Web Client service enabled on Server (Win2012) and client machine.
Trusted the site in IE.
Running IE 32bit
STSSYNC add-on enabled in IE
Nothing in the ULS or event log. Did I miss any other magic.
Praveen Pandey

I've seen situations where upgrading to a newer version of SharePoint leads to a situation where links are broken because they still point to old functionality, and maybe that's the case here. Because the Open With Explorer ribbon option works great, it
seems unlikely there's a client issue, carefully check what that does compared to clicking on the Explorer View.
Kind regards,
Margriet Bruggeman
Lois & Clark IT Services
web site: http://www.loisandclark.eu
blog: http://www.sharepointdragons.com

Windows7 and sharepoint explorer view

I am running windows 7 professional and use sharepoint and IE8, I am not able to get explorer view to work with this system combination.
Any ideas?
[email protected]

Hi,
Click
START
Click Run
Type %systemroot%\system32\
Click Enter
Sort your files in Windows Explorer by Name
Type webfldr
webfldrs.msi is automatically found/selected.
Right click this file, choose repair.
Hi Replying to SnrBA, i am not able to find the webfldr
under %systemroot%\system32\
this does not exsist.
Kamal.R

Accessing explorer view updates modified timestamp only on e-mails (.msg) in SharePoint 2013

Hi All,
We've recently discovered that when users are accessing explorer view in various libraries on SharePoint, libraries which hold emails (.msg) are automatically updating all email modified timestamps with the time explorer was accessed and presenting modified
by as the user who initiated explorer view as well.
It is not all documents, only emails (.msg). This happens every time without fail: When accessing a library in explorer view, right clicking and selecting refresh (or adding a new document to the library via explorer) triggers all emails to have their modified
stamp updated. It creates a single version at the time of refresh if version control is on.
Here is the log in the scenario where I refreshed a library in explorer view which has only one email called pings.msg and it has had its modified timestamp updated to the time of refresh:
Medium Entering monitored scope (Request (PROPFIND:http://...:80/sites/ICT/Shared%20Documents/desktop.ini)). Parent No
Medium Name=Request (PROPFIND:http://...:80/sites/ICT/Shared%20Documents/desktop.ini)
Medium Non-OAuth request. IsAuthenticated=True, UserIdentityName=0#.w|domain\me, ClaimsCount=29
Medium HTTP Request method: PROPFIND
Medium HTTP request depth header: 0
Medium Overridden HTTP request method: PROPFIND
Medium HTTP request URL: /sites/ICT/Shared%20Documents/desktop.ini
Medium HTTP request translate header: f
High [Forced due to logging gap, cached @ 09/12/2014 13:07:41.30, Original Level: Verbose] WOPI is disabled because no discovery data are found.
High [Forced due to logging gap, Original Level: Verbose] SPRequestModule.PreSendRequestHeaders
Medium Leaving Monitored Scope (Request (PROPFIND:http://...:80/sites/ICT/Shared%20Documents/desktop.ini)). Execution Time=12.1815063087627
Medium Leaving Monitored Scope (Request (POST:http://...:80/sites/edrms/_vti_bin/sitedata.asmx:GetContentEx")). Execution Time=428.478759171906
Medium Name=Task: SessionManager.PerformOngoingRequestDepartures
Medium Entering monitored scope (Request (GET:http://...:80/sites/ICT/Shared%20Documents/Pings.msg)). Parent No
Medium Name=Request (GET:http://...:80/sites/ICT/Shared%20Documents/Pings.msg)
Medium Non-OAuth request. IsAuthenticated=True, UserIdentityName=0#.w|domain\me, ClaimsCount=29
Medium HTTP Request method: GET
Medium Overridden HTTP request method: GET
Medium HTTP request URL: /sites/ICT/Shared%20Documents/Pings.msg
Medium HTTP request translate header: f
Medium Spent 0 ms to bind 81408 byte file stream
Medium Spent 16 ms to send 81408 byte file stream
Medium Leaving Monitored Scope (Request (GET:http://...:80/sites/ICT/Shared%20Documents/Pings.msg)). Execution Time=19.2898818145882
Medium Entering monitored scope (Request (HEAD:http://...:80/sites/ICT/Shared%20Documents/Pings.msg)). Parent No
Medium Name=Request (HEAD:http://...:80/sites/ICT/Shared%20Documents/Pings.msg)
Medium Non-OAuth request. IsAuthenticated=True, UserIdentityName=0#.w|domain\me, ClaimsCount=29
Medium HTTP Request method: HEAD
Medium Overridden HTTP request method: HEAD
Medium HTTP request URL: /sites/ICT/Shared%20Documents/Pings.msg
Medium Leaving Monitored Scope (Request (HEAD:http://...:80/sites/ICT/Shared%20Documents/Pings.msg)). Execution Time=7.43690888087732
High [Forced due to logging gap, cached @ 09/12/2014 13:07:41.35, Original Level: Verbose] SQL connection time: 0.0458857201124724
High [Forced due to logging gap, Original Level: VerboseEx] Reverting to process identity
Medium Entering monitored scope (Request (PUT:http://...:80/sites/ICT/Shared%20Documents/Pings.msg)). Parent No
Medium Name=Request (PUT:http://...:80/sites/ICT/Shared%20Documents/Pings.msg)
Medium Non-OAuth request. IsAuthenticated=True, UserIdentityName=0#.w|domain\me, ClaimsCount=29
Medium HTTP Request method: PUT
Medium Overridden HTTP request method: PUT
Medium HTTP request URL: /sites/ICT/Shared%20Documents/Pings.msg
Medium HTTP request translate header: f
Medium Spent 0 ms to read 81408 byte file stream
Medium |No zip central directory found
Medium Information Rights Management (IRM): The email address of the requesting user is successfully set to IRM.
Medium Information Rights Management (IRM): The IRM status of the document [Shared Documents/Pings.msg] is: untried (-1), the return values is: 0x0.
High Leaving Monitored Scope (EnsureListItemsData). Execution Time=22.2785298131466
Medium Spent 16 ms to parse
Medium |No zip central directory found
Medium |Nothing to commit
Any ideas on how to stop this behaviour?

Probably you have an antivirus that scan these files when you are open the library in Explorer View.
Try to configure the antivirus for exclude location.
Hope helps.
http://valygreavu.com/

Sub folders not showing in Explorer view

Hi,
We have a totally standard Sharepoint 2013 installation. We've noticed this week that in some document libraries when opening them up in Explorer view it doesn't display all the sub folders in that library/folder. It's a real pain when users have a folder
with 20+ documents and want to move them somewhere else and can't because one of the folders aren't showing up. Manually moving them one by one is pretty tiresome.
If I remove the subfolder in Sharepoint and then recreate the folder in Explorer view that works fine, so it's not that the name is too long. It's not a permission thing since I'm site collection admin. Same issue on Windows 7 and Windws 8. Tried different
logins. Just can't wrap my head around this issue or what's causing it.
Any ideas?

Hi Kristoffer,
I have seen an attribute for folder object which could control SharePoint folder hide or show in webdav explorer view, you can use PowerShell to output the problematic folder property, see if it the case, then use the PowerShell code to set it's property
with blank value to make it show in explorer view,
Use the PowerShell to get the folder object and then check the property value with this code line $folder.Properties["vti_winfileattribs"]
#folder can be site, library level and folder level
$folder = (Get-SPWeb http://sp).Folders["shared documents"].SubFolders["folder1"]
#hide folder
$folder.Properties["vti_winfileattribs"]="00000016"
#show folder
####$folder.Properties["vti_winfileattribs"]=""
$folder.Update()
https://social.technet.microsoft.com/Forums/lync/en-US/9ceafb38-24dc-466c-b497-2cee062b81cf/explorer-view-hidden-folder-attribute?forum=sharepointgeneral
Thanks
Daniel Yang
TechNet Community Support

Explorer View - Your client does not support opening this list with Windows Explorer MOSS 2007 '

We recently had a major deployement, after which Explorer View started giving error message.
Before deployement, all was working fine.
Error: Your client does not support opening this list with Windows Explorer
Webclient service is already enabled.
The site has been added to trusted site lists.
All Active-x controls have been enabled.
Browser: Internet Explorer 8 - 32 bit.
Microsoft Office 32 bit is also installed.
Thanx in advance.

You could try updating the following registry key on a client PC as a test: HKLM\System\CurrentControlSet\Services\WebClient\Paramenters\AuthForwardServerList to include the URL of your sharpoint site. Add the root site and it might enable this functionality.
Steven Andrews
SharePoint Business Analyst: LiveNation Entertainment
Blog: baron72.wordpress.com
Twitter: Follow @backpackerd00d
My Wiki Articles:
CodePlex Corner Series
Please remember to mark your question as "answered" if this solves (or helps) your problem.

Windows Explorer View, Server 2012 and WebDAV

I am using SharePoint Server 2013 on Windows Server 2012. I cannot get Windows Explorer View working from client machines on this server. These machines are Windows 8, running IE 10 (I am also having problems on my Windows 7 / IE 9 machine).
I have done everything on the client that I have read about (Trusted Site, the WebClient services, the patch mentioned in a Kb article), but to no avail.
The client machines CAN open Windows Explorer View on a SharePoint Foundation site that I have hosted on the internet, although in this instance they access the internet directly, rather than through the company network.
Therefore, I take it that my problem lies either on our SharePoint server, or somewhere in the network. The Proxy does not seem to be a problem as this is bypassed for local sites.
Somedody said for an earlier version of SharePoint that the WebDAV server role should be
disabled (which seems counter-intuitive). Does this make sense, or what else should I be looking at on either my server or in the network environment?

Thanks for the reply.
I get the standard 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 am not using HTTPS.
I do not think that the WebDAV is irrelevant on the server, as there are two separate things there:
Desktop Experience Feature, which installs the WebClient service to allow the server to use WebDAV, and
WebDAV Publiching Role under Common HTTP functions
Curiously, after removign the WebDAV Publishign Role, my Win7/IE9 pc (which is not logged on to my client's domain (although I access their network and use SharePoint in my browser) DOES allow Windows Explorer View.
The domain PCs do not allow it, still. They get challnged for a user name and password three times before they get the standard message. But, I did test a machine of their connecting to an internet-hosted website, and it could use Explorer View.

Issue with document library and explorer view

Hello,
I have couple of issues on which I need some assistance.
We recently backup and restore the SharePoint portal based on 2007 to SharePoint 2010 server.We're facing some issues on it now
When we try to open any office document from a document library it gives a prompt stating below message in image. I check the document, it is nowhere checked out and also I have full control on the site , in fact I am site collection admin.
Open with explorer view is not working. When we click on open with explorer it just refreshes the page and show the same page again.
Need help on this couple of issues.
Regards,
Mandar

In addition to Margriet her solution this article written by Amol Ghuge can help in troubleshooting problems with Explorer view:
http://sharepointknowledgebase.blogspot.nl/2013/09/open-with-explorer-is-disabled.html
- Dennis | Netherlands | Blog |
Twitter

Explorer View

A document library in SharePoint 2013 with over 10,000 documents when opened in Explorer view does not show any content. The message displayed in the browser is "the folder is empty". Explorer view works fine for other other
document libraries in the site with fewer documents. I want to move the documents from the document library to a File server share for archiving purposes. Any suggestions to address the issue will be appreciated.
Thanks
MP

I changed the List View Threshold for the Web App for the site that has the document library from 5000 to 30000 and now I can see content of the document library in Explorer view. I was able
to copy a document to a network drive using Explorer view. Once documents are moved from the Library root to Folders, I will change the setting back to 5000.
The following posting was helpful:
http://stackoverflow.com/questions/6093955/exceeds-the-list-view-threshold-5000-items-in-sharepoint-2010
On my PC, I had increased the value of
FileAttributesLimitInBytes.
Opening document library in Explorer view also worked from a PC on which I had not changed the value for FileAttributesLimitInBytes.
Thanks all for recommendations and suggestions.
MP

Sharepoint Revision History in Explorer View - Is it possible?

Similar Messages

Maybe you are looking for