LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

internal warning 0xB002B199 occurred in DesktopGenInfoVisitor.cpp


@Maxwell.BCool, good move on getting a service request opened up. That's one of the best ways to get things sorted out, I'd focus on that.

Well, the nice people at support at NI and most other places) really focus on closing cases down, not keeping them opened (probably a metric on their performance.)   Unless one's case is impeding important work, the ticket will be closed, a promise to send the case (and my crash report) to R&D, and that's it.

I understand the logic and I'm not expecting someone to fix this problem. I come the forums and sometimes support, mostly to see if someone else has bumped into the same thing. We're on LV2015, LV2017 is the current version, which usually means that unless we can replicate it with LV2017, not that important cases will be just logged.

 

 

0 Kudos
Message 11 of 11
(160 Views)