NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

failed create xml parser (NI TestStand 2010)

Solved!
Go to solution

Hi all,

 

I'm getting an xml parser error when I'm trying to open the edit substep of a custom step I have created from the types palette. I have seen a post where someone faced this same issue but that was in Testand 4.1 version and I'm facing this issue in TestStand 2010. I tried registering the msxml4.dll in the pc but that didn't help. This station being a win7 pc, the dll was in SysWOW64 folder rather than System32. 

 

error.PNG

 

Can anyone help me in fixing this error.

 

regards,
NitzZ

0 Kudos
Message 1 of 5
(5,128 Views)

Hi all,

 

Any help?? I still haven't been able to resolve this.

 

regards,
Nitz

0 Kudos
Message 2 of 5
(5,115 Views)

Hey Nitz,

 

As a test point, could you try running TestStand as an administrator to see if the error persists?

 

Does LabVIEW work properly on this machine, and are you able to perform other actions involving TestStand and LabVIEW interaction? For example, are you able to execute sequences, and open VIs directly from TestStand?

 

I can think of two other things to try:

1) Run the TestStand Version Selector and make this version of TestStand active, even if it already displays as the active version. This will re-register some files on the system and may resolve this.

2) In one case, this issue was resolved by repair-installing TestStand. The repair install process only replaces missing files, but it's possible that this will resolve the issue if a file is not being found.

 

Let us know how it goes, and we'll be happy to help further if those steps do not resolve the issue.

Message 3 of 5
(5,106 Views)

I'd recommend repairing or uninstalling and reinstalling teststand.

 

-Doug

Message 4 of 5
(5,104 Views)
Solution
Accepted by topic author NitzZ

Thank you Daliel-E and Dug9000 for replying and trying to help. I kind of figured out a fix for the issue. My collegues searched the web extensively and figured out that the msxml4.dll installation package for win7 was different from that of winXP and installing the correct version solved the problem. Thanks again..

 

regards,
Nitz

0 Kudos
Message 5 of 5
(5,099 Views)