Troubleshooting PYQT: Application fails to start because the program is not configured correctly in parallel

Made a small program to generate two-dimensional code: http://www.cnblogs.com/dcb3688/p/4241048.html

Run the script directly no problem, with Pyinstaller packaging and then run the direct error:

The application cannot be started because the program's parallel configuration is incorrect. For more information, see the Application event log, or use the command line Sxstrace.exe tool.

Solutions for Online Search:

1. Install Microsoft Visual C + + Redistributable 2. Start-run (enter services.msc)-OK or enter, open: Service (local), turn on Windows Modules Installer service

First, my computer has been installed VC2008, and VC2005 and VC2010 are installed, exclude!

Second, open the local service, found that Windows Modules Installer is already open, exclude!

So just look for clues in the packed message.

Find the information after packaging analysis found:

119753 info:looking forrun-Time Hooks219754 info:analyzing Rthook C:\Python27\lib\site-packages\pyinstaller-2.1.1.dev0-py2.7. egg\pyinstaller\loader\rthooks\pyi_rth_qt4plugins.py319845 info:analyzing Rthook C:\Python27\lib\site-packages\pyinstaller-2.1.1.dev0-py2.7. egg\pyinstaller\loader\rthooks\pyi_rth_pil_image.py419954 info:analyzing Rthook C:\Python27\lib\site-packages\pyinstaller-2.1.1.dev0-py2.7. egg\pyinstaller\loader\rthooks\pyi_rth_image.py522815info:adding Microsoft.VC90.DebugCRT to dependent assemblies of final executable622894 info:searching forAssembly x86_microsoft.vc90.debugcrt_1fc8b3b9a1e18e3b_9.0.21022. 8_none .722894 warning:assembly notfound822894 error:assembly X86_microsoft.vc90.debugcrt_1fc8b3b9a1e18e3b_9.0.21022.8_none notfound923014 info:searching forAssembly X86_microsoft.vc90.debugcrt_1fc8b3b9a1e18e3b_9.0.21022.8_none ...

Is missing VC90.CRT, but can be found in the system:

1608info:wrote E:\www\pyqt\TEST\qrcode_a.spec2684 info:testing forability to set icons, version resources ...3888INFO: ... resource update available4892 INFO:UPX is  notavailable.5Info:processing Hook hook-OS61273 info:processing Hook hook- Time71279 Info:processing Hook hook-Cpickle81434 Info:processing Hook hook-_sre91914 Info:processing Hook hook-CstringioTen2136 info:processing Hook hook-Encodings One2161 info:processing Hook hook-Codecs A4158info:extending PYTHONPATH with E:\www\pyqt\TEST -4161info:checking Analysis -4161 info:building Analysis because out00-Analysis.toc Non existent the4161 info:running Analysis out00-Analysis.toc -4162info:adding Microsoft.VC90.CRT to dependent assemblies of final executable -11481 info:searching forAssembly x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.21022. 8_none . -11485 Info:found Manifest C:\Windows\WinSxS\Manifests\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.21022. 8_none_bcb86ed6ac711f91.manifest +11508 info:searching forfile Msvcr90.dll -11509 info:found File C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.21022. 8_none_bcb86ed6ac711f91\msvcr90.dll +11510 info:searching forfile Msvcp90.dll A11511 info:found File C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.21022. 8_none_bcb86ed6ac711f91\msvcp90.dll at11513 info:searching forfile Msvcm90.dll -11513 info:found File C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.21022. 8_none_bcb86ed6ac711f91\msvcm90.dll -11827 info:analyzing C:\Python27\lib\site-packages\pyinstaller-2.1.1.dev0-py2.7.egg\PyInstaller\loader\_pyi_ bootstrap.py

Suddenly found that the program is looking for a dependent DLL is not X86_microsoft.vc90.CRT but X86_Microsoft.VC90.DebugCRT, It should be debug debug mode run

Look for it on the Internet, and I haven't found X86_Microsoft.VC90.DebugCRT.dll.

Look at the parameter description in Pyinstaller:

----------------------------------------------------------------------------------------------------------

-F,--onefile PY Code has only one file

-D,--onedir py code in a directory (this is the default)

-K,--TK contains TCL/TK

-D,--debug generate EXE file for debug mode

-W,--windowed,--noconsole form exe file (Windows only)

-C,--nowindowed,--console console exe file (Windows only)

-O DIR,--out=dir set spec file output directory, default in Pyinstaller directory

--icon=<file. ico> Join icon (Windows only)

-V file,--version=file join version information files

----------------------------------------------------------------------------------------------------------

I don't have the-D parameter when I pack it, so I don't know if debug here is Pyinstaller, I try to add the parameter-D, the package message still appears:

1  not found 2  for assembly x86_microsoft.vc90.debugcrt_1fc8b3b9a1e18e3b_9.0.21022.8_none ... 3  not found

Same as with no parameter-D effect!

There is no way to only view the files generated by the Pyinstaller, this is still not found the problem, but saw the solution

There is a. manifest file in the build directory

1 <?XML version= "1.0" encoding= "UTF-8" standalone= "yes"?>2 <Assemblymanifestversion= "1.0"xmlns= "Urn:schemas-microsoft-com:asm.v1">3   <assemblyidentityname= "Qrcode_a"processorarchitecture= "x86"type= "Win32"version= "1.0.0.0"/>4   <Dependency>5     <dependentassembly>6       <assemblyidentityname= "Microsoft.VC90.CRT"processorarchitecture= "x86"PublicKeyToken= "1FC8B3B9A1E18E3B"type= "Win32"version= "9.0.21022.8"/>7     </dependentassembly>8   </Dependency>9   <Dependency>Ten     <dependentassembly> One       <assemblyidentityname= "Microsoft.VC90.DebugCRT"processorarchitecture= "x86"PublicKeyToken= "1FC8B3B9A1E18E3B"type= "Win32"version= "9.0.21022.8"/> A     </dependentassembly> -   </Dependency> -   <Dependency> the     <dependentassembly> -       <assemblyidentitylanguage="*"name= "Microsoft.windows.common-controls"processorarchitecture= "x86"PublicKeyToken= "6595B64144CCF1DF"type= "Win32"version= "6.0.0.0"/> -     </dependentassembly> -   </Dependency> + </Assembly>

Sure enough to see:Microsoft.VC90.DebugCRT

Workaround:

Change Microsoft.VC90.DebugCRT in. manifest files to Microsoft.VC90.CRT

In the packaging run, everything ok!

But why the debug mode, I still did not find the problem.

Troubleshooting PYQT: Application fails to start because the program is not configured correctly in parallel