How to trace SxS binding issues that don't show up with sxstrace?
I have some strange issues with SxS binding. I have vendor DLLs that depend on VC9's CRT, MFC, and OpenMP. Originally these DLLs pointed to an old CRT (21022.8), but I updated their manifests to point to the latest release (30729.6161). I need these DLLs to work on client machines without needing the VC9 redistributable installed (i.e. non-administrator install). It's hard to test on my developer machine because I can't get entirely rid of the VC9 redistributable: too many applications are using it (e.g. Everything search, Google Backup). I can delete MFC and/or OpenMP from winsxs though (and the accompanying policy/manifest files).
When I delete OpenMP, I get a SxS configuration error that shows up in the event viewer and I can trace it with sxstrace.exe. Doing that led me to put a Microsoft.VC90.OpenMP.manifest file beside my application along with the vcomp90.dll, and that allowed the app to use the local OpenMP.
But when I delete MFC, I don't get a side-by-side error. Instead I get a popup dialog saying The program can't start because mfc90.dll is missing from computer.. Even after giving my application the Microsoft.VC90.MFC.manifest file, it won't find the mfc90.dll sitting right next to the executable. Because it's not a side-by-side error, sxstrace.exe doesn't tell me anything.
When I monitor DLL access with Process Monitor, I see that it is binding to the VC90.CRT in winsxs (which I can't get rid of because it's in use). Then, without looking in the local directory, it looks for mfc90.dll in winsxs, doesn't find it, then gives the error without looking in any other place.
Why is it behaving this way and how do I fix it?
edit: I don't know if it's relevant, but the vendor DLLs are COM-based which I've wrapped/isolated with Interop DLLs. So I actually only get the The program can't start error when it tries to create the COM object.
windows dll mfc winsxs
asked Nov 27 '18 at 16:36
Matt ChambersMatt Chambers
1,20111431
add a comment |
I have some strange issues with SxS binding. I have vendor DLLs that depend on VC9's CRT, MFC, and OpenMP. Originally these DLLs pointed to an old CRT (21022.8), but I updated their manifests to point to the latest release (30729.6161). I need these DLLs to work on client machines without needing the VC9 redistributable installed (i.e. non-administrator install). It's hard to test on my developer machine because I can't get entirely rid of the VC9 redistributable: too many applications are using it (e.g. Everything search, Google Backup). I can delete MFC and/or OpenMP from winsxs though (and the accompanying policy/manifest files).
When I delete OpenMP, I get a SxS configuration error that shows up in the event viewer and I can trace it with sxstrace.exe. Doing that led me to put a Microsoft.VC90.OpenMP.manifest file beside my application along with the vcomp90.dll, and that allowed the app to use the local OpenMP.
But when I delete MFC, I don't get a side-by-side error. Instead I get a popup dialog saying The program can't start because mfc90.dll is missing from computer.. Even after giving my application the Microsoft.VC90.MFC.manifest file, it won't find the mfc90.dll sitting right next to the executable. Because it's not a side-by-side error, sxstrace.exe doesn't tell me anything.
When I monitor DLL access with Process Monitor, I see that it is binding to the VC90.CRT in winsxs (which I can't get rid of because it's in use). Then, without looking in the local directory, it looks for mfc90.dll in winsxs, doesn't find it, then gives the error without looking in any other place.
Why is it behaving this way and how do I fix it?
edit: I don't know if it's relevant, but the vendor DLLs are COM-based which I've wrapped/isolated with Interop DLLs. So I actually only get the The program can't start error when it tries to create the COM object.
windows dll mfc winsxs
asked Nov 27 '18 at 16:36
Matt ChambersMatt Chambers
1,20111431
1
Question title and question body ask different questions. Which one did you mean to ask? If it's the title, try to enable loader snaps.
– IInspectable
Nov 27 '18 at 20:03
All 3 questions ideally (how to trace it, why it's doing that, and how to fix it). I figured knowing the title question would lead to answers for the other 2 questions, but I'd be ok to skip that step. :) Thanks for the tip on loader snaps, I'm trying that.
– Matt Chambers
Nov 27 '18 at 21:19
add a comment |
I have some strange issues with SxS binding. I have vendor DLLs that depend on VC9's CRT, MFC, and OpenMP. Originally these DLLs pointed to an old CRT (21022.8), but I updated their manifests to point to the latest release (30729.6161). I need these DLLs to work on client machines without needing the VC9 redistributable installed (i.e. non-administrator install). It's hard to test on my developer machine because I can't get entirely rid of the VC9 redistributable: too many applications are using it (e.g. Everything search, Google Backup). I can delete MFC and/or OpenMP from winsxs though (and the accompanying policy/manifest files).
When I delete OpenMP, I get a SxS configuration error that shows up in the event viewer and I can trace it with sxstrace.exe. Doing that led me to put a Microsoft.VC90.OpenMP.manifest file beside my application along with the vcomp90.dll, and that allowed the app to use the local OpenMP.
But when I delete MFC, I don't get a side-by-side error. Instead I get a popup dialog saying The program can't start because mfc90.dll is missing from computer.. Even after giving my application the Microsoft.VC90.MFC.manifest file, it won't find the mfc90.dll sitting right next to the executable. Because it's not a side-by-side error, sxstrace.exe doesn't tell me anything.
When I monitor DLL access with Process Monitor, I see that it is binding to the VC90.CRT in winsxs (which I can't get rid of because it's in use). Then, without looking in the local directory, it looks for mfc90.dll in winsxs, doesn't find it, then gives the error without looking in any other place.
Why is it behaving this way and how do I fix it?
edit: I don't know if it's relevant, but the vendor DLLs are COM-based which I've wrapped/isolated with Interop DLLs. So I actually only get the The program can't start error when it tries to create the COM object.
windows dll mfc winsxs
asked Nov 27 '18 at 16:36
Matt ChambersMatt Chambers
1,20111431
I have some strange issues with SxS binding. I have vendor DLLs that depend on VC9's CRT, MFC, and OpenMP. Originally these DLLs pointed to an old CRT (21022.8), but I updated their manifests to point to the latest release (30729.6161). I need these DLLs to work on client machines without needing the VC9 redistributable installed (i.e. non-administrator install). It's hard to test on my developer machine because I can't get entirely rid of the VC9 redistributable: too many applications are using it (e.g. Everything search, Google Backup). I can delete MFC and/or OpenMP from winsxs though (and the accompanying policy/manifest files).
When I delete OpenMP, I get a SxS configuration error that shows up in the event viewer and I can trace it with sxstrace.exe. Doing that led me to put a Microsoft.VC90.OpenMP.manifest file beside my application along with the vcomp90.dll, and that allowed the app to use the local OpenMP.
But when I delete MFC, I don't get a side-by-side error. Instead I get a popup dialog saying The program can't start because mfc90.dll is missing from computer.. Even after giving my application the Microsoft.VC90.MFC.manifest file, it won't find the mfc90.dll sitting right next to the executable. Because it's not a side-by-side error, sxstrace.exe doesn't tell me anything.
When I monitor DLL access with Process Monitor, I see that it is binding to the VC90.CRT in winsxs (which I can't get rid of because it's in use). Then, without looking in the local directory, it looks for mfc90.dll in winsxs, doesn't find it, then gives the error without looking in any other place.
Why is it behaving this way and how do I fix it?
edit: I don't know if it's relevant, but the vendor DLLs are COM-based which I've wrapped/isolated with Interop DLLs. So I actually only get the The program can't start error when it tries to create the COM object.
windows dll mfc winsxs
windows dll mfc winsxs
asked Nov 27 '18 at 16:36
Matt ChambersMatt Chambers
1,20111431
asked Nov 27 '18 at 16:36
Matt ChambersMatt Chambers
1,20111431
asked Nov 27 '18 at 16:36
Matt ChambersMatt Chambers
1,20111431
asked Nov 27 '18 at 16:36
Matt ChambersMatt Chambers
1,20111431
asked Nov 27 '18 at 16:36
Matt ChambersMatt Chambers
1,20111431
1,20111431
1
Question title and question body ask different questions. Which one did you mean to ask? If it's the title, try to enable loader snaps.
– IInspectable
Nov 27 '18 at 20:03
All 3 questions ideally (how to trace it, why it's doing that, and how to fix it). I figured knowing the title question would lead to answers for the other 2 questions, but I'd be ok to skip that step. :) Thanks for the tip on loader snaps, I'm trying that.
– Matt Chambers
Nov 27 '18 at 21:19
add a comment |
1
Question title and question body ask different questions. Which one did you mean to ask? If it's the title, try to enable loader snaps.
– IInspectable
Nov 27 '18 at 20:03
All 3 questions ideally (how to trace it, why it's doing that, and how to fix it). I figured knowing the title question would lead to answers for the other 2 questions, but I'd be ok to skip that step. :) Thanks for the tip on loader snaps, I'm trying that.
– Matt Chambers
Nov 27 '18 at 21:19
1
1
Question title and question body ask different questions. Which one did you mean to ask? If it's the title, try to enable loader snaps.
– IInspectable
Nov 27 '18 at 20:03
Question title and question body ask different questions. Which one did you mean to ask? If it's the title, try to enable loader snaps.
– IInspectable
Nov 27 '18 at 20:03
All 3 questions ideally (how to trace it, why it's doing that, and how to fix it). I figured knowing the title question would lead to answers for the other 2 questions, but I'd be ok to skip that step. :) Thanks for the tip on loader snaps, I'm trying that.
– Matt Chambers
Nov 27 '18 at 21:19
All 3 questions ideally (how to trace it, why it's doing that, and how to fix it). I figured knowing the title question would lead to answers for the other 2 questions, but I'd be ok to skip that step. :) Thanks for the tip on loader snaps, I'm trying that.
– Matt Chambers
Nov 27 '18 at 21:19
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53504199%2fhow-to-trace-sxs-binding-issues-that-dont-show-up-with-sxstrace%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53504199%2fhow-to-trace-sxs-binding-issues-that-dont-show-up-with-sxstrace%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Question title and question body ask different questions. Which one did you mean to ask? If it's the title, try to enable loader snaps.
– IInspectable
Nov 27 '18 at 20:03
All 3 questions ideally (how to trace it, why it's doing that, and how to fix it). I figured knowing the title question would lead to answers for the other 2 questions, but I'd be ok to skip that step. :) Thanks for the tip on loader snaps, I'm trying that.
– Matt Chambers
Nov 27 '18 at 21:19