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
Hi Lubo, this is likely to be a version mismatch between the MDL and MicroStation.
Which MDL is involved (or is it more than one)?
When do you see the error?
I'm assuming this is appearing in a black text window?
Which version of MicroStation?
Hello, this error is caused when I try to load my own plugin .ma file. The error displays at the start of the microstation. Yes, it appears in console window (so thats why i was wondering if MS keeps some kind of logs which could describe it more properly). Version of MS is kinda old one, MicroStation V8i SS4 08.11.09.867. I mean, the plugin works on other machines but this is a new clean install machine which displays the error, and as I dont have access to the machine its kinda troublesome to troubleshoot this problem. Thats why some more accurate log would come in handy in these situations. I thought reinstall of MS would help but it didn't.
Lubo B said:Hello, this error is caused when I try to load my own plugin .ma file.
Because "MDL" is too fuzzy term with several different meanings: What is "type" of .ma application? Is it old pseudocode application (no dll, only .ma + rsc files), or is it native application (.ma loader + dll files)?
Lubo B said:I mean, the plugin works on other machines but this is a new clean install machine which displays the error
Are versions (MicroStation, Windows as well) the same?
Often, even when probably not this case, different behavior is caused by missing libraries (like C runtime / msvcrt.dll).
Lubo B said:Thats why some more accurate log would come in handy in these situations.
The problem is that it's internal MicroStation error, not Windows one. Maybe to use debugger (e.g. WinDbg) and to attach to the process, can be tried.
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
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.
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.
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.
Power GeoPak 08.11.09.918Power InRoads 08.11.09.918OpenRoads Designer 2021 R2