In our environment, this .dll fails to register properly as a .net 2 assembly, but registers properly as a .net 4 assembly (and things seem to work).
Does that server in question have .net 4 installed on it? Also, it seems that your ConfigMgr install path is on a non-C drive location. We had issues with other .Net assemblies for site components registering properly when installed to the D drive. We had to modify the config of some of the .net assembly registration utils to allow for "loadFromRemoteSources" as described here: http://www.windows-noob.com/forums/index.php?/topic/7401-sms-notification-server-failed-critical-sccm-sp1-sql-2012-sp1/ Hopefully this can get you pointed in the right direction. On Mon, Aug 10, 2015 at 8:46 AM, Beardsley, James < [email protected]> wrote: > I have two SUPs, one internal and one external facing. The external facing > SUP is synched to the internal and the internal is in working order (both > are 2008 R2 servers). I noticed that the WSUS_CONTROL_MANAGER component had > errors on Friday and when I viewed the events, it appears that CM is trying > to reinstall the WSUS role on the external SUP. I’m not sure why its > reinstalling it but after checking the SUPSetup.log on the server, I see > that the failure is .NET related. > > > > > > If I try and manually register the .dll file, I get the following > > > > > > Any ideas on what would cause this? Would it be worth doing a full > reinstall of the role? > > > > Thanks! > > > > *James Beardsley |* Firm Technology Group > > Dixon Hughes Goodman LLP > > > > [image: cid:8644FC49-D5C9-45AE-B387-04FAFC0CC7A5] <http://www.dhgllp.com/> > > > ------------------------------ > > *Confidentiality Notice:* This e-mail is intended only for the addressee > named above. It contains information that is privileged, confidential or > otherwise protected from use and disclosure. If you are not the intended > recipient, you are hereby notified that any review, disclosure, copying, or > dissemination of this transmission, or taking of any action in reliance on > its contents, or other use is strictly prohibited. If you have received > this transmission in error, please reply to the sender listed above > immediately and permanently delete this message from your inbox. Thank you > for your cooperation. > >
