Knowledge Base

WD6X: "Connect to File Server..." Error Choosing File Menu

Article ID: 139854

Article Last Modified on 11/21/2006


APPLIES TO


This article was previously published under Q139854

SYMPTOMS

When you click the File menu in Microsoft Word, you may receive the following Chooser message:
Connect to file server <server name> as guest or registered user.
If you click Cancel, you can continue using Word without loss of functionality. If you click an option other than Cancel, Word may stop responding.

This behavior occurs the first time you try to access the File menu during the current Word session. If you close and restart Word, you will get the error message again.

CAUSE

The Registration Database file is damaged or corrupted.

Microsoft has received reports that this error may also occur if you are using removable media, such as an optical or a Syquest drive.

RESOLUTION

To resolve this problem, remove and rebuild the Registration Database files. To do this, follow these steps:

  1. Quit any open programs.
  2. Copy the Registration Database and the PPC Registration Database files to a floppy disk. (These files are located in your System:Preferences folder.)
  3. Delete the Registration Database and the PPC Registration Database file from your hard disk.
  4. Open the Microsoft folder, which is located at the same level as the Word 6.0 folder.
  5. Double-click each program in the Microsoft folder to register it.
  6. Start Word to register it.
NOTE: Removing the Registration Database may remove critical information for other OLE applications. You may need to rerun Setup for Office 4.x, PowerPoint 4.0, Word 6.0, Microsoft Excel 5.0, and Works 4.0.

For additional information on rebuilding the Registration Database, please see the following article in the Microsoft Knowledge Base.

122378 MacWord 6.0: When and How to Rebuild the Registration Database


Additional query words: chooser network logon login prompt log unmount remote removable storage zip syquest ez unmounting shared connect appletalk hang crash

Keywords: kberrmsg kbbug kbenv KB139854