Microsoft KB Archive/184709

From BetaArchive Wiki

Article ID: 184709

Article Last Modified on 1/22/2007



APPLIES TO

  • Microsoft Project 98 Standard Edition



This article was previously published under Q184709

IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry


SYMPTOMS

In Microsoft Project 98, when you save a project that contains links to another project, you may receive one of the following error messages.

In Windows 95

This program has performed an illegal operation and will be shut down.

If the problem persists, contact the program vendor.

When you click Details, you receive the following error message:

WINPROJ caused an invalid page fault in module WINPROJ.EXE at <address>.

In Windows NT

An application error has occurred and an application error log is being generated.

WINPROJ.EXE
Exception: access violation (0xc0000005), Address: <address>.

CAUSE

This behavior occurs when the registry setting Store Net Names is set to No and you save to a network location a project that contains cross-project links, an inserted project, or shares resources from another project.

NOTE: To view the Store Net Names setting, follow these steps:

  1. On the Windows Start menu, click Run.
  2. Type Regedit.exe, click OK.
  3. In Regedit, expand the following subkey (folder) in the left pane:

        HKEY_CURRENT_USER\Software\Microsoft\Office\8.0\MS Project\Options\Save
                            

    The Store Net Names setting is in the right pane.


WORKAROUND

To work around this behavior use the method appropriate for your situation.

Method 1: Use a Local Disk Drive

Save all projects that contain the cross-project links, inserted projects or that share resources from another project, to a local disk drive. Be sure to save all projects that are related, to the same disk drive.

Method 2: Change the Registry Setting Store Net Names from No to Yes

NOTE: Microsoft Project requires this option to save files to some types of networks.

  • If your network allows you to use Universal Naming Convention (UNC) paths to map to network servers, then you can change the option to Yes. An example of a UNC path is \\ServerName\ShareName


  • If your network requires you to use drive letters to map to network servers, Microsoft Project likely needs the option to be set to No. So this workaround may cause Microsoft Project to fail when saving a project to a network drive.

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.


To change the Store Net Names registry setting from No to Yes, follow these steps:

  1. Quit Microsoft Project if it's running.
  2. On the Windows Start menu, click Run.
  3. Type Regedit.exe, click OK.
  4. In Regedit, expand the following subkey in the left pane:

        HKEY_CURRENT_USER\Software\Microsoft\Office\8.0\MS Project\Options\Save
                        
  5. Double-click the Store Net Names icon in the right pane.
  6. Change the Value Data from No to Yes. Click OK.
  7. On the Registry menu, click Exit.


STATUS

Microsoft has confirmed this to be a problem in the versions of Microsoft Project listed above.

This problem was corrected in Microsoft Project 98 for Windows, Service Release 1 (SR-1).

For additional information about obtaining and installing SR-1, click the article number below to view the article in the Microsoft Knowledge Base:

185102 PRJ98: How to Obtain and Install MS Project 98 SR-1



Additional query words: crash crashes crashing crashed quit quitting quits fail fails failing failed break

Keywords: kbbug kbenv kberrmsg kbfix KB184709