Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Logs not showing failer

Updated: 25 Sep 2010 | 1 comment
h777's picture
0 0 Votes
Login to vote

We have NS 6.x.   I setup a Task job.  This Task will install 3 packages.  Package #1 is Microsoft Virtual C++ runtime.   Packages 2 and 3 are .MSI's.    I deployed this Task to 6 machines and 1 of them failed.   I looked at the logs on the client and I see that the first EXE did run but the second pacage (an .MSI file) never ran and never created any log file.

I looked in c:\Program Files\Altiris\Altiris Agent\Logs on the workstation.  There is 1 log file there called Agent.log.   Inside this file I see nothing that points to the MSI that never ran. 

On the NS server I opened up the Altiris Log Viewer.  I did a filter for the name of the workstation that failed and it shows no results.  

I then went to the log folder on the NS server.  D:\Program Files\Altiris\Notification Server\Logs    I did a search of all files for the name of my workstation that the MSI failed on.   Nothing was found. 

So on the NS server how do you find the log file entry for the failed workstation?  

Comments

jharings's picture
25
Mar
2010
0 Votes 0
Login to vote

Did you try looking at the reports

for sequential software delivery? If I remember correctly, they built in reports don't list error codes, but I seem to remember some custom reports floating around on Altirigos. I can post them if you can't find them, but they aren't my creation.

A few other points: Did you build a dependency between the two tasks? Does the C++ install require a reboot? If it's a Microsoft install of C++, you ought to be able to have a command line that enables logging for it.

Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.