Navisworks 2016 SP4 breaks Exporters - no solution?

[mdhutchinson]

Please see this post...

http://forums.autodesk.com/t5/navisworks-general-discussion/navisworks-2016-sp4-and-exporters/m-p/63...

Navisworks Previous Service Packs also included a SP for the Exporters... or direction to reinstall them after the update.

I went on this and installed the SP4 for Navis 2016. Exporters are now broken.

We would rather depend on NWNavigator for quick 3d coordination instead of having to take a netword license of Naviworks.

But now the Exporters are broken.

Autodesk... please post solution to this.

See the above referenced post and the attached screen shots. 

(I've tried a couple things including renaming the offending dll... the reinstall of the Exports after this, creates another offending dll that causes the same crash.

.NET version is 4.6.1

Please help!

[TravisNave]

Any particular reason you needed to install the service pack?  If it wasn't broken, why fix it? 

I can't remember the last time I installed a service pack for a product unless I was specifically experiencing a problem with the software addressed by the update. 

[mdhutchinson]

The only fix in the release that I care about is the loading of Revit files where it could cause Navis to hang up.

We are getting a couple issues with doing clash detection between Revit based elements and others where the model vanishes from the interface. I was hoping this might make things better.

For quite awhile NWNavigator worked badly, then we moved from 2014 AutoCAD MEP to 2016 and it seemed to straighten out. 

FYI: We just tried... Microsoflt .NET Framework Repair Tool.  This didn't work either.

https://www.microsoft.com/en-us/download/details.aspx?id=30135

[mdhutchinson]

No, I have no solution yet...

I have however rolled back the Navis install to Service Pack 3. This is the last one that allows the Exports, and NWNavigator to function after you reinstall them. I had to totally un-install Navis M, S, and the Exporters, then do a reinstall. This will work until Autodesk follows suite with what they've done in previous SPs.

Thanks

[yurikim]

It seems you have reinstalled to Navisworks 2016 and updated up to SP3. Could you explain more about the behavior that Navisworks Exporters were broken in AutoCAD MEP 2016? Was it a case you were unable to use NWCOUT command? 

[mdhutchinson]

This has happened for several releases now. You can see my older support Case ID: 08880249.. dated 10/19/2013.

NWNavigator is what triggered the bug. In previous versions a reinstall of the Exporters, assuming you have the right exe has fixed the issue in the past. (see http://usa.autodesk.com/adsk/servlet/ps/dl/item?siteID=123112&id=22003207&linkID=10382102)  

For some reason this link doesn't work any more.

NWNavigator runs NWCOut behind the scene. I pops the error and locks up AutoCAD.

I would assume the same error would happed if you ran NWCOut.

See the attached images.

[yurikim]

Please try to uninstall current Navisworks Exporter 2016 and install Navisworks Exporter 2016 (SP4) from here and see if this fixes:

https://lswebtest.autodesk.com/bre_download/media/?https://lswebtest.autodesk.com/bre_download/xml/e...

Hope this helps. Please let me know how it goes.