Hi sidverma,

I'm goming out on a limb here, but I suspect that on the Vista OS, you may have a policy active that prohibits installing applications / files that are not digitally signed, and therefore this error.

Here's how I would go about trying to find the exact problem:



1. Install the application using the "original" vendor installation routine on Vista. Create a log file during install.



2. Using an admin context, delete a couple of files / registry entries so that this will "force" the repair.



3. Using an "normal" user context, attempt to start the application, which if you have carried out step 2 correctly, should invoke the self-repair. If you stilll have problems, then the error occurrs in both the vendor as well as your installation, and therefore is caused by settings / policies on the vista machine. If the error does not occurr, then it has something to do with the changes that you have made to the MSI using your MST, cannot help your here sorry.



I have had *fairly* good results by calling the tech support for Nero (in Karlsbad), but then again, the customer had bought 15000 licenses, so I had some leverage.



Hope this helps a bit,

Cheers

Phil

Phil is right - there can be all sorts of additional security issues on Vista. Did you try with the UAC turned off? There can also be problems with custom actions, as they will usually be configured to run elevated during a normal install, but on repair, the lack of elevation will cause many custom actions to fail. There is an article in the KB listing some issues with Vista and packaging which you may want to review.

Hi EdT,

I'm being a lazy bugger here, any chance that you know off the top of your head the KB's you mentioned?



Cheers

Phil

Folks, we've been having a discussion with the OP over on AppDeploy, too but this info is useful as well.



As Nick says there, have you seen the Nero MSI? Truly, it's a vision. On casual inspection, it looks quite accomplished but when you get into it....Jeez....

Hi Phil,



sorry for the late reply....I had just checked what all you have suggested and the application still gives

an error during Repair of the application. and also i would like to say that vendor does not support any

advertising for this application. the reaosn why i am saying this is because all the features in vendor

msi were "disbaled for advertising" and also non of the shortcuts were advertised shortcuts rather they

were coming from a custom action. We only removed the custom action and put all the shortcuts inside

the shortcut table and made them as advertised. the advertised functionality works fine in XP but in

Vista it throws up this error.

The chances are therefore high that the vendor disabled advertising for the very reason that their repair process is not reliable in all circumstances. I presume your tests with the native MSI without your modifications was successful?



Phil - I too am a lazy b*****, and I can't remember the KB numbers, but typing in Vista as a search term and limiting the search to the Wise product should throw it up.

See if any of the suggestions at 0xC0000005 Access Violation can help.

Are there any "nero" process running during repair and if so does a repair work if you make sure no related process are running?

Have you tried SP1 for Vista to see if that helps?



Also check if there is any new Windows Installer updates that could solve this (just download the latest).

Also, does the event viewer give you any more information regarding the access violation?

Hi AngelId,



there is no message shown in the eventvwr for this.......and we have checked for all the processes that

are running on the machine no process is running at the time of repair....whichever are running we kill

them forcefully...........Or build version is also Vista SP1 only.....do you want the full log of repair to see

Hi All,

the last Nero I packaged was 7.xx so my knowledge is not uptodate, however, that version also did not include advertised shortcuts, and I too had to disable the CA that created the shortcuts, and create them myself in the mst. This was however for XP and worked fine.



I read on Juice that it is OK in a SVS layer, have you thought about that?



cheers

Phil

What problem did you experience attaching the file? You need to ZIP it first, then upload it within the attach dialog, and finally, select it from the upload list and attach it.

The text you inserted looks like it has been truncated as there is nothing in the last 4-5 lines to suggest an error has taken place. We do not recommend posting logs other than as attachments for this very reason.

Hi edt,



I have attached the log file.......sorry for the trouble......could you delete the above message for me please.....i am unable to do so.....

Unable to open the zip file - does not appear to be a valid archive. Can anyone else check and see if they have problems opening this ZIP?

It's broken.

Hi Phil,



Client wants us to deliver a msi package with all the best practices followed which includes advertisement also hence we cannot deliver them a virtualised package on SVS and also this problem might occur sometime in future for Vista......so i am curious to solve it now only......

Hi edt,



Please rename it to .rar and open it using winrar

Hi sidverma,



best practice or not, if the application / msi does not work then the customer has the following chioces:



1. Use "as is" with no advertised shortcuts

2. Find other software



What's the point of delervering something that is *known* to fail?



Cheers

Phil

Hi Phil,



I know that .....but we need to give a proper justification to them as what is the exact reason for which

it is failing. and knowing this reason we can avoid any problems we might face in future

quote:
Originally posted by: sidverma we need to give a proper justification to them as what is the exact reason for which it is failing.

You already have the reason: the vendor is too stupid to fix their package to suport advertised shortcuts. The Nero MSI is such a joke. I don't know why they bother distributing it in that format, given the number of "black box" CAs they have in it.

Sorry, don't have winrar on my work machine.

sidverma,



Please provide the attachment in the zip compression format instead as XP and higher has this support build-in already.

Hi Guys,



I got to know atleast what is causing the issue.......it seems to be working fine with windows installer 4.0

which comes with the Vista OS......but when we run along with windows installer 4.5 it gives this

error...... does nay body know what might be causing this issue .....what extra functionality is present

in windows installer 4.5 which is not there in WI 4.0...

I don't have the time to compare between version 4.0 and 4.5 but maybe What's New in Windows Installer 4.5 will help.

quote:
Originally posted by: sidverma

does nay body know what might be causing this issue

Not me, but I bet ProcMon would show you.

How about reporting to Nero that their install errors on Windows Installer 4.5 and have them fix it?

Hi vbscab,



I have taken the procmon but i am not sure what to look for inside the procmon

Just to check - are you using the correct version of windows installer 4.5 for your operating system? I believe there are three versions targetting XP, Vista RTM, and Vista SP1/Server 2008.

Have a look at the team blog:

http://blogs.msdn.com/windows_...ller-4-5-versions.aspx



However, others are also experiencing errors with windows installer 4.5 - viz:

http://www.nvnews.net/vbulletin/showthread.php?t=117784

PLEASE don't tell us that the installer's installer doesn't do an OS check....

I expect it does, but have not had time to explore this, so it's always worth asking.

hi edt,



I have checked i am using the correct version of windows installer 4.5 i.e 4.5.6001.22162 which is meant for windows vista sp1 as per the link you have fwded....... i have even tried downloading the windows installer 4.5 myself and installing it on a clean machine (machine which contain installer 4.0) but i still got the error.....that is how i came to a conclusion that it is something to do with windows installer 4.5 only....

Looks like your findings are far from unique - try googling on your issue.