Hello guys, is there a way to access some kind of Microstation log when user encounters MDL loader error "OS could not load xx.dll" (error 127) ? Or do I need to manually find out with applications like ProcessMonitor? I was wondering, maybe Microstation keeps more detailed logs somewhere. I talk now about V8I version, but i suppose CONNECT has the same mechanism.
Thanks for the help
One more idea:
Lubo B said:MDL loader error "OS could not load xx.dll" (error 127)
If the application is native code application, I recommend to check all expected depdencies. Some "dependency walker" (like this one) can help to analyze whether all necessary dll (libraries) are available. But what can be tricky is when dlls are in different folders and MicroStation or Windows setting is involved in the dependency resolution.
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
I managed to fix it using Process Monitor logs. I saw that MS tried to load one of my dependencies from different folder than I wanted, causing this trouble. I thought editing MS_ADDINDEPENDENCYPATH will help (like it will use this folder as priority for DLL lookup) but for some reason it wasn't used, so i had to edit the priority of my folder in environment variable Path(basically forcing the right folder to be used first).
Lubo B said:I thought editing MS_ADDINDEPENDENCYPATH will help (like it will use this folder as priority for DLL lookup) but for some reason it wasn't used
Good to know you solved the issue :-)
I remember (not too well) this vairable and general problem of dll location was discussed in the past, but I guess there was no conclusion done at this time.