kloostec

Microsoft has released a hotfix for this issue: https://support.microsoft.com/en-us/kb/3073015 Make sure to reenable the trigger (if you used my workaround), then install the hotfix. I have confirmed that this has fixed the issue in our environment.

1. I'm a developer, so I am familiar enough with SQL and its errors to try to figure out what's going on. 2. Basically, whenever the ClientKeyData table is updated (when a client registers with a new certificate in our case) the trigger takes some of the updated data and throws it into the "TableChangeNotifications" table. Not doing this insert probably breaks some sort of post-processing routine somewhere, but I haven't noticed any issues since I disabled the trigger yesterday. The trigger didn't exist in 2012 R2 without SP. In our environment, the potential risk of this missing post-processing is lower than a complete breakage of our build procedure, especially coming up to summer break when we'll be building and rebuilding hundreds of machines.

I was having the same error on our server. It looks like Microsoft implemented a new trigger in R2 SP1 that is causing the issue. Using SQL Server Management Studio, I disabled the trigger and now the clients appear to be registering successfully. Specifically, I went into CM_PSR (our site database) -> Tables -> dbo.ClientKeyData -> Triggers, then right clicked on SMSDBMON_ClientKeyData_PfxCertsClientKeyData_Chg_upd and chose Disable. If you choose to do this, make sure you reenable the trigger when Microsoft releases the inevitable hotfix that actually corrects the problem...