<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta content="text/html;charset=UTF-8" http-equiv="Content-Type"></head><body ><div style="font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10pt;"><p class="MsoNormal">Apologies if this isn’t the correct channel to ask this in,
but any insight would be appreciated (or direction to better forum for assistance).<br></p><div><br></div><div>I'm
upgrading an SP from v2.5 to v3 on Windows using IIS. No issues with
the Shibboleth upgrade itself and I'm able to have the app
working/authenticating using Shibboleth after the upgrade.<br></div><div><br></div><div>We
are using an A/V product which is loaded as a service using SrvAny
(clamd). Works fine before the upgrade, but after the upgrade to SP 3
the service will no longer load. First attempt throws an error about a
missing .dll (msvcr100d.dll). I've replaced this .dll from another
server but then I get a generic application error. I've tried
reinstalling the visual c redistributable from an older package but have
not had any luck down that path.<br></div><div><br></div><div>Why does the SP3 upgrade remove this .dll and is there a way to manually upgrade and avoid this step?<br></div><div><br></div><div>fwiw,
I do recognize the .dll in question should only be needed for debug,
however I am trying to find the most expedient path to get to v3 first
and can then address the way that service is being used/run.....I hope.<br></div></div><br></body></html>