Could not get needed resource for application [object_name] to be launched (id=-337). Problem: Unable to connect to server [Server_Name]

(Last modified: 28Jun2005)

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

fact

Novell ZENworks for Desktops 4.0.1 - ZfD401

Novell ZENworks Management Agent + Client

Novell Application Launcher (NAL)

symptom

Could not get needed resources for application [object_name] to be launched (id=-337).
Problem: Unable to connect to server [Server_Name]


change

This error occurs when the app object is a) accessing the network using a servername  and  b) is run without the eDir user being logged in (like a force run, workstation associated application... or like a workstation associated application that is launched after logging in "Workstation Only").  When it fails, the Path to File used in the Application Object is \\servername\volname\dirname\filename. (Alternatively, if the source path used is an environment variable like %ZENSERV%, and this variable resolved to the servername, this also would fail). If the servername is changed to serverIP, then it works.

cause

At some point in the bootup process, the servername is being added to Client32's Bad Server Name Cache. When NAL attempts to run the app from the network, it passes the path off to the MUP, which passes the path to Client32, which looks in its cache before trying to resolve the name on the wire. When looking, Client32 finds this server in Bad Name Cache and never goes on the network to try and resolve the servername - but instead reports a failure to the calling application (NAL).  This occurs even when the server name is resolvable, the server is reachable, and the workstation object may even already have connections to that server.

fix

Fixed in zfdagent.msi dated 09 Sept 2004 located at Novell Product Updates

Configure the workstation to use an SLP DA (TID #10059981). If SLP multicasts are being blocked from one network segment to another, the workstation won't be able to resolve the NCP server object name via SLP.

Workaround:
1. Change the application object to use the IP Address of the server instead of the NCP Server Name.
OR
2. Change the Client Properties | Advanced Settings | Bad Server Name Cache Enabled = Off AND Bad Server Name Cache Timeout = 0

document

Document Title: Could not get needed resource for application [object_name] to be launched (id=-337). Problem: Unable to connect to server [Server_Name]
Document ID: 10093943
Solution ID: NOVL98156
Creation Date: 03Aug2004
Modified Date: 28Jun2005
Novell Product Class:Management Products

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.