ActiveX error -2147023149 in LabVIEW 7.1 but not LabVIEW 6.1

[AllanS]

This is an interesting problem. There is a Tektronics ActiveX control for a TLA700 that works flawlessly in LabVIEW 6.1. An upgrade was made to LabVIEW 7.1 and when simple calls are made to this ActiveX component it throws the error "-2147023149". On google I found:

-2147023149 == "The authentication service is unknown."

A final note is VB and VC++ have no trouble using this control on the same machine.

I have searched every possible resource availible and am getting no where on pin pointing where this error could be coming from. Anyone have any ideas or even seen this error before??

[Steven Bird]

Allan,

Have you managed to solve this issue. I work for NI and I am working with another customer on a similar issue. Before escalating the issue further up the NI ladder as it were I wondered if you solved this issue?

Kind Regards


Steven Bird
Applications Engineer
National Instruments

[GlenX]

---

@AllanS wrote:
This is an interesting problem. There is a Tektronics ActiveX control for a TLA700 that works flawlessly in LabVIEW 6.1. An upgrade was made to LabVIEW 7.1 and when simple calls are made to this ActiveX component it throws the error "-2147023149". On google I found:

-2147023149 == "The authentication service is unknown."

A final note is VB and VC++ have no trouble using this control on the same machine.

I have searched every possible resource availible and am getting no where on pin pointing where this error could be coming from. Anyone have any ideas or even seen this error before??

---

Has this issue been solved? I am having the exact same problem.

[AESulzer]

Is there any text associated with the error you are getting?
Can you narrow down at what point in the code the error is being returned?
If you could post a very simplified example with a detailed description, we might be able to lend a hand.

Regards,

[benv]

I have just run into this problem (rather it ran into me...  I was sitting innocently at my desk minding my own business when it was dropped in my lap).

Our IT people upgraded a PC to XP and labview to version 7.1, and the  Automation Open call that formerly worked now throws an Access is Denied error.

I think if we update our analyzer we'll have access to labview drivers or .Net hooks to do a work around, but if anyone has figured this out, I'd appreaciate it.  For starters, it'd be good to know if I should update the PC to 8.20, or if that wouldn't make any difference.  I'm very surprised it appears to be labview version dependant, I would have bet on a windows security issue, or a type library registration issue.

[benv]

I should also point out that instead of the above error number, I see: -2147024891 Access Is Denied in...

[Brian_K.]

Hi benv,

I can see that this problem seems to have come up slowly over time.  By searching for it I can also see that the problem occurs in Visual Basic and Visual C.

Historically the problem has only occured with computers running LV 7.1.  No customers have reported it in later LabVIEW versions, but they also haven't confirmed that the problem went away with LV 8.0.

You may want to look at this KB to see if it is relevent:

http://digital.ni.com/public.nsf/websearch/E153ADE83AEEA7B386256E8C004B7293?OpenDocument

Tell me if it solves the issue.

[benv]

Brian,

dcomconfg is something we've spent a lot of time with over the last few days, and it seems like we've got all our settings where both the page you linked and the Tektronix people agree they should be. 

I think we're going to try to either move to 8.0/20 or roll back to 7.0.

Thanks for the help

[Brian_K.]

Hi benv

Sorry I could not be more help.  If you do upgrade to 8.0 or 8.2, could you give the results.  It would be nice to know for future troubleshooting.

[benv]

Sorry, we didn't go forward to 8.0, but we did get it to work with 7.1.  Updating the TLA software on the analyzer seemed to be the big factor in getting it to work.