A better way to debug MDL loader error 127

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

Parents
  • 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?

    Marc

  • 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.

  • 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)?

    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).

    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.

    With regards,

      Jan

Reply Children