Why do I get error 2147221164?

[HK45acp]

The app was working, then they moved the lab and the app doesn't work anymore.  My job: fix it. 

The local IT Pro has touched the computer, but theoretically didn't do anything that would effect this. I didn't write the code (the author retired) but the basic problem appears to be that it isn't seening the IOTech Personal Daq 3000s.  DaqView, the IOTech app works fine, but nothing in LabView can see them, including numerous example vi's from the daq vendor.  I've tried two things found on the forum

1. delete and replace the Automation Open.vi
2. unregister then reregister the *.ocx files

but neither of these fixed the problem.  The block diagram where the error occurs:

This is in one of the vi's provided by IOTech (Acquisition Initialize.vi).  Probes on the wire from the Refnum constant gave a value of zero.  My understanding is that it's only there to provide a type so this may be correct (?).  The constant has DAQCOMLib.IDaqSystem selected in the ActiveX class, which appears to be correct.  The Refnum out from Automation Open was also zero, which I assume is wrong.

No error in, but the error out wire shows the 2147221164 code and "Class not registered...".

Again, in theory, nobody has touched this code directly.  I'm pretty much out of ideas.  Suggestions?

thx!

[MHoffmann]

Hi,

I would have some additional questions:

1.) Are you using the Report Generation Toolkit for Microsoft Office in your application? Do you acces Microsoft Office over ActiveX?

2.) Can you post a screenshot of the error?

3.) Which LabVIEW and Windows version are you using?

Best regards,

Michael

[HK45acp]

1)  As far as I know, the Report Generation Toolkit isn't being used.  I'll check with the user when I get to work.

2)  A screen shot may be possible, but difficult.  The computer/test set is an isolated setup, but I'll see what I can do.  Is there something in particular you're looking for?

3)  Sorry, meant to add this, but it was late....

     Win XP Pro Sp3

     LabView 2009 Pro Dev Sys, Sp1

     LabvView RT 9.0.1

thx,

[HK45acp]

The Report Generation Toolkit is not being used in the vi.

I can't really get a screen shot, but can tell you exactly what the probe and the Error Out indicator say.

The probe on the Error out terminal of Automation Open.vi (which appears on the Block Diagram of Acquisition Initialize.vi):

Status: True

Code: 2147221164

Source: Class not registered in Acquistion Initialize.vi -> JM_Test.vi

This error code is undefined.  No one has provided a description for this code, or you might have wired a number that is not an error code input.

The Error Out indicator on the Front Panel of Acquisition Initialize.vi says the same thing, except that the last line (This error code is ......) does not appear.

It seems odd that Automation Open would provide a Code and Source, and then say it's undefined.

I also tried copying the entire Block Diagram of Acquisition Initialize into a new, blank vi and using that version.  Didn't help.

thx,

John

[Kira_T]

Hey HK45acp,

Do you have Microsoft Word and Excel installed on this computer?  Sometimes not having them can cause this error. 

Is the administrator on the computer trying to run this VI or is it another user?

Regards,

Kira T

[HK45acp]

Microsoft Office 2007, including Excel and Word, is installed on this machine.

The user does not have Admin privileges (never has), and it originally worked for her.  I log in as an Admin since that was required to do the registration.  The failure symptoms are the same either way.

thx,

[MoReese]

---

@HK45acp wrote:

The Report Generation Toolkit is not being used in the vi.

I can't really get a screen shot, but can tell you exactly what the probe and the Error Out indicator say.

The probe on the Error out terminal of Automation Open.vi (which appears on the Block Diagram of Acquisition Initialize.vi):

Status: True

Code: 2147221164

Source: Class not registered in Acquistion Initialize.vi -> JM_Test.vi

This error code is undefined.  No one has provided a description for this code, or you might have wired a number that is not an error code input.

The Error Out indicator on the Front Panel of Acquisition Initialize.vi says the same thing, except that the last line (This error code is ......) does not appear.

It seems odd that Automation Open would provide a Code and Source, and then say it's undefined.

thx,

John

---

Undefined errors in LV are fairly common.  Most are just general errors and give no information.  This error may have to do with your Active X class.  Is it still pointing to MS Word (Or perhaps your using Excel. I don't recall)?

[HK45acp]

The Refnum constant has DAQCOMLib.IDaqSystem selected in the ActiveX class.  As far as I can tell, the application doesn't point to Excel, Word, or any other MS product.  Test data is saved to a generic ASCII file.

[MoReese]

Yes, I saw that in your original post.  Sorry.

[Kira_T]

Hey John,

This may help to solve your problem.

http://digital.ni.com/public.nsf/allkb/9ACB175F6DE483AE86256B2200776B8B?OpenDocument

It helps to solve problems that occur when you run your executable while not the administrator. Good luck!

Regards,

Kira T