Error: "Could not launch (id=3) Problem: Path specified is invalid."

(Last modified: 05Dec2003)

This document (10014516) is provided subject to the disclaimer at the end of this document.

fact

Novell ZENworks for Desktops 2

Novell ZENworks for Desktops 3.2

Novell ZENworks for Desktops 4 - ZFD4

Novell ZENworks for Desktops 3.2 SP1

Microsoft Windows NT Workstation 4.0

Microsoft NT Service Pack 3

symptom

Error: "Could not launch <application object name> <path to executable> (id=3) Problem: Path specified is invalid."

Error occurs when launching an executable application object.

Error: "Could not launch <application object name> <path to executable> (id=18) There are no more files.

Error: "Could not launch <application object name> <path to executable> (id=67) The network name cannot be found

Error occurs when Unsecured or Secure System User option is selected in the NAL object.  

fact

        When user is logged in as Administrator, or as a User on the NT machine, the problem still occurs.   

        When the user is logged into NetWare as Admin or Admin equivalent, the error still occurs.  

        When the option "Run normal" is selected in the Environment page of the application object, the error doesn't occur.

cause

The "Run as secure and / or unsecure system user" will only work when the workstation object is imported and the workstation object has effective read and file scan rights to the Netware directory that the application object is running the executable from.  

The application object will work fine if just the user is associated to the application object and you don't have the workstation object associated to the application object.  You don't have to associate a workstation to the application, you just have to have the workstation imported for applicatoins to run as the system user.  

The default option "Run normal", would need to be selected if you don't have the workstation object imported.  If the application object is associated to the container object, you will get a message asking you if you would like to associate the application to the:
        
        1. Users in the container.  
        2. Workstations in the container.
        3. Both users and workstations.   
                NOTE: You can select either #1, #2 or #3, in order for the application object to function as either a secure or unsecure system user.

fix

Any of the following suggestions will work.  
        1. Make sure the workstation object is imported if you want to use the Unsecured System user option within the application object. 
        2. Give the workstation object Read and File Scan rights to the directory where the application is located.
        3. If you're running an executable, you can have NAL copy it down to the workstation with the user object's rights under the distribution options section of an application object, then run it locally on the workstation.  This way, NAL doesn't have to depend on the workstation object being logged into the tree to run the application as a system user.

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.