LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error 6

Thanks All

 

Sorry for late reply

 

I have attched the part of the code. This code was working fine for more than a year,all of sudden i have this problem.

 

Thanks

0 Kudos
Message 11 of 17
(976 Views)

I just executed your code for about "29373" times but did not see any error coming up...

 

Are you sure about the file path?

 

Guru

Regards
Guru (CLA)
0 Kudos
Message 12 of 17
(960 Views)

Possible file corruption??

You have been writing to the same file for over a year. The chances of a file corrupting increase with the number of reads and writes.

Have you run a Chckdisk on the HDD to ensure the HDD is not getting tired?

 

Filename shouldn't be the problem here, a checksum error in the file might be causing this error though.

 

-----

Edit:

Are you mapping to a network drive???

this could cause problems if the drive is offline ir the drive mapping has changed and I have seen weird behaviour mapping to network drives before.

 

(Please give us the full path you are entering in the folder box to examine as well.)

Message Edited by James W on 04-21-2010 12:08 PM
CLD; LabVIEW since 8.0, Currently have LabVIEW 2015 SP1, 2018SP1 & 2020 installed
0 Kudos
Message 13 of 17
(959 Views)

Thanks All

 

I change the file everymonth , the file path is\\Ctdwks092\life test data dump\ID 2265 089EDA600 - Drive 13

 

Thanks

0 Kudos
Message 14 of 17
(939 Views)

I guess thats a Mapped drive and as James W meetioned chances that the reconnecting to the drive might not happen when the system is rebooted all the time

 

Guru

Regards
Guru (CLA)
0 Kudos
Message 15 of 17
(922 Views)

Guruthilak wrote:

I guess thats a Mapped drive and as James W meetioned chances that the reconnecting to the drive might not happen when the system is rebooted all the time

 

Guru


 

Yup, You've got a network issue, I saw sonething like this 3-4 years ago when saving to the network at another company.

1) Speak to your network Admin about this

 

****This is the important bit for the work around: ****

2) Write the file locally to the machine every day, and after the successful local write, copy it to the network.

3) Put a popup box on the screen telling you of a failed write on the date that will stay until dismissed but not affect the exectution of your code.

4) (After 2 if you want to be clever) If Error 6 during the Nework copy, try SMTP Emailing it to yourself so you know it has failed and also FWD it to IT admin with an attached subject telling everyone the network is flaky again. - Include date and time of attempted copy function.

 

James

Message Edited by James W on 04-22-2010 09:31 AM
CLD; LabVIEW since 8.0, Currently have LabVIEW 2015 SP1, 2018SP1 & 2020 installed
0 Kudos
Message 16 of 17
(915 Views)

Thanks James

 

This sounds good, i will try this one.

 

Thanks

 

 

0 Kudos
Message 17 of 17
(912 Views)