bcsdtech Posted June 4, 2015 Report post Posted June 4, 2015 HI - Just updated to R2 sp1 from R2. After the upgrade new clients are saying "Certificate = NONE" Usually its self-assigned. Getting this error in StatusAgent.log Registration failed with error 0x80041010 StatusAgent 6/4/2015 9:20:52 AM 4092 (0x0FFC) Failed to add event forwarder for CCM_EVENTFORWARDER_CONFIGURATION.INSTANCEID="SMSBRANCHDP.INSTANCE0",NAME="SMSEVENTLOGFORWARDER" StatusAgent 6/4/2015 9:20:52 AM 4092 (0x0FFC) Also this in CcmRepair.log Database verification failed with result: 0x80004005 but DB: C:\WINDOWS\CCM\InventoryStore.sdf could be opened, skipping DB repair. CcmRepair 6/4/2015 9:20:51 AM 7204 (0x1C24) ClientIDManagerStartup.log [RegTask] - Client registration is pending. Sending confirmation request for GUID:7797D0CB-AB10-46E7-ACA7-A788E6EBC4D2 ... ClientIDManagerStartup 6/4/2015 9:26:56 AM 4092 (0x0FFC) Any help appreciated. Thank you Quote Share this post Link to post Share on other sites More sharing options...
bcsdtech Posted June 4, 2015 Report post Posted June 4, 2015 Also getting this in SMS_discovery_data_manager Microsoft SQL Server reported SQL message 8169, severity 16: [42000][8169][Microsoft] [sql Server]Conversion failed when converting from a character string to uniqueidentifier. : SMSDBMON_ClientKeyData_PfxCertsClientKeyData_Chg_upd Quote Share this post Link to post Share on other sites More sharing options...
bcsdtech Posted June 4, 2015 Report post Posted June 4, 2015 SMS_providers availabilty says - "unknown" I tried to restart service in config mgr service manager and it says Error Communicating with component Quote Share this post Link to post Share on other sites More sharing options...
etruscan Posted June 8, 2015 Report post Posted June 8, 2015 We are having a similar problem in our environment following upgrading to SP1. Were you ever able to get this resolved? Quote Share this post Link to post Share on other sites More sharing options...
denzik Posted June 9, 2015 Report post Posted June 9, 2015 I am also having the same exact issue after upgrading from SCCM 2012 R2 TO SCCM 2012 R2 SP1 same errors in all my logs as the posts above has anyone been able to resolve this? Microsoft? Quote Share this post Link to post Share on other sites More sharing options...
bcsdtech Posted June 9, 2015 Report post Posted June 9, 2015 Not resolved yet.. Quote Share this post Link to post Share on other sites More sharing options...
kloostec Posted June 10, 2015 Report post Posted June 10, 2015 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... 1 Quote Share this post Link to post Share on other sites More sharing options...
bcsdtech Posted June 11, 2015 Report post Posted June 11, 2015 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... Wow. Thank you! That worked!! 1. How did you figure that out? 2. What is that trigger doing? Thanks again!!! It's been 3 days of frustration. Quote Share this post Link to post Share on other sites More sharing options...
kloostec Posted June 11, 2015 Report post Posted June 11, 2015 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. Quote Share this post Link to post Share on other sites More sharing options...
jdenzik Posted June 12, 2015 Report post Posted June 12, 2015 Why does Microsoft not recognize there is a issue? How long before a hot fix will be implemented? Kloostec, have you noticed anything strange in your environment since you have disabled the trigger? Quote Share this post Link to post Share on other sites More sharing options...
