MSVCR80.DLL version conflict

[Mike Blake-Knox]

I have a C++ ActiveX control that is used by JavaScript code in 
Internet Explorer. Recently, a customer installed Acrobat Reader 8.1 
and reported that the ActiveX control wasn't working. In the event 
viewer, there's a error from SideBySide: "Generate Activation Context 
failed for ... . Reference error message: A component version required 
by the application conflicts with another component version already 
active."

Investigation showed that before Acrobat was installed the control was 
using msvcr80.dll requesting 50727.104. If I closed the control and 
installed Acrobat, msvcr80.dll version 50727.163 was immediately 
loaded by Internet Explorer. When we tried to load the control, it 
wouldn't start and the error message was put in the Event Log.

I noticed that the redirect in in the 8.0.50727.163 policy redirected 
8.0.50727.42 to 8.0.50727.163 but didn't redirect 8.0.50727.104. If I 
added a redirect for 8.0.50727.104, the control started fine.

It also started fine if I installed SP1 redistributable.

Why is 8.0.50727.104 not redirected? I thought the whole purpose of
the Side By Side software was to allow multiple versions of the dll to
run at the same time. Is that not correct? How does it apply in this
case?

Thanks

Mike

 

[Charles Wang[MSFT]]

Hi Mike,
Could you please let me know how you saw the policy redirected in
msvcr80.dll 8.0.50727.163? You may also mail me
(changliw_at_microsoft_dot_com) a screenshot of your isssue so that I can
better understand your issue and work more efficient.

If you have any questions or concerns, please feel free to let me know.
Have a good day!

Best regards,
Charles Wang
Microsoft Online Community Support

======================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================

 

[Mike Blake-Knox]

Could you please let me know how you saw the policy redirected in 
msvcr80.dll 8.0.50727.163?

The policy file is:
C:\WINDOWS\WinSxS\Policies\x86_policy.8.0.Microsoft.VC80.CRT_1fc8b3b9a1
e18e3b_x-ww_77c24773

The file's contents were

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<!-- Copyright © 1981-2001 Microsoft Corporation -->
<assembly xmlns="urn:schemas-microsoft-com:asm.v1"
manifestVersion="1.0">

<assemblyIdentity type="win32-policy"
name="policy.8.0.Microsoft.VC80.CRT" version="8.0.50727.163"
processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"/>
<dependency>
<dependentAssembly>
<assemblyIdentity type="win32" name="Microsoft.VC80.CRT"
processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"/>
<bindingRedirect oldVersion="8.0.41204.256-8.0.50608.0"
newVersion="8.0.50727.163"/>
<bindingRedirect oldVersion="8.0.50727.42"
newVersion="8.0.50727.163"/>
</dependentAssembly>
</dependency>

</assembly>

The second bindingRedirect redirects just version 8.0.50727.42 to
8.0.50727.163 but doesn't affect 8.0.50727.104. The .163 files are
dated 6/5/2006. The identical file is on my laptop.

I can send you a screen snapshot if you tell me what you would like it
to show.

Thanks

Mike

 

[Charles Wang[MSFT]]

Hi Mike,
Thanks for your response.

Now I am consulting this issue with our Dev team. The contents of the
policy redirections are just their want. Now this issue is in discussing
and I will get back to you as soon as possible when there is a final
confirmation. I appreicate your patience.

Best regards,
Charles Wang
Microsoft Online Community Support

======================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================

 

[Charles Wang[MSFT]]

Hi Mike,
I just got the confirmation from the Dev team. It is confirmed that this
issue was an older product issue and had been got fixed in the latest
service pack SP1. I think that that is why it started fine after you
installed SP1 redistributable.

They recommend that you redistribute VS2005 SP1 CRTs with your ActiveX
control so that this issue will not happen again.

Please feel free to let me know if you have any questions or concerns. Have
a nice day!

Best regards,
Charles Wang
Microsoft Online Community Support

======================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================