Page 2 of 2
Re: Deploy Manifest defect?
Posted: Wed Mar 30, 2016 2:52 pm
by Alexander Riedel
Ok, well, I need an exe that actually causes the error you originally reported on your side. If you send me something that also works on your side then I will not see much
P.S. The error you see is PowerShell initializing a provider and failing. You need to take that up with Microsoft.
Re: Deploy Manifest defect?
Posted: Wed Mar 30, 2016 3:02 pm
by monoeagle
uploaded the visit_final.exe as zip with default embedded manifest. This file crashed on my testmachine.
Re: Deploy Manifest defect?
Posted: Wed Mar 30, 2016 3:08 pm
by Alexander Riedel
Works perfectly fine here. Windows 7 Pro 64 Bit
Run a Command prompt with admin rights and run this command:
SxsTrace Trace -logfile:SxsTrace.etl
Now run the programm which causes the SideBySide error.
Go back to the command prompt press ENTER to generate the SxsTrace.etl. Now type this:
sxstrace Parse -logfile:SxSTrace.etl -outfile:SxSTrace.txt
Post the content of the text file here please.
Re: Deploy Manifest defect?
Posted: Thu Mar 31, 2016 1:00 am
by monoeagle
=================
Begin Activation Context Generation.
Input Parameter:
Flags = 0
ProcessorArchitecture = AMD64
CultureFallBacks = en-US;en
ManifestPath = C:\Users\UserSNB\Desktop\ViSiT_Final.exe
AssemblyDirectory = C:\Users\UserSNB\Desktop\
Application Config File =
-----------------
INFO: Parsing Manifest File C:\Users\UserSNB\Desktop\ViSiT_Final.exe.
INFO: Manifest Definition Identity is ViSiT_Final.exe.intermediate,processorArchitecture="*",type="win32",version="1.0.0.1".
INFO: Reference: Microsoft.Windows.Common-Controls,language="*",processorArchitecture="*",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0"
ERROR: Line 12: XML Syntax error.
ERROR: Activation Context generation failed.
End Activation Context Generation.
Re: Deploy Manifest defect?
Posted: Thu Mar 31, 2016 1:27 am
by Alexander Riedel
I have extracted the manifest from the file you sent me with this:
http://weblogs.asp.net/kennykerr/manifest-view-1-0
I see no syntax error in the manifest.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<assemblyIdentity processorArchitecture="*" version="1.0.0.1" type="win32" name="ViSiT_Final.exe.intermediate" />
<description>ViSiT_Final</description>
- <dependency>
- <dependentAssembly>
<assemblyIdentity type="win32" name="Microsoft.Windows.Common-Controls" version="6.0.0.0" publicKeyToken="6595b64144ccf1df" language="*" processorArchitecture="*" />
</dependentAssembly>
</dependency>
- <trustInfo xmlns="urn:schemas-microsoft-com:asm.v2">
- <security>
- <requestedPrivileges>
<requestedExecutionLevel level="asInvoker" uiAccess="false" />
</requestedPrivileges>
</security>
</trustInfo>
- <compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1">
- <application>
- <!-- Windows 8.1
-->
<supportedOS Id="{1f676c76-80e1-4239-95bb-83d0f6d0da78}" />
- <!-- Windows Vista
-->
<supportedOS Id="{e2011457-1546-43c5-a5fe-008deee3d3f0}" />
- <!-- Windows 7
-->
<supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}" />
- <!-- Windows 8
-->
<supportedOS Id="{4a2f28e3-53b9-4441-ba9c-d69d4a4a6e38}" />
</application>
</compatibility>
</assembly>
Do you have another machine to try this? Is this something that only shows this behavior on one machine or on more of computers?
Re: Deploy Manifest defect?
Posted: Thu Mar 31, 2016 1:53 am
by monoeagle
At the moment this behaviour is on one machine. I'll reinstall the Testclient and check this again.
A littlebit confusing is the thing, that nothing has changed on this Client. No network Connection, no Updates, just copy the visit file from the DEV to the Test Client throw a shared DIR and run the visit file.
Re: Deploy Manifest defect?
Posted: Sat Apr 09, 2016 12:09 pm
by monoeagle
Hi Alexander,
now I have found time for setup a new machine and test the issue. With the new machine(win7 pro EN x64), same client like the other clients, clean with PS4 and all Updates. The Problem doesn't occour.
I don't know what the other clients problem is, but we can close the thread. If I can get the error in a reproductive way I'll write a message.
greetz