Software Deployment

My guess would be that some property isn't being set because the UI isn't being run. Compare the two sequences.

Hi,

If you are using Wise , then go to components in setup editor. These components have files. Double click them or right click and select details. A pop-up is displayed where you will see a registartion tab. Click on that tab. It has a drop-down list. Select "Do not register" from it. Try this , your problem should be solved.

If you are not using Wise, then for other tools similar options will be available.

Regards,
Nilo

Yeah...I already checked the selfreg table and these are all set to not register by default. And it's not just one dll...it's a host of dlls, ax files and exes.

If you run the setupx.exe with a quiet switch it actually works fine...and that calls the vendor msi anyway, so not sure what's causing it to fail.

Ahead is using the SelfReg table? Jeez...

- Create a transform and load it into your MSI editor.
- Note down or print the names of the files in the SelfReg table.
- Delete all rows in the table or delete the table.
- Now you need to get the COM information out of those files. Depending on the authoring tool you're using, the method will differ. In WPS, there's a command-line utility called WiseComCapture which will produce a .REG file for a DLL or OCX passed to it. For InstallShield (haven't used it for a while), I believe you change the file's properties from 'Self register' to 'Extract COM data'. Perhaps a more experienced IS user can assist here. If you don't have a full-blown authoring tool and are relying on, say, Orca, best of luck!
- Import the .REGs into WPS, electing to have WPS add the advertising entries.

End of registration issues.

Hi Tom,
you have been looking at this notes here:
http://itninja.com/link/techical-guide:-silent-install-for-storagecentral-srm-5.07
And tried the receipt for MSI-only install?
Regards, Nick

Hi Tom,

Could you be more specific on the error message and type that you are having ?
Running through the Setup.exe might install something prior the launching of the vendor msi.
Make a snapshot of the computer, before and after the installation with your setup.exe and see if it adds something that could satisfy the msi install.

Hint:
I've just been throught a painfull package creation of Nero 7.9.6.2 and when performing a silent install I had an error quite similar to yours at the end of the installation.
It was a problem with Directx 9.0c.
In my case I have run a snapshotter prior to the installation of directx and found 2 files that were missing from my C:\Windows\system32 folder.
Those files are d3dx9_28.dll and d3dx9_30.dll. After adding those two files, my MSI could launch silently with no problem.
Hope that helps.
Regards, Alan

Hi Alan, the dll files were already installed. Don't think it's a pre req issue such as Directx. The msi works on its own with the additional properties that don't call the setupx. As soon as you run in with a silent UI it bombs out with the following messages: "Unable to register C:\Program Files\Common Files\Nero\lib\MediaLibraryNSE.dll". This occurs for the majority of the dll files and exes in that folder. You can drop the files from the selfregex table and they get copied across but still cannot register them manually so I can't even write a batch file to do that post install. Very puzzling.

You can drop the files from the selfregex table and they get copied across but still cannot register them manually so I can't even write a batch file to do that post install. Very puzzling.So use ProcMon when you manually register and you'll see straight away what the problem is. It's either missing files which the DLL depends on or permission issues with the registry keys/entries it's trying to write.

Hi,
I am facing similar problems with " registration of dll's" during installation of the MSI. and the strange thing is that its behaving differently on two different images.
But d final testing has to be done on the image throwing "registration error"
Plz suggest how to resolve this error in Installshield.

ORIGINAL: karshi
But d final testing has to be done on the image throwing "registration error"
Plz suggest how to resolve this error in Installshield.Well, the first suggestion would be to read the post above yours. Use ProcMon (or your chosen file/registry/process monitor) to see what is missing. ProcMon will show 'NAME NOT FOUND' for missing file and registry entries. Also, use verbose logging to identify which DLL is not registering correctly and load *that* DLL into Dependency Walker (a free download from Microsoft). that will show all the files which the DLL has to have present in order to work - and register - correctly. In my experience, the overwhelming majority of registration failures is due to missing dependencies. An even bigger clue to that situation is that you have success on one build but not the other: clearly the former contains the required file(s) whereas the latter does not.

Shame on Ahead for building an MSI which attempts to self-register DLLs...

hey thanx a lot,
Ur idea helped a lot and also got more familiar with these two softwares (bit new to me).In this case dependecy walker helped a lot.
wud like to add a simple idea which worked for me.
"we just replaced the 1033.mst with the customized tranform we created and then executed the "setupx.exe". Everything worked fine now[:)]no registration failure, no license acceptance problem."
But, i do have a problem deleting "Nero Scout" shortcut from "program menu->Nero8->Nero Toolkit" and also we are facing problems in removing "NMIndexing Services".
We have scripts which works when run manually, but m not sure about the sequence to be used in custom actions in adminstudio. we have tried a few but it didn't work.
Plz suggest.

But, i do have a problem deleting "Nero Scout" shortcut from "program menu->Nero8->Nero Toolkit"


Have a look at the fourth note in this thread,
http://itninja.com/question/tivoli-and-ms-mdac-2.8432&mpage=1&key=&#23432

it might help (?)

Regards,

Spartacus

Not sure if anyone still has this problem, but I just got it. After a bit of digging with Procmon, it looks like it was missing some DX9 files. You might not be missing the same file, but like VBScab said, get out Procmon and see what's missing.