Excecutable VI generating an error 222 on Keithley 2612A although its run properly when starting from labview 2009 directly

Dear all,
I have a VI which runs perfectly and I can control, a Keithley 2612A for transistor measurements.
The VI run well when I excecute it from the computer which has the platform Labview 2009 (XP OS)
The equipment (ie Keithley 2612A) is linked to another computer which don't have labview 2009.
I installed Run-time-engine 2009 (OS XP 32 bits) on this computer.
Then I create an excecutable of my VI with the "build application" option.
The excecutable VI starts normally on the computer but when I want to run it, I am getting an error message from the Keithley 2612A (which was not the case when I ran the VI directly from the computer haing Labview 2009 installed on it). The error message is 222 (ie parameter too long)
I thought that I did something wrong and I create an excecutable from an original VI from Keithley (ie without any change). I am getting the same error message.
When I create an excecutable with run time engine 2009 included (as it is possible to do it wiht LB 2009) , I am geeting the same error message.
So I need no to check step after step when the message happens but
Does anyone knows anything about such an issue ?
Thank you
Solved!
Go to Solution.

Dear all,
Just for those who might encounter a similar issue.
I found the solution after tackling all possibilities.
The source of the problem was (for unknown reason) that the country setting of the computer was wrong
and decimal numbers were written with a , instead of a point.
Since I reset correctly the country setting, the stand alone files are running normally.
Best regards
Youki

Similar Messages

Error -17600 when switching from LabVIEW Development System to LabVIEW Run-Time Engine in Adapter Configuration

I receive an error message (code -17600) while loading my test sequence after switching from LabVIEW Development System (2009 f3) to LabVIEW Run-TIme Engine using the Adapter Configuration.
ErrorCode: -17600,
Failed to load a required step's associated module.
LabVIEW Run-Time Engine version 9.0.1f3.
When I switch back to the LV development system, everything is OK, and the sequence loads and runs perfectly.
My TestStand Engine Version is 2012 f1 (5.0.0.262).
I'd appreciate any help on this issue.
Roman

Hi Roman,
There are a couple of things you can try:
1) Determine if the LabVIEW RunTime Engine is corrupted in some way. Create a new simple VI with no sub-VIs, using the same LabVIEW Development system you used for mass-compiling the VIs. Create a TestStand step that calls this VI and ensure it runs correctly. Now switch your LabVIEW adapter to use the RuntimeEngine and choose the "Auto detect using VI version" option.
Check if the simple VI is loadable and runs without errors in TestStand.
If the step generates the same error, you should try a re-install of the LabVIEW development system.
If not, its most likely that there is some VI you are using that is not loadable in the LabVIEW Runtime Engine because:
1) Some sub-VI is still not saved in the right version or bitness. Open the VI heirarchy of the top-level VI that you are calling from TestStand and examine the paths of all the sub-VIs to check if they were in the folder you masscompiled and re-save any that are outside this directory.
Also, when you try to close the top level VI, do you get a prompt to save any unsaved files? If so, they could be the sub-VIs that are not saved in the right version. Save all of them.
Check if you are loading any VIs programatically and if these are compiled and saved in the right version as well.
2) There is some feature you are using in your LabVIEW code that is not supported in the LabVIEW RunTime Engine. To check this, add your top-level VI to a LabVIEW project and create a new build specification and create a new executable from this VI.
    Right-click "Build Specifications" and choose "New->Application(EXE)".
    In the Application Properties window, select Source Files and choose the top level VI as the start-up VI.
    Save the properties.
    Right-click on the newly created build specification and choose Build.
Run this executable (it will be run using the LabVIEW RunTime) and check if the VI has a broken arrow indicating that it cannot be loaded and run in the LabVIEW Runtime Engine.
You might need to examine your code and find the feature which is not supported in the LabVIEW RunTime and find an alternative.
Another thing i forgot to mention the last time around is if you are using 64-bit LabVIEW with 32-bit TestStand, then executing code using LabVIEW RTE from TestStand will not work since the 64-bit LabVIEW RTE dll cannot be loaded by the 32-bit TestStand process.
If none of the above steps resolve the issue, consider sharing your LabVIEW code so i can take a look.
Regards,
TRJ

My songs dont download properly when it comes up it shaded in grey and it says error anyone pls help, My songs dont download properly when it comes up it shaded in grey and it says error anyone pls help

My songs dont download properly when it comes up it shaded in grey and it says error anyone pls help, My songs dont download properly when it comes up it shaded in grey and it says error anyone pls help
Im on ipod 6.1.3 non jaillbroken
and i have not bought songs from itunes store

What is the wording of the error message?
When you say download do yo mean:
- directly downloading from iTunes?
- Syncing to computer?

Microsoft Outlook 2010 Error "Another version of Outlook is currently running." when clicking on a mailto link

Our company recently upgraded from Outlook 2007 to Outlook 2010. The mailto links on an intranet work fine on local computers running Outlook 2010 but on the terminal servers, users are getting the following error:
"Another version of Outlook is currently running. Close it and try again."
I have made sure that Outlook is the default mail client.
Home & Business Click2Run has never been installed on the terminal server.
The error happens in standard as well as safe mode.

Hi,
What program is set as default for mailto?
Have you installed Home & Business Click 2 Run before? There is a limitation in click 2 run version that the mailto is trying to use your older version of Outlook.
If this is not the situation, try to test this issue in the safe mode.
Click
Start, point to All Programs, and then point to
Microsoft Office.
Press and hold the
CTRL key, and then click Microsoft Outlook.
If the problem does not occur in the safe mode, this issue might be related to some third-party add-ins in the Office program, we can try to disable them.
Please also set Outlook as the default email client on the computer.
======================
For Windows Vista/Windows 7:
1.
Click Start.
2.
Type "default programs" in the Start Search box.
3.
Click Default Programs under Programs in the search results.
4.
Now click Set your default programs.
5.
Highlight Microsoft Office Outlook or Microsoft Outlook on the left.
6.
Click Set this program as default.
7.
Click OK.
Best Regards,
Sally Tang

Error message "bad check sum" on Satellite pro 6100 when starting up

I recently tried to turn my laptop on when i got the message "bad check sum"(i think it said that) "check system press[f1] to continue. After i pressed f1 it came up an options screen i didnt do anything to it and just continued then it loaded and shut down again. also i have to lie the laptop on its back just for the first green LED to come on and when i have the battery in the charger does not charge the battery and even when it does start to charge and i try to put it on the same sequence of orange LED's appear .
so what does the message bad check sum mean ?
thanks

Hi,
That means that the cmos (bios) battery is low on power and you should hang your machine for minimum a day on AC because the bios battery loads then.
Such error appears when your cmos batt. is not full then the bios losts his settings and the checksum which would be performed by the system at startup will be faulty since the bios needs a check to know if everything is OK.
Its a security feature which indicates if your hardware is ok or not. If the error appears more than once, then you should bring your machine to a technician or at least a local servicepartner for a checkup.
Greets

I get the error code -2146827284 when trying to run an Ecxel macro from LabVIEW.

I am trying to insert data in an Excel workbook and then run a macro which I recorded in Excel to produce a plot.
This worked great on a laptop running W2K + LV7 and Office 2000.
I am now trying to do the same thing on a WinXP + LV7 + Excel 2002 and I get this error.
The complete message is:
"Error -2146827284 occurred at Exception occured in Microsoft Excel, Programmatic access to Visual Basic Project is not trusted
. Help Path is C:\Program Files\Microsoft Office\Office10\1033\xlmain10.chm and context 0 in Excel Import Module.vi->LV report test1.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 to the error code input."
Can anyone shed some light on this. Running a macro is the obvious and easy way to get this work done.
See the attached VI. It includes the macro and some sample data to run it on.
Attachments:
LV_report_test1.vi ‏46 KB

Hi,
I have attached a link to a document that discusses the error you are getting:
Error -2146827284 When Importing a Macro to Office 2002/XP
I hope this helps.
Sincerely,
Feroz
National Instruments

Has anyone encountered a Microsoft Visual C++ Runtime error in Windows 2000 when upgrading from Labview 6.0i to 6.0.2?

When I try to upgrade Labview 6.0i to 6.0.2 by running the setup.exe file I downloaded from the NI site, I immediately get a dialog box with the header "Microsoft Visual C++ Runtime Library" and it says "Runtime Error! Program: C:\setup.exe abnormal program termination."
I'm running Windows 2000, but I've successfully installed it on another computer with the same setup. I'm guess some of the DLL files in system32 has been corrupted or mismatched versions. But I don't know which one...
Anyone know what this means?

Hello,
You can probably solve this problem by going to Start >> Run and typing the following:
Regsvr32 \msi.dll
Where is the folder where the msi.dll file resides on your computer (you can use Start >> Find to find the exact location). Once you do this, the installation of the 6.0.2 update should work properly.
Please let me know if you continue to have any problems. Thanks for your patience on this issue, and have a pleasant day.
Sincerely,
Darren Nattinger
Applications Engineer
National Instruments
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Firefox 4 screwed up, I returned to earlir version & error message re Chrom comes up 8 times now when starting Firefox. how can I fix?

Firefox 4 lost my bookmarks sidebar, started my home page with Yahoo finance in a strange place on Yahoo and generally gave me fits. I ran the install on an earlier version of Firefox which works great after I click on an error message eight times to get Firefox to start. The error box said Chrome Registration Failed the text in the box said "Firefox could not install this item because of Chrome Registration. Please contact the author about this problem." I felt comfortable with version 3.8??? and Firefox 4 isn't comfortable for me and now the earlier version is messed up. How do I get back into my comfort zone. My computer experience started with Heath Disk Operating System, CPM, Windows 1 through 7. I don't like Firefox 4 or Chrome internet browsers. Windows IE caused problems early on with virus and male ware.

Is it still showing up in your ad-on manager?

Error when Starting from PFILE

Hi!
I am in the process of setting up a standby database. The primary is also in the same host as the Standby.
When I create a pfile from the spfile of the primary and try to start the Standby database from the pfile, after changing the appropriate parameters, I get this error
SQL> conn sys/oracle as sysdba;
Connected to an idle instance.
SQL> startup nomount pfile = 'C:\oracle9i\oradata\STBY\initstby2.ora'
ORA-01031: insufficient privileges
But clearly I have connected as sys user... Please help me..
Thanks
Radhika

Radhika,
While creating the pfile for Standby d/b sis u issue the following command on the primary d/b :
- ALTER DATABASE CREATE STANDBY CONTROLFILE AS
'<path of the stdby control file>';
Can I also suggest you to refer to the Data Guard Concepts & Administration Guide. This guide gives a step by step procedure of what exactly a Data Guard configuration is all about and an example to set up a Data Guard Enviornment.
Also I belive since you are a SQL Server Administrator , its also import you go tthrough the Oracle 9i d/b Concepts guide. You do not want to be creating a MAA configuration directly without knowing Oracle internals.
If you have taken the time out to read both the Concepts Guide & the Data Guard guide & you are still facing problems get back on this thread.
Cheers...rCube

Xperia Z3 Compact camera error when starting from locked screen (symbol lock)

Hi
I'm a new owner of Xperia Z3 Compact and I have noticed a problem when launching camera. The app itself works perfectly well but when trying to launch camera from locked phone (screen locked with symbol) it shows only black screen with error message that camera app it unaccessible. After removing lock screen protection both camera symbol on lock screen and dedicated camera button works as intended. Is it supposed to be that way? On my previous phone I could launch camera app without unlocking screen but couldn't access any other parts of the phone. I'd love to have it working the same way here especially with the dedicated camera button.
Hoping for a fast answer.
Regards
Huma

You may need to perform a software repair using PC Companion.The process will erase all internal memory.You might need to charge your device for about 1-2 hours before so the device has at least 60% battery.
Make sure the device is not connected to computer or laptop and turned off (sometimes you have to press power button and volume up until the device vibrates 3 times or on some devices you have to press the small button near the SIM tray or on the back of the device).
Open PC companion->support zone->phone/tablet software update->repair my phone/tablet blue highlighted.Follow the steps given,do not connect your phone until prompted to press volume down while plugging USB cable. If PC companion does not start the repair process, you might need to run it in compatibility mode with Windows 7 (in some cases XP).
All we have to decide is what to do with the time that is given to us - J.R.R. Tolkien

Error "Can't find boot device by boot options" when boot from ISO via AMT

Hello.
When I try to boot from ISO CD via AMT I got an error message:
"Can't find boot device by boot options"
Settings are similar to what I made in HP 8100, 8200 etc - SOL/IDER/KVM, network access enabled
Where could be a problem?
Prod. name: HP Compaq Elite 8300 Microtower PC
Prod. number: B0F41EA

Just wanted to follow up with this as I got a response from HP. It looks like it is at least the 2.9 BIOS version that has this issue. I know that at least the 2.51 BIOS version is unaffected.

UDP Error when upgrading from Labview 8.6 to Labview 2009

I recently updgraded from Labview 8.6 to Labview 2009. I am writing an application to stream data to disk from UDP. My VIs run just fine in Labview 8.6, but when I try to run them in Labview 2009 my UDP read times out despite being able to monitor UDP traffic and see that the data is being sent and nothing in the file is changed from 8.6 to 2009. Is there a known issue related to this?

How are you moniting the UDP traffic? Have you verified that the port you are trying to use is actually available? When you installed 2009 there may have been an additional service installed that may have used the port you're trying to use. If you're running on Windows you can use the command "netstat -n -o -a" to see all the ports that are currently in use, as well as the process ID that has that port open.

Snort 2.9.5 may generate an error if local rules are enabled

After installing SEU 913, which includes Snort 2.9.5, the following symptoms may appear in a Sourcefire deployment:
The sensor may go down
Unable to commit any changes to an IPS policy
Health Alerts state that the IPS/IDS DE exited unexpectedly

Solution
In order to resolve this issue install SEU 915 or higher.
Root Cause
An issue has been identified with custom rules or Emerging Threat rules that can violate the Snort rule syntax. These rules can cause the Detection Engine to repeatedly restart. Sourcefire provided rules do not contain these syntax errors and will not cause this problem.
Snort does rule validation upon start up. With Snort 2.9.4, when a rule is determined invalid, then a warning is written to syslog. However, Snort will continue to load omitting that rule. The Snort delivered in SEU 913 generates an error for invalid rules instead of a warning, which prevents Snort from loading. With the release of SEU 915, we simply made Snort 2.9.5 behave the same way Snort 2.9.4 does, which is to display a warning for invalid rules, but continue to load.
Invalid third party rule syntax is still an issue as SEU 915 will not correct them. To make sure rules are valid you can simply open an IPS policy in the editor and save it, or manually apply the policy. You will be notified if there are any invalid rules active in that policy.

Getting Error 08 when attempting to build exe using LabVIEW 2009 (32 bit) and Windows 7

Testing development platform on Window 7 vs XP. I received following message while building an executable using 2009 32 bit on Windows 7 machine. Same build will work on an XP machine.
Error 8 occurred at Copy in AB_Engine_Copy_Error_Files.vi->AB_Application.lvclass:Copy_Error_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_EXE.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_Application.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: File permission error. You do not have the correct permissions for the file.
=========================
NI-488: DMA hardware error detected.
C:\Program Files (x86)\National Instruments\Shared\LabVIEW Run-Time\2009\errors\Internet Toolkit-errors.txt
Any suggestions?
Thanks

For any who may be having this problem here is a little more information and what I did to get around the issue. (so far)
First I tried a simple vi with a while loop in a project and made an executable build. This worked. I double checked on an XP machine the project that I was having problems with. The executable was built successfully. I changed back to the Windows 7 machine. On the program compatibility trouble shooter I started the LabVIEW 2009 (32 bit) in the XP service pack 2 mode and selected run as administrator. The build was successful.
Note: was logged in as administrator and program would build a simple executable in Windows 7. The executable that would not build had more complex code that included serial communication and calls to lvanlys.dll and nilvaiu.dll.
This may not be a complete fix to the problem but at least in this one case it worked.

"Open Vi Reference" generates a Error 7

Hello,
I am getting "Error 7" from the "Open VI Reference" vi, the name of the vi is wired vi path input. The "Error 7" means that the vi cannot be found. So I went to "Tools ===> Options ===> Paths" and modified the Path so that Labview can find it. But for reasons I do not understand the vi I want to get a reference for cannot be found. So it leads me to beleive that the "Open vi Reference" does not use the path option to find a vi. Any ideas what is going on?
Regards,
Kaspar
Solved!
Go to Solution.

Hello,
Thanks for getting back to me. I have attached a file fo the screenshot of the Block diagram. The "Open Vi Reference" is in the upper left hand corner, which generates a error when I have updated the path options to point to where the file exists.
Regards,
Kaspar
Attachments:
vi_error.GIF ‏21 KB

Excecutabl​e VI generating an error 222 on Keithley 2612A although its run properly when starting from labview 2009 directly

Similar Messages

Maybe you are looking for

Excecutable VI generating an error 222 on Keithley 2612A although its run properly when starting from labview 2009 directly