I just upgraded my Ayanova v3 database to V4 running on SQL Express. The database works perfectly. The system is Vista Business with Service Pack 1. I have downlaoded the AyanovaWBI.msi file - When I double click on it to install I get …
Installation incomplete. Teh installer was interrupted before AyanovaWBI 4.1.5.0 could be installed. You need to restart the installer to try again.
I have rebooted, reset, tried again etc but keep getting the same error?
I ran the .msi file in debug mode and the error appears to indicate that it is NOT compatible with Vist? Here is the log …
=== Logging started: 07/05/2008 23:52:34 ===
Action 23:52:34: INSTALL.
Action start 23:52:34: INSTALL.
Action 23:52:34: DIRCA_CheckFX.
Action start 23:52:34: DIRCA_CheckFX.
Action ended 23:52:34: DIRCA_CheckFX. Return value 1.
Action 23:52:34: AppSearch. Searching for installed applications
Action start 23:52:34: AppSearch.
AppSearch: Property: IISVERSION, Signature: __22EABF4996C44D36AA97873BE05CCB33
Action ended 23:52:34: AppSearch. Return value 1.
Action 23:52:34: FindRelatedProducts. Searching for related applications
Action start 23:52:34: FindRelatedProducts.
Action ended 23:52:34: FindRelatedProducts. Return value 1.
Action 23:52:34: VSDCA_VsdLaunchConditions.
Action start 23:52:34: VSDCA_VsdLaunchConditions.
Action ended 23:52:34: VSDCA_VsdLaunchConditions. Return value 1.
Action 23:52:34: LaunchConditions. Evaluating launch conditions
Action start 23:52:34: LaunchConditions.
Action ended 23:52:34: LaunchConditions. Return value 1.
Action 23:52:34: CCPSearch. Searching for qualifying products
Action start 23:52:34: CCPSearch.
Action ended 23:52:34: CCPSearch. Return value 1.
Action 23:52:34: RMCCPSearch. Searching for qualifying products
Action start 23:52:34: RMCCPSearch.
Action ended 23:52:34: RMCCPSearch. Return value 0.
Action 23:52:34: ValidateProductID.
Action start 23:52:34: ValidateProductID.
Action ended 23:52:34: ValidateProductID. Return value 1.
Action 23:52:34: WEBCA_TARGETVDIR.
Action start 23:52:34: WEBCA_TARGETVDIR.
Action ended 23:52:34: WEBCA_TARGETVDIR. Return value 1.
Action 23:52:34: WEBCA_SetTARGETSITE.
Action start 23:52:34: WEBCA_SetTARGETSITE.
Action ended 23:52:34: WEBCA_SetTARGETSITE. Return value 3.
Action 23:52:34: FatalErrorForm.
Action start 23:52:34: FatalErrorForm.
Info 2898. For VSI_MS_Sans_Serif13.0_0_0 textstyle, the system created a ‘MS Sans Serif’ font, in 0 character set, of 13 pixels height.
Info 2898. For VSI_MS_Sans_Serif16.0_1_0 textstyle, the system created a ‘MS Sans Serif’ font, in 0 character set, of 20 pixels height.
DEBUG: Error 2826: Control BannerBmp on dialog FatalErrorForm extends beyond the boundaries of the dialog to the right by 3 pixels
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2826. The arguments are: FatalErrorForm, BannerBmp, to the right
Info 2898. For VsdDefaultUIFont.524F4245_5254_5341_4C45_534153783400 textstyle, the system created a ‘MS Sans Serif’ font, in 0 character set, of 13 pixels height.
DEBUG: Error 2826: Control Line1 on dialog FatalErrorForm extends beyond the boundaries of the dialog to the right by 3 pixels
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2826. The arguments are: FatalErrorForm, Line1, to the right
DEBUG: Error 2826: Control Line2 on dialog FatalErrorForm extends beyond the boundaries of the dialog to the right by 3 pixels
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2826. The arguments are: FatalErrorForm, Line2, to the right
Action 23:52:34: FatalErrorForm. Dialog created
Action ended 23:52:36: FatalErrorForm. Return value 1.
Action ended 23:52:36: INSTALL. Return value 3.
=== Logging stopped: 07/05/2008 23:52:36 ===
MSI © (48:AC) [23:52:36:309]: Product: AyaNovaWBI 4.1.5.0 – Installation failed.
MSI © (48:AC) [23:52:36:309]: Windows Installer installed the product. Product Name: AyaNovaWBI 4.1.5.0. Product Version: 4.1.5. Product Language: 1033. Installation success or error status: 1603.
Hello
WBI 4.1.5 is installed on many Vista stations, including ours in testing. We have not experienced such an error installing on WBI, nor has any other WBI user contacted us with that error, so Iapologize but I can not give you a definte solution as have not encountered this before.
Here is a possible suggestion to try from a search on Google for the error:
Do post back and identify if that resolved it or not. I also would suggest doing a search online for the different errors (on the screen and in the log, and see if there is something online that may point you in the right direction - do post what you all tried as I will also perform Google search for what you provided and I won’t want to post something that you have already tried
NBo go - A thought though … Is .NET framwork v2 necessary? Vista has v3 by default but not 2?
A step closer - By customizing IIS 7 I was able to get the installer to run but when trying to open the site I get:
HTTP Error 500.22 - Internal Server Error
An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode</H3>
Things you can try:
Migrate the configuration to the system.webServer/modules section. You can do so manually or by using AppCmd from the command line - for example, %SystemRoot%\system32\inetsrv\appcmd migrate config “Default Web Site/”.
Using AppCmd to migrate your application will enable it to work in Integrated mode, and continue to work in Classic mode and on previous versions of IIS.
If you are certain that it is OK to ignore this error, it can be disabled by setting system.webServer/validation@validateIntegratedModeConfiguration to false.
Alternatively, switch the application to a Classic mode application pool - for example, %SystemRoot%\system32\inetsrv\appcmd set app “Default Web Site/” /applicationPool:“Classic .NET AppPool”. Only do this if you are unable to migrate your application.
(Set “Default Web Site” and “Classic .NET AppPool” to your application path and application pool name)
Any Ideas as your documentation does not include an details on configuring IIS 7?
Entered int he command …
c:\Windows\System32\inetsrv>appcmd set app “Default Web Site/AyaNovaWBI” /applicationPool:“Classic .NET AppPool”
Appear to be connecting now so I have posted the results for anyone who encounters these errors with IIS v7 and Vista