I'm trying to crawl a website's data using Import.io desktop app, I'm running this software on a windows server 2008 r2 64bit,32 GB Ram & intel 4770 i7 CPU, But when it's crawling , Suddenly an error appears which asks me to restart the program, The error description contains :
Problem signature:
Problem Event Name: APPCRASH
Application Name: import.io.exe
Application Version: 0.0.0.0
Application Timestamp: 553e7d2c
Fault Module Name: mozalloc.dll
Fault Module Version: 24.0.0.5001
Fault Module Timestamp: 522fa8df
Exception Code: 80000003
Exception Offset: 0000119c
OS Version: 6.1.7601.2.1.0.274.10
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
I've tried to download a new mozalloc.dll and replace the old one with the newer version. Which in this case , Import.io app uses xulrunner version 24, First I've replaced mozalloc.dll version 42 (newest version) with the default import.io's mozalloc.dll file at :
C:\Users\Administrator\AppData\Roaming\import.io\xulrunner-versions\24
But after that , the program interface wasn't showing up. When I opened import.io , it does open in the task manager but windows didn't show up the program's interface.
I've also downloaded the newest xulrunner version and replaced all the files in that folder , Same thing happened again.
I have configured a single node cluster and its is running fine unexpectedly I got the below error and it stopped working. All the hadoop paths are configured in their paths but still I'm getting this error how to come out of this.
/opt/hadoop/hadoop/bin/../libexec/hadoop-config.sh: line 24: /bin/basename: cannot execute binary file
/opt/hadoop/hadoop/bin/../libexec/hadoop-config.sh: line 29: /bin/basename: cannot execute binary file
Warning: $HADOOP_HOME is deprecated.
Error: Could not find or load main class org.apache.hadoop.util.PlatformName
Error: Could not find or load main class org.apache.hadoop.fs.FsShell
I'm building a managed DLL that is bundled in an MSI along with the appropriately signed catalog. MSI installation fails reporting the assembly name, processorArchitecture, etc. Running MSIEXEC with verbose logging, the following is shown:
MSI (s) (64:DC) [14:31:33:754]: Assembly Error:An HRESULT could not be translated to a corresponding Win32 error code.
MSI (s) (64:DC) [14:31:33:785]: Note: 1: 1935 2: {1ADE2A83-E905-4F35-9DD8-61F512CA50E8} 3: 0x800736FD 4: IAssemblyCacheItem 5: Commit 6: BLAHBLAH,version="10.0.62601.0",type="win32",processorArchitecture="x86",publicKeyToken="5f523ae7e6e1b389"
MSI (s) (64:DC) [14:31:33:785]: Assembly Error (sxs): Please look into Component Based Servicing Log located at -207342408ndir\logs\cbs\cbs.log to get more diagnostic information.
MSI (s) (64:DC) [14:31:33:785]: Note: 1: 2205 2: 3: Error
MSI (s) (64:DC) [14:31:33:785]: Note: 1: 2228 2: 3: Error 4: SELECT Message FROM Error WHERE Error = 1935
MSI (c) (7C:1C) [14:31:33:785]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
Error 1935. An error occurred during the installation of assembly 'BLAHBLAH,version="10.0.62601.0",type="win32",processorArchitecture="x86",publicKeyToken="5f523ae7e6e1b389"'. Please refer to Help and Support for more information. HRESULT: 0x800736FD. assembly interface: IAssemblyCacheItem, function: Commit, component: {1ADE2A83-E905-4F35-9DD8-61F512CA50E8}
MSI (s) (64:DC) [14:31:48:019]: Note: 1: 2205 2: 3: Error
MSI (s) (64:DC) [14:31:48:019]: Note: 1: 2228 2: 3: Error 4: SELECT Message FROM Error WHERE Error = 1709
MSI (s) (64:DC) [14:31:48:019]: Product: BLAHBLAH v10.0.62601.0 -- Error 1935. An error occurred during the installation of assembly 'BLAHBLAH,version="10.0.62601.0",type="win32",processorArchitecture="x86",publicKeyToken="5f523ae7e6e1b389"'. Please refer to Help and Support for more information. HRESULT: 0x800736FD. assembly interface: IAssemblyCacheItem, function: Commit, component: {1ADE2A83-E905-4F35-9DD8-61F512CA50E8}
Action ended 14:31:48: InstallFinalize. Return value 3.
Looking at Windows/Logs/CBS.log, I can see:
2014-10-30 14:31:33, Info CSI 0000000c Performing 1 operations; 1 are not lock/unlock and follow:
Install (5): flags: 0 tlc: [BLAHBLAH, Version = 10.0.62601.0, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:5f523ae7e6e1b389}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral]) ref: ( flgs: 00000000 guid: {27dec61e-b43c-4ac8-88db-e209a8242d90} name: [l:0]"" ncdata: [l:62{31}]"C:\Windows\system32\msiexec.exe") thumbprint: [l:128{64}]"c303b9f117203669bdfdbf904a7f1d45e4767da45615a08eff196fb02d093399"
2014-10-30 14:31:33, Error CSI 0000000d#2014/10/30:14:31:33.488 (F) d:\win7sp1_gdr\base\wcp\library\catalog.cpp(263): Error c000038a [Error,Facility=(system),Code=906 (0x038a)] originated in function CCatalog::VerifyCertChainRoot expression: HRESULT_FROM_WIN32((dwError))
[gle=0x80004005]
2014-10-30 14:31:33, Error CSI 0000000e (F) c000038a [Error,Facility=(system),Code=906 (0x038a)] #1131# from CCSDirectTransaction::OperateEnding at index 0 of 1 operations, disposition 0[gle=0xd000038a]
2014-10-30 14:31:33, Error CSI 0000000f (F) 80090352 [Error,Facility=(0009),Code=850 (0x0352)] #1001# from Windows::COM::CComponentStore::InternalTransact(...)[gle=0x80090352]
2014-10-30 14:31:33, Error SXS Transact2 failed with 0x80090352
I've seen numerous report stating that HRESULT 0x800736FD is an internal error and suggests running the Windows System Update Readiness tool. I've done this but it's no different.
There's a report here of someone experiencing the same problem but no response:
https://social.msdn.microsoft.com/forums/windowsdesktop/en-us/5938da72-16a4-46ef-9151-986b4bd6a60b/need-help-in-installing-dll-into-winsxs
I don't think there's anything wrong with the managed DLL since I can manually install it into the GAC using gacutil.
This is driving me bonkers.
Okay, so after LOTS of trial and error, I eventually found the problem.
My MSI is actually 4 merge modules - an unmanaged C++ DLL that needs to be installed in WinSxS, the corresponding VS2005 run-times (don't ask) and a managed C++ wrapper that needs to be installed in the GAC.
One of the merge modules (the managed C++ wrapper) had the same name as the main MSI so when the error message was reported, I thought (naively) that this was the errant module. Of course, the error message is a bit indiscriminate - it was actually the unmanaged C++ DLL (with a different name) that was failing.
The cause of the failure was extremely trivial - the public key token referenced in the manifest for the DLL was wrong. I had mistakenly put the public key token of the Strong Name Key used for the Managed C++ DLL in there rather than the public key token of the Code Signing Certificate.
Sad to say it was a Schoolboy error although, I'm hardly a Schoolboy.
What's annoying is that the error is quite clearly something that could be reported in a much more sensible manner by the installer tool.
So, if you read this and it saves you lots of time, I'm glad. Alas for me, I've lost days of my life that I can never get back.
WinSxS, GAC, assemblies, manifests, yada, yada, yada. It all seems way, way too complicated and fragile to me. Someone, somewhere is having a right good laugh.
I've had nothing but problem with third party merge modules, especially the ones you speak of. Generally it's best to refactor and create a setup.exe bootstrapper/chainer to handle installing those as discrete prerequites. That way they are already there when your MSI installs and not connected to your MSI in anyway.
I created an MSI installer with WiX 3.8 and I get this error in the MSI log when installing it:
InstallFiles: File: Copying new files, Directory: , Size:
Note: 1: 2205 2: 3: Patch
Note: 1: 2228 2: 3: Patch 4: SELECT `Patch`.`File_`, `Patch`.`Header`, `Patch`.`Attributes`, `Patch`.`Sequence`, `Patch`.`StreamRef_` FROM `Patch` WHERE `Patch`.`File_` = ? AND `Patch`.`#_MsiActive`=? ORDER BY `Patch`.`Sequence`
Note: 1: 2205 2: 3: Error
Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1302
Note: 1: 2205 2: 3: MsiSFCBypass
Note: 1: 2228 2: 3: MsiSFCBypass 4: SELECT `File_` FROM `MsiSFCBypass` WHERE `File_` = ?
Note: 1: 2205 2: 3: MsiPatchHeaders
Note: 1: 2228 2: 3: MsiPatchHeaders 4: SELECT `Header` FROM `MsiPatchHeaders` WHERE `StreamRef` = ?
Note: 1: 2205 2: 3: PatchPackage
Note: 1: 2205 2: 3: MsiPatchHeaders
Note: 1: 2205 2: 3: PatchPackage
Action ended 19:15:02: InstallFiles. Return value 1.
How can I fix this error?
Or maybe it is a known WiX/MSI issue that can be safely ignored?
My WiX script is extremely simple, it just installs a shell extension, so I have no idea where this error comes from.
From the GUI point of view, the installation finishes with no visible problem. All files are present as expected in the target installation folder.
See http://msdn.microsoft.com/en-us/library/aa372835(v=vs.85).aspx. 1302 is "Please insert disk". If you want to clean up these log messages (which are harmless) you can add an error table to your MSI.
It's not clear that it's an error anyway, although a potential "insert the disk" situation looks worrying. The other stuff is just that it wants to know if there is any patch sequencing going on, and that requires looking in the Patch table. Since there isn't a patch table that's ok, no sequencing is required. It's the same with those others, 2205 and 2228 are both variations on "no table".
Sometimes installing a patch will require the original MSI file if the installed product isn't quite correct. If it required that MSI file then you would have seen that error and been asked to insert the disk, but if you have a custom message in the Error table it wants to know what it is.
Remember this is a debugging log primarily intended for diagnosing issues with an install. The fact that it says "error" doesn't mean that there are any - as you can seem it logs an "error" every time it makes a query on a table in case that table is there and contains extra information.
I am trying to build a Windows Phone app. I am currently getting an error:
Processing Resources with error: Invalid qualifier value.
File: MakePri
and
Invalid qualifier: (null)
File: MakePRI
I was originally using the Multilingual App Toolkit, but I have since disabled it to no effect. When building with verbose output, I see (personal information redacted):
8>Using "GenerateProjectPriFile" task from assembly "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\AppxPackage\Microsoft.Build.AppxPackage.dll".
8>Task "GenerateProjectPriFile"
8> C:\Program Files (x86)\Windows Kits\8.1\\bin\x86\MakePri.exe New -ProjectRoot [Redacted] -ConfigXml obj\Debug\priconfig.xml -OutputFile [Redacted] -ExtensionDll "C:\Program Files (x86)\Windows Phone Kits\8.1\bin\x86\MrmEnvironmentExtDl.dll" -IndexName 14de7fbe-f3e3-43a8-a9df-dddc72828f37 -Verbose -Overwrite
8> Option Verbose specified
8> Option Overwrite specified
8> Index Pass Completed: obj\Debug\layout.resfiles
8> Scale Qualifiers: 240
8>
8> Index Pass Completed: obj\Debug\resources.resfiles
8>
8>MakePri : error 0x80073b0a: Processing Resources with error: Invalid qualifier value.
8>
8>
8>MakePRI : error 0xdef00042: Invalid qualifier: (null)
8> The command exited with code -2147009782.
8>Done executing task "GenerateProjectPriFile" -- FAILED.
The output in Diagnostic mode does not give much more information.
Scaled images are only needed for the phone, so move them all to the "Assets" folder in the phone project, and single copies in the Windows "Assets" folder without qualifiers in their names. It was the only way I got the error messages to go away.
Solution
I had a portable class library that for some reason had the BCL Build Components installed to it when it didn't use them at all. I removed them from the PCL via Nuget and the problem went away.