The AML is invalid or incorrect for 'nameoftask' for the requested operation.

 I am getting this error message "The AML is invalid or incorrect for 'nameoftask' for the requested operation." when importing a task from Automate 9 to Automate 11.

I have successfully imported some tasks. I am unable to import any other tasks after this error appears.

Hello Jaz,

I would suggest you open a case with us by email [email protected]. Please attach the task to your email so that we can begin working on your issue. 

I can open a case. But the task that I am unsuccessfully importing has a one-line message box that says "Test".

Hello,

I am unable to reproduce the issue with a test task, can you attach your task? 

I was able to reproduce this issue.

Automate 11 is installed on a VM server. When I logged out and restarted my session, the automate icon did not come back up on the taskbar.  

Importing any tasks in this state of Automate will show the error that I described above. The fix for me is to reboot the VM server and to make sure that the Automate icon appears in the taskbar. 

Hi Jaz,

The Automate icon, present or not, would not contribute to the issue. It may be a sign that the serivice itself is crashing. Are there any error messages in the Windows application event logs that reference Automate?

I am having issues when I attempt to import .aml files from Automate 6 to Automate 11. The error I'm getting is:

"The AML is invalid or incorrect for <task name> for the requested operation"

Is there a solution for this? I am getting it regardless of which .aml file I try to import, and I need to import 114 task files (one example is attached). I have seen some other posts reference "DatastoreMigrationUtility.exe", but I don't see this as part of my Automate install. 

Lastly, is it best if I email [email protected] with this issue? 

Hi Nathan,

I was able to import your attached task into Automate v11.1. What version of v11 do you have installed? If it's older than v11.1, please update and try to import again. If the issue persists, please contact [email protected] so that we can create a case and further troubleshoot.

This import issue is still happening to me.

I am running:

Automate Premium 11.1.1.1 

Windows Server 2012 R2 standard

Jaz,

Please open a support case through the community portal so that we can schedule a remote session to further troublshoot.

Any resolution on this besides setting up a call with support. I see in this forum that other users are having the same issue.

I was hoping that there's a patch by now. It's unacceptable for me to set up a call with support every time  we have a new install of Automate --- which we have several.

Hi Jaz,

 If you are still having issues with the import of an AML task, would it be possible for you to send us a task you are having issues with to review and test?  If this is possible please send an email over to [email protected] with the task you are having an issue with and a copy of your TaskService.config.xml file found at the folder path below.

C:\ProgramData\AutoMate\AutoMate 11

In the email, also please verify the Operating System of the machine in question and it's bit level, as well as the version and bit level of the AutoMate software.
Note: Please reference this forum thread in your email.