Revit 2017. When closing a file Revit stops working

[cao]

Hi,

Recently we have an issue with Revit 2017.

When we close a .rvt or .rte file then Revit stops working and closes. If there are more than one file open in a session there is no opportunity for saving the changes of any file.

This doesn't happen with .rfa files.

We get this message:

Best regards,

Rafael

[claudio.chaverri.sievert · Accepted solution]

Please check and report the following:

1. Is Revit updated?  Last update for Revit 2017 is version 2017.2 (Build version: 17.0.1117.0) .
2. If Add-ins are installed into Revit, does the crash continue with all add-ins disabled?
3. Is the issue specific to a particular project?
4. Is the issue specific to a particular user account? (e.g. create a new Administrative account and retest)
5. Is the issue specific to a particular workstation?
6. Is the issue specific to a particular workflow (this can be a bit trickier to identify, but if a user encountering the issue goes to another workstation and finds the same issue (on a system that wasn't previously seeing an issue), this could indicate there is something different in their workflow)?
7. Does the crash occur when the system is put into a simplified startup environment? How to perform a selective startup in Windows
8. Then please upload a journal file.  If there are other machines involved, please upload and distinguish them (i.e. journal.00x.txt.pc1, 2, etc.)

   These are text files that can be used to troubleshoot technical problems with Revit products.
   These files are stored in the following folder:

                               %LOCALAPPDATA%\Autodesk\Revit\<Product name and release>\Journals                                                                                                 

   Please Note: By default, the AppData folder is hidden in Windows. If you have trouble finding the journals folder, please review this document on unhiding folders.

[cao]

Thank you very much,

We will check all these points and will send you the report.

Best regards,

Rafael

[Viveka_CD]

Thank you @claudio.chaverri.sievert the list you provided is helpful for checking and reporting errors.

Hi @cao

One or more of the following lines are found in the journal file recorded by Revit prior to the program closing:

• DBG_WARN: failed to open message_queue named 'Session#####_P0MasterQueue' because The system cannot find the file specified.: line 203 of NOBLE\ManageWorkerServices.cpp
• DBG_WARN: failed to create message_queue named 'Session####_P0MasterQueue' because boost::interprocess_exception::library_error: line 203 of NOBLE\ManageWorkerServices.cpp

Causes:

There is a missing or incorrect registry key.

Solution:

Set the correct value for the affected registry key

Note:

• (Problems caused by improperly editing the Windows registry could render your computer operating system unusable.)
  Microsoft provides a wealth of critical information that you need to know about the registry in the Microsoft Knowledge Base at http://support.microsoft.com.
• Use the Microsoft® Registry Editor only at your own risk and only after backing up the registry as well as the system.dat and user.dat files as outlined for your operating system in the Microsoft Knowledge Base and in the related solution, TS66513. Additional information about the registry is also contained in the Help topics in the Microsoft Registry Editor.

Steps to follow:

• Run REGEDIT from the Start menu and then browse to the following key:

HKEY_LOCAL_MACHINE->Software->Microsoft->Windows->CurrentVersion->Explorer->Shell Folders

• Verify that the following key exists (within Shell Folders):
  Common AppData
  1. If the key does not exist create it (Right click -> New -> String Value)
  2. If the key exists (including having just created it from the step above) verify it contains the following Data (Right Click Modify):
     C:\ProgramData
• After making changes in the registry, reboot the system and retest.

Please mark this response as "Accept as Solution" if it answers your question to benefit other users looking for similar solutions. Kudos gladly accepted.

[fatih.kaplanoglu]

I had the same problem last week. Removing site designer solved my issue