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.
