Community Spring Cleaning week is here! Join your fellow Maveryx in digging through your old posts and marking comments on them as solved. Learn more here!

Alteryx Server Discussions

Find answers, ask questions, and share expertise about Alteryx Server.
SOLVED

After Alteryx Server Update good old "Unable to translate alias" but also a strange ...

PhilipX
5 - Atom

Hello, I lost hours troubleshooting whats the issue and I run into some strange behavior after all I have no idea where to look next

 

Alteryx Version
v. 2019.3.6.20285

 

Issue
1. Create a new db connection (SQL) at the server & add my account and my studio for rights. 

2. Use this db connection for output (SQL) Type Gallery.

3. Run workflow local everything works

4. Upload the workflow to the server >> "Unable to translate alias" issue

 

 

Troubleshooting

1. Remove Gallery and re-include

2. Delete GalleryAlias.xml which is described here: https://community.alteryx.com/t5/Alteryx-Server-Knowledge-Base/Troubleshooting-quot-Unable-to-transl...

3. check everything from this post https://community.alteryx.com/t5/Alteryx-Server-Knowledge-Base/Troubleshooting-the-quot-Unable-to-tr...

4. delete and recreate user account nothing changed

 

Curios stuff

1. Old workflows which are deployed before the update are still running >> scheduled and triggered. Downloading the worklfow (change nothing) and redeploy >> "Unable to translate alias"

2. If I put a select into the same workflow which is doing nothing more than a select to the same database everything works

 

Now I'm running out of ideas and every help is welcome?

1 REPLY 1
raychase
11 - Bolide

I ran into the same issue and learned that asset management is broken in this version, specifically for output tools. When uploading your flow, you'll notice the checkbox beside this particular asset is deselected (and unclickable). You can trick the software into packaging the alias by including an input tool (using the same alias) to act as a dummy. This will allow the asset to be included in the package, and your flow will then work properly on server. According to the release notes, this issue has been resolved in newer versions.