Microsoft KB Archive/826888

From BetaArchive Wiki
Knowledge Base


Article ID: 826888

Article Last Modified on 4/20/2007



APPLIES TO

  • Microsoft Office Standard Edition 2003




SYMPTOMS

You may experience one of the following symptoms:

  • When you try to fill out a form on the SharePoint home page, Microsoft Office FrontPage 2003 may stop responding.
  • When you try to Save As or Publish data in Microsoft Office OneNote 2003, you may receive the following error message:

    Cannot find the URL URL, please check your typing

  • When you use a FrontPage template to create a one-page Web site, you may receive the following error message:

    An Internet Services for Windows (wininet) error occurred.

  • When you use Microsoft Office Word 2003 or Microsoft Office Excel 2003 to edit a document on a SharePoint document library, and then try to save your changes, the changes may not save to the same file that you opened, and the Save As dialog box may not appear.
  • When you try to use FrontPage to open a Web site, the Connecting to Web server dialog box opens, but FrontPage may stop responding.
  • When you try to use any Office program to open a document on a SharePoint Services document library, you may receive the following error message:

    Microsoft Visual Basic
    Run-time error '1177'
    The document name or path is not valid.
    Try one or more of the following:

    • check the path to make sure it was typed correctly
    • On the File menu, click Open. Search for the file using this dialog box


  • When you try to add a network place, you may receive the following error message:

    The folder you entered does not appear to be valid

  • When you try to add several pictures to a picture library, the Microsoft Office Picture Manager may not open, and you may not be able upload pictures.
  • When you try to open a Web site in FrontPage, you may receive the following error message:

    The following folder Folder_Path isn't accessible. The folder may be located in an unavailable location, protected with a password, or the filename contains a / or a \.

  • In Word, when you try to use File Open to open a document that is located on a network share, you are prompted with a Sign In dialog box. However, your pointer may remain as a Busy icon and not a Normal Select icon. As a result, you cannot type your credentials.


CAUSE

This problem may occur if you are trying to connect to a Windows SharePoint Services (WSS) server that has Secure Sockets Layer (SSL) enabled, and you have turned on the Check for server certificate revocation feature in Internet Explorer. When the Web Extensions Client (WEC) checks to see if the server's certificate is revoked, there is a communication problem between the SSL server and the WEC. If the certificate revocation information is not available, you receive the following error message from the SSL server:

ERROR_INTERNET_SEC_CERT_REV_FAILED.

Because WEC does not recognize this error code, an internal error occurs in WEC.

RESOLUTION

To resolve this problem, you must correctly install and configure SSL certificates on both your server and your client computer.

For additional information about how to set up SSL on you server and client computer, click the following article numbers to view the articles in the Microsoft Knowledge Base:

324069 How to set up an HTTPS service in IIS


203805 How to map a client certificate to a Windows NT user account


299875 How to implement SSL on a Windows 2000 IIS 5.0 computer


816794 How to install imported certificates on a Web server in Windows Server 2003


299525 How to set up SSL using IIS 5.0 and Certificate Server 2.0


298805 How to enable SSL for all customers who interact with your Web site in Internet Information Services


MORE INFORMATION

257587 Description of the server authentication process during the SSL handshake


257591 Description of the Secure Sockets Layer (SSL) handshake


STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Keywords: kbstoprespond kbsavefile kbopenfile kberrmsg kbbug KB826888