This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
User is attempting to connect to Hadoop Hive with Active Directory Kerberos (Kerberos SSPI) in Alteryx and getting an error: Failed to get username: Routine Error: Unspecified GSS failure. Minor code may provide more information.
The test button in the ODBC DSN is successful.
A workflow that includes a Python tool may throw an error of the form "Error: unable to read data (C:\AppData\Alteryx\Engine\Engine_23200_be6a9480b4fc4e038a8668b82debdf74_\aa37b5ac-6323-472b-8f0f-5cb0b95b822e\4460abb7be83bae8f01b9bf1238a923c.yxdb)"
In some cases a customer using the Publish to Tableau Server macro encounters the error message "Failed to start a new Hyper instance". The only currently working solution for this is to perform a nuclear uninstall and then reinstall of Alteryx Designer.
This error is usually caused by two things: The file you selected is of a differentformat than what is selected in the File Format drop down in the Configuration window. A .yxdb file you are using as an input has become corrupt. Other causes can be found here:https://community.alteryx.com/t5/Alteryx-Knowledge-Base/Error-FileID-does-not-match-in-the-FileHeader/ta-p/19870 Although extremely rare, if a .yxdb file becoming corrupt is the culprit (one cause is a network connection dropping in the middle of writing the file), you may have a quick and simple way to resolve this potentially stomach-dropping issue: Open up Windows Explorer and navigate to the file. Right-click on the file and choose Properties. Click on the Previous Versions tab. If you're lucky, there isat least one option of the file that you can revert back to you, hopefully allowing you to avert disaster. Obviously, this doesn't just work with Alteryx files, so perhaps this knowledge will come in handy with other files. Thanks for reading!