LabVIEW:EXE generates the error 1003 calling plugin with the type definition

Similar Questions

• Msinfo32.exe generates an Error Message "cannot collect information.

  Hello

  I am running XP Prof with SP3 and made a scan with the perfect system optimizer and it did remove a lot of files he said were copies and since then, Information System says that it can collect Information, cannot access windows management instrumentation software. Windows Management files may have been moved or missing. I tried to use the administrative tools in the Management Console Microsoft and add snap - in following the instructions from microsoft on their site, but still did not help. Also tried to restore as soon as possible and the recovery of deleted files from the optimizer software. Nothing has helped so far. I am also on a network with my laptop which runs on Windows 7, but the have not enabled since I stupidly paid 39.99 for this software now appeasrs to have screwed up my computer. Restoration did do 1 restore and I tried 5 times and it said could not files to an earlier time which is an another prolbem I've had for a while with system restore doesn't work does not correctly. If anyone can help me I would really appericiate it. Thank you my friends.

  PKBISHOP

  Hi PKBISHOP,
   
  The error message occurs if the Windows Management Instrumentation (WMI) service is not started. This can happen if the service is disabled, if a dependent service is not started, or if a problem is preventing start the WMI service. The system information utility will be able to collect information that the WMI service is started.
   
  To correct this information to resolve this problem, see the link below.
   
  Msinfo32.exe generates an Error Message "cannot collect information.

• Error: Copy of master for the Type definition is not found

  See screenshot below please. The typedef is there (I accessed it via windows Explorer and it is not grayed out in the code), and my FPGA VI is not broken, which uses the same exact control. I also have these constants by right clicking and choose create constant, so it's not as if I'm loading the wrong enum. Anyone seen this before?

  

  Because I'm a bad scientist, I don't know exactly what fixed my problem because I changed multiple variables at the same time.

  Here's what I did:

  Deleted the auto of the project folder (doubt this was important, still broken after that)

  Changed my open FPGA VI reference by a bitfile to the use of a VI, selected my FPGA VI, no. MORE CASE RUN ARROW! YAY.

  This finding was brought to go watch my FPGA bitfiles on drive - I've had two of them (weird). Usually a compilation replaces just the old file.

  Just in case where the names give a preview, they are:

  More: NASATTRControlCo_FPGATarget_FPGAMain_25B3817B.lvbitx

  Latest: NASATTRControlCo_FPGATarget_FPGAMain_25AF817B.lvbitx

  I went back to my reference FPGA VI open and selected the most recent bitfile I have compile this morning - no more broken arrow run.

  I have a feeling that this may be due to choose an old bitfile, but usually if the bitfile does not include the control, it will not be displayed in the node control read/write. If someone of OR wish to comment on this I would appreciate the insight on what can happen.

  I wonder if it's because I installed 2010 SP 1? Who knows, but it's fixed now.

• Error using BULK collect with RECORD TYPE

  Hello
  
  I wrote a simple procedure to declare a record type & then by a variable of type NESTED table.
  
  I then selects the data using COLLECT in BULK & trying to access it via a LOOP... We get an ERROR.
  
  ------------------------------------------------------------------------------------------------------------------------------------------------------
  
  CREATE OR REPLACE PROCEDURE sp_test_bulkcollect
  IS
  
  TYPE rec_type () IS RENDERING
  emp_id VARCHAR2 (20).
  level_id NUMBER
  );
  
  TYPE v_rec_type IS TABLE OF THE rec_type;
  
  BEGIN
  
  SELECT employe_id, level_id
  LOOSE COLLECTION v_rec_type
  OF portfolio_exec_level_mapping
  WHERE portfolio_execp_id = 2851852;
  
  FOR indx IN v_rec_type. FIRST... v_rec_type. LAST
  LOOP
  
  dbms_output.put_line ('Emp-' | v_rec_type.emp_id (indx) |) » '|| v_rec_type.level_id (indx));
  
  END LOOP;
  
  END;
  -----------------------------------------------------------------------------------------------------------------------------------
  
  Here is the ERROR I get...
  
  
  -Errors of compilation for the PROCEDURE DOMRATBDTESTUSER. SP_TEST_BULKCOLLECT
  
  Error: PLS-00321: expression "V_REC_TYPE" is not appropriate for the left side of an assignment statement
  Online: 15
  Text: IN portfolio_exec_level_mapping
  
  Error: PL/SQL: ORA-00904: invalid identifier
  Online: 16
  Text: WHERE portfolio_execp_id = 2851852;
  
  Error: PL/SQL: statement ignored
  Line: 14
  Text: COLLECT LOOSE v_rec_type
  
  Error: PLS-00302: component 'FIRST' must be declared
  Online: 19
  Text: LOOP
  
  Error: PL/SQL: statement ignored
  Online: 19
  Text: LOOP
  ------------------------------------------------------------------------------------------------
  
  Help PLZ.

  and with a complete code example:

  SQL> CREATE OR REPLACE PROCEDURE sp_test_bulkcollect
    2  IS
    3  TYPE rec_type IS RECORD (
    4  emp_id VARCHAR2(20),
    5  level_id NUMBER
    6  );
    7  TYPE v_rec_type IS TABLE OF rec_type;
    8  v v_rec_type;
    9  BEGIN
   10     SELECT empno, sal
   11     BULK COLLECT INTO v
   12     FROM emp
   13     WHERE empno = 7876;
   14     FOR indx IN v.FIRST..v.LAST
   15     LOOP
   16        dbms_output.put_line('Emp -- '||v(indx).emp_id||' '||v(indx).level_id);
   17     END LOOP;
   18  END;
   19  /
  
  Procedure created.
  
  SQL>
  SQL> show error
  No errors.
  SQL>
  SQL> begin
    2     sp_test_bulkcollect;
    3  end;
    4  /
  Emp -- 7876 1100
  
  PL/SQL procedure successfully completed.
  

• Write on the Labview EXE Console Ran STANDARD output

  Anyone know if it is possible to write on the STANDARD of a Labview EXE output when run from a Windows console? I don't want to say calling an external my Labview code EXE using the Exec.vi system and get the standard output of the external exe returned to Labview but rather run my EXE Labview as an application of console se and have the Labview application a pass/fail result final to stdout to the output console.

  I found this post which allows to accept command line arguments, but I have not found a clear method to write to the standard output.

  http://digital.NI.com/public.nsf/allkb/17C3AD70493CE0208625666A00763364

  I found this thread on the LAVAG.org site but unfortunately I forgot my password for my account and my account was under an old email address that I no longer have access to in order to reset it. I tried to create a new account, but it is not allowing me to register a new account. There seems to be a solution to this on the 2nd page of the thread, but due the fact that I can not log on the site, I can't download the solution try.

  https://lavag.org/topic/11719-running-a-LabVIEW-exe-from-the-console/?page=2

  aaronb

  As it turns out, my last blog was about this specific topic. I fell on it as a result of some dll which was not "plays well with other children."

  http://www.notatamelion.com/2016/05/05/aint-Misbehavin-thanks-to-external-calls/

  Mike...

• Subvis call go dynamically within an exe file (avoiding the error 1003)

  Hello

  I use an architecture where the main program (compiled into an exe) can be supplied with a user-'plugins', which are collections of screw types inside a folder named especially compared to the exe. They can be called in the exe via 'open reference vi' provided by the corresponding strict vi types and corresponding relative paths.

  I want to avoid having to include one of the plugins in some way in the application builder, because users must be able to create own plugins that the request is totally ignore during the generation.

  In principle, this approach works rather well, since these plugins are not extremely complex, but sometimes, I get an error 1003 when loading a plugin.

  I have read many old posts on this error in this particular situation, mainly using versions of LV 7 or 8 (I use 2012). It was suggested to build a source distribution for each plugin, including everything that is used from vi.lib, instr.lib and user.lib. Indeed, it helped in my particular case - however, it bloats the plugin 'distribution' (which consists originally only a couple of the screws of the user) extremely and complicates the development user side.

  Now some good plugins run from in the exe without having to build a distribution source for them (they still use many vi.lib live) while others don't, and I have no idea why...

  These plugins are wrappers for hardware drivers that allow to control any hardware instrument within the main application via a certain API. So, in a particular case, a plugin that produces the error 1003 uses VISA series features (everything inside... \vi.lib\Instr\_visa.llb) and one without error doesn't (yet he uses several features of... \vi.lib\Utility\...).

  I can solve VISA problems in a simple way by including (only) the VISA-vis opportunity (and typedefs) inside the plugin folder and explicitly link to them (i.e. replace the VISA-vis of vi.lib with those copied to the folder of the plugin - I guess that's also what the source distribution).

  However, I'm confused why certain plugins with work of related vi.lib while others screws produce an error 1003 unless these special screws are explicitly distributed and connected with them...

  Oh and just for completeness: all plugins are working fine if the callee in the development system, the problem occurs only if called from an exe file.

  Novgorod wrote:

  However, I'm confused why certain plugins with work of related vi.lib while others screws produce an error 1003 unless these special screws are explicitly distributed and connected with them...

  Oh and just for completeness: all plugins are working fine if the callee in the development system, the problem occurs only if called from an exe file.

  Do plug-ins that work depend on the screw in vi.lib who are already part of your executable file because the main program uses these same screws?

  All the screws that your plugin needs must be available, if applicable can mean to be already loaded into memory (for the main of the application or another plugin), or can be found on the disk and load.  An executable includes all the screws of vi.lib - it includes only those he uses (and the screws that are marked always 'include' in the build specification).  I suspect that the plugins that work only dependent vi.lib screws which are also used by the main executable file.

• Has anyone got the error after error Adobe statement: Mismatched start and called rollbackUserAction? (Action Import::import to generate the bitmap of the page to communicate WITH US)

  Help!  Full statement of the error:

  Adobe Muse CC has encountered an error and will now close.  Please report the last actions bit that you have taken to this error to the Adobe Muse CC team.

  Not match start and called rollbackUserAction? (Action Import::import to generate the bitmap of the page to communicate WITH US)

  Please send us the .muse file and the file MuseLog.txt to your Documents folder to [email protected]. Include a link to this thread for the context. If the file is larger than 20 MB, you can use a service like Adobe SendNow, Dropbox, WeTransfer, etc. (if you use a service, please include your email address in the body of the message back, given that not all services to include it in the invite sharing they send.) Thank you.

• Application Builder «Browse to LabVIEW.exe» error

  LabVIEW gurus...

  I'm currently building a standalone version of my project.  When I run the application (which is built successfully), LabVIEW makes me search the LabVIEW.exe file.  However, I want this application to run on a computer that will not have installed LabVIEW, and looking up if this file is not an option.

  I know that the reason for this problem is that I use 2 named StrLen and MoveBlock within the library LabVIEW.exe call library functions (to access data from a pointer to a pointer).

  LabVIEW.exe presents itself as one of the dependencies in my project, but I can't understand how to add it to my specifications of generation.  I tried to build a Setup program and include the LabVIEW runtime environment, but this does not work either.

  Any suggestions would be greatly appreciated!

  I'm using LabVIEW 8.6.

  Thank you

  Jason

  In the call to the dll just type LabVIEW without any path. This should work (I used it on 7.1) to automagicallylink it.

  The functions are also in the lvrt.dll which is the main part of the runtime engine.

  Felix

• Cancellation of registration user stored in the shift register event generates the error 1 if Subvi runs intermittently

  Hello

  I'm trying to understand the behavior of the attached excerpt from a larger overall vi functional.

  In a State, I'm generating a user event and in a State later unsubscribe from the event and destroy it.

  Now, if I went through the VI together in one step (i.e., step through events? set to FALSE), the VI runs without generating an error. However, if I run the VI by intermittent and output after each execution of the loop, the vi generates error 1. Why is it so? Please notify. Thank you.

  Peter

  Why are you registration and deregistration of events user, but you have no event structure in your VI who use them?

  When you run events, probaby the event you registered disappears when your VI stops running.  If you were able to keep your VI in the foreground running, then the life of the event would persist.

  The event number still exists in the uninitialized shift register, but it does not say more once your high level VI stops and you get the error 1.

  If it was really a global functional VI, you would terminals connected to the connector table in your VI, you would call this as a Subvi as part of a main VI and life event would persist and you wouldn't mistake 1.

• Loading of a DLL on RT: Missing Export "DecodePointer" "Kernel32.dll" and 7 error when calling the DLL

  Hi, I recently changed to Visual Studio 2010 and Windows 7 64-bit.

  I have an existing Office RT system running RT 2009.  This system calls a DLL that I already built using Visual Studio .net 2003 and Windows XP.

  Since I've recompiled the DLL I get an error 7 file not found error when I call the RT DLL, even if I simply replaced the old DLL with a new one in the file system so the path has not changed.

  I also noticed that the message on the screen connected to the RT system during startup:

  "achieveworldpeace.dll" load error: lack of export 'DecodePointer' of ' Kernel32.dll'.

  Any ideas on this problem?  It is perhaps as simple as a switch in the compiler?

  Thank you.

  I'm not sure it's a simple switch in the project settings in Visual C. The problem is clearly in the standard C runtime library that gets linked to your DLL and refers to exports of Windows which are not available on the RT system. Don't forget that the RT system is a limited Win32 API emulation.

  I usually avoid these problems using Visual C 6 to create DLLs for LabVIEW projects. The standard library of the C runtimes will not know what Windows API reference more recent exports because they have supported even under Win95. So unless your explicitedly reference code not supported RT APIs you wouldn't have problems. If you do not use the standard C file i/o functions and management of memory in your DLL functions, you can also try to link statically C runtime libraries in your DLL, or vice versa depending on what you have now. It may or may not work. Otherwise there is not much else but by using an earlier version of Visual Studio.

• Lack of SubVis error 1003 when VI called Via a server VI

  I have a Labview application that 12E DAQmx functionality to acquire data and uses analysis contained in records vi.lib Labview vi.  The application is compiled in a Bachelor's degree in law with a high-level vi model. I used successfully the VI server technique to launch and control the high level vi using Labview 7 and 7.1.  This technique allows me to open, run, and the façade of access control during execution.  In fact, we have compiled the functionality of separate (implemented in vi) VI in a DLL server and applications such as VB6 to launch the VI, control and he abandoned. This technique worked very well for many years for us.

  Now, we have improved our Labview 2009 application and implemented NI Scope to acquire data from a digitizer PXI-5922.  We use the same functions of analysis like the previous version.  I can run this as a standalone VI, and I can also write another 'Launcher' VI which uses the VI of my VI server solution to launch the application (open, execute, and control).  The problem comes when I try to run the application outside of the Labview development environment. With the help of VB6, I can open the VI, but when I use the VI server to run it I get the error code 1003 (VI not executable). The vi appears with a broken arrow.  By clicking on the broken arrow gives me an error "Missing Subvi.

  To eliminate the 'my' application of the problem, I copied one of the models OR simulated (GenerateDisplay.vit), moved to a test directory and renamed.  I can start and run this vi of the environment of Labview development, as well as using my server VI 'Launcher' mentioned above when running in the Labview development system.  However, I get the error of missing VI again when my new test VI is launched using another application.  I have compiled my application launcher in an executable file (using project folder) and can run the executable file.  However, when my application launcher tries to run my test vi I get the same error of VI missing.  The missing vi is \vi.lib\express\express input\SimulateSignalBlock.llb\subSigGeneratorBlock.vi.

  Thus, it seems that the VI server runs the OK application executing in the Labview development system.  However, when it is launched, apart from that the vi launched test cannot locate its dependencies, which leads me to think there must be a connection problem during execution when executing.  I see all the dependencies in the project file, and these are listed in their correct location.

  Has anyone had a similar experience, or had no idea what goes wrong.  As noted above, this technique worked ok in Labview 7.x using DAQmx so I'm wondering if something changed in the way the runtime throws the dependencies?

  Kind regards

  David

  HI Vivek,

  Thanks for your suggestions.  Solution 2 of the first link (creating a source distrubution) allowed me to create a LLB containing all the dependent inside vi.  I am now able to open and run my test vi without errors by using Server VI of VB6 functions.  I have rebuilt my main application, but have a huge file (> 40 MB) when you include all the dependencies, the vi.lib, the instr.lib and user.lib files.  The application can run ok, but I am now working to optimize its size.  His looks as if I have a good working solution.

  Thanks for your help,

  David

• Measurement and Automation does not open and generates the MAXKnownException error with an unknown exception.

  Measurement & Automation does not open and generates the MAXKnownException error with an unknown exception.

  Heres the log

  Context where the exception was taken:
  (No context - the unhandled exception)

  Size version of Base module
  -------------------- -------- -------- ------------------
  NIMax.exe 00400000 0006 has 000 4.6.0.49152
  ntdll.dll 770E0000 00180000 6.1.7601.18247
  00110000-76060000 6.1.7601.18409 Kernel32.dll
  KERNELBASE.dll 74E00000 00047000 6.1.7601.18409
  SYSFER. 74830000 00072000 12.1.1101.401 DLL
  1BFB0000 0001 NiMaxImp.dll B 000 4.6.0.49152
  Shell32.dll 74E50000 00C4A000 6.1.7601.18429
  Msvcrt.dll 76830000 000AC000 7.0.7601.17744
  74 00000 00057000 6.1.7601.17514 SHLWAPI.dll
  76740000 00090000 6.1.7601.18275 Gdi32.dll
  00100000 76480000 6.1.7601.17514 User32.dll
  Advapi32.dll 75DD0000 000 A 0000 6.1.7601.18247
  sechost.dll 76CC0000 00019000 6.1.7600.16385
  000F0000 rpcrt4.dll 76980000 6.1.7601.18205
  SspiCli.dll 74AE0000 00060000 6.1.7601.18443
  CRYPTBASE.dll 74AD0000 0000 C 000 6.1.7600.16385
  LPK.dll 76470000 0000 has 000 6.1.7601.18177
  USP10.dll 768E0000 0009D 000 1.626.7601.18454
  Ole32.dll 75F00000 0015C 000 6.1.7601.17514
  Msvcp90.dll 739F0000 0008E000 9.0.30729.6161
  Msvcr90.dll 73DB0000 000 has 3000 9.0.30729.6161
  74470000 00009000 6.1.7600.16385 VERSION.dll
  IMM32. 00060000 60000 74 6.1.7601.17514 DLL
  000CC000 76BB0000 MSCTF.dll 6.1.7600.16385
  74320000 00021000 6.1.7600.16385 Ntmarta.dll
  Wldap32.dll 00045000 763E0000 6.1.7601.17514
  Uxtheme.dll 6EB20000 00080000 6.1.7600.16385
  NiMaxUI.dll 1C2D0000 00269000 4.6.0.49153
  Msvfw32.dll 6BE30000 00021000 6.1.7601.17514
  73970000 00032000 6.1.7601.17514 WINMM.dll
  Comctl32.dll 73E80000 0019E000 6.10.7601.17514
  Wsock32.dll 73DA0000 00007000 6.1.7600.16385
  74DC0000 00035000 WS2_32.dll 6.1.7601.17514
  NSI.dll 75AA0000 00006000 6.1.7600.16385
  Oleaut32.dll 76580000 0008F000 6.1.7601.17676
  6D8E0000 003 Mfc90u.dll has 1000 9.0.30729.6161
  MSIMG32.dll 6EBA0000 00005000 6.1.7600.16385
  dwmapi.dll 6EB00000 00013000 6.1.7600.16385
  MFC90ENU. DLL 6EAF0000 0000 D 000 9.0.30729.6161
  NiMaxRes.dll 1BFD0000 0007 has 000 4.6.0.49153
  BtMmHook.dll 10000000 00038000 6.4.0.2900
  PSAPI. DLL 76440000 00005000 6.1.7600.16385
  DCIMAN32. DLL 6E1F0000 00006000 6.1.7601.18177
  MXS.dll 1 B 240000 4.6.0.49152 0000F000
  mxsutils.dll 1B4D0000 00041000 4.6.0.49152
  Msvcp71.dll 7C3C0000 0007C 000 7.10.6030.0
  7 360000 00056000 7.10.6030.0 Msvcr71.dll
  mxsout.dll 1 B 400000 00075000 4.6.0.49152
  64600000 00014000 4.257.3.0 nirpc.dll
  Mswsock.dll 73A 90000 0003C 000 6.1.7601.18254
  profapi.dll 76460000 0000B 000 6.1.7600.16385
  mxMax.dll 1BF20000 00086000 4.6.0.49152
  58000000 00240000 6.5.0.3005 AsstntUI.mxx
  MFC80U. DLL 71210000 8.0.50727.6195 0010F000
  MSVCR80.dll 0009B 000 8.0.50727.6195 72E50000
  Comdlg32.dll 20000 75 0007B 000 6.1.7601.17514
  71180000 00087000 8.0.50727.6195 Msvcp80.dll
  ATL80. DLL 6BD70000 0001 B 000 8.0.50727.6195
  MFC80ENU. DLL 730F0000 8.0.50727.6195 0000E000
  59000000 00582000 6.5.0.3005 mxwTask.dll
  00011000 74180000 6.1.7601.17887 Netapi32.dll
  74170000 00009000 6.1.7601.17514 netutils.dll
  74150000 00019000 6.1.7601.17514 srvcli.dll
  wkscli.dll 74140000 6.1.7601.17514 0000F000
  56000000 00148000 6.5.0.3005 mxwRCEng.dll
  mxcal.mXX 1 A 110000 00056000 4.6.0.49152
  mxcat.mXX 1BE20000 000AB000 4.6.0.49152
  nidmfuiu.mXX 04360000 0010D 000 1.11.0.49152
  NIPALU.dll 64000000 00057000 2.1025.3.0
  64500000 00006000 2.1025.3.0 nipalut.dll
  NIPAL32.dll 00007000 1F700000 2.1025.3.0
  SETUPAPI.dll 76240000 0019D 000 6.1.7601.17514
  CFGMGR32.dll 75DA0000 00027000 6.1.7601.17621
  76220000 00012000 6.1.7601.17621 DEVOBJ.dll
  6 280000 00031000 1.9.0.49152 nimdbgu.dll
  6 000000 00017000 1.9.3.49152 niorbu.dll
  nimstsu.dll 6E180000 0001 has 000 1.11.0.49152
  nimhwcfu.dll 6DFD0000 000 B 6000 1.11.0.49152
  6 050000 0001E000 1.9.0.49152 nidimu.dll
  nimxdfu.dll 0003E000 1.10.0.49152 6D0F0000
  nimxpu.dll 6E1B0000 0000 000 1.11.0.49152 B
  Iphlpapi.dll 74280000 0001C 000 6.1.7601.17514
  WINNSI. DLL 74270000 00007000 6.1.7600.16385
  74B 40000 001BD000 11.0.9600.17126 WININET.dll
  76A 70000 API-MS-Win-Downlevel-User32-L1-1-0.dll 00004000 6.2.9200.16492
  770B 0000 API-MS-Win-Downlevel-shlwapi-L1-1-0.dll 00004000 6.2.9200.16492
  75AB0000 API-MS-Win-Downlevel-Version-L1-1-0.dll 00004000 6.2.9200.16492
  76430000 00003000 6.2.9200.16492 API-MS-Win-Downlevel-normaliz-L1-1-0.dll
  normaliz. DLL 76450000 00003000 6.1.7600.16385
  iertutil.dll 75AC0000 00219000 11.0.9600.17126
  76610000 00005000 6.2.9200.16492 API-MS-Win-Downlevel-advapi32-L1-1-0.dll
  76200000 00017000 6.1.7601.17514 USERENV.dll
  nidmxfu.dll 04470000 0049F000 1.12.0.49152
  nimru2u.dll 6EC70000 00044000 2.10.1.49152
  nimmgluu.dll 69830000 0001E000 1.11.0.49152
  nimercu.dll 6DFB0000 00019000 1.11.0.49152
  MFC71. 00106000 140000 7 7.10.6101.0 DLL
  MFC71ENU. 360000 5 0000E000 7.10.3077.0 DLL
  niGPIBui.mxx B 6, 000000 0008E000 2.7.0.49152
  niIVIui.mxx 02CE0000 000D 0000 4.2.0.49152
  niPXIui.mxx A 671 0000 000BC000 2.1280.1.49152
  niRemPXI.mxx 1 A 270000 00057000 4.6.0.49152
  mxRmCfg.dll 1 has 000000 00090000 4.6.0.49152
  niRMui.mxx 1AD70000 000FD000 4.6.0.49152
  NISRLUI.mxx 6B 500000 00061000 3.4.0.49154
  63800000 00010000 2.7.0.49152 NiSpyLog.dll
  niSWui.mxx 1A3B0000 00072000 4.6.0.49152
  niVISAui.mxx 63360000 0017D 000 4.1280.0.49152
  62 30000 0002E000 4.1280.0.49152 niVISAres2.dll
  RICHED32. DLL 40000 00006000 6.1.7601.17514 6FC
  Riched20.dll 61F70000 00076000 5.31.23.1230
  Wshtcpip.dll 73A 80000 00005000 6.1.7600.16385
  nisysapi.dll 68 has 00000-000B 2000 5.5.2.49152
  Dbghelp.dll 70F20000 000EB000 6.1.7601.17514
  -------------------- -------- -------- ------------------

  Application: C:\Program Files (x 86) \National Instruments\MAX\NIMax.exe
  User name: administrator
  OS version: 6.1.7601 (Service Pack 1)
  Exception code: C06D007E
  Exception addr: 74E0C42D

  Sender's address: 74E0C42D
  Function name: RaiseException
  Module name: KERNELBASE
  Parameters: 00000000 00000001 0518FD84 C06D007E
  Source file: (not available)

  Sender's address: 68A3C6F7
  Function name: DllUnregisterServer
  Module name: nisysapi
  Parameters: 00000000 0518FD50 005F59B8 0000001E
  Source file: (not available)

  Sender's address: 68A53D87
  Function name: DllUnregisterServer
  Module name: nisysapi
  Parameters: 00000350 68A791B8 005F59B8 00000000
  Source file: (not available)

  Sender's address: 68A0DC65
  Function name: nisysInitDiagnosticsByValue
  Module name: nisysapi
  Parameters: 68A 01680 00000001 68A93BB8 FFFFFF01
  Source file: (not available)

  Sender's address: 68A0DFC4
  Function name: nisysInitDiagnosticsByValue
  Module name: nisysapi
  Parameters: 005E2C40 00000000 00000001 00000001
  Source file: (not available)

  Sender's address: 68A 01698
  Function name: nisysInitDiagnosticsByValue
  Module name: nisysapi
  Parameters: 005E2C40 00000000 00000001 00000001
  Source file: (not available)

  Sender's address: 1BE27A73
  Function name: mxGetProvider
  Module name: mxcat
  Parameters: 020469F0 02047084 0518FED0 1BE76CBA
  Source file: (not available)

  Sender's address: 1BE30D2E
  Function name: mxGetProvider
  Module name: mxcat
  Parameters: 02029FA8 02047748 0518FF34 1BE21D4C
  Source file: (not available)

  Sender's address: 1BE35780
  Function name: mxGetProvider
  Module name: mxcat
  Parameters: 00000000 00000000 02047818 020469F0
  Source file: (not available)

  Sender's address: 1BE21D4C
  Function name: (not available)
  Module name: mxcat
  Parameters: 02029FA8 1BE6264D 0518FF7C 73DD3433
  Source file: (not available)

  Sender's address: 1BE21CDC
  Function name: (not available)
  Module name: mxcat
  Parameters: 02030018 00000000 00000000 9192C45C
  Source file: (not available)

  Sender's address: 73DD3433
  Function name: endthreadex
  Module name: MSVCR90
  Parameters: 00000000 0518FF94 7607338A 02047818
  Source file: (not available)

  Sender's address: 73DD34C7
  Function name: endthreadex
  Module name: MSVCR90
  Parameters: 02047818 0518FFD4 77119F72 02047818
  Source file: (not available)

  Sender's address: 7607338A
  Function name: BaseThreadInitThunk
  Name of the module: kernel32
  Parameters: 02047818 00000000 00000000 775D5D69
  Source file: (not available)

  Sender's address: 77119F72
  Function name: RtlInitializeExceptionChain
  Name of the module: ntdll
  Parameters: 02047818 00000000 00000000 73DD345E
  Source file: (not available)

  Sender's address: 77119F45
  Function name: RtlInitializeExceptionChain
  Name of the module: ntdll
  Parameters: 02047818 00000000 00000000 73DD345E
  Source file: (not available)

  If I could come with the OS discs for the thing, I think I'd do a new install of Windows 7.

  Mike...

• error code 1 occurs with the construction of the .exe (problem VI) attached

  The problem that I have been with a particular project was published several times by others.  I read through many threads related to this (or rather related to it).  I tried some things but not all.  I finally started turning off sections of my code to see if the error disappeared.  I have followed the attached VI.  The error code is also attached.  Can someone analyze this VI and see what might be the problem?  It uses .NET objects, so I don't know exactly what the compiler is looking for.  I would point out that this isn't my VI, but the one I copied from the forum here.  As far as the e-mail, the VI works very well in development mode, but obviously I desire a standalone application.

  Also note that I have created a new project and dropped this VI on the first level VI and he built a .exe very well, which makes no sense to me. Maybe someone can shed some light on this issue.  When I tried to return to the initial project, it doesn't have the build.  If you have disabled all instances of this VI in my project (using a diagram to disable), generates the project without an error.  Thanks in advance for your help.

  Reese

  Well, I found a solution, but I still don't know why the original VI would not build in my application.  I just created a new VI copied each code section of the original, little by little, build and then copy some more until all has been copied to.  It built without error every time.  It's a head scratcher, but the only thing I can think is, given the original VI was not my code, there may be a current compatibility issue.  But even once, he worked in a new project, so I'm not sure.  The lesson that I learned from this (and I know better), is not to wait until the end of your project in order to perform a build.  Lesson learned!

• Impossible to uninstall a program error: unable to generate the uninstaller for ca aintivirus E9030 command line.

  Original title: impossible to uninstall the program error msg

  I'm unable to uninstall a program, an error message keeps popping up saying "error E9030 cannot generate the uninstaller for ca aintivirus command line.
  can anyone help?

  Original title: impossible to uninstall the program error msg

  I'm unable to uninstall a program, an error message keeps popping up saying "error E9030 cannot generate the uninstaller for ca aintivirus command line.
  can anyone help?

  Try this... no guarantee

  Start > computer > open C: drive > open the Progran files > y at - it a record of the Ca antivirus?
  If so, open it > is there a uninstaller.exe file here?
  If so, open it and let go about uninstalling.

  Or,

  Start > all programs > CA antivirus > y at - it an option to uninstall?

  Hope one of these AIDS.

• : Error 35 call external function of the object

  I get "error 35: error when calling external object function driverinit on line 302 of the event open"and impossible to open a program. " A few solutions that I found for this search refer to an update to the SQL Server.  The only thing I tried to do lately is to update a printer driver, all was working fine before this.  I got an SQL error on a website trying to access the FAQ section.  I found an article to download an update to the original version of SQL Server 2005 SP2 but not sure if that's what I really do.  Can anyone help?

  CRTet,

  Error 35 is not a common Windows error. It is very likely that the registry scanner above will only cause more problems.
  The error you get is from your application. Given that this is not generated by Windows, I highly recommend directly contacting the support of bookkeeper.

  Cody C
  Microsoft Answers Support Engineer
  Visit our Microsoft answers feedback Forum and let us know what you think.