seeing error message "the loading of a shared library failed. ..." after attempting to export bdf for a part or whole model.

Hi TJ,

 

Are you able to provide a database which produces this problem? We will have to investigate it. My intial investigations did not reveal anything. If you don't like to post the database here, you can send it to mscapex.support@mscsoftware.com.

 

Thanks,

Sanjay.

Hi TJ,

This seems like a PATH issue

1) Can you export bdf out of a simple model?

2) Were you able to export bdf before you installed Jaguar?

3) Did you have any other recent updates besides Jaguar on your system?

Here are my answers:

1) Can you export bdf out of a simple model? No. I tried a model that worked in IL and it failed.

2) Were you able to export bdf before you installed Jaguar? Yes, see 1)

3) Did you have any other recent updates besides Jaguar on your system? Probably. Here is my installation history…



If this is a path issue is there a quick fix? My PC is WIN7 Pro 64bit SP1. My colleague who has Jaguar installed on WIN10 does not have this issue.

-TJ

Mahmud,

I tried the export with a trivially simple model that works in APEX IL (1 part - small mesh and some RBE's) and it fails, so the issue is probably not model-related.

 

this is my path currently : 

C:\MSC.Software\Patran_x64\20180\bin;%INTEL_DEV_REDIST%redist\ia32_win\mpirt;%INTEL_DEV_REDIST%redist\ia32_win\compiler;%INTEL_DEV_REDIST%redist\intel64_win\mpirt;%INTEL_DEV_REDIST%redist\intel64_win\compiler;C:\ProgramData\Oracle\Java\javapath;C:\Program Files\Microsoft HPC Pack 2012\Bin\;C:\Program Files\Microsoft MPI\Bin\;C:\Program Files (x86)\Intel\iCLS Client\;C:\Program Files\Intel\iCLS Client\;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Program Files (x86)\RSA Security\RSA SecurID Software Token\;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Microsoft Compute Cluster Pack\Bin\;C:\MSC.Software\Marc\2014.1.0\marc2014.1\tools;C:\MSC.Software\Marc\2014.1.0\marc2014.1\bin\win64;%systemroot%\System32\WindowsPowerShell\v1.0\;%systemroot%\System32\WindowsPowerShell\v1.0\;C:\Python27;C:\Program Files\MSC.Software\MSC CoSim\1.6;C:\Program Files\MSC.Software\MSC CoSim\1.6\cosim_redist;C:\Program Files\MSC.Software\Adams\2018_1\bin;C:\Program Files\MSC.Software\Adams\2019_2\bin

 

 

there was also a PATH BACKUP variable:

 

this was my PATH BACKUP value : C:\MSC.Software\Patran_x64\20180\bin;%INTEL_DEV_REDIST%redist\ia32_win\mpirt;%INTEL_DEV_REDIST%redist\ia32_win\compiler;%INTEL_DEV_REDIST%redist\intel64_win\mpirt;%INTEL_DEV_REDIST%redist\intel64_win\compiler;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\MSC.Software\Patran_x64\20170\bin;C:\ProgramData\Oracle\Java\javapath;C:\Program Files\Microsoft HPC Pack 2012\Bin\;C:\Program Files\Microsoft MPI\Bin\;C:\Program Files (x86)\Intel\iCLS Client\;C:\Program Files\Intel\iCLS Client\;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Program Files (x86)\RSA Security\RSA SecurID Software Token\;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Microsoft Compute Cluster Pack\Bin\;C:\MSC.Software\Marc\2014.1.0\marc2014.1\tools;C:\MSC.Software\Marc\2014.1.0\marc2014.1\bin\win64;%systemroot%\System32\WindowsPowerShell\v1.0\;%systemroot%\System32\WindowsPowerShell\v1.0\;C:\Python27;C:\Program Files\MSC.Software\Adams\2018_1\bin;C:\Program Files\MSC.Software\Adams\2019_beta\bin;C:\Program Files\MSC.Software\MSC CoSim\1.6;C:\Program Files\MSC.Software\MSC CoSim\1.6\cosim_redist

 

Have you disabled the DOS short names on your system?

 

If you list the Apex folder in DOS

 

"dir /X "MSC Apex""

 

you should have and output like

...

"13.01.2020 16:43   <DIR>         2019-6~3    2019-699173"

...

"2019-6~3 " is the short name that is required in DOS scripts.

 

 

 

 

here is what I see ...

resolved by searching C:\Windows\System32 for lib*.dll Found 2 that don't belong there per Mahmud. (libmmd and libifportmd) renamed these two dlls to dll_saved extension. This fixed the problem. Export of bdf now works.

 

We deliver libifportmd.dll & libmmd.dll but some other non-MSC application had apparently placed older versions of these dll's into C:\Windows\System32  . While copying dll's into customer's C:\Windows\System32 is a bad practice; Apex is trying to put safeguards around it but we have not covered all cases yet. We published the case with  libifcoremd.dll previously in a SimCompanion article https://simcompanion.mscsoftware.com/infocenter/index?page=content&id=KB8023348