mscordacwks.dll from target machine not accepted

Use this forum for questions on how to use .NET Memory Profiler and how to analyse memory usage.
Post Reply
rplaire
Posts: 5
Joined: Wed Feb 17, 2016 9:05 pm

mscordacwks.dll from target machine not accepted

Post by rplaire » Wed Feb 17, 2016 9:10 pm

Greetings,

I have a dump from a target machine which requires mscordacwks.dll 4.6.1063.1 32 bit. I obtained this dll and sos.dll and the prompting dialog will not accept it to open the dump. When I click "Ok" the dialog reappears. Why is this? What can be done to convince Memprofiler I have the right version?

Memprofiler prompt:
.NET Runtime Version Mismatch_NetMemProfiler_(1197).png
Mscordacwks.dll properties:
mscordacwks.dll Properties_explorer_(1199).png
32 bit:
__(1201).png
__(1201).png (10.35 KiB) Viewed 4239 times

Andreas Suurkuusk
Posts: 1005
Joined: Wed Mar 02, 2005 7:53 pm

Re: mscordacwks.dll from target machine not accepted

Post by Andreas Suurkuusk » Thu Feb 18, 2016 2:50 pm

This is most likely caused by the fact that the "sos.dll" file on your machine doesn't match the "sos.dll" file from the target machine. The profiler doesn't detect whether the version mismatch is caused by "sos.dll" or "mscordacwvks.dll". Usually it is mscordacwks (this file must match the exact version), but for a more major version mismatch the sos.dll file must also be specified.

Anyway, can you copy the sos.dll file from the target machine and specify it in the bottom field in the ".NET Runtime Version Mismatch" window? Hopefully the import will work better then.
Best regards,

Andreas Suurkuusk
SciTech Software AB

rplaire
Posts: 5
Joined: Wed Feb 17, 2016 9:05 pm

Re: mscordacwks.dll from target machine not accepted

Post by rplaire » Wed Apr 06, 2016 1:40 am

Yea, that was it. I was confused that that field was not optional since the "OK" button was active while the SOS field was unfilled.

Post Reply

Who is online

Users browsing this forum: No registered users and 7 guests