Comments
6 comments
-
Hi Stephen,
Sorry you're having problems, however since SQL Prompt isn't throwing this exception I don't think the problem lies there. I'll have a chat with some of the other guys here to see what's up.
Thanks,
Bart -
Stephen, what's the CPU in your machine please? The reason I ask is that this problem is related to something outside .NET making changes to one of the FPU register.
Thanks,
Bart -
OK, really stupid question: do you have the Times New Roman and Tahoma fonts installed?
Thanks,
Bart -
Also can you verify for me that you're using SQL Dependency Tracker 2.1 please?
Thanks,
Bart -
CPU: Pentium M 1.7 (Thinkpad R50p)
Duh, ummm, yup, fonts are all present and correct
SQL DT 2.2 installed.
Haven't noticed the bomb the last couple of times I've used DT. I did install SQL Bundle on 1/26 at 4:30 pm, after reporting the font problem earlier that day that arose from the SQL Prompt Bundle install on 1/23, so it appears that the SQL Bundle install has fixed the issue. If not, I'll be sure to report back... -
OK thanks Stephen. It's actually a .NET bug with the world's worst workaround. We can fix it when it occurs, assuming we can identify where it's occurring, but it's so rare it's virtually impossible to reproduce.
Cheers,
Bart
Add comment
Please sign in to leave a comment.
A fix version was issued (to me, at least) that was working great - NO Exceptions!
Could you re-bundle SQL Prompt Bundle, please and include the fix...
Thanks.