<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle18
{mso-style-type:personal-compose;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-GB" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p><span style="font-size:10.0pt">Hi Scott,<br>
<br>
So essentially does that mean that any referenced component within an application that uses the same dll as Shibboleth e.g. xerces-c_3_2.dll will fail?<br>
<br>
Our current solution therefore is to either reference a different version of the Crystal Reports runtime which uses an earlier version of that dll, which isn't really viable, or to use Shibboleth 2.6.1.4 and ISAPI.<br>
<br>
Which presumably means going forward we would need to monitor the versions of the file being used by future releases of both products to see whether there is a compatible path to upgrade either without file conflicts?<br>
<br>
Kind regards<br>
<br>
<br>
Damian<br>
<br>
<br>
Damian Crawford<br>
<br>
-----Original Message-----<br>
From: users <users-bounces@shibboleth.net> On Behalf Of Cantor, Scott<br>
Sent: 19 January 2021 15:10<br>
To: Shib Users <users@shibboleth.net><br>
Subject: Re: Shibboleth SP 3 causes issues with the Crystal Reports Runtime Engine<br>
<br>
On 1/19/21, 10:02 AM, "users on behalf of Damian Crawford (JCAD)" <users-bounces@shibboleth.net on behalf of damian@jcad.co.uk> wrote:<br>
<br>
> The Crystal runtime does install the xerces-c_3_2.dll so I guess<br>
> this is where the conflict is occurring...is any way around this that you can think of at this stage?<br>
<br>
Nothing I can think of. I don't do anything to the library, it's built from source. I suspect they used a different compiler, so it's impossible for them to use mine and impossible for the SP to use theirs.<br>
<br>
-- Scott<br>
<br>
<br>
--<br>
For Consortium Member technical support, see <a href="https://wiki.shibboleth.net/confluence/x/coFAAg">
https://wiki.shibboleth.net/confluence/x/coFAAg</a><br>
To unsubscribe from this list send an email to users-unsubscribe@shibboleth.net</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><img border="0" width="1" height="1" style="width:.0104in;height:.0104in" id="_x0000_i1025" src="https://t.sidekickopen85.com/s2t/o/5/f18dQhb0S7n28cVQ4MW10qfgt59hl0VW7_jsyP5JR-jdW4n-06M58y_L6N59hR9P3vCKLf2zm-WM03?si=8000000001392132&pi=ad8ba9a1-4a13-4605-b454-8366567173ce"><o:p></o:p></p>
</div>
</body>
</html>