Jump to content


SCCM DB - AAG - CLR failure after failover to secondary

Recommended Posts

Our SCCM DB is on an AAG. When it fails over to one node we get the error: 

An error occurred in the Microsoft .NET Framework while trying to load assembly id 65541. The server may be running out of resources, or the assembly may not be trusted. Run the query again, or check documentation to see how to solve the assembly trust issues. For more information about this error:   System.IO.FileLoadException: Could not load file or assembly 'smssqlclr, Version=

when we set trustworthy on and change the DB owner, it works... but when it fails over to the other node... the other node starts giving the same error. 

Has anyone faced such an issue for the SCCM DB on AAG, and what was done to resolve it permanently without having to change owner, trustworthy settings every time a failover happens.

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Create New...