Any way to auto-ignore error 1904, "failed to register"?
A frustrating re-occurance when repackaging (I am using Wise), is the error 1904, Module xxxx failed to register. If I run the MSI manually, I can hit ignore and continue on. Is there any way to auto-ignore these errors? I know I can go in and fix each one, but it is a pain and it is an ongoing problem. [:@]
0 Comments
[ + ] Show comments
Answers (13)
Please log in to answer
Posted by:
AngelD
16 years ago
To prevent DLLs from being added to the SelfReg table:
Select Options from the Tools menu
In the Advertising tab uncheck the "Automatically add self-registration" checkbox
Changing a DLL to not register versus clicking ignore produces the same result -- the DLL does not register.
Yes they produce the same result.
But you're ignoring an error that shouldn't be there in the first place, right?
Have a look at Rule 19: Avoid Using the SelfReg Table
Tao of the Windows Installer, Part 2
Select Options from the Tools menu
In the Advertising tab uncheck the "Automatically add self-registration" checkbox
Changing a DLL to not register versus clicking ignore produces the same result -- the DLL does not register.
Yes they produce the same result.
But you're ignoring an error that shouldn't be there in the first place, right?
Have a look at Rule 19: Avoid Using the SelfReg Table
Tao of the Windows Installer, Part 2
Posted by:
MicrosoftBob
16 years ago
Posted by:
nheim
16 years ago
Posted by:
nheim
16 years ago
Posted by:
MicrosoftBob
16 years ago
Posted by:
nheim
16 years ago
Posted by:
MicrosoftBob
16 years ago
Perhaps I'm misunderstanding you...this is the situation...
I do a snapshot of an application install and generate an MSI file. When I run this MSI file on a test workstation, I get the error "Module xxx.dll failed to register", to which I can click ignore, and continue the install. I do what you described above and select "Do not register" and generate a new MSI. Then it installs on the test workstation without the error because it doesn't try to register the DLL. Well, that is the same as clicking ignore, in my opinion. In both cases, it does not register the DLL.
[sm=rolleyes.gif]
I do a snapshot of an application install and generate an MSI file. When I run this MSI file on a test workstation, I get the error "Module xxx.dll failed to register", to which I can click ignore, and continue the install. I do what you described above and select "Do not register" and generate a new MSI. Then it installs on the test workstation without the error because it doesn't try to register the DLL. Well, that is the same as clicking ignore, in my opinion. In both cases, it does not register the DLL.
[sm=rolleyes.gif]
Posted by:
AngelD
16 years ago
First of all I wouldn't use the self registration (SelfReg table), even Microsoft doesn't recommend this.
Make sure to capture these into the Registry table or/and the advertise related tables.
I know that Wise Package Studio some times adds DLLs to be registered even though they doesn't support to be registered.
In my opinion, clicking Ignore isn't the same thing as preventing them from being registered, you just tell the installation to go ahead with the installation anyway.
Make sure to capture these into the Registry table or/and the advertise related tables.
I know that Wise Package Studio some times adds DLLs to be registered even though they doesn't support to be registered.
In my opinion, clicking Ignore isn't the same thing as preventing them from being registered, you just tell the installation to go ahead with the installation anyway.
Posted by:
MicrosoftBob
16 years ago
How do I choose to not use the self registration (SelfReg table)? I'm not familiar with that option.
Why does Microsoft recommend not to use the SelfReg table? Is it because of problems like this?
Changing a DLL to not register versus clicking ignore produces the same result -- the DLL does not register.
Why does Microsoft recommend not to use the SelfReg table? Is it because of problems like this?
Changing a DLL to not register versus clicking ignore produces the same result -- the DLL does not register.
Posted by:
MicrosoftBob
16 years ago
Thanks, I'll try unchecking that option.
Since it looks like this SelfReg table has all these inherent problems, one wonders why Microsoft even included it, and what advantages it has, if any.
>> But you're ignoring an error that shouldn't be there in the first place, right?
Call me lazy if you want, but it just got to be extremely irritating to "fix" yet another MSI package. [;)]
Hopefully, this option will be an easy way to prevent the problem from happening in the first place.
Since it looks like this SelfReg table has all these inherent problems, one wonders why Microsoft even included it, and what advantages it has, if any.
>> But you're ignoring an error that shouldn't be there in the first place, right?
Call me lazy if you want, but it just got to be extremely irritating to "fix" yet another MSI package. [;)]
Hopefully, this option will be an easy way to prevent the problem from happening in the first place.
Posted by:
AngelD
16 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.