Environment
Novell ZENworks Desktop Management 7
Novell NetWare 6.5 Server
Microsoft Windows XP Professional SP2 Workstations
Novell Client 4.91
Novell NetWare 6.5 Server
Microsoft Windows XP Professional SP2 Workstations
Novell Client 4.91
Situation
Corporate environment with approximately 50 users creates a
standard set of NAL applications for common settings and
software.
One NAL application configured as a Chained App will not install successfully for one user. The error follows his login to any machine he uses.
The error message on a Windows XP desktop is:
Application Launcher Status
A dependent application failed to install.
[Fully Qualified Application Name] (id=1009)
This application is a Windows .EXE, not an .MSI file. And, if it is called by clicking on the app's icon instead of using NAL, it appears to install correctly.
One NAL application configured as a Chained App will not install successfully for one user. The error follows his login to any machine he uses.
The error message on a Windows XP desktop is:
Application Launcher Status
A dependent application failed to install.
[Fully Qualified Application Name] (id=1009)
This application is a Windows .EXE, not an .MSI file. And, if it is called by clicking on the app's icon instead of using NAL, it appears to install correctly.
Resolution
The user account in question had restrictions on his Windows
Profile for business reasons.
When NAL tries to install the application, it returns an error because Windows is restricted from full access to the Profile.
The error also occurs when the application is installed manually, but Windows hides the error from the Desktop interface. NAL does not hide the error, but passes it through.
When NAL tries to install the application, it returns an error because Windows is restricted from full access to the Profile.
The error also occurs when the application is installed manually, but Windows hides the error from the Desktop interface. NAL does not hide the error, but passes it through.
Additional Information
In this case, it appears to be a NAL error, but it is not. NAL is
only the messenger.
All of the native NAL error codes begin with D0xx or 53xx. If the error shown is different than these, then it is a different Service or Application running on Windows generating the error.
All of the native NAL error codes begin with D0xx or 53xx. If the error shown is different than these, then it is a different Service or Application running on Windows generating the error.