tag:blogger.com,1999:blog-7396481053359703519.post653376234962176339..comments2024-03-26T04:04:33.060+01:00Comments on Henk's blog: Unknown SQL error in ConfigMgr after installing DotNet updatesHenk Hoogendoornhttp://www.blogger.com/profile/01066841733613965112noreply@blogger.comBlogger9125tag:blogger.com,1999:blog-7396481053359703519.post-41679965929225193552016-09-30T18:44:34.278+02:002016-09-30T18:44:34.278+02:00As this is post from 2013, DO we still have this i...As this is post from 2013, DO we still have this issue as I am seeing this error since SQL SP was updated on SQL Server which is running 2012 OS. Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7396481053359703519.post-82937128162407339912013-11-18T09:50:47.082+01:002013-11-18T09:50:47.082+01:00Just do a search on Installed Updates for KB283539...Just do a search on Installed Updates for KB2835393, KB2804576 and KB2840628. Don't know of another issue at the moment..Henk Hoogendoornhttps://www.blogger.com/profile/01066841733613965112noreply@blogger.comtag:blogger.com,1999:blog-7396481053359703519.post-6541719804077718372013-11-18T04:45:58.121+01:002013-11-18T04:45:58.121+01:00Hi, I have the same error in my Logs but Dont have...Hi, I have the same error in my Logs but Dont have any .NET 4 updates installed. Im running Server 2012 R2 with SQL 2012 SP1. Any suggestions??Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7396481053359703519.post-27565509922621393632013-07-29T18:35:50.751+02:002013-07-29T18:35:50.751+02:00Thank you for this post. Argh.Thank you for this post. Argh.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7396481053359703519.post-5756380306576888522013-07-26T17:26:36.381+02:002013-07-26T17:26:36.381+02:00It's been a long time since I've had an up...It's been a long time since I've had an update break something. I forgot how annoying it is. Mean while I think I have broken WDS. Ugh.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7396481053359703519.post-57578050344493735862013-07-23T06:33:55.350+02:002013-07-23T06:33:55.350+02:00For is seems it only is a issue with SQL Server 20...For is seems it only is a issue with SQL Server 2012 (all versions). Just follow steps mentioned in the update!Henk Hoogendoornhttps://www.blogger.com/profile/01066841733613965112noreply@blogger.comtag:blogger.com,1999:blog-7396481053359703519.post-89227578297904443382013-07-23T06:31:41.381+02:002013-07-23T06:31:41.381+02:00Thanks for mentioning!Thanks for mentioning!Henk Hoogendoornhttps://www.blogger.com/profile/01066841733613965112noreply@blogger.comtag:blogger.com,1999:blog-7396481053359703519.post-80683892777301466592013-07-22T20:08:22.101+02:002013-07-22T20:08:22.101+02:00Captured by Brian Mason first...
http://myitforum...Captured by Brian Mason first...<br /><br />http://myitforum.com/myitforumwp/2013/07/18/configmgr-product-team-explains-kb2840628-issues-and-workarounds/ Rod Trenthttp://www.myitforum.comnoreply@blogger.comtag:blogger.com,1999:blog-7396481053359703519.post-59147932183431325772013-07-15T22:31:09.120+02:002013-07-15T22:31:09.120+02:00I just had this same issue. I suspected it might ...I just had this same issue. I suspected it might be due to Windows Updates since that was the only thing that changed on the SCCM server. I did not, however, know which updates were the culprit. Thank you for your post as you saved me quite a bit of time.Anonymousnoreply@blogger.com