InstallAware

Hello ,

I am creating installware patches for an existing install. I can create the patch .exe , but also I need a single network pushable MSI from it. I used to create single MSI packages for netwrok users using the Group Policy wizard and providing the path for installware compressed .exe. But now when I use the same wizard and provide the path for .exe file in the Upgraded Package folder, the wizard fires an error saying that the exe is not an installware compressed exe.

Can you please help me to create a network pushable MSI from my upgrade patch?

By the way my install package is a single file type...not a web or DVD...

Thanks

Dear User,

honestly, I am able to use GP wizard with an InstallAware patch exe without any problem.

Can you give more info in order to try to replicate your issue?
A project that I can verify?

Let me know.

Regards

Well I have a existing full install ... I make changes to it and I try to build patch for it.
Maybe the reason is that I get an error at the end of making the patch . the error is : Error during build: Unable to create patch database [Cannot generate a primary transform.] ....Can you help me to get rid of this error?

But event the above error , I still see the exe upgrade file is created in the patch folder...but when I try the GP wizard to make MSI , I get the error I mentioned in my first post?

Thanks

FrancescoT wrote:Dear User,

honestly, I am able to use GP wizard with an InstallAware patch exe without any problem.

Can you give more info in order to try to replicate your issue?
A project that I can verify?

Let me know.

Regards

Dear User,

I suspect that problem is related because probably you missed some steps.

have you done as follow to build your patch?

- in your patch project add any required reference to build patches against older versions of your product (full build setup files).
- execute a full build of your patch project.
- execute the patch build.

Let me know.

Regards

yes , I confirm that follow all the steps as you mentioned.
The thing is that the base install is an existing install which we have for years now.
Can the issue be from versioning ? my base version is 2.8.9 and I try to create patch 2.8.9.1

The only difference between the procedure I follow and the one in the white paper, is that my base installation is a Single File type and not a web deploy.
So as it was advised on white paper, I used the trick there to get the extracted exe from the temp file and use that as my base!!!!

Any advise?

FrancescoT wrote:Dear User,

I suspect that problem is related because probably you missed some steps.

have you done as follow to build your patch?

- in your patch project add any required reference to build patches against older versions of your product (full build setup files).
- execute a full build of your patch project.
- execute the patch build.

Let me know.

Regards

Dear User,

first of all any patch project must have the same version number that you used fror your base project.
If your base project have 2.8.9 as version number, any subsequent patch related to that project, must have 2.8.9 as version too.

Are you able to replicate your issue with a very simple project that I can test?

Regards

oh , so you think the issue is from versioning ? well this is a really bad news. If I create the patch with the same version of the base project, then some of our users will not be able to push the MSI in their network for patching since the new MSI should have higher version to MSI be pushed.

Sure, I will try to reproduce it on a simple project...can I be in touch through email?

FrancescoT wrote:Dear User,

first of all any patch project must have the same version number that you used fror your base project.
If your base project have 2.8.9 as version number, any subsequent patch related to that project, must have 2.8.9 as version too.

Are you able to replicate your issue with a very simple project that I can test?

Regards

Dear User,

yes, could be an issue due the version number.

Send your project to: [email protected]

Regards