Msi Error 1904 Failed To Register
Contents |
Windows Installer (MSI) Windows Installer (MSI) Error Messages Help with MSI (Microsoft Installer) error 1904: Module [2] failed to error 1904 windows 7 register. HRESULT [3]. 0 Comments [ + ] Show Comments error 1904. module failed to register Comments Please log in to comment Rating comments in this legacy AppDeploy message board thread won't
Hresult -2147024770
reorder them,so that the conversation will remain readable. Answers 0 This error may occur during installation if another program, including memory-resident and anti-virus programs, are running and using any version of the file being updated by the setup. This error may also occur if the folder where the file is located includes a single quote or apostrophe ('). If this is the case, choose a folder that does not include the single quote to resolve the error. In most situations, you can safely click Ignore. Related Links: OFF2000: Error 1904 During Office 2000 Setup OFFXP: Error 1904 and Error 1919 When You Try to Repair Office Error: "Error 1904. Module C:\\bpbox.ocx failed to register. HRESULT. Contact your support personnel." ESRI KB Aricle 19654 Note: if you choose to handle the registraion manually, keep in mind that ActiveX EXEs can be registered using applicationame.exe /regserver. Regsvr32 will not work right with them. Answered 04/28/2004 by: AppDeploy.com Please log in to comment Please log in to comment 0 The quickest fix is to remove the dll from the self register table. Often installations include DLLs for applications that are not loaded. If the DLL can't find an entry point it will not register. Answered 12/20/2007 by: KentD Please log in to comment Please log in to comment 0 In Wise Package Studio remove the rows of the affected files in the tables "SelfReg" and/or "ISSelfReg". Answered 04/15/2008 by: packateer Please log in to comment Please log in to comment Answer
be down. Please try the request again. Your cache administrator is webmaster. Generated Thu, 20 Oct 2016 19:18:32 GMT by s_nt6 (squid/3.5.20)
Problems Search SelfRegModules fails or hangs Having trouble running Advanced Installer? Got a bug to report? Post it all here. Post Reply Search Advanced search 4 posts • Page 1 of 1 cpede Posts: 3 Joined: Mon Apr 19, 2010 11:31 am SelfRegModules fails or hangs Quote Postby cpede » Tue Apr 20, 2010 7:26 am OK, I'm in total panic. Ready to release and just find out that my MSI DLL registrations does not work.The problem originally started with my InstallShield Express project. Suddenly the installation crashed in msiexec, or sometimes continued but without registering most of my dlls.Normally I would get an error when a dependency was missing or I made a bug in my DLLRegisterServer. But this is different.I reduced my setup to a few files and the problem is reproducible. I contacted InstallShield but they kept directing my in the Extract COM information direction, instead of self registration of my dlls. However I do other stuff in my self registration and this has worked for many many years without any problem.I ensured that there is no dependency problems etc. When the problem occurs I can do Dependency Walter and a manual registration using regsvr32 on the dll without any problems.I then downloaded Advanced Installer to give that a try on my files. It also fails, but in this case I can get a log, that points me in the direction of the problem. And sure enough the problem lies in the self registration of my dlls.Code: Select allMSI (s) (B0:0C) [12:20:00:272]: Executing op: RegSelfReg(File=Common.Storage.dll,FileID=My.dll)
SelfRegModules: File: My.dll, Folder: C:\Program Files\My Company\MyTest\
Error 1904. Module C:\Program Files\My Company\MyTest\My.dll failed to register. HRESULT -1073741819. Contact your support personnel.
MSI (s) (B0:0C) [12:21:12:602]: Product: MyTest -- Error 1904. Module C:\Program Files\My Company\MyTest\My.dll failed to register. HRESULT -1073741819. Contact your support personnel.And again when doing it manually it works.I suspect some kind of service pack, policy, virus scanner, firewall to be the cause of this. Some must have experienced this also.A colleague of mine is also struggling with a similar access problem, plea