ActionMan.NoResultsFile error

  • 7003627
  • 23-Jun-2009
  • 27-Apr-2012

Environment

Novell ZENworks 10 Configuration Management with Support Pack 2 - 10.2

Situation

A bundle action set to run as user fails when user can't access system temp directory to create the temporary results file.
 
ERROR (from ZCC):
 
ActionMan.NoResultsFile
 

Resolution

 This is fixed in version 10.2.1 - see KB 7003766 "ZENworks 10 Configuration Management 10.2.1 - update information and list of fixes" which can be found at https://www.novell.com/support

Additional Information

Prior to 10.2.1, even when the action is set to run as User, the Output.xml file (containing the results of the action) is written to the system temp directory.  This is typically defined as %WINDIR%\temp on the system drive.
 
In 10.2.1 and higher, the results file is written to user temp directory when run as user.
 
ERROR (from zmd-messages.log):
 
[DEBUG] [06/23/2009 21:15:40.103] [1400] [ZenworksWindowsService] [24] [] [StandaloneHandler] [] [Warning: can't open handler output file C:\badtemp\d156b101-906d-4a22-9a6c-02c6e648a844\74ed9ebbb2d31d75d69bf9ae631b8c24-Registry_Edit-138865Output.xml.
System.IO.FileNotFoundException: Could not find file
...
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)
   at Novell.Zenworks.ActionManager.StandaloneHandlerHandler.GetExeResults(String name, String output, Session session)] [] []
[ERROR] [06/23/2009 21:15:40.572] [1400] [ZenworksWindowsService] [24] [] [BundleManager] [ActionMan.NoResultsFile] [Could not find a results file for Registry Edit.  Message: Could not find file 'C:\badtemp\d156b101-906d-4a22-9a6c-02c6e648a844\74ed9ebbb2d31d75d69bf9ae631b8c24-Registry_Edit-138865Output.xml']

Feedback service temporarily unavailable. For content questions or problems, please contact Support.