Deploy Manifest defect?

This forum can be browsed by the general public. Posting is limited to current SAPIEN license holders with active maintenance and does not offer a response time guarantee.
Forum rules
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.

Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
This topic is 7 years and 11 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.
User avatar
Alexander Riedel
Posts: 8479
Last visit: Thu Mar 28, 2024 9:29 am
Answers: 19
Been upvoted: 37 times

Re: Deploy Manifest defect?

Post 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 :D

P.S. The error you see is PowerShell initializing a provider and failing. You need to take that up with Microsoft.
Alexander Riedel
SAPIEN Technologies, Inc.
User avatar
monoeagle
Posts: 108
Last visit: Fri Jan 26, 2024 10:44 am

Re: Deploy Manifest defect?

Post by monoeagle »

uploaded the visit_final.exe as zip with default embedded manifest. This file crashed on my testmachine.
User avatar
Alexander Riedel
Posts: 8479
Last visit: Thu Mar 28, 2024 9:29 am
Answers: 19
Been upvoted: 37 times

Re: Deploy Manifest defect?

Post 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.
Alexander Riedel
SAPIEN Technologies, Inc.
User avatar
monoeagle
Posts: 108
Last visit: Fri Jan 26, 2024 10:44 am

Re: Deploy Manifest defect?

Post 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.
User avatar
Alexander Riedel
Posts: 8479
Last visit: Thu Mar 28, 2024 9:29 am
Answers: 19
Been upvoted: 37 times

Re: Deploy Manifest defect?

Post 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.
  1. <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
  2. - <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
  3.   <assemblyIdentity processorArchitecture="*" version="1.0.0.1" type="win32" name="ViSiT_Final.exe.intermediate" />
  4.   <description>ViSiT_Final</description>
  5. - <dependency>
  6. - <dependentAssembly>
  7.   <assemblyIdentity type="win32" name="Microsoft.Windows.Common-Controls" version="6.0.0.0" publicKeyToken="6595b64144ccf1df" language="*" processorArchitecture="*" />
  8.   </dependentAssembly>
  9.   </dependency>
  10. - <trustInfo xmlns="urn:schemas-microsoft-com:asm.v2">
  11. - <security>
  12. - <requestedPrivileges>
  13.   <requestedExecutionLevel level="asInvoker" uiAccess="false" />
  14.   </requestedPrivileges>
  15.   </security>
  16.   </trustInfo>
  17. - <compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1">
  18. - <application>
  19. - <!--  Windows 8.1
  20.  -->
  21.   <supportedOS Id="{1f676c76-80e1-4239-95bb-83d0f6d0da78}" />
  22. - <!--  Windows Vista
  23.  -->
  24.   <supportedOS Id="{e2011457-1546-43c5-a5fe-008deee3d3f0}" />
  25. - <!--  Windows 7
  26.  -->
  27.   <supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}" />
  28. - <!--  Windows 8
  29.  -->
  30.   <supportedOS Id="{4a2f28e3-53b9-4441-ba9c-d69d4a4a6e38}" />
  31.   </application>
  32.   </compatibility>
  33.   </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?
Alexander Riedel
SAPIEN Technologies, Inc.
User avatar
monoeagle
Posts: 108
Last visit: Fri Jan 26, 2024 10:44 am

Re: Deploy Manifest defect?

Post 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.
User avatar
monoeagle
Posts: 108
Last visit: Fri Jan 26, 2024 10:44 am

Re: Deploy Manifest defect?

Post 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
This topic is 7 years and 11 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.