Transactional replication - can't create publication

  • Hi all,

    I have a newly created Windows 2008R2 (64bit) server with MSSQL 2012 standard edition installed, acting as it's own distributor.

    I have just gone to create the first publication on this particular server and I am getting an error with the snapshot agent.

    "A .NET Framework error occurred during execution of user-defined routine or aggregate "sp_scriptdropinsreconciliationproc_sqlclr":"

    I can be pretty sure it has nothing to do with the subscription, because I didn't even get to that stage.

    I have done some browsing and all that I can find is something about a known problem after applying the .Net update KB2840628[/url]...

    the only problem is my server has not had the update applied.

    Any help would be greatly appreciated.

    David

  • Run the below and paste the results .

    Select * from sys.dm_clr_loaded_assemblies

    select * from sys.dm_clr_task

    Most of the CLR issues causes due to memory spike, .net DLLs supporting SQL to run are currupted.

    The immediate solution will be restarting the SQL services.

  • This occurred for us due to Windows Updates. A specific .NET update caused our replication and SharePoint systems to break. Uninstalling the update fixed it immediately.

    The update that caused this issue in our case was KB2840628

  • Hi sqldba725 and david.bianco

    thank you both for your replies. I have fixed the problem... well I will say so far so good.

    One of the possible cause I found on the internet was windows update KB2840628, the only problem was I did not have it installed.

    Anyway to cut a long story short, I cloned the VM's involved and ran ALL the Windows updates to do with .Net Framework... tested and replication now works. I will spend some time of the next couple of days testing/reviewing before changing the actual production VM's. "fingers crossed"

    Thanks for the replies greatly appreciated.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply