internal error - 'can't load child loader...'

Hello,
I just installed NW manage 2015 (service pack 2) from the NW page and it seems have been successful. I am able to load/open .nwd files just fine.
however when i attempt to open/merge/append an acad MEP 2011 file, i receive the following (see attachments) error message;
"...handle serverity (eERROR) component....can't load child loader from lclddwg2014.dll"

This is an error I haven't seen yet in my 4+ years of using navisworks...any and all help will be greatly appreciated.

my machine stats:
HP elitebook
Windows 7 64-bit
4gb ram
Intel i5
running a healthy acad MEP 2011 for over 3 years now...


Thank you!
-md

You likely need to change the DWG Reader version in the Navisworks settings. This determines (among other things) which vertical version it interprets the content as. If you did a straight install without touching the Options its likely still set as 2015, which is going to be different than your installed 2011 content and enablers.

I did find the 'dwg loader version' setting in the options editor dialog, changed the setting to each version listed (my list shows 2008 to 2015) and it still fails to load... i wonder if the 2015-install contains a missing and/or rogue .dll(s) that is causing this behavior.
i'm surprised no one else has encountered this.

Thanks for your info though!

Michael, did you find a resolution for this? I am having the same error when trying to open DWG files in Navisworks Simulate. The DWG is in a 2013. I've tried files from both AutoCAD 2013 and AutoCAD 2015, I get the same error. I've run a repair on Navisworks, which doesn't seem to help. I am currently trying to install Naviswoks 2015 to see if that'll be better.

hello!
no, unfortunately i was not able to get this resolved. which is too bad.
my workaround is to export to .dwf , jump through the 'transform' hoops in order for the model to have to right orientation, append to nw 2015. i'm using 2015.
hopefully autodesk will address at some point and i'm surprised there haven't been more installs encountering this issue.

hope this helps!