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
FYI
While this is probably not the source of your issue, you should be aware that SS4 is not certified to run on Windows 10, nor Windows 11. It might run fine, but there is definitely the possibility of some things not working. SS4 is also no longer supported by Bentley, so you will be essentially on your own when troubleshooting any issues stemming from that.
MaryB
Power GeoPak 08.11.09.918Power InRoads 08.11.09.918OpenRoads Designer 2021 R2
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.
Regards,
Jan
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:but it looked fine
DependencyWalker tells only what is configured in the file itself, not whether it was found or not. Plus, it!s a tree, so directly linked libraries can require other files...
To ensure the same workspace can also help, because there are variables defining where to find .ma files and dependency dll files.
Its plugin .ma consisting also of DLL. I sent DependencyWalker app to client and asked them to send me a screenshot, but it looked fine(even though as u said, its kinda tricky when DLLs are not in same folder). I hope Process Monitor log will tell me more.
Jan Šlegr said:Are versions (MicroStation, Windows as well) the same?
Well actually i havent thought about Windows version. Because i didn't try it on windows 11 yet.