Importing table data is an easy enough task in SQL Server 2005 - but this week we stumbled across this error message:
Error 0xc0202009: Data Flow Task: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Expected the TEXT token in data stream for bulk copy of text or image data.".
(SQL Server Import and Export Wizard)
Funny thing is, there were only nvarchar(max) columns on the table, and no binary columns whatsoever. A bit of searching and more staring at the table definition finally pointed out us in the right direction - the target table has a computed field in it, like so:
Although we had told SSIS to <ignore> it, this error came up. The only work around for SSIS: remove the computed field before doing the import.
Adding an alert via the Team Foundation Power Tools Alerts Editor (October 2008) is innocent enough:
If you close and reopen the Alerts Editors, the alert definiton is still there (in the above screenshot for "A work item was assigned to me"). However, closing & reopening VS is a different thing - now your alert definition is gone - poof, vanished mysteriously.
It took a while and quite a bit of searching, but finally I found out why and made a slight change:
The username that is pre-filled in in the "Send to:" field doesn't work - you have to use your email address! That much for trusting defaults, but I'm more than happy that it now works as advertised.