hi all,
My application Nero 8 is giving an error in Repair in Vista OS. The repair works fine in XP OS but when i am
trying to repair the same application in Vista it gives me an error saying that "Installer stopped prematurely". when
i looked into the log for repair i found the following lines during the Installfiles standard action which as giving
problem:

MSI (s) (1C:54) [05:44:27:494]: Internal Exception during install operation: 0xc0000005 at 0x000A83FC.
MSI (s) (1C:54) [05:44:27:494]: WER report disabled for non-console install.
MSI (s) (1C:54) [05:44:27:494]: Internal MSI error. Installer terminated prematurely.

when we look into services the windows installer service is terminated.....also even if we restart it the same error occurs during the next repair of the same application....
Anybody has any idea regarding this. any help would be appreciated.


Thanks and Regards

Sidharth
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
Hi Guys,

Please help us regarding this.....urgent help required.

Thanks and Regards

Sidharth
Answered 10/21/2008 by: sidverma
Senior Yellow Belt

Please log in to comment
0
- Have you tried the vendor's support services?
- Monitor the repair with ProcMon (or your favoured process/file/registry monitor) to see exactly what's going on. I'd wager it's almost certainly a permissions-related issue.
Answered 10/21/2008 by: VBScab
Red Belt

Please log in to comment
0
I tried that out but we get nothing from it....actually it gives this error during installfiles(I am sure about this because i have tried by commenting the installfiles action and it did not through any error) standard Action ....we found out
on the internet that it is related to digital signature checking inside For the external cabs(not sure though) which happens only in vista.....but not able to find out why this exception is coming and for which cab it is coming.....
Also i have tried the following things:
1.) removed all the assemblies.
2.) Removed all the services and system32 files.
3.) made component attribute for all the component as "do not overwrite" so that none of the files are in use during repair.

All the above solutions did not work....

do you want me to show you the whole Log from the Repair?
Answered 10/21/2008 by: sidverma
Senior Yellow Belt

Please log in to comment
0
So....you found out that the issue was likely to be the requirement for digital signature so you set about destroying the guts of the application in various ways to bypass that requirement? Bizarre....

On this page http://www.microsoft.com/windows/compatibility/Search.aspx?type=Software&s=nero a number of products in the Nero suite are marked as 'Get paid upgrade' which is presumably MS's strangulated English for ' You need to get an upgrade, for which you have to pay'. I'd be badgering the vendor or, more likely, encouraging my users to use CDBurnerXP which is a) free, b) crash-free and c) works on Vista straight out of the box. http://cdburnerxp.se/
Answered 10/22/2008 by: VBScab
Red Belt

Please log in to comment
0
ya i would do that too....but the problem here is i am not the user but the packager of the application....and whatever client tells me to package i have to package that....
I did all those changes to find out the root cause of the problem but was unable to do so.....anyways if you check the source of Nero 8 application you will find out that it does not contain any shortcuts which are advertised and all the features are also present as not advertisbale......which means the vendor itself does not support any advertising.... it is when we try to make advretised shortcut we get this error......... but still there should be some explaination to this error.....also we cannot get away by saying only this that vendor does not support it........
that is the reason why we are finding about the solution to this problem.
Answered 10/22/2008 by: sidverma
Senior Yellow Belt

Please log in to comment
0
It might have helped to explain at the outset that it is the addition of advertised shortcuts which is causing you problems. For me, it's a stretch to describe that as a 'repair'. A repair generally refers to the replacement by the installer engine of files or registry entries which have been removed. The point is arguable, I guess, but still, a clear explanantion of the problem might have saved some time.

Now, when you say:
it is when we try to make advretised shortcut we get this error does that mean at compile-time (i.e. when trying to build the transform) or at run-time (i.e. when the MSI/MST is run on the target workstation?
Answered 10/22/2008 by: VBScab
Red Belt

Please log in to comment
0
Hi sidharth,
Nero is one hell of an MSI!
This MSI file is full of custom actions, custom tables and lot of tables get altered during runtime and so on.
So, there are most likely pretty good reasons, that advertising is disabled.
I would make sure, that the repair option in ARP is disabled.

Other solutions would be to do a complete repackaging (this is the only app which comes as MSI so far, where i recommend this!)
The best way would be, to do a transition of the present MSI into an "regular" MSI. But this needs in deep knowledge of the product (and a lot of time).
There is an other unofficial distribution of nero at updatepack.nl.
Regards, Nick
Answered 10/22/2008 by: nheim
Tenth Degree Black Belt

Please log in to comment
0
Hi vbscab,

sorry could not explain the problem clearly earlier.....will explain it now. The error comes during the Self- repair
of the application and it comes only in vista and not in XP.
by self-repair i mean when i delete a particular file and launch the advertise shortcut of the application or
when i try to forcefully repair the application through msiexec /f. Now these shortcuts were not advertised in the
source but we made them as advertised.
The only starnge thing is that the repair works fine in XP and but does not work on Vista. so it has to do
something with windows installer 4.0 or later version technology which is causing this error to occur.

Thanks and regards

Sidharth
Answered 10/22/2008 by: sidverma
Senior Yellow Belt

Please log in to comment
0
Are you editing the shortcuts within the MSI itself to change them to advertised or are you using a transform in which those shortcuts which you are replacing or removed and substituted with your own?
Answered 10/22/2008 by: VBScab
Red Belt

Please log in to comment
0
we have used a transform to change the shortcuts to advertised.....will that make any difference??....since i can see all the changes getting reflected
Answered 10/22/2008 by: sidverma
Senior Yellow Belt

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