NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Failed create the XML Parser (TestStand 4.1.1)

Hi,

 

recently I get XML-Errors in TestStand Editor and user-specific User Interface (refer screenshots in attachement). In December 2008 both programs works fine. But since this year I get these two errors. I assume one of the following updates can be possible reason of the errors:

 

 - Microsoft Security Bulletin MS08-078 / Security Update for Internet Explorer (960714) or
 - Firefox 3.0.5 (2008120122)

 

Both updates was installed in December before I try to start the TestStand applications this year. Anybody knows how I can restore the old functionality of TestStand?

 

Thank you in advance.

 

Kind regards

Christian

Christian

Test Engineering
digades GmbH
www.digades.com
Message 1 of 6
(5,799 Views)

Christian -

We will try to help figure this out. A few quick questions. It seems that you know exactly what has been installed on the system, so I would assume that no NI updates were installed. What version of LabVIEW are you using? What OS are you using, and is it 32- or 64-bit? Have you seen this on any other system that has similiar NI software versions?

Scott Richardson
https://testeract.com
Message 2 of 6
(5,785 Views)
Hello Scott,

in combination with TestStand 4.1.1 Editor we use LabVIEW 8.6. The user-specific User Interface is running on LV Runtime Engine 8.6. These versions has been installed before December 2008. There was no NI update in period of error occurance.

The error occures only at my developer system (refer attachement to more system information). At production system the user-specific User Interface is still running, but there are no windows updates executed since December 2008.

Kind regards
Christian
Christian

Test Engineering
digades GmbH
www.digades.com
Message 3 of 6
(5,774 Views)
It was suggested by someone here that the Activex XML Parser server that LabVIEW is calling is getting unregistered. I assume that it is attempting to call one of the msxml*.dll files in the C:\windows\system32 directory. The VI that is failing is BDE_createXML_Msg.vi. Do you have the source for this VI? You might want to try to just register the msxml DLLs using regsvr32.exe.
Scott Richardson
https://testeract.com
Message 4 of 6
(5,741 Views)

Hello Scott,

 

exactly that was the cause of error: Class MSXML Version 4.0 was not longer registered on my developer system.

 

While opening BDE_createXML_Msg.vi in LabVIEW a warning message advised against different ActiveX Type Libraries (expected library is version 4.0, detected library is version 5.0, see attachement). In Class Browser were'nt any item of version 4.0. Probably one of the named sofware updates killed the registration in December.

 

But in C:\WINNT\system32\ I found msxml4.dll an have registered as you suggested. After this procedure both errors not longer occures.

 

Thank you once more for help.

Christian

Christian

Test Engineering
digades GmbH
www.digades.com
Message 5 of 6
(5,725 Views)

Hi,

 

I just encountered the exact same problem, I'm also running Labview Developer Suite 2009 with Test Stand 4.1.1.

 

cd \WINDOWS\system32

regsvr32 msxml4.dll

 

got things to work again.

 

Thanks for the posting!

 

Best regards

Simon

0 Kudos
Message 6 of 6
(5,316 Views)