Hi All,

I am trying to upgrade the package but whiler upgrading i am getting below error in event vwr

"Product: FidelityInformationServices_ACBSClient_5.3.208.769_B1.0 -- The display resolution of this computer must be 1024 x 768 or higher to successfully install the FidelityInformationServices_ACBSClient_5.3.208.769_B1.0. Currently, the resolution is set to 640 x 480. Please change the computer's resolution and run the installation again."

B1.0 is the version which is in production now.

There is one launch condiotion in which check for the resolution of the display i removed in my package but it is not upgrading the package instead it is throwing above error .



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 packenegg,
time to switch on logging.
In the logfile you will see, that this error almost certain will come from the already installed package.
Is it not possible to switch your screen to this resolution?
The installed package was installed with it, i guess.
Regards, Nick
Answered 09/05/2008 by: nheim
Tenth Degree Black Belt

Please log in to comment
0
Hi Nheim,

Thaks for the reply.

Yes the new version got installed with the older version
Answered 09/05/2008 by: packengg
Orange Belt

Please log in to comment
0
Hi packenegg,
Yes the new version got installed with the older version
What does this mean? Don't have a clue.
Regards, Nick
Answered 09/05/2008 by: nheim
Tenth Degree Black Belt

Please log in to comment
0
because of this ..both the version co-existed on the machine simultaneously....
Answered 09/05/2008 by: packengg
Orange Belt

Please log in to comment
0
Hi packenegg,
This can have different reasons.
How can you have both versions installed? I thought this error was a show stopper!
Does the installation run trough after clicking the error away?
If yes, the scenario could be like this:
The older, installed package has this condition.
You try to install the newer version with the condition removed, the older gets detected.
Therefore the new one tries to remove the older one. The remove process is basically the same thing as you would invoke it by hand but silent.
Then the condition of the older one kicks in an trows this error.
You can easily test this by yourself: Remove the old version by Hand and see if this error comes up.
Then the "msidbUpgradeAttributesIgnoreRemoveFailure" bit is almost certainly set in the upgrade table.
Regards, Nick
Answered 09/05/2008 by: nheim
Tenth Degree Black Belt

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