Please reinstall it or repair it."I already reinstalled the TestStand but still it doesn't work.Hope to hear from you.Thank you very much and Mabuhay!Ryan A. Windows NT/2000 Login to Windows using a UserID that has administrator privileges. Normally when you deploy to a target machine, TestStand will automatically pick the latest installed version of the LabVIEW Run-Time Engine if it cannot find the LabVIEW Development System when you Is there a way to remedy this and still keep 8.0 installed? 0 Kudos Message 3 of 10 (1,634 Views) Reply 0 Kudos Re: Error Code: -18002 RayFarmer Trusted Enthusiast 11-07-2005 Check This Out
But if all the examples are going to cause me this much grief, I'll need to go a different route. Thismay be due to the fact that the run-time server cannot dynamically search for VIs like the LabVIEW development environment can. My Profile | RSS | Privacy | Legal | Contact NI © 2014 National Instruments Corporation. RayFarmer Trusted Enthusiast 05-05-2005 12:50 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report to a Moderator Hi Ryan,Do you get the http://digital.ni.com/public.nsf/allkb/D82FEAF0B4BA293A862575710053E252
Select Start»Run and enter dcomcnfg.exe. United States MY ACCOUNT   INNOVATIONS SHOP SUPPORT COMMUNITY Home Community Home : Most Active Software Boards : NI TestStand : What is the solution for "Error Code: -18002"? You must give permissions to the appropriate users so that they can access the remote server. To resolve this, change the LabVIEW Adapter configuration on the development computer by using steps 1-3.
Poor|Excellent Yes No Document Quality? From “Accessible Server Resources”,“VI properties and methods” and “Application methods and properties” are checked off. “Machine access list” contains your PC. “Exported VIs list” includes ‘*’ marks. Click any VIs which you added to the original project (under Project Files in the center) and check the box to Rename this file in the build and add "UI_" to This is common when you deploy a TestStand system to a target computer where the LabVIEW Run-Time Engine is going to be used instead of the LabVIEW Development System.
Ray Farmer 2005-09-14 18:14:22 UTC PermalinkRaw Message Hi, You also have to make sure the teststand folders containing VI's are also mass compiled with 7.1.1 RegardsRay Farmer Caribe 2005-09-15 10:14:57 UTC PermalinkRaw Message Rye Member 05-04-2005 06:30 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report to a Moderator Hello dear Experts,I am using LABView This is has been fixed in the source code and all you need to do is re-build the user interface executable.On a machine that has the LabVIEW Professional Development System, open check over here My next task involves using TestStand with LabVIEW, CVI, and Agilent VEE modules.
All test VIs and their entire hierarchy must be saved using the exact same version of LabVIEW that was used to build the run-time server. LabVIEW does not allow callers to directly invoke ancestor versions of the object's method. After fixing these, your problem should have solved easily. — Ruby Islam Login or Signup Now to post comments Related Posts LabView: Error -50103; operation could not be completed as specifiedIssues Bilaos, ECEManila 0 Kudos Message 3 of 10 (1,543 Views) Reply 0 Kudos Re: What is the solution for "Error Code: -18002"?
I think your VIs must be version 5.x Regards Ray Farmer RegardsRay Farmer 1 Kudo Message 9 of 10 (1,569 Views) Reply 1 Kudo Re: Error Code: -18002 AllenP Active Participant This displays the Component Services dialog window. Poor|Excellent Yes No Document Quality? For checking VI Server settings, Start LabVIEW.
Also be careful if you have multiple versions of the same VIs on your system. his comment is here Please tell us why. I installed the evaluation copy of LabVIEW 8 on my PC. Select Start»Run and enter dcomcnfg.exe.
If you only have a simple Operator Interface you may not have access to this menu. You must give permission to the appropriate users so that they can access the LabVIEW server. To do this: Run dcomcnfg from the command line, which displays the Distributed COM Configuration Properties application window. http://cygnussoft.com/labview-error/labview-error-code-9.html RayFarmer Trusted Enthusiast 05-09-2005 02:40 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report to a Moderator Hi Ryan,If you just have
Allen P. Now I have changed it to LV7.1 development system. RayFarmer Trusted Enthusiast 05-04-2005 07:13 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report to a Moderator Hi,The problem is your vi
Only users who have launch permission will be able to access the server. The run-time server may by using a copy of the VIs that were saved in a different version of LabVIEW. Select the Security tab. Is there a simple way to convert the VIs that came with the course manual from (I think) version 6.x to 8.0?
If it is LabVIEW Run-Time Engine 8.0, I would expect this problem. Poor|Excellent Yes No Document Quality? To resolve the issue, select Class Member Call from the Call Type listbox. http://cygnussoft.com/labview-error/labview-error-code.html See ‘LabVIEW:’ message for more details.
If i couldnt find any solution, I have planned to revert back to LV 7.1 version. Thank you,Sasi AllenP 2005-11-21 16:11:18 UTC PermalinkRaw Message Sasi,The LV 7.1.1 RTE replaces the LV 7.1 Here are the things that are needed to be ensured: ActiveX isn’t checked off in “Protection” section. This displays a list of VIs that are exported by LabVIEW.