![]() ![]() INFO: Attempt to probe manifest at C:\Program Files\Quest Software\Vintela Authentication Services\\. ![]() INFO: Attempt to probe manifest at C:\Program Files\Quest Software\Vintela Authentication Services\. INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_64\\7.762_1fc8b3b9a1e18e3b\. INFO: Resolving reference ,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="7.762". INFO: Did not find manifest for culture en. INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_64\\7.1434_en_1fc8b3b9a1e18e3b\.DLL. INFO: Resolving reference for culture en. INFO: Did not find manifest for culture en-US. INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_64\\7.1434_en-US_1fc8b3b9a1e18e3b\.DLL. INFO: Did not find the assembly in WinSxS. INFO: Resolving reference for culture en-US. ![]() INFO: Resolving reference ,language="*",processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="7.1434". INFO: Post policy assembly identity is ,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="7.1434". INFO: Publisher Policy redirected assembly version. INFO: Find publisher policy at C:\Windows\WinSxS\manifests\amd64_policy.8.0._1fc8b3b9a1e18e3b_7.1434_none_09bed9ebface8562.manifest INFO: Resolving reference for culture Neutral. INFO: Resolving reference for ProcessorArchitecture amd64. INFO: Manifest Definition Identity is (null). INFO: Parsing Manifest File C:\Program Files\Quest Software\Vintela Authentication Services\vgp-mmc.dll. ManifestPath = C:\Program Files\Quest Software\Vintela Authentication Services\vgp-mmc.dllĪssemblyDirectory = C:\Program Files\Quest Software\Vintela Authentication Services\ THE FAILED TRACE DURING MSI INSTALLATION: Here are the relevant portions of the sxstrace: The failed installation has the following error: 'ERROR: Cannot resolve reference ,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="7.762".' and also complains: 'INFO: No publisher policy found.'.Īny ideas? I saw one post that said to use the "Windows Installer Self-Registration table (SelfReg)" option instead of the InstallShield Self-registration table. I used sxstrace.exe on Windows Server 2008 圆4 to see what was going on during the MSI installation and during the successful manual registration. The strangest thing is that I can manually self register those components from the command line using regsvr32 after the MSI has failed. I have the VC80.MFC redistributable in my InstallShield project, so I don't know why that should be failing. Those that fail are all dependent on MFC. I saw a post that said to use self register for 64-bit components instead.ĥ of my COM components self register successfully and 3 fail. I have 8 COM components that I'm trying to get to self register from an MSI created in InstallShield 2008 (I had hoped to use COM extraction, but that feature is not supported yet!?!?). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |