Similar Questions

• "Call the executable" allows the environment variable "path"?

  Hello

  It seems that when you use the step type "call the executable" you need to enter the absolute path of the executable, or the absolute working directory, in the definition of "call settings" step.  I seem not to be able to put in a *.exe by himself in the path and have the command is found, even if I can't enter this same command on the command line (windows 7).  Is it possible to configure this step to use the windows ' path' environment variable to search for the executable?

  David J.

  You can do the following:

  (1) specify cmd.exe for the file path.

  (2) specify "/c yourexe.exe" for the argument expression

  This will launch a command window and tell it to run your application with the simple file name.

  The reason why you can't put just yourexe.exe in the path of file is that TestStand made its own resolution of file path that is different from what the window command. It uses its directories to search to resolve relative paths. If you do not have to specify an absolute path for the file path parameter, but it must be compared to a TestStand search directory or the current sequence file.

  Hope this helps,

  -Doug

• How to close a cmd window 'call the executable '.

  Hello

  I have the following sequence in the 2013 Teststand

  1. the installation program

  "Call the executable" call a java program in a cmd window. --> This step works

  2 main

  A call to the java program "n" dll .net times--> this step works

  3 cleaning

  How to close the cmd window opened by "executable call?

  TKS

  

  You can create another not executable call.  The file path is TASKKILL and arguments are "/F /IM cmd.exe/t.  This will close all open windows cmd.

  Pulido Technologies LLC

• Problems running code on another PC, the executable runs on two computers

  We recently uploaded a LV 2010 licence from one workstation to another and tried running a few global code 2010 LV LV and executable made from the code to the "new" code development station

  The executable runs without problem. The code will not initialize one of both devices on a MIL-STD-1553 of the SBS NIC is installed in the workstation.

  Why the executable work so perfectly while code originating the executable has problems? Seems there must be something to do with the new position and/or SBS card.

  Experience with these types of problems during the migration to a new development computer (mine is running Win XP and LV2010) are very much appreciated.

  Thank you

  My guess would be a device driver missing for the card of the SBS.

  Of course, GE did not the memo specifying the product support materials should be easy to access

  

  I guess you have to beg for support from GE.

• If you run the program Setup 'Run as Administrator', executable runs with high fees?

  Hello

  Installer of LV chose "run the executable at the end of installation.
  If you run the installation program "Run as Administrator", the executable runs with high fees?

  Best regards

  My apologies - configure when the installer to "run the executable at end of installation", it will run this executable with the admin rights because the installation program itself requires administrator rights.

  LabVIEW installation program can create registry keys for you.

  For your more advanced customization (e.g. selection modules), you have to look different (e.g. InnoSetup) using a solution of installation or you would need to write an executable in LabVIEW that you run after installation that allows you to select the Setup programs you want and run them using System Exec.

• Dynamically short VI of the executable

  I try to run one of the screws of a source distribution that is outside the main executable file. When my program is not an executable (only source code), everything works fine. But the VI does not run when it is called executable, unless I open the front panel of the VI before running the EIS.

  Is it possible to run the VI without actually opening the front panel? I can probably hide after that opening but it would be better if he never shows up.

  abdel2 wrote:

  [...] -Now manually open dynamic Vi.vi. You will see that it is not executed. [...]

  And this is expected behavior. The reason is simple: you open a new vi, not that what we called the executable.

  LV uses "Instances of the Application" in order to distinguish between the different contexts of execution.

  The executable is running in another instance of the application then the VI in the development environment.

  If you want to transfer data between the development environment and exe, you must follow the instructions of this KB.

  hope this helps,

  Norbert

• Shared variable of subjects with the executable in real-time

  We have a PXi target running Labview time real 8.5 and we use a series of shared variables for communication between the target and the client software. The code was developed (and used) in the last 2 years, and presented no problems with the shared variables when they are deployed since the Project Explorer (for the target and the laptop based client software). However, when you try to run an executable version on the system time PXI real target of exactly the same engine code variable shared seems to fail during the initial loading. Since it is an executable, it is difficult to display errors, but it seems that the accident occurred at the beginning of the program when we try to initialize a number of shared variables. Sometimes it loads but probably only 10% of the time. When you plug the tool to debug for code and restarting the executable, runs without any problem. However, once we managed to capture and error (error-1950678982 the shared variable client side read buffer is full).

  I checked a number of messages in the Knowledge Base (e.g. how to deploy Variables of a compiled executable shared network?), but it still has not solved the problem. Thoughts and suggestions?

  Adrian

  I tested it for a few hours now and I can't make it fail again. The big difference in my implementation was to use your suggestion, and no wire the error cluster through the method since the error it generates caused a number of questions later. So let me summarize the final configuration that seems to work then:

  -during the execution and executable on a target time real 8.5, startup not connected to a client. Library of shared variable hosted on the target and should load by itself.

  -J' added a flat structure sequence on the vi 'main' (top of page vi executable) with a node (as shown above) Invoke method in the first structure with a timer to 10 seconds and the rest of the code in the second part of the structure. The shared variable library has been copied to the target in a data directory and the path provided to the method (the same way as above) and the IP address is that of the target.

  I discovered that it takes about 8-9 seconds for the shared variable engine and library to start (I don't remember is that past exactly that) and it is important to wait this time to initialize shared variables or the behavior is unpredictable. The method always generates the error 1043 (function not supported) but I simply ignore it now, and it seems to work.

  Thanks for your help! I will let you know if there is some instability in the future, but everything looks good from here.

• Error 7 only during the executable to call the library node function

  Hello

  I'm having some trouble with LabVIEW, creating an executable work of my application. The program communicates with a sensor of moving laser Keyence LK-G5000 series with drivers provided by Keyence. When you run the program in the development environment, the program runs without any problem. However, when the construction program and run the program with an executable file, the program generates error 7 as shown below:

  

  After looking through the previous posts on error 7 and executable environment on the forums AND I found that a lot of people mentioned that the development environment and runtime environment use different path structures. I also found a guide of NOR to solve this problem here:

  http://digital.NI.com/public.nsf/allkb/FD7DE8BC8FFC256C862565F4006BE363

  However, after following these instructions, I always get error 7 only when executing the program in an executable environment.

  I've never used any .lvlib library in the past before, so I don't know if this may have been the issue (it was provided by Keyence.) The library includes 2 private screws that can only be called within the library, so I don't think I can go without using the library. There are screws in the library that use the DLL files (which are also included in this same library) through the node library function call in LabVIEW that appear not to be included when I create an executable file. Adding even manually the DLL files to the folder where the executable generates the same error 7.

  Is this what I remember in my code to allow the program to function within the executable?

  Fasteners are drivers for Keyence, my top level VI (GeoREF-Keyence controller.vi) and all my sub live

  Best regards

  Victor

  Executables are taking a different path, as a start to debug the path as an indicator and see which path is being planned in executable mode?

• An error appears after the rule of matadata Execute running

  Hi Expert

  I'm tring to load the data of the EBS GL to HFM (11.1.2.3). After I chreated four matadata rules account, entity, Custom1 and Custom2 in feature sets of metadata, I try to click the Execute button to execute these rules. Error below. Do you have any experience with this?

  2014-04-23 22:07:42, 699 FATAL [AIF]: error of COMM LKM support members in HFM - metadata support to HFM

  Traceback (most recent call changed):

  File '< string >", line 346, in loadMembers

  ODIHAppException: com.hyperion.odi.common.ODIHAppException: [SERVER] properties are required.

  The mistake of studio ODI as below:

  Failed session: 63501: ODI-1217: COMM_LOAD_MEMBERS_TO_HFM Session (63501) fails with return code 7000.
  ODI-1226: COMM members in HFM load step fails after 1 attempt.
  ODI-1240: flow COMM support members in HFM fails during an operation of integration. This flow of charge target table target modeling.
  Caused by: org.apache.bsf.BSFException: exception of Jython:
  Traceback (most recent call changed):
  File "< string >", line 27, < module >
  File '< string >", line 346, in loadMembers
  at com.hyperion.odi.hfm.ODIHFMAppWriter.beginLoad(ODIHFMAppWriter.java:161)
  at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:597)

  com.hyperion.odi.common.ODIHAppException: com.hyperion.odi.common.ODIHAppException: [SERVER] properties are required.

  at org.apache.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:146)
  at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.execInBSFEngine(SnpScriptingInterpretor.java:322)
  at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.exec(SnpScriptingInterpretor.java:170)
  at com.sunopsis.dwg.dbobj.SnpSessTaskSql.scripting(SnpSessTaskSql.java:2473)
  at oracle.odi.runtime.agent.execution.cmd.ScriptingExecutor.execute(ScriptingExecutor.java:48)
  at oracle.odi.runtime.agent.execution.cmd.ScriptingExecutor.execute(ScriptingExecutor.java:1)
  at oracle.odi.runtime.agent.execution.TaskExecutionHandler.handleTask(TaskExecutionHandler.java:50)
  at com.sunopsis.dwg.dbobj.SnpSessTaskSql.processTask(SnpSessTaskSql.java:2913)
  at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2625)
  at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:580)
  at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:468)
  at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:2128)
  at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1931)
  to oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$ 2.doAction(StartScenRequestProcessor.java:580)
  at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:216)
  at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor.doProcessStartScenTask(StartScenRequestProcessor.java:513)
  to oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$ StartScenTask.doExecute (StartScenRequestProcessor.java:1073)
  at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:126)
  to oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$ 1.run(DefaultAgentTaskExecutor.java:50)
  at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:50)
  at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor.executeAgentTask(DefaultAgentTaskExecutor.java:41)
  at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor.doExecuteAgentTask(TaskExecutorAgentRequestProcessor.java:93)
  at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor.process(TaskExecutorAgentRequestProcessor.java:83)
  at oracle.odi.runtime.agent.support.DefaultRuntimeAgent.execute(DefaultRuntimeAgent.java:68)
  at oracle.odi.runtime.agent.servlet.AgentServlet.processRequest(AgentServlet.java:562)
  at oracle.odi.runtime.agent.servlet.AgentServlet.doPost(AgentServlet.java:516)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:821)
  to weblogic.servlet.internal.StubSecurityHelper$ ServletServiceAction.run (StubSecurityHelper.java:227)
  at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
  at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:27)
  at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
  to oracle.security.jps.ee.http.JpsAbsFilter$ 1.run(JpsAbsFilter.java:119)
  at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
  at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
  at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
  at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:163)
  to weblogic.servlet.internal.WebAppServletContext$ ServletInvocationAction.run (WebAppServletContext.java:3696)
  at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
  at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
  at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
  at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
  at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
  Caused by: Traceback (most recent call changed):
  File "< string >", line 27, < module >
  File '< string >", line 346, in loadMembers
  at com.hyperion.odi.hfm.ODIHFMAppWriter.beginLoad(ODIHFMAppWriter.java:161)
  at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:597)

  com.hyperion.odi.common.ODIHAppException: com.hyperion.odi.common.ODIHAppException: [SERVER] properties are required.

  at org.python.core.PyException.fillInStackTrace(PyException.java:70)
  at java.lang.Throwable. < init > (Throwable.java:181)
  at java.lang.Exception. < init > (Exception.java:29)
  to java.lang.RuntimeException. < init > (RuntimeException.java:32)
  to org.python.core.PyException. < init > (PyException.java:46)
  at org.python.core.PyException.doRaise(PyException.java:200)
  at org.python.core.Py.makeException(Py.java:1166)
  at org.python.core.Py.makeException(Py.java:1170)
  at org.python.core.Py.makeException(Py.java:1174)
  at org.python.core.Py.makeException(Py.java:1178)
  to $2 org.python.pycode._pyx403.loadMembers (< string >: 414)
  to org.python.pycode._pyx403.call_function (< string >)
  at org.python.core.PyTableCode.call(PyTableCode.java:165)
  at org.python.core.PyBaseCode.call(PyBaseCode.java:297)
  at org.python.core.PyBaseCode.call(PyBaseCode.java:191)
  at org.python.core.PyFunction.__call__(PyFunction.java:385)
  at org.python.core.PyMethod.__call__(PyMethod.java:215)
  at org.python.core.PyMethod.instancemethod___call__(PyMethod.java:221)
  at org.python.core.PyMethod.__call__(PyMethod.java:206)
  at org.python.core.PyObject.__call__(PyObject.java:367)
  at org.python.core.PyObject.__call__(PyObject.java:371)
  to org.python.pycode._pyx408.f$ 0 (< string >: 27)
  to org.python.pycode._pyx408.call_function (< string >)
  at org.python.core.PyTableCode.call(PyTableCode.java:165)
  at org.python.core.PyCode.call(PyCode.java:18)
  at org.python.core.Py.runCode(Py.java:1204)
  at org.python.core.Py.exec(Py.java:1248)
  at org.python.util.PythonInterpreter.exec(PythonInterpreter.java:172)
  at org.apache.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:144)
  at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.execInBSFEngine(SnpScriptingInterpretor.java:322)
  at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.exec(SnpScriptingInterpretor.java:170)
  at com.sunopsis.dwg.dbobj.SnpSessTaskSql.scripting(SnpSessTaskSql.java:2472)
  at oracle.odi.runtime.agent.execution.cmd.ScriptingExecutor.execute(ScriptingExecutor.java:47)
  at oracle.odi.runtime.agent.execution.cmd.ScriptingExecutor.execute(ScriptingExecutor.java:1)
  at oracle.odi.runtime.agent.execution.TaskExecutionHandler.handleTask(TaskExecutionHandler.java:50)
  at com.sunopsis.dwg.dbobj.SnpSessTaskSql.processTask(SnpSessTaskSql.java:2913)
  at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2625)
  at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:577)
  at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:468)
  at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:2128)
  at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1930)
  to oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$ 2.doAction(StartScenRequestProcessor.java:580)
  at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:216)
  at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor.doProcessStartScenTask(StartScenRequestProcessor.java:513)
  to oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$ StartScenTask.doExecute (StartScenRequestProcessor.java:1073)
  at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:126)
  to oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$ 1.run(DefaultAgentTaskExecutor.java:49)
  at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:49)
  at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor.executeAgentTask(DefaultAgentTaskExecutor.java:41)
  at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor.doExecuteAgentTask(TaskExecutorAgentRequestProcessor.java:92)
  at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor.process(TaskExecutorAgentRequestProcessor.java:83)
  at oracle.odi.runtime.agent.support.DefaultRuntimeAgent.execute(DefaultRuntimeAgent.java:68)
  at oracle.odi.runtime.agent.servlet.AgentServlet.processRequest(AgentServlet.java:562)
  at oracle.odi.runtime.agent.servlet.AgentServlet.doPost(AgentServlet.java:516)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
  to weblogic.servlet.internal.StubSecurityHelper$ ServletServiceAction.run (StubSecurityHelper.java:227)
  at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
  at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
  at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
  at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
  to oracle.security.jps.ee.http.JpsAbsFilter$ 1.run(JpsAbsFilter.java:119)
  at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:324)
  at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:460)
  at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
  at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
  at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
  at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
  at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:163)
  at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
  to weblogic.servlet.internal.WebAppServletContext$ ServletInvocationAction.wrapRun (WebAppServletContext.java:3730)
  to weblogic.servlet.internal.WebAppServletContext$ ServletInvocationAction.run (WebAppServletContext.java:3696)
  at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
  at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
  at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
  ... 4 more

  1. open ODI Studio Console

  2. connect to your repository FDMEE

  3. go to the topology

  4. develop Hyperion Financial Management

  5. double click on HFM_SERVER

  6 enter your cluster HFM 'Cluster (data server).

  7. save all

  Please mark this question as useful to the answer so that others can see

  Concerning

• I want that thunderbird to run in the background when I call the default mail client

  I have a software which sends emails for reports. The software calls the default mail client (Thunderbird) and sends the e-mail. However, this open Thunderbird and gets in the way. Is there anyway this could send the email without opening Thunderbird? Can it run in the background like outlook express? It should be closed after the e-mail was sent.

  http://KB.mozillazine.org/Thunderbird_3.0_-_New_Features_and_Changes#Send_in_Background

  Open Tools(or AppMenu/Options)/Options/Advanced/general/Config. Editor, paste mailnews.sendInBackground into the search box, and then double-click the preference to set it to true.

• error 1004 during the VI of the executable call

  I'm implementing the tutorial "create a windows NT service using LabVIEW", but I had no success. When I start my VI client I get the error 1004: the VI is not in memory. I always work with the normal executable, not the service again. Later, I will cross this bridge.  I made sure the data that generator VI has been included in the executable file (see attached files - no cookie generator VI, just a random number generator), and I have configured the server of VI in Project Explorer.  If I run the service VI in LabVIEW (not executable) and change the customer VI to search in memory rather than communicate through ports, then everything works perfectly, so I think that the problem is related with a certain configuration of the executable file.  Any help will be appreciated.

  There are several points here:

  (1) change the Boolean constant in svcSrvr.vi to a control, otherwise the VI does not appear in the exe file (even if it is specified in the build specification) [this looks like a bug to me]

  (2) in the application, use a different port (if not the project is still listening on this port as well as the application cannot listen on the same port), that is to change the port number in the application.ini. Solution: close the project before you run the exe.

  (3) wire "localhost" (or the name of the computer) the reference of the application open machine name entry.

  Hope this helps,

  Daniel

• I get an error, "the executable file that this service is configured to run does not implement the service" when I try to synchronize the time in Windows XP.

  After trying to fix the error of time synchronization by typing net start w32time that receipt of the message in the title.  In addition, type net stop w32time responded that the service was not working.

  Original title: the executable that this service is configured to run does not implement the service

  After checking the configuration in the registry and check or update if necessary from the link below:

  Then the time errors that I got from the command prompt window:
  Order--> net stop w32time & net start w32time
  Response--> The Windows Time service is not started.

  Order--> net start w32time
  Response--> system error 1083.
  The executable program that this service is configured to run in does not implement the service.

  --> Command w32tm/Resync /rediscover
  Response--> sending command to local computer resync...
  The following error occurred: the RPC server is unavailbale. (0x800706BA)

  Hi Mitchell_G,

  Thank you for keeping us posted.

  The steps of items offered in the previous post?

  We know if you need help. We will be happy to help you.

  Thank you.

• Can not run the executable file by LV7.1

  Hi all

  I'm surprised, I can't build and run the executable file LV7.1.

  I used to write a few vi with LV7.1 and built the executable according to these vi. It was no problem to build and run this executable file at that time. Now I can open these vi well with LV7.1, bu I can't run this executable file, it will be a mistake, please refer to the attachment. I'm trying to compile an executable file according to a simple vi, and then I can't run this exe file much more.

  Can you help me solve this problem? Thank you in advance.

  Evan

  @Christian: this is not correct.

  One of the reasons to do this is if LV 7.1.1 is installed, and then you install an application, including the runtime engine built in 7.1. It corrupts the execution engine.

  See here: http://digital.ni.com/public.nsf/allkb/680E61A4D02158A186256F7A0073C228

  Daniel

• connected as long as User1 I can only access the srv record (Explorer) - execute / run as he is denied (the path not found or insufficient rights)

  Original title: denied enforcement program

  Configuration:
  -Win server 2003 standard (in the Working Group)
  -Portable Acer Aspire 5100, Windowx XP Home Edition sp3

  Problem:
  On laptop, there are 3 users: administrator (administrators), (power user) User1 and User2 (user).
  Logged on as administrator or User2 I can access the server disk, run the executable SRV drive etc, but connected as
  User1, I can only access the srv record (Explorer) - execute / run as it is denied (the path not found or)
  insufficient rights). The same phenomenon occurs even if User1 receives administrator rights.
  On the server side there is no restriction or limitation to User1 (because it's in the group, where
  any member of this group (also User2) has no problem). Logging as User1 on others
  PC there is no problem.
  Grateful for any suggestions / help.
  Marjan

  Hello

  Try to take possession of the file or program and check.

• the contents of this file cannot be decompressed the executable file that you are attemptiong to run

  The contents of this file cannot be decompressed the executable file you are trying to run has been corrupted you can get another copy of the file check its integrity and try again.

  You have not told us what you're doing or what program you are trying to use...