Re: Error Thread.cpp Line 1938
Hello Sly, Are you, by chance, running on a Dell Dimension 4500 Slimline Series desktop (or similar model)? Due to limited PCI slots on some of these models, they require a PCI expander/splitter that allows for 2 PCI devices to be plugged into the same slot. You may have the GPIB card and the network interface card (NIC) connected to the same PCI slot. If this is the case, the NIC might stop working a well. This may be a system resource conflict issue. You should remove the network card (or any other card that may be sharing the same PCI slot) to fix this problem. Please let me know if this particular situation applies to you. If not, post the applicable portions of your code and any other information that may be useful, and I=92ll be happy to look further into it. Have a nice day! Robert M Applications Engineer National Instruments
Re: Error Thread.cpp Line 1938
Hi Robert, I do have a Dell PC, but it's a Dimension 2400. I do not have a GPIB card on my system. The only card that I have is a network card. I got the same error today, but it also included a bunch of Open File VI errors with it. Don't know if that will help. Also, something that I forgot to mention is that I am opening Microsoft Access with Labview. I got this VI from your website that allows Labview to open application with the press of a button. I am not sure if that's the problem. I don't think it is because it always happen overnight when no activity is present. I was going to included the source code but I kept getting this error that I couldn't. I was wondering if I could email it to you. You can reach me at [EMAIL PROTECTED] to let me know if I can email you my source code. Thanks!
Error Thread.cpp Line 1938
Hi, I keep getting this error when I run my executable. I am using Labview 6.1 on Windows XP. I followed the troubleshooting guide from NI website to disable the run in multithread and I am not calling any library(that I know of). My application does use the Database connectivity toolkit which communicates with a Microsoft Access Database and I am using Kepware OPC server to communicate with an HC900. The error doesn't show up right away. It seems to happen after it runs for 12 hours or more. I disabled the hibernation on my PC, the screen saver, I also disable a whole lot of services that loads when windows opens and I still keep getting the error. Another thing that my application does is it stores temperature values into files. I am using multiple open, write and read file VI. I was thinking that maybe this is the problem, but I have created other application in the past that uses multiple of the same VI with no problem. Another thing that comes into mind is that the files that are being created are being open also into graph/chart. Could this error happen when I try to open and write to the same file at the same time. Any help at this time would be much appreciated. Thanks in advance
