Internal error in window.cpp at line 15521

[TS9]

I have gotten this error message multiple times ever since I started using Labview 7 a few weeks ago. Labview 7 never crashes with this error. Instead, the next time I launch it, it comes up with a message saying this error occurred. The log file generated is:
####
#Date: Thu, Nov 13, 2003 9:57:58 AM
#OSName: Windows NT
#OSVers: 5.0
#AppName: LabVIEW
#Version: 7.0
#AppKind: FDS



D:\lvworm\src\mgsource\window.cpp(15521) : DWarn:
$Id: //labview/branches/Wormhole/dev/mgsource/window.cpp#283 $
0x00B840AC - LabVIEW + 0
0x00B84427 - LabVIEW + 0
0x00B7FF57 - LabVIEW + 0
0x77E11D0A - USER32 DispatchMessageW + 26
0x77E11BC8 - USER32 GetAppCompatFlags2 + 555
0x77E172B4 - USER32 Dispat
chMessageA + B
0x00B84CA0 - LabVIEW + 0
0x00B3C46B - LabVIEW + 0
0x00C0813C - LabVIEW + 0
0x77E9CA90 - KERNEL32 CreateProcessW + 15A6
0x00000000 - LabVIEW + 0

I am running under Windows 2000. I believe it may have something to do with a virtual desktop manager utility I have (Deskwin) which allows you multiple desktops to place different programs on. If I have Labview7 up on one desktop and go to another and come back, both front & block panels do not refresh properly and I have to drag the panel off screen and bring it back to get it to refresh. Usually, after that if I go to a different desktop and back, the display is ok. I have ran Deskwin with both Labview 5 & 6 with no problems (except probes would not always refresh).

Any ideas?
Thanks,
Trish

[Zvezdana S.]

Trish,
LabVIEW 7 has this new method of error reporting. It will not crash LabVIEW when a .cpp error happens, but it will warn you about the error the next time you launch LabVIEW. You should still be able to use your VI with no problems, which was not always the case with these internal errors in previous LabVIEW versions.
To troubleshoot this error further, I would ask you to send the error report directly to NI. You can do this from the error dialog window that pops up when you start LabVIEW. Please attach the log file, steps that reproduce the error, mention the specifics with you system with virtual desktop, and if possible attach a simple example that demonstrates the problem (the simplier the example the easier it will be to troubleshoot it)
Thanks.
Zve
zdana S.
National Instruments

[Been bitten by LabVIEW]

Was this ever resolved?

[muks]

You have just dug a very old thread. Anyway have you seen this already?