Does anybody know why Wise freezes when installing in windows 2003 server. What happens is: i double click on the installation package from the server. my app is a web app so in the package there are settings for IIS...anyway, when i double click on the package the welcome screen comes up to start installing, the only thing is that the "Next" button is not there, only the "Cancel" button. Wise admitted this is a defect(read quotes below) but what I don't understand is what am I supposed to do. It says in their "workaround" that if i need to check certain IIS features, I'll have to use a system search and set a launch condition......I have no clue what I'm supposed to do to make the installation work with Windows 2003 server. I create .net applications so there are settings for IIS that I need to set. Does anybody know what exactly i'm supposed to do? (wise works fine in w2k server)
thanks,
Ivonne
"Thank you for submitting the product defect report regarding the installation of your .MSI crashing when executed on Windows 2003 server.
We recently determined that the problem is with the
GetIISFeaturesEnabled custom action found in the User Interface and
Execute Immediate sequence. This custom action performs several checks
to determine if certain functionality exists on the server.
Unfortunately, there is also a bug that renders execution of VB scripts
impossible (our dialogs changes are executed using VB script).
If you do not need to check for a certain IIS feature, I recommend
deleting the GetIISFeaturesEnabled action and proceeding. If you do need
to check for certain IIS features, then you will need to use a System
Search and set a Launch Condition based on the results of that search.
Please see Wise Solutions Knowledgebase article 1433 entitled "Creating
Launch Conditions Based on a System Search"
(
The tracking number for the defect is 31270.
I apologize for the inconvenience.
Best regards,
DANIELLE DESROSIERS
Technical Support Issues Analyst
Wise Solutions Inc.
"
thanks,
Ivonne
"Thank you for submitting the product defect report regarding the installation of your .MSI crashing when executed on Windows 2003 server.
We recently determined that the problem is with the
GetIISFeaturesEnabled custom action found in the User Interface and
Execute Immediate sequence. This custom action performs several checks
to determine if certain functionality exists on the server.
Unfortunately, there is also a bug that renders execution of VB scripts
impossible (our dialogs changes are executed using VB script).
If you do not need to check for a certain IIS feature, I recommend
deleting the GetIISFeaturesEnabled action and proceeding. If you do need
to check for certain IIS features, then you will need to use a System
Search and set a Launch Condition based on the results of that search.
Please see Wise Solutions Knowledgebase article 1433 entitled "Creating
Launch Conditions Based on a System Search"
(
The tracking number for the defect is 31270.
I apologize for the inconvenience.
Best regards,
DANIELLE DESROSIERS
Technical Support Issues Analyst
Wise Solutions Inc.
"