Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

installing msi getting app metering error

Created: 17 Mar 2011 • Updated: 22 Apr 2011 | 7 comments
This issue has been solved. See solution.

i'm working with xp sp3 clients, i'm using cms 7.x

i'm pushing out a software packages--msi ,  msiexec /I "xxx.msi" /quiet   as the command line

when it's ran i get the error

" could not find a matching application in the app metering summary file for application details. "

any clue on this one? i have 5 of them to run and the first one ran without a problem.

Comments 7 CommentsJump to latest comment

KSchroeder's picture

Hi Redfox,

This is a case of log obsession...it is OK to have that "could not find.." error in the log.  It won't hurt anything.  I think it is due in part to having Windows Installer running multiple instances (one or two by SYSTEM, and another by the logged on user).

Thanks,
Kyle
Symantec Trusted Advisor

For Forum threads, please click "Mark as Solution" if answered.
For all content, please give a thumbs up if you agree with or support the post.

mclemson's picture

I thought by saying it was an error that it actually showed up as a red Error, not a blue warning or one of the informational, trace, or verbose levels.

What severity was this log item, Redfox?

Mike Clemson, Senior Systems Engineer, ASC
Intuitive Technology Group -- Symantec Platinum Partner
intuitivetech.com

KSchroeder's picture

I have seen these in my log (on NS 6) and they are Info-level messages.  Maybe it is graded higher (as warning or error) on 7.x, but regardless they are not important.

Thanks,
Kyle
Symantec Trusted Advisor

For Forum threads, please click "Mark as Solution" if answered.
For all content, please give a thumbs up if you agree with or support the post.

Redfox707's picture

the pushes/software installs are failing and this only error showing in the logs, so no obsession here-that i know of.

the severity is 4

mclemson's picture

If you're installing software (e.g. Adobe Reader) on a client computer, and it fails, you won't find the reason in the Altiris logs.  Youi'll need to examine Windows event viewer for details.

I'd recommend copying the files to a local client and running your command without the /quiet statement, perhaps replacing it with /passive so that it runs without interaction, but alerts you if there's an error.  A likely cause is that it's running into an issue during the install, like a reboot required, a pre-requisite not installed, a service not running, an input required, a EULA to be agreed to, etc. etc.

Mike Clemson, Senior Systems Engineer, ASC
Intuitive Technology Group -- Symantec Platinum Partner
intuitivetech.com

KSchroeder's picture

Also add /l c:\acroread.log to your command line. Sorry I misunderstood your original issue Redfox

Thanks,
Kyle
Symantec Trusted Advisor

For Forum threads, please click "Mark as Solution" if answered.
For all content, please give a thumbs up if you agree with or support the post.

Redfox707's picture

ran the msi with passive switch and added the log file and i was able to find out what was going on

 

thanks for all the info.

SOLUTION