ActiveX with LabView error 0x80070002

trying to use LabView to control another program which has a COM interface. I can select the Interface from the Ref control and I can see the methods associated with it but the Invoke call always returns an error and the errors are different. 0x8007002, 0x8003000E(??) I need more detail on how LabView uses the registry to attach to the COM object. I have read a bunch of various docs but still don't have a clear picture of what steps occur. The program is a seperate .EXE running in it's own address space not a .dll. Any COM Automation wizards out there?

Hi twowheels,
I am sorry for the misunderstanding with the COM interface. Which methods in the Type library are you trying to access? One possible method for finding out the correct way to reference the functions is to find someone else’s code that calls the method correctly and rebuild the process in Labview. I hope this is helpful and I understand the situation now.
Andy K.
Applications Engineer
National Instruments

Similar Messages

Bug Appeal: LV6 activeX with Excel; Error -2147319784

At Thu, 16 Nov 2000 14:55:00
"Dominic Lavoie" wrote:
<-2147319784 Old format or invalid type library.
Dominic and others
This is an old bug in LabVIEW that I have been fighting
with for several years. The problem (as I have seen it) is that
LabVIEW for some reason on some PC's suddenly becomes unable to read
from the (NT-) registry that Excel is installed as an
available ActiveX component on the machine. In my case the
Excel8.olb file.
Under earlier verion of LabVIEW no error messages
was generated, but you could see the problem when entering
the list over ActiveX classes, Type library. Suddenly the Excel
would be gone from this list, and it will not come back no matter
how you try to install, reinstall or reconfigure the Excel (or Office)
system. (And the Regsvr32 program does not handle OLB files.)
The only way I have heard to fix it, is to reformat the
harddisk and install the OS and everything fresh. But you might
see the problem coming back again.
There might be a possibility that this bug is not NI's, but one
in the OS. When I use other programs to View/Edit the registry,
these programs have no problems of detecting the Excel library.
So I believe it is a LabVIEW bug !
When working with Excel and ActiveX with this problem
meant that you had to manually browse to the OLB file each time you
would want to work with it, or you would sometimes get messed up
the wires and VI's working against the Excel library.
Now, under LabVIEW 6i, this situation creates the error message
-2147319784, and the problem suddenly seems much bigger.
I have reported this bug two month ago to NI, together with some
other people that has seen the same problem. So far NI has not
been able to locate the problem in detail or done anything with it,
as far as I have been informed.
This has been a very frustrating experience for me, because there are
many other features under 6i that I would like to use right away.
But since I am working a lot with Excel as a data format from LabVIEW,
I cannot proceed with 6i before they have broken this bug.
So now I would like the LabVIEW community to help me push NI
a little in their effort to debug this one.
All questions of course assuming that you have installed Excel
on your PC.
Could as many as possible out there check out if,
when testing the ActiveX/Excel examples;
A) under 6i; do you get the Error -2147319784 ? (YES or NO)
B) under 5.1.1 or earlier; can you run the example Write Table to XL.vi ?
(YES or NO)
C) if B=NO, can you locate the Excel library in the ActiveX class list ?
(YES or NO)
D) Where in the world are you located (country) ?
(Some has speculated that this bug might be connected to a problem
with different OS versions in different parts of the world.)
E) What version of Excel are you using ?
F) What OS are you running ?
If you can't do both A and B/C, send me the one you can.
Please report your results directly to me.
DO NOT REPLY TO THIS LIST. I will send a
summary after a couple of weeks, to let you know
the results. And also if NI seems to make any progress here.
best regards
Martin Plassen

"[email protected]" wrote in message
news:[email protected]...
> Martin, I'm not sure how to reply directly to you. (I can't find your
> email address or anything.) I may be experiencing a very similar
> problem. I am trying to generate Excel reports using LabVIEW 6.0
> under a Windows 2000 OS. Under Win95 in LabVIEW 4 I had no problem
> but I recently updated. Now I can't even open Excel using the NI
> distributed LabVIEW 6i Excel toolkits from ni.com. When I execute the
> Open Excel vi I get a Windows error message, "Labview.exe has
> generated errors and will be closed by windows. An error log is being
> created." Could this be the same problem dominic was having under WIN
> NT?
dmbillings
It seems NI has been so kind as to remove the fix on this problem
from their Knowledgebase. Well, I dug up some old e-mails on the subject,
and here's one you should look through. According to NI this problem
should have been fixed under LV 6, so I really hope this is not what you are
facing...
Martin
Good news for all of you,
we have a bug-fix that seems to do the trick.
Here's the recipe , with my words:
Do You have the bug ?
You can confirm that the bug is there, by opening a new file in LabVIEW,
in the diagram, insert an Automation Open.VI, right-click on it,
Select ActiveX class, Browse, and check the Type Library list.
You should not see the Microsoft Excel5 and 8 library in the list,
if the bug is there.
As I have suspected for a long time, the whole bug was related to
how LabVIEW read the registry at startup to locate all ActiveX
components on the machine.
Here's the fix to try out;
1. Open the RegEdit program
2. Under HKEY_CLASSES_ROOT locate the TypeLib
3. Locate the Excel-key
On my machine this is {00020813-0000-0000-C000-000000000046}
(You will find it on top part, I think, not necessary to browse long
down.)
4. There are two base keys there, named "1.0" and "1.2".
Under the "1.0"-key, right-click and create new key, name it "0"
(zero).
5. Under the new "0"-key, create a new key kalled "win32".
6. Under the "1.0"-"9"-"win32" key you will find the link to the
Excel5-library on the machine, copy this link into the key you created
under pt 5.)
On my machine this is "C:\Program Files\Microsoft
Office\Office\XL5EN32.OLB".
That's all. Exit RegEdit.
Afterwards, check again that the Microsoft Excel5 and 8 libraries
is on the LabVIEW list mentioned above. After restarting LabVIEW of
course. It is not necessary to restart the PC.
Attached you wil find two gifs showing how this should look
in RegEdit before and after the described operation.
Good luck
PS: hacking around is the registry are do be done with
caution. The wrong actions here could have large consequences.
The two attached pictures should help you out,
but if you feel uncomfortable by working with the registry,
try to hook on to some hacker around that has been there before.
As I understand it, this is the reason that NI asked me also not to
give this info directly to the List-server. So please don't do it
you either. I plan to put the word out about the fix, not with these
details, but with a reference to the NI Knowledgebase that soon will
have this info.
You are welcome to send me a conformation that you see the
fix is working, or worst case, not.
Martin

Lost ActiveX connection with LabVIEW server

I have called LabVIEW in TestStand and tried to execute the test cases .
While executing I got the following error: ( Lost ActiveX connection with LabVIEW server.
The LabVIEW adapter will try to reconnect on the next execution attempt.-18001; An error occurred accessing the LabVIEW ActiveX automation server.).

Same error. Is anyone from NI going to bother commenting on this? It's been >8 months...

Controlling Labview with C#: error code -2147352571

Hi,
I need to call LabVIEW and pass parameters to LabVIEW from C# so that I can use labview as a sort of "driver" to control my signal generator from C#.
I found this tutorial for controlling LabVIEW from C#: http://zone.ni.com/devzone/cda/epd/p/id/3838
It contains a C# project that calls a vi which acts as a calculator, parsing a string and computing an answer.
     I am trying to use this file as a base to work from by changing a few lines to make C# code that calls a different vi (the one that controlls my signal generator).
I have attached both the Signal_Generator_Controller_For_Sentry_Testing.vi and the CallLV project that I modified and the origional from NI.
I get this error when I click "Run vi" from the C# gui:   Type mismatch. (Exception from HRESULT: 0x80020005 (DISP_E_TYPEMISMATCH))
If I click "view detail" from the "COMException was unhandled", I find that the error code is -2147352571. The error occurs at this line in the C# code:
//Call the VI
vi.Call(ref param1,ref param2);
     Here are the experiments I performed (that didn't solve the problem):
Since the demo vi that NI made is contained in a llb file, I built a project that contained this vi, added an llb file to the project, and put Signal_Generator_Controller_For_Sentry_Testing.vi in the llb file.
My vi is all inputs (the only output is the signal generator, which is not on the front pannel, obviously). I have tried changing the connector pane so that one of the connectors was an output.
I have tried googling the error messages: there isn't anything specific enough to this problem (C# communicating with labview), the error message occurs in situations in multiple programming languages.
I have tried passing the parameters "by val" rather than "by ref", but a different error occurs.
     Here is what I am able to deduce/ what I have noticed:
The vi that NI created to demo communicating with C# "seems to be unable to leave run mode". When you call Labview from C#, the front pannel comes up and you cannot select the "stop button": it is grey. The Pause button doesn't stop exectution either. This makes me think that the vi was compiled in a different manner. I am more inclined to believe that teh vi is formated incorrectly rather than the C# code working improperly.
The types of the two parameters, param1 and param2, going into the call statement are "string" and "object" respectively. This is the same as with the NI code, which works fine. It is not an error with an incorrectly sized array parameter; that gives a different error message and I have fixed that problem. So, even though the error message says "type mismatch, I don't think that the input parameters to the Call function are incorrect.
   To Reproduce this error:
I have Microsoft Visual C# Express 2008 Edition
I am using Labview version 8.6
In my version of the C# code, in this line: string vipath = @"C:\Program Files\National Instruments\LabVIEW 8.6\builds\Sentry_Test\Sentry.llb\Signal_Generator_Controller_For_Sentry_Testing.vi";
You will have to change the directory to wherever you store the vi.
You will need the "Labview" Library so that the C# line "using Labview" will work. I think it is downloaded by default either by labview or visual studio.
In the C# file that NI created, you must add a fourth parameter '3' in the line vi= lv.GetVIReference(vipath,"",true) as the last parameter. You get a compiler error otherwise. That was a mistake NI made.
Thank you for the help.
--Zach
Attachments:
CallLV_Zachs _Version.zip ‏126 KB
callLV_NI_Version.zip ‏48 KB
Signal_Generator_Controller_For_Sentry_Testing.vi ‏12 KB

Zach,
Unfortunately, I do have more of a knowledge
of how to control objects using ActiveX in LabVIEW and not the other way
around. What ActiveX properties and methods are you using in your code and what are the input parameters that you are trying to pass? You mentioned that you only have two input parameters, but the VI you posted has 3 inputs. My guess would be that if you are indeed seeing a type mismatch, it is trying to pass an data type LabVIEW does not know what to do with. This has been seen when trying to pass strings as Task data types (like the VISA Session).
ColeR
Field Engineer

I am using report generation toolkit 1.1 with Labview 7.0 and Office 2003 professional. The create new report VI opens Excel but throws error (-2147167262- from automation open VI) when I try to open MS word. please help...

I am using report generation toolkit 1.1 with Labview 7.0 and Office 2003 professional. The create new report VI opens Excel but throws error (-2147167262- from automation open VI) when I try to open MS word. please help...

Hi Leo22,
Does this error occur if you use any of the example programs that come shipped with LabVIEW? I would try opening one of the examples that write data to Word and see if those give you an error. Also, have you tried just putting down a New Report.VI and change the report type to Word? If this simple vi (that's all you need to open Word) breaks, I would check to see if there are any instances of Word still open. Check the task manager to see if any word processes are still open. There should not be a problem accessing Word 2003 from LabVIEW 7.0. If neither of these solutions work, please give some more detail about your application and we can research further. Thanks!
Jeremy L.
National Instruments
Jeremy L.
National Instruments

Problems with Labview and Windows XP with error -2147217865

Hello. Im a new beginner in Labview and am having a problem with a error message
I dont understand. Im running Labview on a pc-logger with windows XP.
The program is written by a guy on my university, and logs voltage from
a solar cell panel. He doesnt have the time to check in to it, so Im supposed to
find out what's wrong.
The error message is as follows :
Error -2147217865 occured at Cmd Execute.vi->DB Tools Insert
Data.vi->Solcelle.vi
Possible reasons :
Exception occured in Microsoft OLE DB Provider for ODBC Drivers,
[MySQL][ODBC 3.51 Driver][mysqld-3.23.38-log]Can't open file :
'solcelledata.MYD'. (errno: 145). in Rec Create - Command.vi-
>Cmd Execute.vi->DB Tools Insert Data.vi->Solcelle.vi
I really hope someone can tell me what's wrong and specifically what to do
with it, or possibly guide me to someone who could suggest a solution to this
problem.
Reguards
chrisdee

Hi Chrisdee,
(.. not to discount what TimoS has suggested, however...)
Embedded in the error information you provided:
... Can't open file : 'solcelledata.MYD'.
Sounds like the program needs this file? Has the program been moved to a new location?
just a wild guess!
Cheers
Message Edited by Dynamik on 10-06-2005 04:53 AM
When they give imbeciles handicap-parking, I won't have so far to walk!

Error, in Getting started with Labview. Chapter 3, part 4.

Hi.
Still struggling on, trying to find the time to work through the "Getting Started with LabVIEW" document.
Only 19 days left to go, and I'm still only in chapter 3!...
Right. In the "Saving Data When Prompted by a User" exersise, part 4...
4.   Right-click the Signals input of the Write To Measurement File
      Express VI and select Insert Input/Output from the shortcut menu to
      insert the Comment input.
Problem is, that option is greyed out, so not available!...
I did what the instructions said, I right clicked on the "Signals" input, and it doesnt do what it says on the tin!
Any pointers?   Please don't mention search the help, I've crashed the entire LV environment 3 times now, trying to search for something in there. It's OK if it finds someting, but it seems to bomb at times, when there is some ambiguity when searching.
Also, I won't be able to do anyting with any replies for a day or two, as I have to go up country to a customer, and mess about with hot oil, high volts, and lots of RF. It never ends.   (I've still got the day job to do, while trying to fight my way through this "evaluation". 30 days of "Use" would be better, than 30 calendar days for some of us.)
Regards.
Dave Baxter.
Technical Manager: AR-UK Ltd.
AR United Kingdom
OK... Who let the smoke out?

Hi Dennis, and everyone else..
That is not how it looks when first dropped on the BD. On my machine, it is partialy expanded by default, after you clear the Configure dialog that pops up ocupying most of the screen.
Again, if it makes a difference to the way the Right Click shortcut menu works, it should be documented in the Getting Started document, especialy as it seems to be a critical point.
OK, explain this...
I've just rubbed out the save to file VI, cleaned up the broken wires etc, and then planted a new one on the BD. Once I cleared the Configure dialog that covers up most of the screen before you see it the first time, the VI was partialy expanded. I forget the exact list, but "Signals" was not at the top.
I did *EXACTLY* the same again, deleted it, cleaned up, and then planted a fresh new one. That DID appear that time with nothing but the "Signals" item showing, and two down caretts below that, indicating more items.
So......
Why the different behaviour each time, on the same BD, in the same session. Some underlying working data not being correctly initialised when invoked? Of course, that never happens, right? ('C' programmes eh?)
Trying some more, it seems the behaviour loosley depends on just how close to the edge of the While loop grey border you place it.   Odd.   I have a 1280x800 screen to play with, and a 1280x1024 second screen I use for the Getting Started document. That is the absolute maximum I can have, due to hardware limits.
I also find, that if you fully expand the "Write to Measurement File" VI block, then fully collapse it, then expand it again, all the items in that list have changed places! Why?
I had noticed earlier that there is no uniformity in the layout of even the items common to many if not all VI blocks (error in, and error out to name but two) Sometimes one is above the other, sometimes the other way round, sometimes they are not even ajacent to each other. Has that been done as a source of minor ammusement or something?
Talking to another colegue here, who just wandered in to see how I was getting on with this. Seems he also has tried the introductory entry into LV (V8.something) in the past. But he too, found too many things that behaved differently from one time to another, so abandoned it as a lost cause, then decided to learn how to use Visual Basic with NI-GPIB IO instead.   Not without issues either he said, but at least it all behaves exactly the same, each and every time.
End of the day now...
Regards.
Dave B.
OK... Who let the smoke out?

Labview 8.5.1's MathScript window failed running imread with an error "A problem occurred in a subVI call."

Hi,
I am trying to port a Matlab program into a MathScript script. Following is the first few lines of the script:
clear;
image1=imread('C:\LV_VertAlign\DSC_0104.jpg','jpg');
image_double1=im2double(image1);
image_gray11=rgb2gray(image_double1);
In the first line, imread is supposed to read in a photo taken from a DSLR camera, so I think it's a 32-bit image. And this is the error I got when trying to run this script in the Labview 8.5.1's Mathscript windows:
"Error in function imread at line 2. A problem occurred in a subVI call."
What is the problem here? and why does it complain about a subVI call?
Thanks for any help to point me in the right direction.
-Anh

Hello Anh,
As you may know, LabVIEW MathScript is implemented on top of LabVIEW. The error message you received indicates that a problem occurred in one of the LabVIEW subVIs that MathScript calls. As Jim indicated, the problem is in the file type specifier you passed to the function. MathScript requires the use of 'JPEG' and not 'jpg' or even 'jpeg.' In this case, we could return a better error message. I have filed a bug report (115804) for this issue.
You will find that once you fix this, the im2double and rgb2gray functions are not supported. In LabVIEW MathScript, you generally can execute scripts written in the MATLAB® language syntax. However, the MathScript engine executes the scripts, and the MathScript engine does not support some functions that the MATLAB software supports.
We will look into adding these functions in a future release of LabVIEW MathScript. If you need this functionality now, these functions are very simple to write yourself. If you are performing additional image analysis in your script, you may wish to purchase the IMAQ toolkit. It doesn't add any functions to MathScript at this time, but you could continue your analysis outside of MathScript with LabVIEW VIs.
MATLAB® is a registered trademark of The MathWorks, Inc.
Grant M.
Staff Software Engineer | LabVIEW Math & Signal Processing | National Instruments

Coming up with the error - "Runtime error '429': ActiveX Component Can't cr

Hi,
While trying to edit the XML tag in a .rtf file (Microsoft Word 2010), coming up with the error - "Run time error '429': ActiveX Component Can't create object.
Any help in resolving this is greatly appreciated.
Rgds,
Kiran Panditi

Remove and reinstall dotnetfiles by running setup.exe located at the following path:
32 Bit Win 7
C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\DotNetInstallFiles
64 Bit Win 7
C:\Program Files (x86)\Oracle\BI Publisher\BI Publisher Desktop\DotNetInstallFiles
FYI, BI Publisher Template Builder 10.1.3.4 does require Administrator rights to run.
Cheers,
ND
Use the "helpful" or "correct" buttons to award points to replies / Mark the thread as answered, if your question is answered.

Error when building Installer with USI 1.5.0 with Labview 8.5

I used to build an installer with Labview 8.2 and included this additional installer USI 1.5.0 but now with labview 8.5 it gives me an error:
"Locate the "NI LabVIEW" distribution. LabVIEW needs to copy a component installed or updated by the distribuiton to conitnue building the installer"
Any advice

Hi reza_sed,
Thank you for contacting National Instruments. When you get this message, are you prompted for a location of this installer (CD drive or something)? Sometimes if components are installed together, certain dependencies are created. You might be able to add the installer to a LabVIEW 8.2 installer with no problem, but the installer cannot be found when using a different version of LabVIEW. You might try uninstalling USI, then copying the install files from the CD or from our website to your hard drive and then installing from there. Then, you should be able to include the additional installer.
Another thing that may be happening is that the LabVIEW Run-Time Engine you have for 8.5 does not support NI-USI. The full version of the Run-Time Engine supports NI-USI, but the web browser only version does not. Make sure you select the full version when installing.
Donovan

Error -18004 with LabVIEW Adapter using LabVIEW Run Time Engine 7.1.1

Hi to all,
I am trying to use the LabVIEW Run Time Engine 7.1.1 instead of the Development System for executing VIs in TestStand with the LabVIEW adapter.
The Problem is that I get the following error, saying that my VIs cannot be executed:
-18004; An error occurred accessing the LabVIEW Run-Time Engine DLL.
All my VIs were masscompiled with LabVIEW 7.1.1
How do I manage this problem, in other words how do I get my VIs in TestStand to run with the LV Run Time Engine?
Thanks for you help,
- Caribe -
PS: I configured the adapter to use the LabVIEW Run Time Engine 7.1.1. When I check back in the dialog "LabVIEW Adapter Configuration" the selector went back to LV Runtime 7.1??? Thats weird dude!

Hi Caribe,
Did you find any solution to this weird behaviour? Even I am facing the same problem! If we set the adapter as LV 7.1.1 runtime engine, it changes back to LV 7.1 runtime engine.
I am also facing -18002 error after mass compiling LV 7.1 folder and my source code folder.
If you can share your solution, that would be of great help to me. If i couldnt find any solution, I have planned to revert back to LV 7.1 version.
Thank you,
Sasi

LabVIEW load error code 3 when opening VI with LabVIEW 2010

I got this error when I try to open a VI saved in 8.6.1 with LabVIEW 2009 and 2010.
The VI open correctly with 8.6.1.
It's appening with only one VI. All other VIs are OK.
Anyone experience this problem?
What can I do to get over this bug?
Dany
Dany Allard

Same issue here too. Could anyone help me to open it?
Attachments:
Peak Detector.vi ‏34 KB

Error when trying to set up OPC I/O server with LabView 2009

Hi.I get an error when I try to set up OPC I/O server with LabView 2009 and the DSC module. If I open an empty project, right click ”My Computer”. Select new / I/O Server… and then OPC Client, the following error appears: Unable to browse OPC Server from the selected machine.Error -2147467262 occurred at GetOPCServerList.viPossible reason(s):LabVIEW: (Hex 0x80004002) No such interface supported. I have tried to repair LabView, but with no luck. Any idea what it could be?

The problems are not related to each otherOk then. Lets try getting this solved. Lemme dig......

CreateTsMedia failed with error 0x80070002

Trying to create a task sequence media "capture media" and its failing. I have trying a ton of things. The key errors are below including the entire log. How do I fix this? Frustrating!
server 2008 r2
sccm 2012 R2 CU1
I have removed the boot package and recreated it. ADK 8.1 is install on local computer. MDK 2013 is also install on local computer.
![LOG[Resources file not found in toolkit.
The system cannot find the file specified. (Error: 80070002; Source: Windows)]LOG]!><time="20:29:28.656+240" date="09-09-2014" component="CreateTsMedia" context="" type="3" thread="21452"
file="mediatoolkit.cpp:173">
<![LOG[Failed to create media generator (0x80070002)]LOG]!><time="20:29:28.656+240" date="09-09-2014" component="CreateTsMedia" context="" type="3" thread="21452" file="createtsmedia.cpp:342">
<![LOG[CreateTsMedia failed with error 0x80070002, details='']LOG]!><time="20:29:28.656+240" date="09-09-2014" component="CreateTsMedia" context="" type="1" thread="21452" file="createtsmedia.cpp:355">
<![LOG[ ===============================================================]LOG]!><time="20:28:38.564+240" date="09-09-2014" component="CreateTsMedia" context="" type="1" thread="5872"
file="createmedia.cpp:979">
<![LOG[Begin media creation: ]LOG]!><time="20:28:38.565+240" date="09-09-2014" component="CreateTsMedia" context="" type="1" thread="5872" file="createmedia.cpp:980">
<![LOG[Media: capture]LOG]!><time="20:28:38.567+240" date="09-09-2014" component="CreateTsMedia" context="" type="1" thread="5872" file="createmedia.cpp:267">
<![LOG['Provider'=nasd-sql1.nasd.local]LOG]!><time="20:28:38.567+240" date="09-09-2014" component="CreateTsMedia" context="" type="1" thread="5872" file="createmedia.cpp:208">
<![LOG['Site Code'=NAZ]LOG]!><time="20:28:38.567+240" date="09-09-2014" component="CreateTsMedia" context="" type="1" thread="5872" file="createmedia.cpp:208">
<![LOG['Distribution Points(s)'=NASD-SCCM-DP.NASD.LOCAL]LOG]!><time="20:28:38.567+240" date="09-09-2014" component="CreateTsMedia" context="" type="1" thread="5872" file="createmedia.cpp:208">
<![LOG['Boot Image Package ID'=NAZ00097]LOG]!><time="20:28:38.568+240" date="09-09-2014" component="CreateTsMedia" context="" type="1" thread="5872" file="createmedia.cpp:208">
<![LOG['Physical Media Type'=UFD+FORMAT]LOG]!><time="20:28:38.568+240" date="09-09-2014" component="CreateTsMedia" context="" type="1" thread="5872" file="createmedia.cpp:208">
<![LOG['Media Destination'=F:\]LOG]!><time="20:28:38.568+240" date="09-09-2014" component="CreateTsMedia" context="" type="1" thread="5872" file="createmedia.cpp:208">
<![LOG[Media label: 'Configuration Manager 2012']LOG]!><time="20:28:38.568+240" date="09-09-2014" component="CreateTsMedia" context="" type="1" thread="5872" file="createmedia.cpp:1025">
<![LOG[Creating media from Admin Console]LOG]!><time="20:28:38.568+240" date="09-09-2014" component="CreateTsMedia" context="" type="1" thread="5872" file="createmedia.cpp:1029">
<![LOG[COMMAND LINE: ]LOG]!><time="20:28:38.568+240" date="09-09-2014" component="CreateTsMedia" context="" type="1" thread="5872" file="createmedia.cpp:929">
<![LOG[CreateMedia.exe /K:capture /N:**** /P:nasd-sql1.nasd.local /S:NAZ /C:**** /D:NASD-SCCM-DP.NASD.LOCAL /L:Configuration Manager 2012 /B:NAZ00097 /T:UFD+FORMAT /F:F:\ ]LOG]!><time="20:28:38.568+240" date="09-09-2014"
component="CreateTsMedia" context="" type="1" thread="5872" file="createmedia.cpp:930">
<![LOG[Another thread has been started to create TS media]LOG]!><time="20:28:38.568+240" date="09-09-2014" component="CreateTsMedia" context="" type="1" thread="21452" file="createmedia.cpp:589">
<![LOG[======= CreateCaptureMedia invoked =======]LOG]!><time="20:28:38.569+240" date="09-09-2014" component="CreateTsMedia" context="" type="1" thread="21452" file="createtsmedia.cpp:1207">
<![LOG[---------------------------- CreateTsMedia ----------------------------]LOG]!><time="20:28:38.569+240" date="09-09-2014" component="CreateTsMedia" context="" type="1" thread="21452"
file="createtsmedia.cpp:245">
<![LOG[Requested output path: F:\ (UFD+FORMAT)]LOG]!><time="20:28:38.569+240" date="09-09-2014" component="CreateTsMedia" context="" type="1" thread="21452" file="createtsmedia.cpp:267">
<![LOG[Total number of TS variables: 0]LOG]!><time="20:28:38.569+240" date="09-09-2014" component="CreateTsMedia" context="" type="1" thread="21452" file="createtsmedia.cpp:106">
<![LOG[Temporary directory 'C:\Users\MFAHEY~1.NAS\AppData\Local\Temp\_tsmedia_21452' created, free space on drive 'C:' is 3925 MB]LOG]!><time="20:28:38.570+240" date="09-09-2014" component="CreateTsMedia" context=""
type="1" thread="21452" file="tempdirectory.cpp:87">
<![LOG[Opened WMI namespace '\\nasd-sql1.nasd.local\root\SMS\site_NAZ' ]LOG]!><time="20:28:38.641+240" date="09-09-2014" component="CreateTsMedia" context="" type="1" thread="21452" file="mediafactory.cpp:924">
<![LOG[Local computer is MTIT7230]LOG]!><time="20:28:38.664+240" date="09-09-2014" component="CreateTsMedia" context="" type="1" thread="21452" file="utils.cpp:384">
<![LOG[Package manager created successfully]LOG]!><time="20:28:38.665+240" date="09-09-2014" component="CreateTsMedia" context="" type="1" thread="21452" file="mediafactory.cpp:408">
<![LOG[Local computer is MTIT7230]LOG]!><time="20:28:38.666+240" date="09-09-2014" component="CreateTsMedia" context="" type="1" thread="21452" file="utils.cpp:384">
<![LOG[Creating policy manager]LOG]!><time="20:28:38.666+240" date="09-09-2014" component="CreateTsMedia" context="" type="1" thread="21452" file="mediafactory.cpp:444">
<![LOG[Setting up Install Toolkit]LOG]!><time="20:28:38.666+240" date="09-09-2014" component="CreateTsMedia" context="" type="1" thread="21452" file="mediatoolkit.cpp:214">
<![LOG[Copying package NAZ00097 to C:\Users\MFAHEY~1.NAS\AppData\Local\Temp\_tsmedia_21452\Cache]LOG]!><time="20:28:38.787+240" date="09-09-2014" component="CreateTsMedia" context="" type="1" thread="21452"
file="packagemgr.cpp:334">
<![LOG[Retrieving info for package NAZ00097.6]LOG]!><time="20:28:38.788+240" date="09-09-2014" component="CreateTsMedia" context="" type="1" thread="21452" file="packagemgr.cpp:1042">
<![LOG[Content library is on remote system 'NASD-SCCM-DP.NASD.LOCAL']LOG]!><time="20:28:39.576+240" date="09-09-2014" component="CreateTsMedia" context="" type="1" thread="21452" file="utils.cpp:617">
<![LOG[Connected to remote registry service on 'NASD-SCCM-DP.NASD.LOCAL']LOG]!><time="20:28:39.660+240" date="09-09-2014" component="CreateTsMedia" context="" type="1" thread="21452" file="utils.cpp:691">
<![LOG[Content Library: Local Path='E:\SCCMContentLib', Remote Path='\\NASD-SCCM-DP.NASD.LOCAL\SCCMContentLib$', File Library Usable Drives='E:\,C:\']LOG]!><time="20:28:39.690+240" date="09-09-2014" component="CreateTsMedia"
context="" type="1" thread="21452" file="utils.cpp:830">
<![LOG[Registering package NAZ00097.6 with content at \\NASD-SCCM-DP.NASD.LOCAL\SCCMContentLib$]LOG]!><time="20:28:40.018+240" date="09-09-2014" component="CreateTsMedia" context="" type="1" thread="21452"
file="packagemgr.cpp:591">
<![LOG[VerifyContentHash: Hash algorithm is 32780]LOG]!><time="20:29:23.140+240" date="09-09-2014" component="CreateTsMedia" context="" type="1" thread="21452" file="downloadcontent.cpp:1829">
<![LOG[Hash value of package NAZ00097 is verified]LOG]!><time="20:29:28.373+240" date="09-09-2014" component="CreateTsMedia" context="" type="1" thread="21452" file="packagemgr.cpp:494">
<![LOG[ADK installation root registry value not found.]LOG]!><time="20:29:28.375+240" date="09-09-2014" component="CreateTsMedia" context="" type="1" thread="21452" file="wimfile.cpp:197">
<![LOG[Loaded C:\Windows\system32\wimgapi.dll]LOG]!><time="20:29:28.375+240" date="09-09-2014" component="CreateTsMedia" context="" type="1" thread="21452" file="wimfile.cpp:334">
<![LOG[Opening image file C:\Users\MFAHEY~1.NAS\AppData\Local\Temp\_tsmedia_21452\Cache\NAZ00097\boot.NAZ00097.wim]LOG]!><time="20:29:28.375+240" date="09-09-2014" component="CreateTsMedia" context="" type="1"
thread="21452" file="wimfile.cpp:412">
<![LOG[Applying image 1 to volume C:\Users\MFAHEY~1.NAS\AppData\Local\Temp\_tsmedia_21452\Toolkit]LOG]!><time="20:29:28.585+240" date="09-09-2014" component="CreateTsMedia" context="" type="1" thread="21452"
file="wimfile.cpp:603">
<![LOG[Closing image file C:\Users\MFAHEY~1.NAS\AppData\Local\Temp\_tsmedia_21452\Cache\NAZ00097\boot.NAZ00097.wim]LOG]!><time="20:29:28.651+240" date="09-09-2014" component="CreateTsMedia" context="" type="1"
thread="21452" file="wimfile.cpp:448">
<![LOG[Resources file not found in toolkit.
The system cannot find the file specified. (Error: 80070002; Source: Windows)]LOG]!><time="20:29:28.656+240" date="09-09-2014" component="CreateTsMedia" context="" type="3" thread="21452"
file="mediatoolkit.cpp:173">
<![LOG[Failed to create media generator (0x80070002)]LOG]!><time="20:29:28.656+240" date="09-09-2014" component="CreateTsMedia" context="" type="3" thread="21452" file="createtsmedia.cpp:342">
<![LOG[CreateTsMedia failed with error 0x80070002, details='']LOG]!><time="20:29:28.656+240" date="09-09-2014" component="CreateTsMedia" context="" type="1" thread="21452" file="createtsmedia.cpp:355">
<![LOG[Media creation process that was started from Admin Console completed.
]LOG]!><time="20:29:28.737+240" date="09-09-2014" component="CreateTsMedia" context="" type="1" thread="5872" file="createmedia.cpp:1065">
<![LOG[CreateMedia.exe finished with error code 80070002]LOG]!><time="20:29:28.737+240" date="09-09-2014" component="CreateTsMedia" context="" type="2" thread="5872" file="createmedia.cpp:1123">

I did intergrate MDT 2013 with configmgr on the server and on my workstation
I did a full install of ADK 8.1 and also tried ADK 8.0.
ADK 8.1 is installed on the Site server.
SAme problem.
<![LOG[======= CreateCaptureMedia invoked =======]LOG]!><time="11:32:51.280+240" date="09-13-2014" component="CreateTsMedia" context="" type="1" thread="1324" file="createtsmedia.cpp:1207">
<![LOG[---------------------------- CreateTsMedia ----------------------------]LOG]!><time="11:32:51.281+240" date="09-13-2014" component="CreateTsMedia" context="" type="1" thread="1324"
file="createtsmedia.cpp:245">
<![LOG[Requested output path: J:\ (UFD+FORMAT)]LOG]!><time="11:32:51.281+240" date="09-13-2014" component="CreateTsMedia" context="" type="1" thread="1324" file="createtsmedia.cpp:267">
<![LOG[Total number of TS variables: 0]LOG]!><time="11:32:51.281+240" date="09-13-2014" component="CreateTsMedia" context="" type="1" thread="1324" file="createtsmedia.cpp:106">
<![LOG[Temporary directory 'C:\Users\MFAHEY~1.NAS\AppData\Local\Temp\_tsmedia_1324' created, free space on drive 'C:' is 3796 MB]LOG]!><time="11:32:51.282+240" date="09-13-2014" component="CreateTsMedia" context=""
type="1" thread="1324" file="tempdirectory.cpp:87">
<![LOG[Opened WMI namespace '\\nasd-sql1.nasd.local\root\SMS\site_NAZ' ]LOG]!><time="11:32:51.357+240" date="09-13-2014" component="CreateTsMedia" context="" type="1" thread="1324" file="mediafactory.cpp:924">
<![LOG[Local computer is MTIT7230]LOG]!><time="11:32:51.381+240" date="09-13-2014" component="CreateTsMedia" context="" type="1" thread="1324" file="utils.cpp:384">
<![LOG[Package manager created successfully]LOG]!><time="11:32:51.381+240" date="09-13-2014" component="CreateTsMedia" context="" type="1" thread="1324" file="mediafactory.cpp:408">
<![LOG[Local computer is MTIT7230]LOG]!><time="11:32:51.383+240" date="09-13-2014" component="CreateTsMedia" context="" type="1" thread="1324" file="utils.cpp:384">
<![LOG[Creating policy manager]LOG]!><time="11:32:51.383+240" date="09-13-2014" component="CreateTsMedia" context="" type="1" thread="1324" file="mediafactory.cpp:444">
<![LOG[Setting up Install Toolkit]LOG]!><time="11:32:51.383+240" date="09-13-2014" component="CreateTsMedia" context="" type="1" thread="1324" file="mediatoolkit.cpp:214">
<![LOG[Copying package NAZ0009B to C:\Users\MFAHEY~1.NAS\AppData\Local\Temp\_tsmedia_1324\Cache]LOG]!><time="11:32:51.500+240" date="09-13-2014" component="CreateTsMedia" context="" type="1" thread="1324"
file="packagemgr.cpp:334">
<![LOG[Retrieving info for package NAZ0009B.3]LOG]!><time="11:32:51.500+240" date="09-13-2014" component="CreateTsMedia" context="" type="1" thread="1324" file="packagemgr.cpp:1042">
<![LOG[Content library is on remote system 'NASD-SCCM-DP.NASD.LOCAL']LOG]!><time="11:32:52.221+240" date="09-13-2014" component="CreateTsMedia" context="" type="1" thread="1324" file="utils.cpp:617">
<![LOG[Connected to remote registry service on 'NASD-SCCM-DP.NASD.LOCAL']LOG]!><time="11:32:52.287+240" date="09-13-2014" component="CreateTsMedia" context="" type="1" thread="1324" file="utils.cpp:691">
<![LOG[Content Library: Local Path='E:\SCCMContentLib', Remote Path='\\NASD-SCCM-DP.NASD.LOCAL\SCCMContentLib$', File Library Usable Drives='E:\,C:\']LOG]!><time="11:32:52.316+240" date="09-13-2014" component="CreateTsMedia"
context="" type="1" thread="1324" file="utils.cpp:830">
<![LOG[Registering package NAZ0009B.3 with content at \\NASD-SCCM-DP.NASD.LOCAL\SCCMContentLib$]LOG]!><time="11:32:52.669+240" date="09-13-2014" component="CreateTsMedia" context="" type="1" thread="1324"
file="packagemgr.cpp:591">
<![LOG[VerifyContentHash: Hash algorithm is 32780]LOG]!><time="11:34:25.934+240" date="09-13-2014" component="CreateTsMedia" context="" type="1" thread="1324" file="downloadcontent.cpp:1870">
<![LOG[Hash value of package NAZ0009B is verified]LOG]!><time="11:34:32.496+240" date="09-13-2014" component="CreateTsMedia" context="" type="1" thread="1324" file="packagemgr.cpp:494">
<![LOG[ADK installation root registry value not found.]LOG]!><time="11:34:32.497+240" date="09-13-2014" component="CreateTsMedia" context="" type="1" thread="1324" file="wimfile.cpp:207">
<![LOG[Loaded C:\Windows\system32\wimgapi.dll]LOG]!><time="11:34:32.497+240" date="09-13-2014" component="CreateTsMedia" context="" type="1" thread="1324" file="wimfile.cpp:344">
<![LOG[Opening image file C:\Users\MFAHEY~1.NAS\AppData\Local\Temp\_tsmedia_1324\Cache\NAZ0009B\boot.NAZ0009B.wim]LOG]!><time="11:34:32.498+240" date="09-13-2014" component="CreateTsMedia" context="" type="1"
thread="1324" file="wimfile.cpp:422">
<![LOG[Applying image 1 to volume C:\Users\MFAHEY~1.NAS\AppData\Local\Temp\_tsmedia_1324\Toolkit]LOG]!><time="11:34:32.713+240" date="09-13-2014" component="CreateTsMedia" context="" type="1" thread="1324"
file="wimfile.cpp:613">
<![LOG[Closing image file C:\Users\MFAHEY~1.NAS\AppData\Local\Temp\_tsmedia_1324\Cache\NAZ0009B\boot.NAZ0009B.wim]LOG]!><time="11:34:32.770+240" date="09-13-2014" component="CreateTsMedia" context="" type="1"
thread="1324" file="wimfile.cpp:458">
<![LOG[Resources file not found in toolkit.
The system cannot find the file specified. (Error: 80070002; Source: Windows)]LOG]!><time="11:34:32.775+240" date="09-13-2014" component="CreateTsMedia" context="" type="3" thread="1324"
file="mediatoolkit.cpp:173">
<![LOG[Failed to create media generator (0x80070002)]LOG]!><time="11:34:32.775+240" date="09-13-2014" component="CreateTsMedia" context="" type="3" thread="1324" file="createtsmedia.cpp:342">
<![LOG[CreateTsMedia failed with error 0x80070002, details='']LOG]!><time="11:34:32.775+240" date="09-13-2014" component="CreateTsMedia" context="" type="1" thread="1324" file="createtsmedia.cpp:355">
<![LOG[Media creation process that was started from Admin Console completed.
]LOG]!><time="11:34:32.868+240" date="09-13-2014" component="CreateTsMedia" context="" type="1" thread="8832" file="createmedia.cpp:1065">
<![LOG[CreateMedia.exe finished with error code 80070002]LOG]!><time="11:34:32.868+240" date="09-13-2014" component="CreateTsMedia" context="" type="2" thread="8832" file="createmedia.cpp:1123">

Why does labview 2009 32-bit closes up with no error message?

Hello.
I am developing an application using a PCI-6534 board, Windows XP SP3, and LabVIEW 2009 32-bits. In this application I am generating a 300 Hz signal using the P2.0 digital line. I am trying to make digital acquisition using the P0 port (8 bits), using N-sampling. The program that generates the 300 Hz clock, works with no problem. However, when I start running the program that performs the data acquisition, LabVIEW suddenly closes up with no error message. The LabVIEW windows just disappear from the screen.
As for me it looks like a LabVIEW bug.
In case anyone decided to help me, I could attach the programs so that you could check them.
What can I do to solve this problem?
Thank you.

I had the same problem with one of our applications. I supplied gigabytes of process monitor and desktop execution toolkit logs, but nothing was resolved. I upgraded from WS2003 and LV2009sp1 to W7 64b and LV2010, per NI's recommendation but the problem persists. I had the corresponding service ticket open for 3 months where NI said the application ran fine for them on W7 with 2010. (long story)
I understand your frustration, and I recommend getting your local application engineer involved as an advocate with application support.. If you pay for service, pound on them to provide it. My $0.02.

ActiveX with LabView error 0x80070002

Similar Messages

Maybe you are looking for