Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<h1>Fix</h1> <p>No fix is known at this time.</p> <h1>Workaround</h1> <p>Disabling the <strong><em>Tablet PC Input Service</em></strong> (a.k.a. tabtip.exe) from the Services panel in Control Panel.</p> <h1>Details</h1> <p>A few weeks ago I contacted Microsoft Developer support about this issue. I corresponded with a support engineer on the WinForms team and we figured out that this issue was in some way caused by <em>Accessibility.dll</em> being loaded into my application whenever Microsoft's <em>Tablet PC Input Service (tabtip.exe)</em> was running. This service is present on at least all Windows 7 Enterprise installations but is generally only running if you have a tablet PC or have ever installed any sort of pen input device on your PC. I had used a Wacom Bamboo pen tablet on my PC in the past so it made sense why this service was running. <em>Note that it was determined that neither the method I used to populate the <code>DataGridView</code> nor any of the properties I set had anything to do with the issue.</em></p> <p><em>Accessibility.dll</em> is a Microsoft library that allows certain peripherals (pen tablets and especially assistive devices) to more easily interact and get extra information about forms and the controls contained on forms. I'm not 100% sure on this but I believe that this library is loaded into every running Windows process automatically if such a peripheral is installed.</p> <p>After examining a dump that I had provided, the Microsoft engineer was puzzled by the code path that the <code>DataGridView</code> decided to go down and found that <em>Accessibility.dll</em> was the culprit that allowed let it happen. He admitted that <code>DataGridView</code> should not be doing this and that this seemed like a problem on their end. However, he was unable to reproduce the problem on his end even after turning on the Tablet PC Input Service on both his PC and a freshly made Windows 7 VM. So while he was able to identify the key players that caused the problem on my PC he was not able to find root cause and hence unable to pursue it further.</p> <p>This may be attributed to my particular pen tablet device (Wacom) or something else all together. Its unknown. If anyone else encounters this problem, please contact me. The engineer invited me to contact him if I was ever able to narrow down the cause. For now, just keeping the service off prevents the issue.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload