When attempting to export a template object or the entire galaxy to a .aaPKG file, Archestra quickly reports that the export is complete. However, the "Export Automation Object" dialog box remains empty and a 0kb .aaPKG file is created. This issue is occurring while using Wonderware 10.1 and Application Server 3.1 SP3 on Windows Server 2008 R2. Typically, I backup the template by exporting it to a .aaPKG file before and after making any development changes to the application. However, after a few days of development, I am unable to export the latest version of the application. While I can still check the template in and out and make changes, I am encountering difficulties with the export process. Additionally, the Platform Manager indicates that my GR Node is showing "Shutdown (startup failed)." I am considering reinstalling the entire package, but this would result in losing days of work without a successful .aaPKG export. Has anyone else faced a similar issue before? Any assistance would be greatly appreciated.
When attempting to start the platform, the SMC Logs reveal various errors and warnings related to missing mappings and failed component creations. The machine in question does not have a mapped Z:\ drive, leading to errors like CoCreateInstance failures and unspecified HRESULTs. Additionally, runtime components are not registered, resulting in multiple invariant failures during system startup. These errors point to issues with the engine automation object and design server component, leading to unexpected exceptions and a failed operation. The process ultimately exits with error code 8000ffff. The logs indicate a need for troubleshooting and resolution of these issues to ensure smooth operation of the platform.
I am encountering a similar issue. Can anyone provide a solution or fix for this problem?
For those wondering, the issue persists in System Platform 2020 even after more than a decade.
It sounds like you're experiencing quite the conundrum. From my experience, the issue you're facing may be due to a corrupt object in your galaxy. Since you're able to check in and out templates, it suggests the issue isn't with the entire galaxy but with a specific object within it. I suggest you attempt to export smaller groups of templates or individual templates to isolate the problem. As for the GR Node showing "Shutdown (startup failed)", this could be indicative of connection or configuration issues. Double-check your nodes, communication settings, and link parameters. A complete reinstallation should be last resort, as you'd lose your progress. Hopefully this helps!
This sounds like a bit of a tricky issue you're facing there. However, before you go ahead and reinstall the whole package, there might be a couple of things you could try. First, check the system platform log files for any errors or warnings pertaining to the export function. Sometimes, you can spot an anomaly there that could help in isolating the problem. Second, ensure that you're not exceeding the set memory limitations of the software, as this could prevent successful exports. Lastly, give the restart function a whirl one more time. Sometimes a correct shutdown and restart can iron out the kinks in the system.
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: - This issue could be related to a potential glitch or error within the export process, possibly caused by compatibility issues or system configurations. It may require troubleshooting or investigating further to identify the root cause.
Answer: - Troubleshooting steps could include checking for any errors or warnings in the Platform Manager, verifying system requirements, ensuring proper permissions, and potentially seeking support from Wonderware or the software community for assistance.
Answer: - The "Shutdown (startup failed)" status for the GR Node could indicate a problem with the node's startup process. It may be necessary to investigate the cause of the startup failure, check system logs, and potentially restart or troubleshoot the GR Node to resolve the issue.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.