NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

AxtiveX Error sCode=0xffffbba4

I get the following message dialog AxtiveX Error sCode=0xffffbba4.  Followed by a Run-Time-Error dialog Details: Error executing substep 'Post'  Error Code: -17500, Operation Failed when executing the property loader step.  This test is part of a long  test sequence.  The error occurs when using Widows XP. The error does not occur when using Widows 2000 on the same test sequence.
 
What is the source of this error?  
0 Kudos
Message 1 of 9
(4,953 Views)
Hi Alamo,

Are you able to run a simple sequence that uses the Property Loader step?  Try doing that to see if you get the same error.  If you do get the same error, repair the TestStand 4.0 installation to see if that fixes it.
0 Kudos
Message 2 of 9
(4,928 Views)

Terry,

The problem does not occur when running this sequence by itself, only when part of a larger sequence.  We are using TestStand 2.0.  Please let me know if I can provide additional information.  Can you tell me what causes error 0xffffbba4?

Thanks

0 Kudos
Message 3 of 9
(4,909 Views)
Hi,

Unfortunately, 0xffffbba4 error appears to be a general ActiveX error and doesn't help figure out why you are receiving this error.  Do you get this error the first time that you run this property step or after multiple times?  Also, are you trying to load from a text file, excel, or a database?
0 Kudos
Message 4 of 9
(4,867 Views)

Terry,

I'm loading the file from an Excel spread sheet.  The error happend every time I ran the sequence.  Then I rebooted the PC and the sequence would run sevral times with out happening and then it would start happening again.  I have removed the Windows XP PC from the factory so that I can try to trouble shoot the problem.  Do you have any suggestions where I should start?  

0 Kudos
Message 5 of 9
(4,856 Views)
Hi,

To troubleshoot this, you could try to put this propertyloader step in a sequence by itself and loop on that step repeatedly to see if you get the error.  This is a difficult issue to troubleshoot, since it appears to work if you just run the sequence by itself, but if ran with the larger sequence it fails.  Also, is the Excel file that it is opening always the same file or are you using an expression to determine the file path?  If you are using an expression, then verify that the variable that it is using is always valid.
0 Kudos
Message 6 of 9
(4,823 Views)

Hi,

What information are you loading via the property loader?

Regards

Ray

Regards
Ray Farmer
0 Kudos
Message 7 of 9
(4,817 Views)

Terry,

The property loader step is in a sequence by itself so I can try looping to see if that shows anything.  The file that is loaded is the same file every time and is defined in the proporty loader step.

Thanks

0 Kudos
Message 8 of 9
(4,808 Views)

Ray,

The properties being loaded are,

Result.Measurement[0].Comp and Result.Measurement[0].Limits.Low.

Thanks

0 Kudos
Message 9 of 9
(4,807 Views)