Fatal Error during installation
3 posts
• Page 1 of 1
Fatal Error during installation
I am attempting to install version 16 windows 64 bit classic non-commercial and keep receiving an error message "Fatal error during installation. Installation reported an installer reported an error". This is happening while installing APL IME for 64 bit windows.
Is there a log file that can be examined to determine why this install keeps failing. Tried a clean boot but that made no difference.
Is there a log file that can be examined to determine why this install keeps failing. Tried a clean boot but that made no difference.
+←--------------------------------------------------------------→
+ Jay Moskowitz
+←--------------------------------------------------------------→
+ http://www.linkedin.com/in/jay-moskowitz-5745b83
+
+ Jay Moskowitz
+←--------------------------------------------------------------→
+ http://www.linkedin.com/in/jay-moskowitz-5745b83
+
-
jmosk - Posts: 69
- Joined: Thu Jul 18, 2013 5:15 am
Re: Fatal Error during installation
It is worth looking in Control-Panel -> Programs and Features to see if there is an IME already installed .. and if there is, attempt to uninstall it, and then try to install the IME afresh. If that doesn't work, can you drop support@dyalog.com a note and we'll see what we can do to get this to work.
As it is, the IME is not used when entering APL characters into Classic Dyalog APL; you only need to install it if you want to type APL characters into other applications - which must support IME inputs. Such applications include the Microsoft Office suite of applications, and PuTTY amongst others.
As it is, the IME is not used when entering APL characters into Classic Dyalog APL; you only need to install it if you want to type APL characters into other applications - which must support IME inputs. Such applications include the Microsoft Office suite of applications, and PuTTY amongst others.
-
AndyS|Dyalog - Posts: 263
- Joined: Tue May 12, 2009 6:06 pm
Re: Fatal Error during installation
For everyone who reads this thread who has install problems with Dyalog for Microsoft Windows:
A) When installing, please tick the "Enable installer logging" box.
This will generate an installer log file which will tell us what has gone wrong.
The log will be a text file located in a folder like this “C:\Users\<your name here>\AppData\Local\Temp\” and named something like dyalog_apl-64_170_Non-commercial_20181222_135926.log).
B) There is a known issue 8527. We can get this Fatal Install Error when trying to install our IIS ASP.NET samples.
The answer for this is:
1) temporarily turn on IIS in Control Panel/Programs and Features/Turn Windows features on or off.
2) Add a "Default Web Site" if there isn't one.
3) install Dyalog
4) Then, turn off IIS if you needed to turn it on.
If this does not help, please send the installer log file to Dyalog Support.
Regards,
Vince
p.s. For issue 8527, there will be text like this in the log:
WriteIIS7ConfigChanges: Error 0x8007007e: WriteIIS7ConfigChanges Failed.
MSI (s) (A0:F4) [00:02:01:037]: Closing MSIHANDLE (2342) of type 790536 for thread 9296
CustomAction WriteIIS7ConfigChanges returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
A) When installing, please tick the "Enable installer logging" box.
This will generate an installer log file which will tell us what has gone wrong.
The log will be a text file located in a folder like this “C:\Users\<your name here>\AppData\Local\Temp\” and named something like dyalog_apl-64_170_Non-commercial_20181222_135926.log).
B) There is a known issue 8527. We can get this Fatal Install Error when trying to install our IIS ASP.NET samples.
The answer for this is:
1) temporarily turn on IIS in Control Panel/Programs and Features/Turn Windows features on or off.
2) Add a "Default Web Site" if there isn't one.
3) install Dyalog
4) Then, turn off IIS if you needed to turn it on.
If this does not help, please send the installer log file to Dyalog Support.
Regards,
Vince
p.s. For issue 8527, there will be text like this in the log:
WriteIIS7ConfigChanges: Error 0x8007007e: WriteIIS7ConfigChanges Failed.
MSI (s) (A0:F4) [00:02:01:037]: Closing MSIHANDLE (2342) of type 790536 for thread 9296
CustomAction WriteIIS7ConfigChanges returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
- Vince|Dyalog
- Posts: 439
- Joined: Wed Oct 01, 2008 9:39 am
3 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 0 guests
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group