This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Installscript dll call crashes with 0x80040707 error
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 29, 2009
09:40 PM
Installscript dll call crashes with 0x80040707 error
I am trying to call a dll function. It worked a week ago now not.
attached is the installscript code and a sample of the dll that I am calling.
Sorry I didn't put the whole dll code in. It is a huge assembly. I can get in more detail if needed.
I cannot figure out what happened. It worked a week ago now it crashes on the dll call. Earlier today it was simply returning that it couldn't perform the checks. i realized that somehow the file was removed from the support files directory of the install. I put it back in and now I am getting the errors.
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 30, 2009
08:14 AM
Ok, I found the correct version of the dll I was calling and have replaced the other one and no longer get the error. However I am still not getting any result back from it.
Can someone tell me if I am correctly setting that object using DotNetCoCreateObject? I am not sure if I am passing in the correct parameters. Is the second parameter that is called assemblyandclassname really just supposed to be the classname?
Can someone tell me if I am correctly setting that object using DotNetCoCreateObject? I am not sure if I am passing in the correct parameters. Is the second parameter that is called assemblyandclassname really just supposed to be the classname?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 30, 2009
09:43 AM
Whew, Got part of it figured out. It is an issue with the function that i need to call within the dll.
It opens another issue so I will start a seperate thread for that. This issue is resolved.
It opens another issue so I will start a seperate thread for that. This issue is resolved.