LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

DOMUserDefRef.dll

Hello Everyone,

I am currently having a problem with building an executable that is interchanging data with a XML file.

I can build the application and when trying to run it, I get an unidetifieable error messages from Windows telling my that my application has to be shutdown due to an error with the file DOMUserDefRef.dll.

It seems to me that the file is missing, ALTHOUGH it is included in the <data> subdirectory of the build.

I then tried to add it manually with including the paths "C:\Programs\National Instruments\LabView 8.6\resource\DOMUserRefDef.dll" and "C:\Programs\National Instruments\LabView 8.6\resource\nixerces27.dll"into the "My Computer"section but this didn't help either. In the build specifications the two above mentioned files are always included and copied into the <data> subdirectory. When looking into the dependencies, the name DOMUserDefRef.dll is also mshown, but without a path specified.

I have included the lvproj file and hopefully somebody can tell me what is wrong or missing here.

0 Kudos
Message 1 of 8
(4,959 Views)

Hi,

 

maybe your files are damaged in the past and now you'll get these error now from your system.

Do you have the opportunity to get this files from a "clean" system, maybe from a PC which is preferably new. You just try to copy the files into your build and see if it works.

You can also try to choose only the "nixerces27.dll" for your build and see if the error still shows up

 

Michal F.

0 Kudos
Message 2 of 8
(4,930 Views)

Hello Michael,

 no, this didn't help. I can remove the DOM DefRefUser.dll from the "My Computer" section, but it is still in the dependencies and is not removeable there.

I have started this project some weeks ago, but I only now came to the point of building it.

Do you know if LabView 2009 users reported the same problem?

 

Thanks for your reply

Ralf-Peter

0 Kudos
Message 3 of 8
(4,917 Views)

Hello Michael,

I found the error:

I am using the XML close VI  to close the file after reading. When running the VIs in the development environment the sequence of first reading the data and then closing the XML worked fine, but in the executable it seems there was a runtime problem, so the file was closed before all reading of XML objects was done.

Here I encountered a problem with LabView again that I found several times before:

The error messages that LabView generates are of no use especially when it come to use data from other platforms or data formats.

A pop-up error message in the executable saying "DOMUserDefRef.dll error" and even "DOMUserDefRef.dll missing" leads  you in the completely wrong way.

A simple message saying "File reading error: File closed before end of read operation" would be absolutely perfect and give you all informations that you need for solving problems.

Error codes like -2627 "Unknown user error" or -2629 "Unknown error"are completely useless as well.

0 Kudos
Message 4 of 8
(4,907 Views)

Seems like this has been independantly reproduced! as explained here

Smiley Surprised

Add the following vi to your project and see if things improve

CM.pngEyeDeeTenTee.png

 

ALSO: Note yet another occurance of the context help not updating!  Whats the vi name in the title bar? Now look at the Context Help banner "Untitled 3.vi"  Smiley Frustrated

 

 


"Should be" isn't "Is" -Jay
Message 5 of 8
(4,899 Views)

rpweber.

 

What version of the app builder are you using?


"Should be" isn't "Is" -Jay
0 Kudos
Message 6 of 8
(4,885 Views)

Great stuff! I have had the problem that after masscompile of a project A I have got warnings during loadup of project B telling me that the path to DOMUserDefRef.dll has been changed - though I do not use any VI calling that dll. I have tried a lot to get rid of this problem without success. Now I have added that VI you have suggested to my project and: I do not get the warnings any more! Thank you very much for this tip!

0 Kudos
Message 7 of 8
(4,854 Views)

Addition: I have then removed the added VI from the project B again and now the project B can still be opened without warnings! - My guess is that it is just enough to open-save-close the "new.vi" and the "close.vi" from the NI_XML.lvlib to solve problems of that kind.

0 Kudos
Message 8 of 8
(4,851 Views)