hi VBScab,

i'm asking for your help because i saw you having the answer for that kind of things;

what is the error 0x80004005?

how do you translate those errors into human language?

thanks man!
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
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
Answered 11/14/2011 by: jmaclaurin
Third Degree Blue Belt

Please log in to comment
0
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
Answered 11/14/2011 by: bearden3
Purple Belt

Please log in to comment
0
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!
Answered 11/14/2011 by: kardock
Second Degree Green Belt

Please log in to comment
0
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. .
Answered 11/28/2011 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment
0
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|]
Answered 11/28/2011 by: bearden3
Purple Belt

Please log in to comment
2
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...
Answered 11/29/2011 by: VBScab
Red Belt

Please log in to comment
0
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 ;-)
Answered 11/29/2011 by: kardock
Second Degree Green Belt

Please log in to comment
0
You support your clients without WebEx? LogMeIn? Remote Desktop Connection?
Answered 11/29/2011 by: VBScab
Red Belt

Please log in to comment
0
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!
Answered 11/29/2011 by: kardock
Second Degree Green Belt

Please log in to comment
0
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. :)
Answered 11/29/2011 by: bearden3
Purple Belt

Please log in to comment
Answer this question or Comment on this question for clarity