Hi,

I am using wise package studio 7.0
I am having an application which is having same package code as previous version.Because of this its not getting upgraded.But,the option to generate a new package code in summary information is disabled.Now how can i make it work so that the older version gets upgraded.

Pls help me in this regard.

Thank you.
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
Is your WPS help file missing?

- Go to the 'Setup Editor' pane
- Select the 'Product' tab.
- Select 'Summary' in list-box
- Double-click the 'Package Code' field
- In the 'Summary Details' dialog, click the 'Generate' button to create a new Package Code
Answered 03/13/2008 by: VBScab
Red Belt

Please log in to comment
0
I tried to do that...but the Generate tab in summary details is disabled(it is not highlighted)
Answered 03/13/2008 by: Jahnavi
Senior Yellow Belt

Please log in to comment
0
A thousand apologies...once again, I've failed to read and inwardly digest.

I don't know why that would occur, to be honest. If it were me and I needed a quick turn-around, I'd simply use a GUID-generator EXE or script and paste the new GUID into the 'Summary' table directly.
Answered 03/13/2008 by: VBScab
Red Belt

Please log in to comment
0
I tried this but still the application is not getting upgraded.
Answered 03/13/2008 by: Jahnavi
Senior Yellow Belt

Please log in to comment
0
Hi,
I too face this same issue.. i tried all the following options but still no success..
1. The package code even if changed, by changing the value in the summary table, will get reverted back once it is closed and reopened. also even if manually changed and then you try an installation, still it takes the earlier package code. In brief, the package code of an mst could not be changed as it is dependent on the msi 4 this..
2. The package code could not be changed in the MSI, as on saving it may give you a lot of other errors(cannot compress files...). Also you are not allowed make changes in a vendor MSI.
3. I tried to install the package by changing the product code and passing the command line property "REINSTALLMODE = vomus" (To override the cache memory), by which i was able to actually install but ended up with uninstallation errors and also in ADD OR REMOVE PROGRAMS, I can actuallly see both the versions being displayed(though only the current version is being installed).
So is there any other way to actually clean up the cache memory of the target machine before installing the package bcoz i guess tat wud actually help both of us in removing all these difficulties...
thanks in advance..
Answered 03/13/2008 by: rayz_0020
Senior Purple Belt

Please log in to comment
0
Hi,


I resolved my issue by changing the package code in the msi. But, i am facing a new problem.here is the description:

I am installing older version(let it be app1.0) and then up on it newer one(let ir be app 2.0).
It is getting upgraded and the application is working properly in both admin and test user accounts.
But, I can see the application displayed in add/remove programs only when logged in as admin user.
when i logged in as test user it is not displayed.

When i installed only my current version i can see that it is displayed both in admin and test user.
the problem comes when i upgraded the application

The application i am working is webex meeting manager 7.0.4

Itried the following solutions:

I went to HKLM/SOFTWARE/Microsoft/windows/currentversion/uninstall and checked for display name and it is present
I didn't found any ARPSYSTEMCOMPONENT in my application

Can any one tell me why this is happening.....i am sure many might have already faced this issue....kindly help me

Thanks in advance.
Answered 03/16/2008 by: Jahnavi
Senior Yellow Belt

Please log in to comment
0
It sounds like you guys are probably doing a "save as" in Wise and maybe that's why you're generating packages with the same package codes. Just a thought.

I think your most recent problem might be due to a user-based installation (not setting the ALLUSERS property)
Answered 03/17/2008 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
ORIGINAL: Jahnavi
I resolved my issue by changing the package code in the msi. But, i am facing a new problem.here is the description:
If you did that to a vendor's MSI, you will have exactly the same problem at the next upgrade or patch. Good luck.
Answered 03/18/2008 by: VBScab
Red Belt

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