Is there any reason why the NA 2008.1 SDK won't install on a Vista machine? I get an error, "Installer has shut down".
I tried custom and got the same results. Do you change any of the custom settings?
Some here,
"Installation ended prematurely because of an error."
Thank you that was helpful. In this modern day and age that is all I get. Do I go back to the prior version I just uninstalled?
Don't forget you are writing a program for programmers you could give a little bit more info as to what the error was or where to get more info.
Who knows maybe we can help you help us but that is all we get. I bet that helps you all as much as it helps me.
Event Log:
Windows Installer installed the product. Product Name: Infragistics NetAdvantage for .NET 2008 Vol. 1 CLR 2.0. Product Version: 8.1. Product Language: 1033. Installation success or error status: 1603.
I an install with logging turned on NetAdvantage_NET_20081_CLR20_Product -l* log.txt
I think I know what the issue is. This might be related to someone who picked options and chose not to install asp.net stuff. Going to try some things. I hope this info helps someone to maybe help us.
This is Vista with SP1 BTW.
Action 18:47:16: callsslcra. Action 18:47:19: WiseVirtDirCallDll. WiseWeb: Action CreateWebSitesAndVDirs starting...WiseWeb: All website creation completeWiseWeb: Creating virtual directory/web directory (ig_common)Action 18:47:19: CreateVDir. Creating Virtual DirectoryCreateVDir: ig_commonWiseWeb: Failed to create/update virtual directory correctlyWiseWeb: Creating virtual directory/web directory (ig_common/20081CLR20)Action 18:47:19: CreateVDir. Creating Virtual DirectoryCreateVDir: ig_common/20081CLR20WiseWeb: Failed to create/update virtual directory correctlyWiseWeb: Creating virtual directory/web directory (ig_common/20081CLR20/Forms)Action 18:47:19: CreateVDir. Creating Virtual DirectoryCreateVDir: ig_common/20081CLR20/FormsWiseWeb: Failed to create/update virtual directory correctlyWiseWeb: Creating virtual directory/web directory (ig_common/20081CLR20/Forms/WebSchedule)Action 18:47:19: CreateVDir. Creating Virtual DirectoryCreateVDir: ig_common/20081CLR20/Forms/WebScheduleWiseWeb: Failed to create/update virtual directory correctlyWiseWeb: All virtual directory/web directory creation completeWiseWeb: Memory clean-up completeWiseWeb: CreateWebSitesAndVDirs action endingAction ended 18:47:19: InstallFinalize. Return value 3.Action 18:47:19: Rollback. Rolling back action:Rollback: WiseVirtDirCallDllRollback: callsslcraRollback: Writing system registry values...Rollback: Creating shortcuts...Rollback: Creating duplicate files...Rollback: Copying new files...Rollback: Creating folders...Rollback: Removing ODBC components...Rollback: Updating component registration...Action ended 18:47:40: INSTALL. Return value 3.
.
Action ended 18:47:41: ExecuteAction. Return value 3.Action 18:47:41: Fatal_Error. Action start 18:47:41: Fatal_Error.Action 18:47:41: Fatal_Error. Dialog createdAction 18:47:44: WiseCleanup. Action start 18:47:44: WiseCleanup.Action ended 18:47:44: WiseCleanup. Return value 1.Action ended 18:47:44: Fatal_Error. Return value 2.Action ended 18:47:44: INSTALL. Return value 3.
Same here... thanks for the info
I installed the IIS 6 Management and that fixed the problem for me. Although it would have been nice for the error message to state this. I think it would save people quite a bit of time.
Daniel
At my Vista 64 bit system it is the Service Pack 1 for Vista. If I install it two needed services for the IIS (WAS and another one) can't be started. And therefore I deinstalled the SP1 and I could install the NA SDK.But still there seems no solution for this problem and I am still working without the SP1. Sighing greetingsReiner
I just ran into a need for ASP.NET and needed to install it.
I installed the IIS 6 Management and that fixed the problem.
It seems that the problem is SP1 on Vista because the services WAS and W3SVC won't start. But I did not find a solution until now. EDIT: Now I deinstalled the whole IIS 7 with the result that it is impossible to reinstall IIS at all.