Miktex NEXT: Build formats broken after update on virgin install
MiKTeX source code moved to GitHub
Brought to you by:
csc
Menu
▾
▴
#2551 Miktex NEXT: Build formats broken after update on virgin install
After encountering some (unrelated) problems, I decided it was time for a fresh install.
I removed the previous version via uninstall, did the obligatory restart Windows is known and famous for and installed MiKTeX 2.9 using the current installer: basic-miktex-2.9.6161-x64 on a Win7 x64 System.
After installing it, I used the Admin Settings to Refresh FNDB and rebuild all formats (via Update Formats). It worked as expected.
I then used the Admin Updater to set my virgin install to MiKTeX NEXT (I do need LuaLaTeX for some of my work) and reran the installer multiple times until there were no more files to update.
[On a side note: Would it be possible to ask automatically if the user would want to restart the update process if there were files left out by the update?]
Then I ran Refresh FNDB and Update Formats again, the later of which failed with the following transcript:
Sorry, but miktex-makefmt did not succeed for the following reason:
miktex-pdftex.exe failed on etex.ini.
The log file hopefully contains the information to get MiKTeX going again:
[user path]/AppData/Local/MiKTeX/2.9/miktex/log/miktex-makefmt.log
You may want to visit the MiKTeX project page, if you need help.
Sorry, but "MiKTeX Configuration Utility" did not succeed.
The log file hopefully contains the information to get MiKTeX going again:
[user path]/AppData/Local/MiKTeX/2.9/miktex/log/initexmf.log
You may want to visit the MiKTeX project page, if you need help.
The revevant part of miktex-makefmt.log:
2016-11-21 15:38:13,919Z INFO makex - Creating the etex format file...
2016-11-21 15:38:13,933Z INFO makex - Running miktex-pdftex.exe...
2016-11-21 15:38:13,978Z FATAL miktex-makefmt - miktex-pdftex.exe failed on etex.ini.
The same for initexmf.log:
2016-11-21 15:38:13,531Z INFO initexmf - starting: MiKTeX Configuration Utility (MiKTeX 2.9.6100 NEXT 64-bit)
2016-11-21 15:38:13,544Z INFO initexmf - Creating language.dat, language.dat.lua and language.def...
2016-11-21 15:38:13,701Z INFO initexmf - starting: MiKTeX Configuration Utility (MiKTeX 2.9.6100 NEXT 64-bit)
2016-11-21 15:38:13,728Z INFO initexmf - running 'miktex-makefmt.exe --engine=pdftex --dest-name=etex --no-dump etex.ini --engine-option=-tcx=cp227.tcx --verbose --admin --enable-installer'
2016-11-21 15:38:13,984Z FATAL initexmf - The executed process did not succeed.
2016-11-21 15:38:13,984Z FATAL initexmf - Info: fileName="C:\MiKTeX 2.9\miktex\bin\x64\miktex-makefmt.exe", arguments="--engine=pdftex --dest-name=etex --no-dump etex.ini --engine-option=-tcx=cp227.tcx --verbose --admin --enable-installer", exitCode="1"
2016-11-21 15:38:13,984Z FATAL initexmf - Source: Libraries\MiKTeX\Core\Process\Process.cpp
2016-11-21 15:38:13,984Z FATAL initexmf - Line: 159
Might this be related to the “November package refactoring”?
Discussion
The behavior is the same BTW whether I insall MiKTeX within Program Files or within an unrelated folder on my system HDD.
Please attach the log files.
These are all MiKTeX log files I've got. Do you need anything else?
Last edit: NWeyand 2016-11-21
This should be fixed with the latest update.
Hmmmm... I'm sorry, but now the updater seems to have completely died. Here is the complete update log so far:
And here is the mpmcli log mentionned in the previous output:
Note that I always ran the updater without selecting/deselecting any packages from the list, so sometimes I had to rerun it multiple times until all packages were installed (or failed to install).
I've attached a screenshot of the exact error message on update failure:
Last edit: NWeyand 2016-11-23
Does this file exist:
If it exists, what happens if you run
in an admin command window?
The file exists (BTW, you have two wrong slashes instead of backslashes in that first line if that makes a difference). and if I let it run via regsvr32, it gives me the following error message:
“The module "[the correct path].dll" failed to load.
Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependent .DLL files.
The specified module could not be found.”
Last edit: NWeyand 2016-11-23
Sorry for the mistake, I was looking in the wrong dir. :D
Any news?
I have the same problem with "regsvr32 MiKTeX209-next-core.dll".
Seems the cause are these missing .DLLs: