T-SQL editor error - by Ming Tsai

Status : 


Sign in
to vote
ID 785917 Comments
Status Active Workarounds
Type Bug Repros 0
Opened 4/30/2013 7:24:12 AM
Access Restriction Public


T-SQL editor does not work. (empty)

I got this error when I click on SQL Server Object Explorer:

System.TypeInitializationException: 'Babel.LineScanner' 的型別初始設定式發生例外狀況。 ---> System.InvalidProgramException: Common Language Runtime 已經偵測到無效的程式。 於 Babel.LineScanner..cctor() --- 內部例外狀況堆疊追蹤的結尾 --- 於 Babel.LineScanner..ctor() 於 Microsoft.VisualStudio.Data.Tools.SqlLanguageServices.LanguageService.GetScanner(IVsTextLines buffer) 於 Microsoft.VisualStudio.Package.LanguageService.GetColorizer(IVsTextLines buffer) 於 Microsoft.VisualStudio.Package.LanguageService.GetColorizer(IVsTextLines buffer, IVsColorizer& result) 於 Microsoft.VisualStudio.Editor.Implementation.LanguageServiceClassificationTagger.TryCreateTagger(ITextBuffer textBuffer, IVsFontsAndColorsInformationService fontAndColorInformation, Int32 longBufferLineThreshold, LanguageServiceClassificationTagger& classifier) 於 Microsoft.VisualStudio.Editor.Implementation.LanguageServiceClassificationTaggerProvider.CreateTagger[T](ITextBuffer buffer) 於 Microsoft.VisualStudio.Text.Tagging.Implementation.TagAggregator`1.GatherTaggers(ITextBuffer textBuffer)
Sign in to post a comment.
Posted by Microsoft on 4/29/2014 at 12:30 PM
Thank you for reporting this issue. This issue has been fixed in Visual Studio 2013. You can install a trial version of Visual Studio 2013 with the fix from: http://go.microsoft.com/?linkid=9832436
Posted by Microsoft on 7/3/2013 at 9:06 AM
Please install the June 2013 release of SSDT. We were unable to repro - it's probably an issue that'll be solved with a new installation or repair of the old one.
Posted by Microsoft on 4/30/2013 at 7:52 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 4/30/2013 at 7:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)