Learn to use Visual Studio, Visual Studio Online, Application Insights and Team Foundation Server to decrease rework, increase transparency into your application and increase the rate at which you can ship high quality software throughout the application lifecycle
UPDATE - This issue has been fixed in TFS 2012 Update 3 RC2, which is available here: http://support.microsoft.com/kb/2835600
This post is to report a known issue with alerts in Team Foundation Server 2012 Update 3 RC1. There is a partial workaround, which should be applied to the configuration database BEFORE upgrade to RC1 if possible. This issue will be fixed in Update 3 RC2.
This bug causes some alert subscription evaluations in TFS to fail with an exception (an XPathException), even though they are actually valid. Upon receiving the exception, the exception handler will treat the corresponding subscription as invalid and delete it. The alert will not be sent, and will be removed from the system incorrectly.
We believe this problem is fairly widespread, and customers who use their server regularly can expect to see the bug arise almost immediately after upgrade. It will occur as soon as an event (such as a check-in, creation of a work item, etc.) is triggered on the server.
Those affected by this bug will see errors in the following form:
[EntryInfo]Message: TF53010: The following error has occurred in a Team Foundation component or extension...
Detailed Message: The subscription for contained an invalid condition ""PortfolioProject" = 'XYZ AND "CoreFields/StringFields/Field[Name='Created By']/NewValue" = '@@MyDisplayName@@' AND "CoreFields/StringFields/Field[Name='Authorized As']/NewValue" <> '@@MyDisplayName@@'" which could not be evaluated.Exception Message: 'USER' as an invalid token. (type XPathException)
If you are thinking of upgrading your server to Update 3 RC1, please contact Microsoft Customer Service and Support (CSS) or TFCare a*t Microsoft d*ot com for a SQL script that should be applied to your configuration database first. This script will not stop the alert evaluation exception from being thrown, but it will prevent the TFS notification job from deleting alert subscriptions. Instead, the alert will simply be skipped.
Note: If you have already upgraded to Update 3 RC1 and seen this issue occur, you will still benefit from applying the workaround. It will be too late to recover any deleted alerts, but the script will prevent any further subscriptions from being deleted. At this point it will be safe to re-create any alert subscriptions that were deleted.
We greatly appreciate the feedback we've gotten so far from those who have installed our RC's and hope you will continue to do so. Your input goes a long way towards ensuring our RTM releases are of great quality. For step-by-step assistance applying the workaround, you should contact CSS. If you have experience applying SQL scripts to your TFS databases, you can simply email the product team at tfcare a*t Microsoft d*ot com for a copy of the workaround script. As always, if you find any additional issues with this release, please email the product team or open a bug on Connect.
I get a key length warning when I applied the above to my (already upgraded environment):
Warning! The maximum key length is 900 bytes. The index 'PK__#33A0343__8CD42C8A35887CB1' has maximum length of 1040 bytes. For some combination of large values, the insert/update operation will fail.
Warning! The maximum key length is 900 bytes. The index 'PK__#3770C52__8CD42C8A39590D95' has maximum length of 1040 bytes. For some combination of large values, the insert/update operation will fail.
The environment seems ok though.
Hi Peter - That warning can be safely ignored.