I have a problem with repairing a package, the package is RasterCAD. I'll try to explain the process that we follow here first as it's always worked perfectly until today!

  • Deployment is done via sms 2003
  • We obviously create transforms for vendor apps. When we create a transform we have an internal company version for this (no change to ProductVersion property). For our first deployment this is version 1 then if we need to make changes to the same package without deploying a new version of the vendor app it becomes version 2. e.g
    RasterCAD_11.0.0_BE_v1.msi - initial version
    RasterCAD_11.0.0_BE_v2.msi - Updates required to user files and permissions
  • When we deploy these types of updates we tend to have a pre-requisute vbscript that sms runs to determine if Version 1 is installed or advertised and if it is uninstalls it. Then sms continues and installs version 2
For RasterCAD the vendor package has an internal cab file. I have added files to the package which I have done in an external cab file (again no issues with this).
RasterCAD contains files in the users profile and HKCU keys so on first run it repairs. as I say never been a problem before but the install fails because it cannot locate the external cab file. But it is looking at the distribution point for RasterCAD_11.0.0_BE_v1 rather than RasterCAD_11.0.0_BE_v2.

I've looked in the registry HKLM\SOFTWARE\Classes\Installer\Products\GUID\Sourcelist\Net
and see 2 entries
1 - value \\Server\share\Folder1 - this is the distribution point for BE_v1
2 - value \\Server\share\Folder2 - this is the distribution point for BE_v2

My understanding of this is that the package would check both areas and find the CAB file in \\Server\share\Folder2

If I check the reg settings for other packages we've done there are loads entries under the Net key and there are no issues.

Sorry for the long explaination but does anyone have any ideas on why this may be happening?

Cheers
Rich
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
When we deploy these types of updates we tend to have a pre-requisute vbscript that sms runs to determine if Version 1 is installed or advertised and if it is uninstalls it. Then sms continues and installs version 2

First this, is the product code for both these installers same, because from your explanation, it seems that both have same unique product details. If the product code are same, this could be a problem try changing the product code for v2 and see if it helps. but please try it on test machine first. It's just a possible solution.

or maybe try deleting registry value entry one...

1 - value \\Server\share\Folder1 - this is the distribution point for BE_v

let me know if it helps...
Answered 07/02/2009 by: PackageExpert
Blue Belt

Please log in to comment
0
First this, is the product code for both these installers same, because from your explanation, it seems that both have same unique product details

Yes the ProductCode is the same, it's the same vendor msi so I don't want to go changing the ProductCode. I'm not attempting to upgrade though I'm uninstalling the previous package so this shouldn't cause any issue.

or maybe try deleting registry value entry one...

1 - value \\Server\share\Folder1 - this is the distribution point for BE_v


This isn't something that I can remove from the package it's managed by the windows installer service.
Answered 07/03/2009 by: timmsie
Fourth Degree Brown Belt

Please log in to comment
0
Is this on one machine or all? I suspect you're going to have to do something with the source list, since the engine is clearly having trouble with it. As a test, I'd be tempted to edit the list to see if the problem goes away. If it does, consider manipulating the list via the WindowsInstaller.Installer object in script...perhaps storing the existing setting, changing it, doing the install and then restoring it?
Answered 07/03/2009 by: VBScab
Red Belt

Please log in to comment
0
It was a problem on all machines for about 2 days.

But as if by magic, today it's started working correctly again.

I have a feeling that there may have been a problem with the sms dp's at some point. Even though I could browse to them it seems windows installer couldn't.

thanks for the suggestions though
Answered 07/03/2009 by: timmsie
Fourth Degree Brown Belt

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