Stump the Panel

SharePoint QA

Stump the Panel » End Users and Information Workers

1. 

   SharePointCurious
   Member

   (Note: these issues arise regardless of whether the document is opened from the library or via a direct link.)

   When a user clicks on a .docx document in one of the libraries, a new IE window opens and the user is prompted to open/save. If the user selects Open, the toolbar icon for MS Word (if open) flashes and nothing else happens.

   If the user clicks Save, the document saves to the location specified by the user. However, if the user double-clicks on the document to open it, the following message appears in Word: "[File name] cannot be opened because there is a problem with its contents." If the user clicks the Details button for more information, he/she is told "The file is corrupt and cannot be opened." However, if the user now selects the Open button, he or she is given the option to recover the contents of the document. The document then seems to open normally.

   With .doc files, a new IE window opens, and the user is prompted to open/save. If the user chooses Open, word flashes and the user must know to go to Word in order for the document to open--a minor annoyance (training issue).

   PDF files open normally in another window.

   Posted 1 year ago #
2. 

   AutoSponge
   Administrator

   What type of authentication does your site use?

   Was 'Enable Client Integration' set to Yes for that authentication method?

   Posted 1 year ago #
3. 

   SharePointCurious
   Member

   Thanks for the speedy response!

   On authentication: we are using NTLM-based authentication, and client integration is enabled. In this environment, IIS is configured by MOSS to utilize Integrated Windows Authentication. This is the only way that we can get IE to pass user credentials automatically. Using any other browser will force the user to authenticate.

   Posted 1 year ago #
4. 

   Chris Quick
   Moderator

   If you are using Firefox, you can allow NTLM to authenticate properly. Follow these steps to allow authentication with Firefox:

   1. In the address bar, type about:config
   2. In the filter bar that appears, type ntlm
   3. Locate network.automatic-ntml-auth.trusted-uris and double-click.
   4. Type all of the URL's you wish to automatically authenticate against separated by a comma (i.e. http://mysite.sharepoint.com, http://intranet.sharepoint.com).
   5. Click OK
   6. Navigate to your site to verify the functionality.

   Chris

   Posted 1 year ago #
5. 

   AutoSponge
   Administrator

   Are you using Vista and/or IE7?

   Is your site a Trusted location in IE?

   Posted 1 year ago #
6. 

   SharePointCurious
   Member

   We're using Windows XP and IE 7. (The site hasn't yet been set up for Firefox compatibility.)

   The site (with urls both http:// and https://) has been added to trusted sites. The trusted sites have been configured to allow automatic login with current user name and password.

   Posted 1 year ago #
7. 

   AutoSponge
   Administrator

   Does the user have Office 2003 or 2007 installed?

   Posted 1 year ago #
8. 

   SharePointCurious
   Member

   Office 2007.

   Posted 1 year ago #
9. 

   AutoSponge
   Administrator

   SharePointCurious,

   I'm not going to admit being stumped yet but you seem to have all the right configurations in place. I have a couple questions that relate to the files/machines you're testing with and one more about the server.

   Server:
   - Are you using Port 80 (default HTTP) or 443 (default SSL) for the site in question?

   File/machine:
   - Are you testing with Word, Excel, or other?
   - Do any of the files have password protection?
   - Does this happen for all users?
   + If yes, can you test on a different build (like IE6, different network, etc.)?
   + If no, who has this working and what is different?
   - Are the files in 2007 (e.g., .docx) or 2003 (e.g., .doc) format?
   - Are you running the client application in compatibility mode?
   - Has cookie handling been overridden in the browser (under Privacy > Advanced)?

   Posted 1 year ago #
10. 

    SharePointCurious
    Member

    Thanks for all your help on this. Feel free to punt on this one--it's a doozy, for sure. Quick answers to your questions:

    Server:
    - Are you using Port 80 (default HTTP) or 443 (default SSL) for the site in question?

    Not immediately sure.

    File/machine:
    - Are you testing with Word, Excel, or other?

    Word, Excel, PowerPoint....

    - Do any of the files have password protection?

    Nope.

    - Does this happen for all users?

    All folks we've tried....

    + If yes, can you test on a different build (like IE6, different network, etc.)?
    + If no, who has this working and what is different?

    Yup, we'll be trying this....

    - Are the files in 2007 (e.g., .docx) or 2003 (e.g., .doc) format?

    .docx. .doc works fine, so for the moment we're just having everyone Save As to that format.

    - Are you running the client application in compatibility mode?

    No.

    - Has cookie handling been overridden in the browser (under Privacy > Advanced)?

    Nope.

    Posted 1 year ago #
11. 

    AutoSponge
    Administrator

    QUOTE:
    "- Are the files in 2007 (e.g., .docx) or 2003 (e.g., .doc) format?

    .docx. .doc works fine, so for the moment we're just having everyone Save As to that format."

    That seems really odd to me. You may want to focus on the Office folders of your client machines. In some cases of upgrades I've heard of people having certain DLLs still being used from the 2003 version. Can you test on a computer with Office 2007 that was not upgraded from 2003?

    Also, does the document library have "Display as a Web page" selected under Advanced? If it does, turn that off and try again. There is an HttpHandler that transforms .docx to HTML and if yours is having problems, we want to test without it in the way.

    Posted 1 year ago #
12. 

    SharePointCurious
    Member

    Both great thoughts.

    Just tried uploading/downloading from a machine that has Office 2007 but did not upgrade from 2003. No dice.

    Checked the document library, and "Display as a Web Page" is not selected.

    Let me spend some more time with our developers and see what we can come up with. Thanks for all your help!

    Posted 1 year ago #
13. 

    AutoSponge
    Administrator

    SharePointCurious,

    This is really sounding like an IIS issue.

    You didn't know what ports were being used, I'll go ahead and say that the client applications (like Word) only know how to use default ports. If you have the default ports closed at the server's firewall it will block webdav access from the clients.

    Can you get other webdav features working? Like can you view a library or list from Word?

    Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.