The Revit Clinic

Error 17

I want to pass along a technical solution and a bit of additional information to troubleshoot a licensing status some users have come across.  The most common cause of this “error 17” status is a corruption of the CascadeInfo.cas file.  This could occur where the workstation may have crashed, or where there was an event such as a power loss.  When this does occur the CascadeInfo.cas file is not properly closed out, and could potentially become corrupt.  The next time Revit is launched the file cannot be read resulting in the error, along with a floating licensing error.

Renaming or deleting the file will recreate it automatically the next time Revit 2010 products are launched.  In most cases this resolves the error status, but there are a few possible scenarios where the following troubleshooting technical solution should be helpful.   For example adding the FLEXLM_TIMEOUT variable has been known to resolve the status as well.  I have included the link below:

Revit 2010 error 17 license status troubleshooting

If after following the above process the issue persists please collect the requested files in the technical solution and log a support request or contact your reseller.

FNP_ACT_Installer.dll error when installing

When attempting to install your Revit 2010 product, you might receive the following error and the installation rolls back:

1: 5 2 Failed to Load FNP_ACT_Installer.dll. 3: 126

This error is caused by a conflict in a Macrovision DLL file on the machine, most often seen after installing AutoCAD 2010. To resolve the error you can do the following:

1. Download one of the following zip files, based on the Operating System that you are running:
   
   32 bit Vista/XP: Download FNP_Act_Installer_32_bit
   64 bit Vista/XP: Download FNP_Act_Installer_64_bit
   
   
2. Extract the DLL file to C:\Program Files\Common Files\Autodesk Shared\AdLM\R1, overwriting any existing version.

After replacing the DLL you should be able to install.

I'm a PC... and a Mac!

Now, Revit products will officially be supported by Autodesk for both Apple Bootcamp and the Parallels virtualized machine software.

I have been running Parallels for a while, and it is great to get all the power out of the Mac OS while still being able to work in Revit. 

Read the Offical Press Release

Here is a bit of it:

“SAN RAFAEL, Calif., Sept. 24 /PRNewswire-FirstCall/ -- Autodesk, Inc. (Nasdaq: ADSK), a leader in 2D and 3D design, engineering and entertainment software, and Parallels, a worldwide leader in virtualization and automation software, announced that they have signed an agreement to make Parallels Desktop for Mac Autodesk's preferred Mac virtualization software.

Autodesk will now support use of AutoCAD software, AutoCAD LT software, Autodesk Inventor Professional software, Autodesk 3ds Max software, Autodesk 3ds Max Design software and the Autodesk Revit software platform for building information modeling (BIM) on Mac OS X via Parallels Desktop. Autodesk added official support for these products on the Mac via Boot Camp earlier this year.”

Hope you enjoy the option of being a PC and a Mac!

A few updates

Hi Everyone,

No, I haven't disappeared of the face fo the earth.  Its been a busy few months here at the Factory along with some weeks of vacation, a wedding (not mine), moving into my first home, and just generally trying to stay above water.  Then of course, there is our 8 month old puppy, Moose.

But enough of the excuses.  Now to catch up.

I have a few updates that I wanted to make sure that I shared with you in case you haven't seen them yet.   They occurred over the last few months, but I wanted to call them out here.   Make sure that you check out the following solutions:

Support for Revit 2010 products and Windows 7

Revit Network License Troubleshooting

As well, make sure you check out the first Hotfix we have released for Revit 2010 products:

Hotfix - Crash when deleting or modifying walls

Hopefully, the solutions and the hotfix can help answer some questions you may have and solve some problems. 

Oh yeah, I almost forgot, Go Pack Go!

Investigate Product Stability Issues

Check out this new video solution that I just finished about troubleshooting and investigating pesky product stabilty problems (ie crashing) in Revit.  Hope you like the video. 

10 Linked \ Imported File Tips

Continuing the series of 10 quick tips, here are some topics for linked or imported files.  Please note any videos included below are for workflow reference and do not contain sound…

1.  TAB select \ copy linked objects

You can toggle object selection through a linked file using the “TAB” key to select, and open Element Properties as needed to view the object information.

Along with this, once selected you can copy & paste the object directly from the link into the host file using the clipboard copy and paste tools: Video Example

2.  Hosting component families on a linked file

Component families need to be of “face-based” type in order to detect a linked model as a host.

3.  Revit links instance count

For each instance of the linked file, Revit adds a number under "Revit Links" when expanded so they may be individually toggled for overrides: Video Example

4.  Deleting all instances of a linked file

If all instances of a linked file are deleted you should receive a warning.  However the link reference still appears in Manage Links, and can be unloaded \ reloaded.  If the file is reloaded and it is still not visible, there may not be any active references in the project and it should be removed \ re-inserted: Video Example

5.  Hide elements in view

You can hide portions of a linked Revit or CAD link as needed using the “TAB” key to select objects >Hide in View > Elements.  For a CAD file, select the instance > Query > Delete or Hide in View: Video Example

6.  Central file or local file link?

When linking a Revit project file into a host project, ensure the link was last saved as a central file.  Links that are considered local files will check for a related central file as they are loaded.  This can cause a performance hit which can be avoided by ensuring all links are central files.

7.  2 mile warning on import

If you receive the “Revit cannot import because it will create a Revit model that is larger than 2 miles across” warning and the CAD file contents are within 2 miles in size, there are 3 items to verify:

1.  Turn on all layers in the AutoCAD file and zoom extents to ensure there are no stray objects.
2.  Not only check a top view in AutoCAD but also open an elevation and 3D view to ensure the entire model placement is within a 2 mile area.
3.  If the CAD file contains AEC objects, ensure to set PROXYGRAPHICS to 1 in the CAD file.  This can reduce the occurrence of this warning when these objects are present to ensured they are properly displayed.

8.  View annotation through a linked file

If the linked file contains annotation such as room tags or dimensions, and you wish to show this in the host project, set the “Visibility \ Graphic Overrides” to “Linked View” or “Custom”: Video Example

9.  Selectively toggle linked files in a schedule view

You can toggle visibility and of linked files in a schedule table view: Video Example

10.  When to split apart your Revit project file?

There is a good explanation in our Model Performance Technical Note regarding when to split apart your project file which I have included below:

Consistent customer practice is to break up a large model into multiple files of about 160 MB each for
32-bit Revit, or 200 MB for 64-bit Revit, then link together the resulting project files. Such a procedure
will work best if the user can work on one file while the other links are unloaded for a majority of the
time.