PDA

View Full Version : 0002:0005 error during install



MarkRiffey
02-25-2019, 10:14 AM
Yep, I've seen the FAQ on this topic:)

My guess is that this failure (the load failure / access denied) is happening when the installer tries to dynamically load our Clarion DLL (which does some license checking). The results of this attempt do not change despite the user disabling their AV. We do have a fairly recently updated code signing cert, so that could be a tangent as well.

Even with Webroot and Windows Defender disabled, the 0002:0005 error persists.

What other escape routes out of this situation are there, outside of complete removal of the AV tools or delivering a ZIP? Obviously, neither are particularly desirable.

Thanks in advance,

Mark

linder
02-26-2019, 05:12 AM
Hi Mark,

do you have a screenshot available? And is there any error code after the "0002:0005" error?

Because the code signing cert is new (and does not have any reputation), I would suggest to build a reputation first. I can send you our "reputation builder" project file if you want.

IMO, the protection software "locks" the temporary folder actions in your case.

Friedrich

linder
02-26-2019, 05:20 AM
By the way, error "0002:" indicates that it comes from the STUB loader. The second part "0005" is GetLastError() ERROR_ACCESS_DENIED (Access is denied).

The STUB loader unpacked the decompression library LSUNPACK into the temporary Windows folder (this succeeded in your case). Otherwise, we would have seen a "0001:" error. After the unpacking process it used "LoadLibrary" to load the LSUNPACK library. This failed with ERROR_ACCESS_DENIDED. In other words, the protection software blocked the LoadLibrary Windows API action.

Friedrich

MarkRiffey
02-26-2019, 10:40 AM
Hi Mark,

do you have a screenshot available? And is there any error code after the "0002:0005" error?

Because the code signing cert is new (and does not have any reputation), I would suggest to build a reputation first. I can send you our "reputation builder" project file if you want.

IMO, the protection software "locks" the temporary folder actions in your case.

Friedrich

Projection project - worth a try.

No additional error code.

Here's the screenshot:

4870

MarkRiffey
02-26-2019, 10:41 AM
BTW, even removing the AV software (webroot - a particularly aggressive tool from what I can see) - the install fails with the same error.

Mark

linder
02-27-2019, 03:28 AM
Yes, I see. Definitely the "Access denied" error I mentioned.

1. setup.exe starts
2. setup writes LSUNPACK decompression library into the temporary Windows folder (SUCCESS!)
3. setup uses the LoadLibrary Windows API to load the successfully created LSUNPACK library (FAILS!). This load process fails with ERROR_ACCESS_DENIDED in your case.

So "something" on this machine locks the component in the temporary Windows folder. It's a typical "false-postive".

Friedrich

linder
02-27-2019, 03:29 AM
Mark,

what about Windows Defender? Is it enabled and active on this machine?

Friedrich

linder
02-27-2019, 03:46 AM
Here are some similar "Error 0002:0005" issues:

http://www.lindersoft.com/forums/showthread.php?47704-FAQ-What-does-installer-quot-Error-Code-0002-0005-quot-mean&p=88669#post88669

http://www.lindersoft.com/forums/showthread.php?47722-Error-Code-0002-0005&p=88814&highlight=0002%3A0005#post88814

http://www.lindersoft.com/forums/showthread.php?47876-Error-code-0002-0005&p=89702&highlight=0002%3A0005#post89702

Friedrich

MarkRiffey
02-27-2019, 09:19 AM
Yes, I see. Definitely the "Access denied" error I mentioned.

1. setup.exe starts
2. setup writes LSUNPACK decompression library into the temporary Windows folder (SUCCESS!)
3. setup uses the LoadLibrary Windows API to load the successfully created LSUNPACK library (FAILS!). This load process fails with ERROR_ACCESS_DENIDED in your case.

So "something" on this machine locks the component in the temporary Windows folder. It's a typical "false-postive".

Friedrich


Dev was not signing these dlls prior to yesterday. That has been corrected. Will be interesting to see if that resolves it. Might be worth adding a warning to your compile-time process that unsigned dynamically loaded dlls could fail to load at runtime. Not that we would know<g>

MarkRiffey
02-27-2019, 09:19 AM
Mark,

what about Windows Defender? Is it enabled and active on this machine?

Friedrich


Supposedly it was disabled as well, but I have my doubts on that:)

MarkRiffey
02-27-2019, 09:20 AM
Here are some similar "Error 0002:0005" issues:

http://www.lindersoft.com/forums/showthread.php?47704-FAQ-What-does-installer-quot-Error-Code-0002-0005-quot-mean&p=88669#post88669

http://www.lindersoft.com/forums/showthread.php?47722-Error-Code-0002-0005&p=88814&highlight=0002%3A0005#post88814

http://www.lindersoft.com/forums/showthread.php?47876-Error-code-0002-0005&p=89702&highlight=0002%3A0005#post89702

Friedrich


Yep, I had already lived vicariously through others using those 3 posts:)

linder
02-27-2019, 12:47 PM
Hi Mark,

IMO, it does not resolve this specific "0002:0005" loader issue. Because something "blocked" the Windows API LoadLibrary action on this machine, the LSUNPACK decompression function was not available and the setup.exe did not continue with the "support file" processing. So your own (unsigned) DLLs could not trigger any false-positive action.

But you are absolutely right. Unsigned "support file" DLLs are definitely candidates for a false-positive nightmare. I have added your compiler warning idea to the ToDo list. BTW, perhaps we can add an option to automatically code-sign the support file(s). Thank you for your suggestion.

Friedrich

MarkRiffey
02-28-2019, 02:03 PM
I have added your compiler warning idea to the ToDo list. BTW, perhaps we can add an option to automatically code-sign the support file(s). Thank you for your suggestion.

Friedrich


That would be quite handy and might save everyone time and trouble. Thank you.

Mark