Hi everyone,
Recently I have faced issue while opening workflow in dynamics 365 for operations. i did not have .Net version 4.6.2 installed so it was asking for updated versions. So i installed same and found WFs are working pretty fine.
But in other system I am getting below error related to System.Deployment.Application.InvalidDeploymentException (ManifestParse). Please check screenshot for error.
Please tell me what should I do in this case. I have tried to find solution but it is asking for some kind of hot fix that I am unsure.
Thanks in Advance!
Regards,
Smit Patel
Which browser do you use in “other systems”. Didn’t you find any more details in event logs?
PLATFORM VERSION INFO
Windows : 6.1.7601.65536 (Win32NT)
Common Language Runtime : 4.0.30319.42000
System.Deployment.dll : 4.6.1590.0 built by: NETFXREL2
clr.dll : 4.6.1590.0 built by: NETFXREL2
dfdll.dll : 4.6.1590.0 built by: NETFXREL2
dfshim.dll : 4.0.41209.0 (Main.041209-0000)
SOURCES
Deployment url :
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
- Exception reading manifest from https://URL: the manifest may not be valid or the file could not be opened.
- Deployment manifest is not semantically valid.
- Deployment manifest identity contains missing or unsupported processor architecture.
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
OPERATION PROGRESS STATUS
ERROR DETAILS
Following errors were detected during this operation.
- [7/10/2017 2:51:26 PM] System.Deployment.Application.InvalidDeploymentException (ManifestParse)
- Exception reading manifest from https://URL
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.ManifestReader.FromDocument(String localPath, ManifestType manifestType, Uri sourceUri)
at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestDirectBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
— Inner Exception —
System.Deployment.Application.InvalidDeploymentException (ManifestSemanticValidation)
- Deployment manifest is not semantically valid.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSemanticsForDeploymentRole()
at System.Deployment.Application.ManifestReader.FromDocument(String localPath, ManifestType manifestType, Uri sourceUri)
— Inner Exception —
System.Deployment.Application.InvalidDeploymentException (InvalidManifest)
- Deployment manifest identity contains missing or unsupported processor architecture.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSemanticsForDeploymentRole()
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.
i am using Internet explorer in both systems.
The messages says that “Deployment manifest identity contains missing or unsupported processor architecture”. What processor architecture do you have in those systems that don’t work? It’s the same as in the system that works?
Yeah system in which it is working is 64 bit architecture and system in which it is not working is 32 bit architecture…
Bingo! The last step if verifying it in system requirements and indeed, “The Workflow Editor ClickOnce application requires a 64-bit compatible operating system”.
