Software Deployment

LOL...actually, I remember posting a reply to this and it was more or less exactly the same as Lewis's. Lord knows what happened to it.

Anyway, as I say, it was more or less word-for-word, save for the addition that, for these errors (unlike, say, errors returned by WMI queries) only the last 2 (or 4?) digits are relevant. In this case, we're looking at error 5 which, as we all know - having commited the DOS error table to memory - is 'Access denied'.

So, if the registration od DLLs/OCXs is failing, it'll be because the account being used doesn't have sufficient privileges to write to the location.

Needless to say, a session with ProcMon would have brought that to light in seconds but I may not have mentioned that particular tool before...

Ok, I'm not VBscab, but I'll give it a shot...

That specific error (its more a general error than specific) basically means that something failed. Commonly, its something that is called that is not properly registered like a dll or ocx. The general side could mean the file is not registered, is corrupted, is not what the application is looking for (version, wrong file), is not installed, is not in the location its supposed to be, etc....

Check the event logs for more detail or enable verbose logging in hopes to capture where its failing.

HTH

If you get an MSI error -2147467259, convert the decimal number to hex, giving you FFFFFFFF80004005.
Drop the leading "F"s giving you 80004005.

Looking in the winerror.h file, the Hex value 80004005 (decimal: -2147467259) gives an Error Description of "Unspecified error." Of course that's not helpful at all. :(

Look at this link to see if it helps you any:
http://www.computerperformance.co.uk/Logon/code/code_80004005.htm

the error is related to 6 ocx & 1 dll files. it could be the registration of these. at least, i have a clue. let's hope it will help fix this.

thanks!

there is an exe in the windows resource kit that translates the error codes. I can't remember its name of the top of my head I will try and dig it out. .

It's been 2 weeks since you posted this... VBScab must be on holiday. [:)]

Or maybe he figured his AppDeploy "backups" can handle the load! [8|]

ProcMon is kind of hard to run when the problem appears on a customer's computer, distributed by sccm, and the behavior never happened in tests ;-)

You support your clients without WebEx? LogMeIn? Remote Desktop Connection?

actually, the point was not what was the error, but how do you know the error?

i'm looking for the way to found out by myself when i get an error like that.

thanks!

Kardock,

Please take a look at post #3 again. I tried to specifically address your question.

The hyperlink not only helps you with the particular error you got (0x80004005) but also gives details about the other errors as well.

Good luck. :)