This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- version comparison failed
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 28, 2008
10:12 AM
version comparison failed
I'm running IS2008 pure InstallScript. I've just created a new release with a new GUID, and everytime I try and re-install (It is supposed to find the previous install and prompt to uninstall) it gives me the "version comparison failed" error. I read somewhere a while ago that if you change the GUID is should go away and it isn't... Anyone else have this issue?
Thanks
Thanks
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 28, 2008
10:31 AM
Hello retzcat,
Please elaborate it more in depth. Because I am working with Major upgrade write now may be I can help you.
Thanks
Sachin Pawar
Please elaborate it more in depth. Because I am working with Major upgrade write now may be I can help you.
Thanks
Sachin Pawar
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 28, 2008
10:43 AM
Elaborate in what way? I have given the install a new guid under the General Information tab, Product Properties option.
In my Uninstall.rul I have it looking for the previous GUID as well as the new current GUID so that if it is found, it is to uninstall the application.
// Check for previous version of TL2009.01
PerformUnistall("TL2009 (00)",UNINSTALL_PATH+"\\{0AB53C79-C9DF-47E4-B544-52E547C59D01}",
"\""+COMMONFILES^"\\INSTAL~1\\PROFES~1\\RunTime\\0701\\Intel32\\Ctor.dll\",LaunchSetup \""+PROGRAMFILES+"InstallShield Installation Information\\{0AB53C79-C9DF-47E4-B544-52E547C59D01}\\setup.exe\" -uninst",
WINSYSDIR^"rundll32");
// Check for previous version of TL2009
PerformUnistall("TL2009 (00)",UNINSTALL_PATH+"\\{A917A368-72D6-4EA4-9A69-1B026F1EB10B}",
"\""+COMMONFILES^"\\INSTAL~1\\PROFES~1\\RunTime\\0701\\Intel32\\Ctor.dll\",LaunchSetup \""+PROGRAMFILES+"InstallShield Installation Information\\{A917A368-72D6-4EA4-9A69-1B026F1EB10B}\\setup.exe\" -uninst",
WINSYSDIR^"rundll32");
I also have my Product version number as 2009.01.00
In my Uninstall.rul I have it looking for the previous GUID as well as the new current GUID so that if it is found, it is to uninstall the application.
// Check for previous version of TL2009.01
PerformUnistall("TL2009 (00)",UNINSTALL_PATH+"\\{0AB53C79-C9DF-47E4-B544-52E547C59D01}",
"\""+COMMONFILES^"\\INSTAL~1\\PROFES~1\\RunTime\\0701\\Intel32\\Ctor.dll\",LaunchSetup \""+PROGRAMFILES+"InstallShield Installation Information\\{0AB53C79-C9DF-47E4-B544-52E547C59D01}\\setup.exe\" -uninst",
WINSYSDIR^"rundll32");
// Check for previous version of TL2009
PerformUnistall("TL2009 (00)",UNINSTALL_PATH+"\\{A917A368-72D6-4EA4-9A69-1B026F1EB10B}",
"\""+COMMONFILES^"\\INSTAL~1\\PROFES~1\\RunTime\\0701\\Intel32\\Ctor.dll\",LaunchSetup \""+PROGRAMFILES+"InstallShield Installation Information\\{A917A368-72D6-4EA4-9A69-1B026F1EB10B}\\setup.exe\" -uninst",
WINSYSDIR^"rundll32");
I also have my Product version number as 2009.01.00
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 28, 2008
11:05 AM
I've got it.. I had the version number as 2009.01.00 and it needs to be 09.01.00... Why can't it be a larger number?????
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 29, 2008
12:26 AM
Hello,
The version number must contain only numbers, and it must be in the format aaa.bbb.ccccc, where aaa represents the major version number, bbb represents the minor version number, and ccccc represents the build number. The maximum value for the aaa and bbb portions is 255. The maximum value for ccccc is 65,535.
Remember you can have product version like 255.255.65535.1.9 also, but installer only considers the major.minor.build numbers out of it.
Thanks
Sachin Pawar
The version number must contain only numbers, and it must be in the format aaa.bbb.ccccc, where aaa represents the major version number, bbb represents the minor version number, and ccccc represents the build number. The maximum value for the aaa and bbb portions is 255. The maximum value for ccccc is 65,535.
Remember you can have product version like 255.255.65535.1.9 also, but installer only considers the major.minor.build numbers out of it.
Thanks
Sachin Pawar