We are using a third party component to interface between QuickBooks and Laserfiche, and WorkFlow pulls data out and populate client files. There is an issue where the entire process hangs and the only way to temporarily fix it is to reboot the Laserfiche Server. After looking into the event viewer on the server, I see only this SideBySide error with the following details: Show "Activation context generation failed for "c:\program files (x86)\common files\laserfiche\Server\Setup.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9200.16384_none_418c2a697189c07f.manifest. Component 2: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9200.16384_none_893961408605e985.manifest." I can't seem to find anything on this issue. There are a few that have seen the SideBySide error, but for other applications, and the fixes they had (or didn't have, as some trails just ended with generic resolutions so I don't know what really fixed it for them) are irrelevant to this issue. One of the fixes was the end-user had reinstalled his computer's OS, and that fixed it for him, which is just not possible on this server. Looking into it from a Microsoft side, it seemed to be program related more than Operating System related. This topic describes the . Manifest file errors do not have an associated error code. The validation results manifests are not created when a terminal manifest file error occurs. For more information, see Understanding the manifest summary. Terminal manifest errors prevent the reporting of Non-Terminal JSON Line Validation Errors. The manifest file extension or contents are invalid.The training or testing manifest file doesn't have a file extension or its contents are invalid. To fix error The manifest file extension or contents are invalid.
The manifest file is empty.The training or testing manifest file used for training exists, but it is empty. The manifest file needs a JSON Line for each image that you use for training and testing. The manifest file size exceeds the maximum supported size.The training or testing manifest file size (in bytes) is too large. For more information, see Guidelines and quotas in Amazon Rekognition Custom Labels. A manifest file can have less than the maximum number of JSON Lines and still exceed the maximum file size. You can't use the Amazon Rekognition Custom Labels console to fix error The manifest file size exceeds the maximum supported size. To fix error The manifest file size exceeds the maximum supported size.
The S3 bucket permissions are incorrect.Amazon Rekognition Custom Labels doesn't have permissions to one or more of the buckets containing the training and testing manifest files. You can't use the Amazon Rekognition Custom Labels console to fix this error. Unable to write to output S3 bucket.The service is unable to generate the training output files. To fix error Unable to write to output S3 bucket. Check that the Amazon S3 bucket information in the OutputConfig input parameter to CreateProjectVersion is correct. FYI: I was unsure how many techies, or Zoom employees visit and view this forum for techical errors, so I decided to persevere and find how to raise a support ticket. It took a bit of navigating, but I finally found the link: Hopefully this will help someone: From this support article: https://support.zoom.us/hc/en-us/articles/201362003-Zoom-technical-support See the link titled Web Ticket Request: https://support.zoom.us/hc/en-us/requests/new It seems that some technical issues can be resolved by downloading the "Cleanzoom.zip" file, unzipping and running the executable Cleanzoom.exe. Reboot, and then download the latest Zoom Meeting version. The cleanzoom.zip can be downloded here: https://support.zoom.us/hc/en-us/article_attachments/360084068792/CleanZoom.zip It seems possible from my reviewing the Windows Event 78 Log data, that some older updates (in-place upgrades or updater routines) where not cleaning up old (unused/unwanted) 32-bit code, so both X86 (32-bit) and amd64 (64-bit) routines were called incorrectly during startup, causing conflicts. The Cleanzoom.exe program semed to fix this up OK. |
