Introduction


When you open Office documents from a website you may experience odd behaviors that you wouldn't normally see opening other files that are not related to Office or would not notice if you were opening the documents from the local file system or a network share. Common issues involve clicking on a hyperlink to an Office document in a webpage and seeing an
authentication prompt and not expecting one or files opening read-only when you are expecting to be able to edit them.

This article describes what to look for and basic troubleshooting steps you can perform on the client machine and even some tips on what to look for on the web server side (or web application side) as well.

Understanding More


One important distinguishing piece of information to understand is the differentiation between going to just a plain web server such as IIS or Apache with static web pages or accessing a file from a web application or web solution such as SharePoint because SharePoint handles things like WebDAV itself and uses certain protocols like WebDAV and FrontPage RPC or FPRPC for short. The reason it's important to know the difference is because you may not think (or want or have rights) to look on the server side.

That's why the server information is important to collect right away. A networking trace just off the client sometimes can tell you the type of server and many times even the web application in the responses from the server.

But that's getting a little ahead of ourselves, especially if you don't know how to read network traces or know anything about HTTP. But that's not hard to learn and is good if your job involves troubleshooting network problems.

This article mainly targets opening Word, Excel, and PowerPoint documents from a web server. And in many scenarios Visio and Publisher documents as well. OneNote has a known issue with SharePoint sites where requiring check-out or requiring columns on the document library will cause synchronization to fail in OneNote. The only way around that is to disable that setting in the SharePoint document library settings.

The main issues I'm targetting are focused on opening Office documents from a server with authentication prompts or as read-only. But that doesn't mean these steps won't help diagnose and resolve other integration issues with Office and a web server. Think of this as a general practice guide for troubleshooting Office interacting with a web server.

Related Knowledgebase Articles


*MSDAIPP (aka Rosebud) was the WebDAV protocol provider in Windows XP but it also ships with Office. However, in Vista and Windows 7 it uses WebClient as the WebDAV protocol provider. So only consider using 2459200 if the client is running Windows XP.

Environment Information to Collect and Document


What is the environment like? This information is important to collection and document to help IT and support staff troubleshoot the cause of the problem.
  • Server OS version and service pack
  • Web application, if any
  • Client OS version and service pack
  • Office version and service pack
  • Authentication on server (Integrated Windows authentication, anonymous, forms based authentication)
  • Is anonymous authentication enabled?
  • Does the server have SSL enabled? (https://)
  • Any intermediate devices such as proxy servers, gateways, load balancers, or other network appliances the client has to traverse through to get to the server and vice versa?
  • Web browser (Internet Explorer, FireFox, Safari, Chrome) used if opening from webpage (as opposed to from Office application (File/Open)

Troubleshooting Questions and Actions to Take

  • Understand (clarify) and define the problem and scope (how many clients affected, how many users, servers, locations, internal, external)
  • Search our knowledgebase http://support.microsoft.com/ for known issues.
  • When did the problem start? Has it ever worked?
  • What's the impact/severity?
  • Force a repair of Office or other standalone Office application on the client from Control Panel/Add or Remove Programs (now Programs and Features in Vista/Windows 7) May require a reboot.
  • Is the site you are trying to access from the client an intranet name or FQDN? http://servername/ or http://servername.contoso.com/?
  • Is the WebClient service enabled on the client machine? What is the startup type (Disabled, Manual, Automatic)? Is the service started or stopped? If disabled set to Manual.
  • Do you need to be able to edit the document? Or is opening as read-only fine?
  • Are the workstation (client) and user in the same domain as the web server? If not is there a domain trust?
  • Is the site added to Trusted Sites zone in Internet Options on the client? If not, add it and see what happens.
  • How are you trying to open the file from the client? From a webpage, from Windows Explorer (WebDAV), from the Office application itself?
  • Do you have permissions to the file on the server? In the web application?
  • Is Windows Firewall enabled on the client or server? Try disabling on both.
  • Are there any other Office versions installed on the client machine? Such as Visio, Project, or SharePoint Designer, or standalone application such as Office Standard 2010 with Access 2010? Mixed versions like Office 2003 with Visio 2007 or Office XP with Office 2010? This can cause problems with SharePoint since Office installs client side components for SharePoint integration such as the Upload Multiple Documents ActiveX control.
  • Is WebDAV enabled on the server? This doesn't apply to SharePoint because it handles WebDAV itself. You don't need to and shouldn't install WebDAV on the web front end in IIS. Doing so can cause problems, mainly opening files in edit mode.
  • If SharePoint, is Client Integration enabled or disabled in the web application's authentication settings?
    • What is Browser File Handling set to in the web application settings? Permissive or Strict?
  • Is URL Scan installed on the server?
  • Disable anti-virus and test. If possible, uninstall anti-virus and test.
  • Disable any client-side firewalls
  • Check proxy settings in Internet Explorer (Tools, Internet Options, LAN settings). Try toggling Automatically detect settings. Try manually setting a proxy and adding an exception in Advanced proxy settings.
  • Get a network trace of the problem from the client using a network capture tool such as Network Monitor or Wireshark. If site is over SSL it's better to get a Fiddler trace because it has the option Decrypt SSL Traffic.
  • Run Process Monitor on the client and capture events during the problem.
  • Disable any 3rd party service and startup applications using MSConfig.exe, restart and test.
  • It may be necessary to get a simultaneous network trace from both client and server.