{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 够拽才男人 的问题《SSIS Debugger wont show Progress》','https://www.manongdao.com/q-866569.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
Just wondering if anybody has faced this issue.It does not seem to be package specific and is sporadic. I simply start my SSIS debugger in Visual Studio. The debugger loads and does nothing, I know the package is running because I can see the DTSDebugger in the Task Manager and if I let it run long enough it completes. But I don't get the tick marks or the record counts etc. I have to close my Visual Studio and open it again and it works fine. Please feel free to comment if any information is needed.
相关问题
- SQL Server Import Wizard doesn't support impor
- Resharper 7 on VS2012 ignores assembly redirect in
- Error installing MVVMCross from nuget into a PCL
- Why can't I bind to winproc?
- Bulk insert from excel to sql for selective fields
相关文章
- Visual Studio Hangs on Loading UI Library
- SSIS solution on GIT?
- “Csc.exe” exited with code -1073741819
- Add Fakes Assembly option missing
- Visual Studio wants to build with wrong platform t
- Visual Studio 2012 debug tests keyboard shortcut
- How can I manually fail a package in Integration S
- Visual Studio: How to properly build and specify t
Just noticed that I did not have to exit Visual studio as a whole. If I close my package in Visual studio and open it again, it debugs just fine. Guess it might be a bug or something where it does not reload the execution results in some cases. At least this is a better work around instead of having to close and reopen Visual Studio.