VI Logger crashes during data acquisiton, Engine error, code -2144767259

[Middy]

Using VILogger with Windows XP to log an analogue channel using a PCI6013 card. I had no problems for many months. Now I suddenly keep getting an error (see attached pic) about 1-2 secs after I start to run the task.

I have tried upgrading VILogger to v1.0.1 and upgrading NIDAQ etc. Still getting the error. I have tried completely uninstalling the software (including removing references to National Instruments from the registry) and reinstalling it. Still no luck. I am at a loss as to what to try next. Is anyone else having the same problem?

I saw someone else was having the same problem on this forum a couple of years ago but they solved the problem by uninstalling/reinstalling
the software. That has not worked for me 😞

cheers,
Andrew Middleton

[Mike Wogden]

We are having exactly the same problem.
The system worked on Friday but crashes on Monday.
Must have been a good weekend.
We are using NI-DAQ 7.1.0f1, VI Logger 1.1.1 and Labview Run Time 7.0

Hardware is: PCIMIO16E-4 with SC2345, 2 off AI04, 2 off AI03 and 1off A010.

Your help would be apprieciated.

Thanks

Mike...

[Jeremy_C]

Are you able to successfully acquire data with test panels in MAX? When you tried to uninstall everything, did you delete the C:\Program Files\National Instruments folder on your hard drive?

[Middy]

Couldn't remember whether I did delete the folder so I tried uninstalling it again. I obviously forgot to delete the folder the first time round because it works fine now after re-installing. Thanks for your help....

[Jeremy_C]

Just to clarify, some files are purposefully not removed when some software is uninstalled, specifically some MAX configuration files. This is intentional so that previous settings are maintained. However, in this case it sounds like some of those files may have been corrupted, which a simple uninstall reinstall will not fix. That is why deleting the National Instruments folder forced those files to be reinstalled, which fixed your issue. Thanks for letting me know that your issue was resolved. Have a nice day.

[Bejo]

I had the same problem last week.

After having re-installed twice VI Logger 1.0.1, I was still experiencing the same problem.

Although, I did not attempt to delete the National Instrument folder because I did not want to go through re-installing others National Instruments applications already installed in the same folder.

I found a fix by deleting the "c:\Program Files\National Instrument\Max\config.mxs" file and re-activating the "config.daq" and re-importing the "VI-Logger.xml", stored from a recent calibration. As Max is reloaded after having flushed the MXS file, it creates a new clean "config.mxs" file. The system configuration is empty, i.e. no virtual channel, no Logger task as well. The activation of the DAQ file and the importation of the VI Logger tasks from a stored XML back-up recovers everything.

You must be cautious when deleting the MXS file because it contains the index to previously recorded data with VI Logger. If the data can still be recovered, should the MXS file not being too corrupted, it could be wise to store a copy of the MXS file for later use. Otherwise, flushing the file is the easiest.

Should you don't have a previously back-up copy of the DAQ and the XML files, it appeared that it is still possible to create the two backup files prior to delete the MXS file. Using the MAX embedded export tools, proceed with the backup files creation. One step for each file creation is required. After deleting, moving or deleting the MXS file, re-load the configuration from the freshly created DAQ and XML files. It should work also but it is not confirmed at this point.

It appeared that the MXS file gets corrupted some how and causes VI Logger not being able to use the file anymore.

It was much easier and faster than having to re-install the whole thing without knowing exactly what was going on.

If someone else have any success with my proposal, it would be great that the results be communicated to the NI users community.

Regards!

Benoit Joly,
Software specialist
Amtek engineering services

P.S. There is a typo in the original subject, the error code is not:-2144767259, but instead: -2147467259, as found in the attached picture originally provided. I only mentioned this for allowing the search engine to come up with this comment for allowing anybody else looking for the same error code to find this discussion faster, as opposed to what I went through.

[Tiff]

I had the same problem this week with VI logger 1.1.1. I followed the advice of Benoit Joly in deleting the config.msc (was .msc not .msx in my version) but this didn't solve the problem for me (maybe something else got corrupted?). Ended up uninstalling VI logger and Daq drivers, deleting NI folder and starting again by reinstalling everything - bit of a pain but works now!

[AaronC]

I followed Tiff's idea, however, my issue didn't go away; I repeated the procedure twice! On my third try, instead of updating to Vi Logger 1.1.1, I installed our original version of Vi Logger 1.0.1 and USED that version. After using Vi Logger for a day, I updated to Vi Logger 1.1.1 and our problem did not re-occur.

I hope, NI will resolve this software issue. Thanks to all the users that shared their experience with this particular software issue.