DBC or LDF Format Database File Can Not Be Loaded at NI-XNET Database Editor

Updated May 16, 2024

Reported In



Issue Details

I am able to load certain DBC or LDF databases using the NI-XNET Database Editor. However, when attempting to load specific DBC or LDF database files, I encounter the following error:

The database specified could not be loaded. Either it does not exist, or it is not a valid XNET database.
Why can’t some databases be loaded in the NI-XNET Database Editor? How can this issue be resolved?


The NI-XNET Database Editor may encounter difficulties parsing database files for several reasons. To resolve this issue, follow the steps outlined below.

Setting a Compatible Format (DBC only)

The problem could stem from a compatibility issue, as the DBC file format is proprietary to Vector and not an international standard like FIBEX. To avoid compatibility issues, you need to convert it to DBC format, that is compatible. This requires the use of Vector CANdb++, a freeware automotive database editor.

The steps below explain how to export a compatible DBC file:
  1. Download CANdb++  from Vector’s website.
  2. Open the database in CANdb++ that you wish to convert.
  3. Navigate to File » Export » Into CANdb Network Files...
  1. Check the Use compatible DBC format option in the window and select OK to export the DBC file.
  1. Open the converted DBC file in the NI-XNET Database Editor.

Confirming Text Encoding (for LDF, DBC)

DBC does not specify the text encoding. NI-XNET currently assumes the file is in the operating system’s default locale, which can cause issues when importing files produced on systems with alternate codepages. To solve this problem, follow these steps:

  1. Remove the non-English characters in the database.
  2. Revert to the version prior to NI-XNET 19.1 or earlier.
  3. Set the OS language as English and load the .ldf file. Then revert the language settings back to the local language if you need to use localized LabVIEW.
  4. Convert the file to UTF-8 and back again using Notepad. This appears to fix the encoding, and the file can import as expected. This must be performed on a system using the database’s language codepage. The procedure is performed by:
  • Opening the file in Notepad (You will see that the current encoding is ANSI in the bottom-right of the screen).
  • Select File » Save As, change the text encoding to UTF-8, click on Save.
  • Select File » Save As, change the text encoding back to ANSI, click on Save.
  1. Open the file in the XNET Database Editor.

Clearing NI-XNET Database Editor Cache

The error can also be caused by corrupted or incompatible cached databases with the same alias that might have been left by a previous NI-XNET installation. In this case, it is recommended to clear the NI-XNET Database Editor cache following the next steps:

  1. Navigate to C:\ProgramData\National Instruments\NI-XNET\dbCache.
  2. Delete the affected databases in the directory.
  3. Re-create the aliases for the database in the NI-XNET Database Editor.

Adding the Database as an Alias

You can add the database by selecting File » Manage Aliases » Add Alias... This process may not solve the issue but it will provide an Error code and more information to solve it.