1512 installed on Vista

Viewing 10 posts - 1 through 10 (of 11 total)
  • Author
    Posts
  • #1210
    dscycler
    Participant

    Vista put up a dialog at the end of the install indicating that the install did not complete properly. I’ve seen this with other program and in the end they work fine so I decided to ignore the warning and accept the install. However there appear to be major issues. Event Application log details below…….

    Activation context generation failed for “E:Program FilesFirefly Media Serverpluginsout-daap.dll”. Dependent Assembly Microsoft.VC80.CRT,processorArchitecture=”x86″,publicKeyToken=”1fc8b3b9a1e18e3b”,type=”win32″,version=”8.0.50727.762″ could not be found. Please use sxstrace.exe for detailed diagnosis.

    Activation context generation failed for “E:Program FilesFirefly Media Serverpluginsrsp.dll”. Dependent Assembly Microsoft.VC80.CRT,processorArchitecture=”x86″,publicKeyToken=”1fc8b3b9a1e18e3b”,type=”win32″,version=”8.0.50727.762″ could not be found. Please use sxstrace.exe for detailed diagnosis.

    Activation context generation failed for “E:Program FilesFirefly Media ServerFireflyShell.exe”. Dependent Assembly Microsoft.VC80.CRT,processorArchitecture=”x86″,publicKeyToken=”1fc8b3b9a1e18e3b”,type=”win32″,version=”8.0.50727.762″ could not be found. Please use sxstrace.exe for detailed diagnosis.

    Activation context generation failed for “E:Program FilesFirefly Media ServerFireflyShell.exe”. Dependent Assembly Microsoft.VC80.CRT,processorArchitecture=”x86″,publicKeyToken=”1fc8b3b9a1e18e3b”,type=”win32″,version=”8.0.50727.762″ could not be found. Please use sxstrace.exe for detailed diagnosis.

    There are 4 unsuccesful attempts to start FireflyShell.exe. The Firefly Media Server service and Bonjour service appear to be running. But Firefly is not visible from my M1000.

    Let me know what I can do.

    Thanks…….
    David

    #9688
    rpedde
    Participant

    @dscycler wrote:

    Vista put up a dialog at the end of the install indicating that the install did not complete properly. I’ve seen this with other program and in the end they work fine so I decided to ignore the warning and accept the install. However there appear to be major issues. Event Application log details below…….

    That’s a manifest problem. I noticed it didn’t bind the manifest to the installer, so I knew that would happen. I’ll try and find out what its issue is.

    Activation context generation failed for “E:Program FilesFirefly Media Serverpluginsout-daap.dll”. Dependent Assembly Microsoft.VC80.CRT,processorArchitecture=”x86″,publicKeyToken=”1fc8b3b9a1e18e3b”,type=”win32″,version=”8.0.50727.762″ could not be found. Please use sxstrace.exe for detailed diagnosis.

    Did it drop a msvcp80.dll and a msvcr80.dll in your program directory?

    #9689
    dscycler
    Participant

    Hi Ron,

    They are both in E:Program FilesFirefly Media Server.

    David

    #9690
    dscycler
    Participant

    By the way, after the “upgrade” install I completely uninstalled. The uninstall appeared to work. However the 2nd “fresh” install produced the same result as the upgrade.

    The uninstall totally removed the config file as well.

    David

    #9691
    rpedde
    Participant

    @dscycler wrote:

    By the way, after the “upgrade” install I completely uninstalled. The uninstall appeared to work. However the 2nd “fresh” install produced the same result as the upgrade.

    The uninstall totally removed the config file as well.

    David

    1514 is building now. Should be out of the toaster in 45 minutes or so. Can you check that when its done?

    #9692
    dscycler
    Participant

    It is there, but only 72.6 Kb. Vista reports that the installer is damaged.

    Can you check it?

    #9693
    dscycler
    Participant

    I assume you are working on a new Windows installer. This am you put up everything but Windows. Just checking and no real rush. Folks are still downloading the one that doesn’t appear to work.

    #9694
    rpedde
    Participant

    @dscycler wrote:

    I assume you are working on a new Windows installer. This am you put up everything but Windows. Just checking and no real rush. Folks are still downloading the one that doesn’t appear to work.

    Yup, I messed with it and it looks like the version of nsis I was using didn’t get along with the manifest embedder program.

    Got another one and it’s building as we speak…

    — Ron

    #9695
    dscycler
    Participant

    Well there are still the side by side errors when Firefly starts up.

    +++++
    Activation context generation failed for “E:Program FilesFirefly Media ServerFireflyShell.exe”.Error in manifest or policy file “E:Program FilesFirefly Media ServerMicrosoft.VC80.CRT.MANIFEST” on line 11. Component identity found in manifest does not match the identity of the component requested. Reference is Microsoft.VC80.CRT,processorArchitecture=”x86″,publicKeyToken=”1fc8b3b9a1e18e3b”,type=”win32″,version=”8.0.50727.762″. Definition is Microsoft.VC80.CRT,processorArchitecture=”x86″,publicKeyToken=”1fc8b3b9a1e18e3b”,type=”win32″,version=”8.0.50608.0″. Please use sxstrace.exe for detailed diagnosis.
    +++++

    The parsed sxstrace.exe output is:
    +++++
    =================
    Begin Activation Context Generation.
    Input Parameter:
    Flags = 0
    ProcessorArchitecture = x86
    CultureFallBacks = en-US;en
    ManifestPath = E:Program FilesFirefly Media ServerFireflyShell.exe
    AssemblyDirectory = E:Program FilesFirefly Media Server
    Application Config File =


    INFO: Parsing Manifest File E:Program FilesFirefly Media ServerFireflyShell.exe.
    INFO: Manifest Definition Identity is (null).
    INFO: Reference: Microsoft.VC80.CRT,processorArchitecture=”x86″,publicKeyToken=”1fc8b3b9a1e18e3b”,type=”win32″,version=”8.0.50727.762″
    INFO: Reference: Microsoft.Windows.Common-Controls,language=”*”,processorArchitecture=”x86″,publicKeyToken=”6595b64144ccf1df”,type=”win32″,version=”6.0.0.0″
    INFO: Resolving reference Microsoft.VC80.CRT,processorArchitecture=”x86″,publicKeyToken=”1fc8b3b9a1e18e3b”,type=”win32″,version=”8.0.50727.762″.
    INFO: Resolving reference for ProcessorArchitecture x86.
    INFO: Resolving reference for culture Neutral.
    INFO: Applying Binding Policy.
    INFO: Find publisher policy at E:WindowsWinSxSmanifestsx86_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.312_none_91939f3c671de810.manifest
    INFO: No binding policy redirect found.
    INFO: Begin assembly probing.
    INFO: Did not find the assembly in WinSxS.
    INFO: Attempt to probe manifest at E:WindowsassemblyGAC_32Microsoft.VC80.CRT8.0.50727.762__1fc8b3b9a1e18e3bMicrosoft.VC80.CRT.DLL.
    INFO: Attempt to probe manifest at E:Program FilesFirefly Media ServerMicrosoft.VC80.CRT.DLL.
    INFO: Attempt to probe manifest at E:Program FilesFirefly Media ServerMicrosoft.VC80.CRT.MANIFEST.
    INFO: Manifest found at E:Program FilesFirefly Media ServerMicrosoft.VC80.CRT.MANIFEST.
    INFO: End assembly probing.
    INFO: Resolving reference Microsoft.VC80.CRT.mui,language=”*”,processorArchitecture=”x86″,publicKeyToken=”1fc8b3b9a1e18e3b”,type=”win32″,version=”8.0.50727.762″.
    INFO: Resolving reference for ProcessorArchitecture x86.
    INFO: Resolving reference for culture en-US.
    INFO: Applying Binding Policy.
    INFO: No publisher policy found.
    INFO: No binding policy redirect found.
    INFO: Begin assembly probing.
    INFO: Did not find the assembly in WinSxS.
    INFO: Attempt to probe manifest at E:WindowsassemblyGAC_32Microsoft.VC80.CRT.mui8.0.50727.762_en-US_1fc8b3b9a1e18e3bMicrosoft.VC80.CRT.mui.DLL.
    INFO: Did not find manifest for culture en-US.
    INFO: End assembly probing.
    INFO: Resolving reference for culture en.
    INFO: Applying Binding Policy.
    INFO: No publisher policy found.
    INFO: No binding policy redirect found.
    INFO: Begin assembly probing.
    INFO: Did not find the assembly in WinSxS.
    INFO: Attempt to probe manifest at E:WindowsassemblyGAC_32Microsoft.VC80.CRT.mui8.0.50727.762_en_1fc8b3b9a1e18e3bMicrosoft.VC80.CRT.mui.DLL.
    INFO: Did not find manifest for culture en.
    INFO: End assembly probing.
    INFO: Resolving reference Microsoft.Windows.Common-Controls,language=”*”,processorArchitecture=”x86″,publicKeyToken=”6595b64144ccf1df”,type=”win32″,version=”6.0.0.0″.
    INFO: Resolving reference for ProcessorArchitecture x86.
    INFO: Resolving reference for culture en-US.
    INFO: Applying Binding Policy.
    INFO: No publisher policy found.
    INFO: No binding policy redirect found.
    INFO: Begin assembly probing.
    INFO: Did not find the assembly in WinSxS.
    INFO: Attempt to probe manifest at E:WindowsassemblyGAC_32Microsoft.Windows.Common-Controls6.0.0.0_en-US_6595b64144ccf1dfMicrosoft.Windows.Common-Controls.DLL.
    INFO: Did not find manifest for culture en-US.
    INFO: End assembly probing.
    INFO: Resolving reference for culture en.
    INFO: Applying Binding Policy.
    INFO: No publisher policy found.
    INFO: No binding policy redirect found.
    INFO: Begin assembly probing.
    INFO: Did not find the assembly in WinSxS.
    INFO: Attempt to probe manifest at E:WindowsassemblyGAC_32Microsoft.Windows.Common-Controls6.0.0.0_en_6595b64144ccf1dfMicrosoft.Windows.Common-Controls.DLL.
    INFO: Did not find manifest for culture en.
    INFO: End assembly probing.
    INFO: Resolving reference for culture Neutral.
    INFO: Applying Binding Policy.
    INFO: Auto Servicing Policy redirected assembly version.
    INFO: Post policy assembly identity is Microsoft.Windows.Common-Controls,processorArchitecture=”x86″,publicKeyToken=”6595b64144ccf1df”,type=”win32″,version=”6.0.6000.16386″.
    INFO: Begin assembly probing.
    INFO: Attempt to probe manifest at E:WindowsWinSxSmanifestsx86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.6000.16386_none_5d07289e07e1d100.manifest.
    INFO: Manifest found at E:WindowsWinSxSmanifestsx86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.6000.16386_none_5d07289e07e1d100.manifest.
    INFO: End assembly probing.
    INFO: Resolving reference Microsoft.Windows.Common-Controls.mui,language=”*”,processorArchitecture=”x86″,publicKeyToken=”6595b64144ccf1df”,type=”win32″,version=”6.0.6000.16386″.
    INFO: Resolving reference for ProcessorArchitecture x86.
    INFO: Resolving reference for culture en-US.
    INFO: Applying Binding Policy.
    INFO: No publisher policy found.
    INFO: No binding policy redirect found.
    INFO: Begin assembly probing.
    INFO: Did not find the assembly in WinSxS.
    INFO: Attempt to probe manifest at E:WindowsassemblyGAC_32Microsoft.Windows.Common-Controls.mui6.0.6000.16386_en-US_6595b64144ccf1dfMicrosoft.Windows.Common-Controls.mui.DLL.
    INFO: Did not find manifest for culture en-US.
    INFO: End assembly probing.
    INFO: Resolving reference for culture en.
    INFO: Applying Binding Policy.
    INFO: No publisher policy found.
    INFO: No binding policy redirect found.
    INFO: Begin assembly probing.
    INFO: Did not find the assembly in WinSxS.
    INFO: Attempt to probe manifest at E:WindowsassemblyGAC_32Microsoft.Windows.Common-Controls.mui6.0.6000.16386_en_6595b64144ccf1dfMicrosoft.Windows.Common-Controls.mui.DLL.
    INFO: Did not find manifest for culture en.
    INFO: End assembly probing.
    INFO: Parsing Manifest File E:Program FilesFirefly Media ServerMicrosoft.VC80.CRT.MANIFEST.
    INFO: Manifest Definition Identity is Microsoft.VC80.CRT,processorArchitecture=”x86″,publicKeyToken=”1fc8b3b9a1e18e3b”,type=”win32″,version=”8.0.50608.0″.
    ERROR: Component identity found in manifest does not match the identity of the component requested. Reference is Microsoft.VC80.CRT,processorArchitecture=”x86″,publicKeyToken=”1fc8b3b9a1e18e3b”,type=”win32″,version=”8.0.50727.762″. Definition is Microsoft.VC80.CRT,processorArchitecture=”x86″,publicKeyToken=”1fc8b3b9a1e18e3b”,type=”win32″,version=”8.0.50608.0″.
    ERROR: Activation Context generation failed.
    End Activation Context Generation.
    +++++

    Hopefully this will be helpful to you.

    David

    #9696
    rpedde
    Participant

    @dscycler wrote:

    Microsoft.VC80.CRT,processorArchitecture=”x86″,publicKeyToken=”1fc8b3b9a1e18e3b”,type=”win32″,version=”8.0.50608.0″.

    Argh… that’s the wrong manifest. Wonder how that got there. Good thing this new side-by-side activation is so darn easy and convenient.

Viewing 10 posts - 1 through 10 (of 11 total)
  • The forum ‘Nightlies Feedback’ is closed to new topics and replies.