Solved

Unable to open Word .doc/docx from Sharepoint 2007

Posted on 2010-08-18
8
2,007 Views
Last Modified: 2012-05-10
Windows Server 2003 (32-bit, Standard, SP2)
Citrix PS 4.5
Office 2003 Pro (2007 converters installed)
Sharepoint 2007
Internet Explorer 7

Hi,

Using the above setup, none of our users can open .doc files from within Sharepoint and .docx files can only be opened in read only mode within IE.

Attempting to open a .doc file results in Word opening with a blank screen, i.e. no document displayed and no blank template.  If Word is left open in this state and the .doc file is opened again from within Sharepoint, the following error is displayed:

Compile error:
Syntax error

The macro in question is as follows (with the 4th line highlighted):

Private Sub TmpDDE()
WordBasic.AppShow
Rem _DDE_ReadWriteOnSave
WordBasic.FileOpen Name :=, Revert := 0
End Sub

I've managed to work out that it is using the following file association registry key to call Word:

HKEY_CLASSES_ROOT\Word.Document.8\shell\OpenAsReadOnly

I've compared this key to a working XP Pro machine with the same versions of Office and IE and they're absolutely identical.

I've figured that the following DDE command is what should be passing the file path to Word as "%1", but is failing and passing blank details instead:

[AppShow][REM _DDE_ReadWriteOnSave][FileOpen .Name="%1",.Revert=0]

Googling this issue returns a handful of results with people suffering from the same issue, but no resolution details.  Does anybody know what may be causing this problem?

Cheers

0
Comment
Question by:WelshPretender
  • 4
  • 4
8 Comments
 
LVL 61

Expert Comment

by:gheist
Comment Utility
0
 

Author Comment

by:WelshPretender
Comment Utility
Hi,

While this problem applies to .docx files too, it is a bigger problem with .doc files, so the IFilters won't have anything to do with the issue.

Cheers
0
 
LVL 61

Expert Comment

by:gheist
Comment Utility
interop assembles for office 2003?
0
 
LVL 61

Expert Comment

by:gheist
Comment Utility
0
Free Trending Threat Insights Every Day

Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

 

Author Comment

by:WelshPretender
Comment Utility
I've had a look around and can't see anywhere that states SharePoint uses the interop assemblies when opening documents.  However, this got me thinking ...

SharePoint uses the sharepoint.opendocuments class to open files within a document library.  This class is loaded by owssupp.dll.  We have just one copy of the file within the Office11 directory (19/04/2007  14:10  99,680 bytes).

According to an article - http://www.sharepointvoodoomagic.com/ - opening any SharePoint document library within IE should load the SharePoint Open Documents class.  Going to ... Tools > Manage Add-ons > Enable or disable add-ons > Addons currently loaded in IE ... should display the class.  However, I can't see this on our servers or the working XP machine I'm using.  I'm guessing this article is a bit of a red herring.

I've unregistered and re-registered owssupp.dll, receiving the apparently benign and ignorable "DllRegisterServer in C:\Program Files\Microsoft Office\OFFICE11OWSSUPP.DLL failed. Return code was: 0x80070716" error, but still no joy.

Any thoughts?

Cheers
0
 
LVL 61

Expert Comment

by:gheist
Comment Utility
sharepoint is in .net and uses dcom ....
that hints me ...
0
 

Author Comment

by:WelshPretender
Comment Utility
I've installed the interop assemblies, but still no joy I'm afraid.

I'm now convinced that the issue has something to do with the owssupp.dll.  The link within SharePoint uses DispEx() onclick, which apparently should give the 'Open read only/Edit' radio button options.  However, I only get a warning about opening files from IE.

Is there any way of confirming whether this dll has been registered and is functioning correctly?

Cheers
0
 

Accepted Solution

by:
WelshPretender earned 0 total points
Comment Utility
I found the problem in the end.  The following registry key was missing:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\WINWORD.EXE

I copied the key from another machine and now all is ok.

Cheers
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Recently Microsoft released a brand new function called CONCAT. It's supposed to replace its predecessor CONCATENATE. But how does it work? And what's new? In this article, we take a closer look at all of this - we even included an exercise file for…
Using Word 2013, I was experiencing some incredible lag when typing.  Here's what worked for me....
This video shows and describes the main difference between both orientations in Microsoft Word. Viewers will understand when to use each orientation and how to get the most out of them.
The viewer will learn how to make their project stand out over others by learning how to change colors and shapes, add spaces, change directions, and add bullets to their charts.

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now