{"id":3033,"date":"2013-05-15T14:24:00","date_gmt":"2013-05-15T14:24:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/visualstudioalm\/2013\/05\/15\/known-issue-and-workaround-for-tfs-2012-update-3-rc1\/"},"modified":"2019-02-14T17:54:34","modified_gmt":"2019-02-15T01:54:34","slug":"known-issue-and-workaround-for-tfs-2012-update-3-rc1","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/devops\/known-issue-and-workaround-for-tfs-2012-update-3-rc1\/","title":{"rendered":"Known Issue and Workaround for TFS 2012 Update 3 RC1"},"content":{"rendered":"<p><span style=\"font-size: large\"><strong><span class=\"info-text\">UPDATE &#8211; <\/span><\/strong><span class=\"info-text\">This issue has been fixed in TFS 2012 Update 3 RC2, which is available here: <span style=\"color: #1f497d;font-family: 'Calibri','sans-serif'\"><a href=\"http:\/\/support.microsoft.com\/kb\/2835600\">http:\/\/support.microsoft.com\/kb\/2835600<\/a><\/span><\/span><\/span><\/p>\n<p>&nbsp;<\/p>\n<p><span class=\"info-text\">This post is to report a known issue with alerts in Team Foundation Server 2012 Update 3 RC1.&nbsp; There is a partial workaround, which should be applied to the configuration database BEFORE upgrade to RC1 if possible.&nbsp;&nbsp;This issue will be fixed in Update 3 RC2.<\/span><\/p>\n<p>&nbsp;<\/p>\n<h3>Description<\/h3>\n<p><span class=\"info-text\">This bug causes some alert subscription evaluations in TFS to fail with an exception (an XPathException), even though they are actually valid.&nbsp; Upon receiving the exception, the exception handler will treat the corresponding subscription as invalid and delete it.&nbsp; The alert will not be sent, and will be removed from the system incorrectly.&nbsp; <\/span><\/p>\n<p><span class=\"info-text\">We believe this problem is fairly widespread, and customers who use their server regularly&nbsp;can expect to see the bug arise almost immediately after&nbsp;upgrade.&nbsp;&nbsp;It will occur as soon as an event (such as a check-in, creation of a work item, etc.) is triggered on the server.&nbsp; <\/span><\/p>\n<p><span class=\"info-text\">Those affected by this bug will see errors in the following form:<\/span><\/p>\n<p><span style=\"color: #808080\">[EntryInfo]<\/span><br><span style=\"color: #808080\">Message:&nbsp;&nbsp;&nbsp; TF53010: The following error has occurred in a Team Foundation component or extension<\/span><span style=\"color: #808080\">&#8230;<\/span><\/p>\n<p><span style=\"color: #808080\">Detailed Message: The subscription for&nbsp; contained an invalid condition &#8220;&#8221;PortfolioProject&#8221; = &#8216;XYZ AND &#8220;CoreFields\/StringFields\/Field[Name=&#8217;Created By&#8217;]\/NewValue&#8221; = <a href=\"mailto:'@@MyDisplayName@@'\"><span style=\"color: #808080\">&#8216;@@MyDisplayName@@&#8217;<\/span><\/a> AND &#8220;CoreFields\/StringFields\/Field[Name=&#8217;Authorized As&#8217;]\/NewValue&#8221; <strong><span style=\"color: #ff0000\">&lt;&gt; <a href=\"mailto:'@@MyDisplayName@@'\"><span style=\"color: #ff0000\">&#8216;@@MyDisplayName@@&#8217;<\/span><\/a>&#8220;<\/span><\/strong> <span style=\"color: #ff0000\">which could not be evaluated<\/span>.<\/span><br><span style=\"color: #808080\">Exception Message:<span style=\"color: #ff0000\"> &#8216;<strong>USER<\/strong>&#8216; as an invalid token. (type <strong>XPathException<\/strong>)<\/span><\/span><\/p>\n<p>&nbsp;<\/p>\n<h3>Workaround<\/h3>\n<p>If you are thinking of upgrading your server to Update 3 RC1, please contact&nbsp;<a href=\"http:\/\/msdn.microsoft.com\/en-us\/hh361695?WT.mc_id=SMCfoot_ENUS_TEXT\">Microsoft Customer&nbsp;Service and Support (CSS)<\/a>&nbsp;or TFCare a*t Microsoft d*ot com for&nbsp;a SQL script that should be applied to your configuration database first.&nbsp; This script will not&nbsp;stop the alert evaluation exception from being thrown, but it will prevent the TFS notification job from deleting alert subscriptions.&nbsp; Instead, the alert will simply be skipped.<\/p>\n<p>Note: If you have already upgraded to Update 3 RC1 and seen this issue occur, you will still benefit from applying the workaround.&nbsp; It will be too late to recover any deleted alerts, but&nbsp;the script&nbsp;will prevent any further subscriptions from being deleted.&nbsp; At this point it will be safe to re-create any alert subscriptions that were deleted.&nbsp;<\/p>\n<p>We greatly appreciate the feedback we&#8217;ve gotten so far from those who have installed our RC&#8217;s and hope you will continue to do so.&nbsp; Your input goes a long way towards ensuring our RTM releases are of great quality.&nbsp; For step-by-step assistance&nbsp;applying the workaround,&nbsp;you should&nbsp;contact CSS.&nbsp; If you have experience applying SQL scripts to your TFS databases, you can simply&nbsp;email the product team at&nbsp;tfcare a*t Microsoft d*ot com for a copy of the workaround script.&nbsp; As always, if you find any additional issues with this release, please email the product team or open a bug on Connect.<\/p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>UPDATE &#8211; This issue has been fixed in TFS 2012 Update 3 RC2, which is available here: http:\/\/support.microsoft.com\/kb\/2835600 &nbsp; This post is to report a known issue with alerts in Team Foundation Server 2012 Update 3 RC1.&nbsp; There is a partial workaround, which should be applied to the configuration database BEFORE upgrade to RC1 if [&hellip;]<\/p>\n","protected":false},"author":66,"featured_media":45953,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[253,1],"tags":[],"class_list":["post-3033","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-azure-devops-server","category-devops"],"acf":[],"blog_post_summary":"<p>UPDATE &#8211; This issue has been fixed in TFS 2012 Update 3 RC2, which is available here: http:\/\/support.microsoft.com\/kb\/2835600 &nbsp; This post is to report a known issue with alerts in Team Foundation Server 2012 Update 3 RC1.&nbsp; There is a partial workaround, which should be applied to the configuration database BEFORE upgrade to RC1 if [&hellip;]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/3033","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/users\/66"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/comments?post=3033"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/3033\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media\/45953"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media?parent=3033"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/categories?post=3033"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/tags?post=3033"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}