Hi,

I have created a wise scritp wrapper for a vendor msi. when I install and launch the application on Windows 7, its throwing an error saying a dll was not registered. When I am trying to register it with regsvr32.exe, it saying dll was loaded, but the call to DllRegisterServer failed with error code 0x80020009. When I run cmdline in Administrator mode and register the dll, it went fine. so how can I manage it in the wise script.

Thanks.
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
HELLO ravi,

u can use vbscript also as:

Set wshell = CreateObject("WScript.Shell")
ashell.Run("regsvr32.exe /s " & "<Path of dll file>")

Tried to use runas command in wse

regards
MM
Answered 11/18/2010 by: mayur_mak
Senior Purple Belt

Please log in to comment
0
Hi Mayur,

Thanks for the reply. I tried with the VB script, still not working. You mentioned to try runas command in wse. How can we do that?

Thanks.
Answered 11/18/2010 by: ravi223966
Senior Yellow Belt

Please log in to comment
0
Ravi,


Please check if your application (msi) have any self reg entries in selfreg table. If u have any, then try to make the self reg table emply by seft-registing the specific components.

You can also register .dll files with msiexec /y - register
/z - unregister thru custom actions.

Sreedhar.
Answered 11/18/2010 by: sreedharko
Orange Belt

Please log in to comment
0
My guess would be that the account you're installing with has insufficient rights to write to either HKLM\Software\Classes or the specific key(s) where the registration information would be written. A few seconds using ProcMon will determine that.

Quite why anyone in your position would imagine that a non-admin account could be used to install software - especially on Windows 7 - escapes me.
Answered 11/19/2010 by: VBScab
Red Belt

Please log in to comment
0
Thanks for the replies.

I created a Transform to vendor msi by adding the dll to selfreg table and it solved the problem.

Thanks.
Answered 11/19/2010 by: ravi223966
Senior Yellow Belt

Please log in to comment
0
SelfReg is The Work of Satan. If the DLL has any dependencies which are missing on your target machines, registration by this method will fail. You should use the advertising tables.
Answered 11/19/2010 by: VBScab
Red Belt

Please log in to comment
0
is it 64 bit OS?
Answered 11/20/2010 by: rock_star
Black Belt

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