We recently migrated our WSS 3.0 SP2 implementation to new WFEs on Windows Server 2008 R2 64-bit. Before doing that, the WFEs were running on Windows Server 2003 R2 32-bit. I did not change the version of WSS in this process. Same version and same build. The method that I used was simply adding the 64-bit servers to the farm and then removing the old 32-bit servers. Everything works great ... except: We had unblocked the mdb file extension a long time ago allowing users to store Access Databases in their document libraries. There was no problem with using the database as long as the users knew that they when they needed to work with the databases that they would need to do so using Explorer View. I just found out (a couple of weeks after the migration) that user can no longer work with their Access Databases in Explorer View. If they try to access an Access Database through Explorer View they get the following error: "Microsoft Office Access can't find the database file '\\mysite.com\ceo\my database.mdb.' Make sure you entered the correct path and file name." I had the users try to map a network place to the same location and using the network place they get a different error: "Microsoft Office Access is unable to open the data access page The file does not exist, or you do not have read access to the file." The users access has not changed. The users desktop O/S have not changed (XP). I have Windows 7 on my workstation. When I try to access the mdb file from Explorer View nothing happens. I get an hour glass then nothing. I've checked both workstation and server Event Viewer and found nothing reported. I would appreciate any assistance. ----------------------------------------------------------

You may want to check the web client service on the machines. It should be in a started state.

Thank you The WebClient service on the Windows 7 computer is turned on (started | automatic). I will check with the XP user to see if they have theirs turned on. Thank you for the quick reply.

Is the WebDAV Publishing Role in Windows 2008 enabled? If so, disable. For SharePoint to work with WebDAV IIS7's WebDAV must be disabled. tk

The WebClient service is in a started | automatic state on both the XP workstation and the W7 workstation. Both WFEs report that the WebDAV Publishing role is "not installed." Thank you for your help with this. I don't understand why mdb files seem to be the only ones affected. I appreciate any help.

Which version of Office (specifically Access) are they using? I have all kinds of problems with the Office 2010 betas doing this kind of stuff. tk

They have an Access 2000 database out there. This is the one that they were having an issue with. I have since put Access 2003 and Access 2007 databases out there and we have the same issue with all three so I assumed that it was not version specific. I do wonder if there is some security update from Microsoft on either the Windows 2008 R2 server or the XP desktop that prevents opening Access databases through WebDAV.

Hi, Please try to install this hotfix:http://www.microsoft.com/downloads/details.aspx?FamilyId=17C36612-632E-4C04-9382-987622ED1D64&displaylang=en By the way, this whitepaper provides general as well as troubleshooting information on using the Explorer View of Windows SharePoint Services. Hope it will be helpful to you.Whitepaper - Understanding and Troubleshooting the SharePoint Explorer Viewhttp://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=c523ac7a-5724-48be-b973-641e805588f4 Thanks & Regards.Lily Wu

No, that is not the answer.I have not replied because the change that you suggested was a workstation change. Workstations, in our company, are not supported by IT. We have to put in a ticket with Finance and wait for them to implement the change.The hotfix was not present on the workstation. Finance applied the hotfix and restarted the client to no avail. We are already familiar with the whitepaper you supplied and it is not helpful at this time.We've decided to open a ticket with Microsoft for this issue.

Hey, I don't know if you already have this resolved, but I ran into a similar problem today and figured I'd post my findings. Perhaps this will be helpful. From what I can tell, when running SharePoint on top of IIS 7, Access files (MDB) get blocked at all three layers of the service stack: IIS, ASP.NET, and SharePoint. So simply removing them from the blocked file list in the SharePoint Central Administrator isn't enough -- both IIS and ASP.NET still have mechanisms that get in the way. Disabling IIS MDB Blocking To stop IIS from blocking MDB files, I had to fire up the IIS Manager MMC snap-in and browse to the site that was mapped to my SharePoint web application. I double-clicked on the "Request Filtering" icon and saw that the ".mdb" extension was listed as not allowed. The first thing I did was right-click on the ".mdb" entry and select "Remove...". Then, for good measure, I clicked on the "Allow File Name Extension..." link and added ".mdb", which then explicitly listed the ".mdb" extension as allowed. Disabling ASP.NET MDB Blocking Stopping ASP.NET from blocking MDB files was a little tricker. The default web.config file for all web sites (defined in %System%\Microsoft.NET\2.X.X.XXXXX\CONFIG) contains the following HTTP handler entry that effectively blocks the downloading of MDB files: <add path="*.mdb" verb="*" type="System.Web.HttpForbiddenHandler" validate="True"/> This can be overridden in the web.config file for your SharePoint web application by adding the highlighted line to the httpHandlers section: <httpHandlers> <remove verb="*" path="*.mdb" /> <remove verb="GET,HEAD,POST" path="*" /> … </httpHandlers> After taking those three steps -- unblocking MDB files in SharePoint, IIS, and ASP.NET -- I was finally able to get it to work. *whew* Another day in the office...

This solution worked for us as well. Thank you very much :-)