community
cancel
Showing results for 
Search instead for 
Did you mean: 

alteryx server Knowledge Base

Definitive answers from Server experts.
This is most likely caused by a licensing error or an issue that can arise from the AlteryxService shutting down unexpectedly .  It can also be due to an incorrect or expired license, or a correct license not being installed with admin rights, or in the case of Runtime-only users (this type of license has been phased out for all but a few legacy clients).
View full article
The beauty of Alteryx is the ability to make repeatable data processes time and time again. But, if that wasn't good enough, we have the ability automate these workflows through scheduling!
View full article
Receiving the error below when attempting to schedule a module?   “An error occurred in the scheduler. Server Error: 500 Server Error GetExpectedValue: Expected “Container” but got “Sid” Incorrect type requested 1 actual 4”   Post v10.5 release, your Alteryx Server and working environment must be of the same version in order to enjoy the upgrades of the release and still be able to commit scheduled workflows correctly. When the versions of your worker and server do not match, you’ll receive the error above. While our recommendation is to be using the most up to date release, you can always upgrade or revert your designer version either at our Downloads page (current version) or the Previous Releases webpage. To check on the version you’re using, you can navigate in the Designer to the Help >> About menu.
View full article
Want to start scheduling workflows? First, you will need to connect to the controller of your server   When connecting your desktop to the Controller, you need two things: the machine name of the server and the controller token.   1. What’s a machine name, you ask? It is also known as the full computer name. On the machine housing Alteryx Server, the machine name can be found here - Control Panel\System and Security\System. Mine looks something like computername.domain.com.     2. The Controller token comes from Alteryx System Settings, also located on the machine that houses the server. It is under Controller>General. Click View, copy and paste the controller token into notepad and save it somewhere safe! *Regenerate only if completely necessary, this will cause issues for existing schedules*     You are now ready to connect to the Controller!   3. Go to Options>View Schedules>Controller dropdown>Connect to Controller   And the final step is copying and pasting the Machine name and Controller token you gathered earlier.     Happy scheduling!    
View full article
This is Part 4 of the Alteryx Gallery Series - The Gallery Series only refers to the Alteryx Server where you can host your Private Alteryx Gallery. This Article with refer to 'Alteryx Gallery' as a privately hosted Gallery on the Alteryx Server.  Part 1 Alteryx Gallery Series - The Lay of the Land 101: Gallery Admin Edition  Part 2 Alteryx Gallery Series - The Lay of the Land 101: User Edition  Part 3 Alteryx Gallery Series: App Publishing & Version Control 101 - Alteryx Community    With the enormous potential of the Alteryx Gallery it is important to utilize all of its power into making better data driven decisions. But, what if you are unsure how to shape the Gallery for your particular use case? This article outlines a few of the potential ways you can do that.   Data Analyst This is a simple way of organizing the Gallery if you have a small groups of Alteryx Content creators who develop end solutions for Business Decision Makers in certain internal departments. You have a few Data Artisans who create, parametrize and upload the Applications (Gallery Admin will need to assign Data Artisan level permissions for these users) They all have private studios to develop in to push content up (Default) They have the ability to create Collections for end users and invite them to join (End users will need to have signed up to the Alteryx Gallery or be in the Domain where the Alteryx Gallery is hosted) The owner of the collection will then have to use the ‘users’ tab inside the collection to add the end user who will then be able to run the reports as a ‘Viewer’ of the Collection.   Departmental (Functional) You have a group of Alteryx creators who make custom applications for particular departments. You would like to share these applications across multiple users within that department. You have a few Data Artisans who create, parametrize and upload the Applications (Gallery Admin will need to assign Data Artisan level permissions for these users) The Gallery Admin has created a Studio (Subscription) for that particular department and given the Alteryx creators Artisan permissions to that studio. As Data Artisans can only belong to one studio at once, the application they build in the Alteryx Designer will now ‘land’ in that departments private studio. (Use this as a development platform). Once the application have been tested, the Gallery Admin can then assign the Data Artisans to a collection whereby they can upload the finished applications. The Gallery Admin can then add the end users to that collection to run the applications as “Viewers”   Departmental (Consumer) You have multiple different departments consuming these applications from one set of Alteryx creators. The end users just want to run the application without knowing any of the Alteryx behind the scenes logistics. As Data Artisans can only publish to one studio (subscription) at a time, it may be useful to have a cross-functional studio to house applications for different departments. The Gallery Admin know can just assign one subscription/studio key to each Data Artisan. The Data Artisan uploads to this one cross-functional studio Once the applications have been uploaded to the Studio they can then be published to the end users in the specific department collections. The users have already been invited to that collection by the Gallery Admin.   Hierarchy (Varied End Users) You have a range of end users requesting detailed reporting The Gallery Admin assigns a cross-functional studio for all Data Artisans. Analysts require a greater range of detail for their UI on their applications. Therefore, the Gallery Admin creates a collection for analysts and invites the Data Artisan to publish the more detailed applications here. Management require more cohesive and precise reporting so these application are hosted in a different collection for these users. All of the end users (analysts & management) are invited as viewers to just run the workflows.   Best,   Jordan Barker Solutions Consultant 
View full article
This is Part 3 of the Alteryx Gallery Series - The Gallery Series only refers to the Alteryx Server where you can host your Private Alteryx Gallery. This Article with refer to 'Alteryx Gallery' as a privately hosted Gallery on the Alteryx Server.  Part 1 Alteryx Gallery Series - The Lay of the Land 101: Gallery Admin Edition  Part 2 Alteryx Gallery Series - The Lay of the Land 101: User Edition  Part 4 Alteryx Gallery Series: How to make the most of your Alteryx Gallery – Use Cases    The main draw of the Alteryx Gallery (other than scheduling) is the ability to create Analytic Applications!  Analytic Applications allow data analysts to parametrize Alteryx Designer workflows, so Business decision makers can interact with a user friendly interface and create custom reports faster on a daily, weekly or monthly basis.   Often these Applications need updating without interrupting end user interaction. Through the version control offered in the Alteryx Gallery, it makes it easier to track application development and prevent disruption for the end user. This article explains the conventions of uploading and apps and version control.   Before reading this article there a few pre-requisites to ensure you can publish apps: Your permission level is set as a Data Artisan in the Alteryx Gallery (You cannot publish up to the Alteryx Gallery without this permission level) The Analytic Application functions successfully from the designer   Publishing an Analytic App From the File Menu, go to Save As “My Company’s Gallery” You can then name the workflow and provide any comments or details specific to version being “saved” Once you click “Save”, Alteryx will publish the workflow and validate that it runs without errors in your gallery environment.   Upload to your Private Studio If you are a Data Artisan in the Alteryx Gallery you will have a Private Studio. If you have not already been added to another Studio, the Private Studio will be your default location when uploading an App from the Alteryx Designer. You can only belong to one Private Studio or Studio at a time.   You want to publish to a Studio (Subscription) The studio you belong to will populate in the ‘Location’ section when uploading to your company’s gallery. If this does not populate with the correct studio name you need to contact the creator of the studio or Gallery Admin. When you File>>Save As>>>Local Gallery from the Alteryx Designer you should see the studio (subscription) you are belong to.   You want to Publish to a Collection To publish to a collection you will need to have Data Artisan Permissions for the whole Gallery. If you are a Data Artisan in the Alteryx Gallery you will have your own private studio but you also have the ability to create collections. Other Artisans in your company’s Gallery can add you to collections they create. When you first upload your app to the Alteryx Gallery it will ‘land’ in your Private Studio (You only get a Private Studio if you are a Data Artisan). From your Private Studio you can click on your app and then there will be a ‘Sharing’ icon. You will then have the option to ‘Add to Collection’       This will then give you an option to select the collections you have access too or the option to create a new collection.     You want to publish to the Public Gallery If you choose to publish to the Public Part of your company’s gallery it will give access to everyone who can access your company’s gallery. Users often upload to the public gallery if they are testing proof of concepts or uploading demo version of Apps. To upload to the public gallery you can upload to your private studio and then choose to share the app in the public gallery.    I want to run this app with certain credentials  Within Alteryx Server 10.5+ there is the ability to manage certain 'Run As' credentials for certain Applications and Workflows ran on the Alteryx Server.  There are few different configurations you can select when setting up the Alteryx Gallery Speak to your Alteryx Server Gallery Admin if you are unsure which setting is available for you   What are the settings? These setting are found on the Gallery Admin page under 'System Settings'   Allow users to set options for credentials when saving a workflow The best practice would be to ask users for their credentials so they can only access the data they have privileges for within your internal IT environment.  The interface will look like the screenshot below. When uploading an App from your Alteryx Designer (File>>Save as>>>My Company's Gallery) you can click on 'Workflow Options' & 'Set Workflow Credentials'.    This will give the user three options    'User is not required to specify credentials' - The application/workflow will run as the default Alteryx Server user account (Run As settings in system settings on server config).  'User must specify their own credentials' - When running the application from the Alteryx Gallery the users will have to enter in credentials    'Always run this workflow with these credentials' - The user can enter the credentials at this point, however preset credentials can be added within the Alteryx Gallery Admin section ("Workflow Credentials")   Always run workflows wither server or studio default credentials This will run any workflows with the default Alteryx Server user account (Predefined in the Alteryx Server System Settings) This could be a general account that allows all users to access the data they need to.  This is useful when testing out the Alteryx Server for scheduled workflows   Require users to enter their own credentials when running any workflows 'User must specify their own credentials' - When running the application from the Alteryx Gallery the users will have to enter in credentials        Version Control Workflows saved in the Alteryx Gallery can be shared with others who can then open them within the Alteryx Designer, make changes to them, and save them back to the Alteryx Gallery. When changes to a workflow are saved back to an Alteryx Gallery a new version of that workflow is created, and the previous version of the workflow is maintained.   IMPORTANT! To re-version an app you just need to hit the save icon in the Alteryx Designer once you have uploaded to the Alteryx Gallery for the first time. If you have already uploaded the app to the Alteryx Gallery and then go to File>>Save as>>>My Company’s Gallery, it will re-upload that same app twice. To see the version you can click on my company’s Gallery and it will populate with all the workflows, apps and macros. Within here you can click on the versions icon and it give you access to the various different versions for that workflow, app or macro.   Useful Links Are you are looking for more information on the Best practices for App Building? You may need to load the input files for your app if your Alteryx Server does not have access to these files. You can do this through adding files to the application you are uploading. What tools can be published within my app to the gallery I want to use the Gallery API to call on Apps, where can I find my API and Secret Keys   Best,   Jordan Barker Solutions Consultant     
View full article
Alteryx Server on Azure Prerequisites To work with Alteryx Server on Azure, you will need: An Azure subscription. If you don’t have an Azure subscription, you can sign up for a free trial. Microsoft Remote Desktop (RDP) software. Remote Desktop is used to connect to the virtual machine (VM) running Alteryx Server. An Alteryx Server license. An Alteryx Server installer. Installers can be downloaded from alteryx.com. Select your Windows Server version and VM size Select a Windows Server version and VM size that meets or exceeds the system requirements for Alteryx Server. Take a look at Azure’s VM size table to see what size best fits your needs. Make sure to consider price vs. performance. Larger VMs perform better but cost more.    Step 1: Create a VM   1. Log in to the Azure portal. 2. Click on the Newbutton in the top left.     3. Click on Virtual Machines   4. Choose a version of Windows Server. Select Windows Server 2012 R2 Datacenter if you don’t have a preference.    5. At the bottom of the page, click the Create button.   6. Fill out the required information in the Basicssection of the Create Virtual Machine pane. Click the OK button at the bottom to move on after you’ve filled out the required fields. Name: A name for your VM. User name: A user that will have the ability to RDP into the VM. Password: The password for the above user. Subscription: If you have multiple subscriptions, choose which subscription to put the VM in. Resource group: Resource groups help group together related VMs. Either create a new resource group or place the new server into an existing group of similar resources. Location: Where you’d like the server to be placed. You should select a location that will be closest to your users for optimum performance.   7. In the Sizesection, choose a size that meets the tech specs for Alteryx Server. When ready, click the Select button at the bottom.   8. In the Settingssection, configure the various settings for how you’d like to configure the VM. Generally, you’ll want to leave the defaults in place. For Availability Set select None. Click the OK button at the bottom when done.   9. Review the VM settings in the Summarypane and make sure everything looks correct. Click the OK button at the bottom when ready.   10. Click on the VM once it’s been deployed. Click Settings > Network Interfaces > $INTERFACE > Network security group > Inbound security rules > Addto start adding a new rule to the security group.   11. Add a rule for HTTP access. This will allow installations of Alteryx Designer to talk to the Alteryx Server VM. Give the rule a name and change the Protocol to TCP. It is highly recommended to change the Source setting to be locked down to an IP address or an IP range that you control. When finished, click the OK button. Add more access rules as needed for any other IP addresses or IP ranges. Step 2: Connect to the VM   Click on the Virtual Machinesentry on the left side of the page. Click on the VM’s name in the list. Click on the Connect This will download an .rdp file for Remote Desktop connections. Open the file downloaded in the previous step. If you see a warning that the publisher of the remote connection can’t be identified, click Connect. This will open a new Remote Desktop connection. Enter the user name and password set during VM creation. Step 3: Install Alteryx Server Installing Alteryx Server in Azure is similar to installing on any other server.   Note: If you plan on using a Gallery with Windows authentication, you’ll need to set up Active Directory in Azure. For more information, see Install a replica Active Directory domain controller in an Azure virtual network in the Azure documentation. Download the installer from alteryx.com. Note: The default security policy of Internet Explorer in Azure is set to High. This means that you’ll have to manually add downloads.alteryx.comto your list of trusted sites.   OR Copy the installer from your computer. If you’ve already downloaded the Alteryx Server installer to your computer, you can copy it as you would any other file into a folder on the Azure VM. Double-click on the installer from the Azure VM. This process is the same as installing Alteryx Server on any other computer. Step 4: Connect to Alteryx Server   Activate your license. Get the Controller Token from the Azure VM from the Alteryx System Settings Open port 80 on the Windows Firewall. In Alteryx Designer, go to Options > Schedule Workflow. In the Controllerdropdown, select Connect to Controller... Paste in the DNS name or IP of the Azure VM and the Alteryx Server Controller Token from Step 2.
View full article
If you are getting an error message 'Workflow exceeded maximum runtime of XX seconds and was canceled', you may need to change your system settings to allow a workflow to run longer.  From Alteryx Designer, go to Options --> Advanced Options --> System Settings.  (Note: if you are running Alteryx Server and don't see the System Settings, you will need to contact your server administor and have them help you make changes to the System Settings).  Click 'Next' until you get to the Worker Configuration.  If the 'Cancel jobs running longer than (seconds)' option is checked, the seconds can be increased here.     This message will be generated for scheduled workflows and workflows being run from a gallery if the option has been checked and the workflow runs longer than the setting allows.      
View full article
I have encountered a few situations recently that resulted in data loss because a backup of the Alteryx Server wasn't available. I can't stress enough the importance of regularly backing up your server. This article, the first of two-part series, will cover some options and best practices to ensure you have the necessary backups available in the event they are needed. Part II will focus on the embedded MongoDB instance  provided with the Alteryx Server install. If you are utilizing a user-managed MongoDB instance, please refer to MongoDB's documentation for backup and recovery procedures at https://docs.mongodb.org/manual/administration/backup/.   Let's go over some widely accepted best practices for backing up servers and databases:   Schedule Regular Backups - Backing up consistently on a scheduled basis is key to ensure you minimize data loss and downtime. I recommend backing up nightly during non-peak hours to minimize potential impact to users and for the minimal amount of data loss in the case of a crash or another failure. If backing up nightly isn't feasible, scheduling weekly backups is also an option. The important thing is to set a regular schedule.   Keep Historic Backups for a Defined Period - Sometimes the unexpected happens and a backup fails, becomes corrupt, gets lost/deleted, or the issue isn't noticed immediately (causing the problem state to be present in the backups). Having historic backups available helps ensure you have a backup available, and allows you to choose one created before the issue began.   Store Backups on Network or SAN Storage - Storing your backups on the same server where the data resides runs the risk of those backups not being available during a failure event. Let's consider what happens when your server suffers a disk failure. If the backups are stored locally on that disk, then they are gone too, making recovery impossible.  However, if your backups are stored on the network they would not be impacted by a failure event on the server.   Keep a Copy of the Backup Off-Site - This falls along the same lines as above. If the only backups are on a file server in the same data center as the Alteryx Server, and that data center suffers a disaster, you will lose both your server and your backups. Keeping an additional copy offsite will allow you to bring the server back up in the Cloud or at another data center if need be.   Validate your Backup Files - You should periodically check to ensure your backups are occurring successfully, and confirm that the backups are valid and usable. There is nothing worse than putting a backup process in place and then finding out after a failure occurs that the backups stopped working 6 months ago or that all of your backups aren't usable.    Practice your Recovery Procedures Regularly - Recovery drills allow you to become familiar with the restoration process and the amount of time needed to return to a fully functional state in the event of a disaster. Practice is also proven to reduce the occurrence of mistakes, and can save valuable time. I recommend running a recovery drill quarterly or bi-yearly.   Keep in mind that, in most cases, backing up the entire server including the OS and all data isn't necessary. In fact, it can actually significantly increase the average time to restoration. Instead, I would recommend backing up only the critical data and configuration files for the server. This is because it is significantly faster to clean install the server and necessary software, and then restore the backed up data/configuration than it is to restore the entire server. This is especially true in the case of virtual servers, as deploying a new virtual server takes minutes in most cases. These limited backups can also reduce the time it takes to complete and validate the backups and reduce the storage needs/costs involved in keeping those backups.   Part 2 - Alteryx Server Backup & Recovery Part 2: Procedures    
View full article
Question How do I find my Gallery API Key and Secret? Answer In order to be able to find your Gallery API Key and Secret, your Private Gallery account must first be API Enabled. To check this, a Gallery Admin will need to log in and go into the Subscriptions section. From there, the Admin can select your user account, and at the bottom there's a setting for API Enabled:   Once that setting is set to "Yes", you can log in to your own account and go into the Settings by clicking the gear icon in the top right corner. From there, click on the Private Studio tab and scroll down to find your API Key and Secret: Click the "Show" button to reveal your API Secret so you can enter it where requested when working with the API.
View full article
The Run the Worker as a Different User a.k.a “Run As” option in the System Settings allows the Worker to run the Alteryx Engine as a different user.  By default, the Scheduler runs using the Local System Account. When accessing these other environments, credentials that have Admin rights are recommended. This removes any chance of workflow failure if permissions change for non Admin user.   Run as Different User:   Scheduler: - If a Worker machine needs to run workflows that access files or data from a location that requires specific credentials to access it, the machine can be configured to run the workflows as a specified user or account.   Server: - When clients are sending database connections to the Gallery, they will need to send the app to the Gallery that works with their system settings. Otherwise, the app will fail since it will not connect to their local instance of the database on their machine.   Alteryx > Options > Advanced Options > System Settings     Troubleshoot:   My workflow runs fine through the GUI but it fails through the Scheduler   This is can be a sign of permission issues.  For the workflow to run successfully it needs access to the resources it is referencing such as network drives, files, database connections, and such. Check all of your Inputs and Outputs to verify whether the connections are local or remote.  If you are connecting to a network file share open Alteryx > Options > Advanced Options > System Settings and click Next until reaching Run the Worker As a different user……..and???   I have configured Alteryx Server to run workflows as a specified user, but they are failing.   You may be encountering this issue if the Worker machine that is configured to run the workflows as a specified user does not have the appropriate permissions in the workspace folder where files are stored. Double-click the System Settings icon on your desktop to open the System Settings window and check the following settings:   Identify the Workspace folder specified on the Worker > General screen. Open Windows Explorer and navigate to that folder. View the folder properties. On the Security tab, verify that the user specified as the Run As user exists in the list of users. If it does not, add it. On the same tab, highlight the specified user and ensure it has the following permissions: Modify / Read & Execute / Read / Write. I’ve set up the Run As and it has been working, but now my modules have started failing. Check if the password has changed recently Additional Information:   Safe and Semi-safe options for the Alteryx Gallery can only be used if the Worker > Run As setting has been enabled.      
View full article
The Composer File (pcxml) is a file type that contains a proprietary language used by Alteryx for reporting purposes. What this means for use in the Gallery is that an end user will have the ability to choose among XLSX, PDF, DOCX, ZIP and HTML file types for output.       In order to use the pcxml format, you will need to use the Render tool, which can be found in the Reporting section of the tool palette. A basic Table tool connected to the Render tool will suffice for a grid report, shown respectively.               The configuration for the Render tool will require two things, first, that the Output Mode is set to choose a Specific Output File. The Gallery validation of the workflow will fail in the Public Gallery unless a specific output is set. Next, select the pcxml file type for output and name the file. Upon loading the workflow to the Gallery you’ll see that the dependency changes to an externals path “_externals\1\name.pcxml”, this is expected. The second configuration property to set is the Data Field in the Report Data section. We will need to reference the table created using the basic Table tool.     Now load the workflow to the Gallery and that’s it! Enjoy the flexibility of reporting file formats the pcxml Composer file has to offer!   Note: Workflow and all images created in this article are from Alteryx version 10.1   Tony Moses Client Services Representative
View full article
Say you have an App or a Workflow that seems to be taking a long time to run and you just want to stop it rather than letting it run its course. Here is how you can manually stop the process.   First a connection to the Controller will have to be made in Alteryx Designer under Options—Schedule Workflow or View Schedules. Once connected, under the Options—View Schedules—Queue tab, a list of workflows running on the Gallery or Scheduler are listed.    Find the correct job.  A job that is running on the Gallery will have a long alphanumeric string under the Scheduled by filed.  If you see something that looks like a Windows UserID (the non-highlighted job below) that is a job that is running from the Alteryx Scheduler, this is not the one you want.   Highlight it and click on the Cancel Job (the minus symbol in a circle) button.     Once 'Cancel Job' is clicked a warning will pop up.     Click 'Yes' to confirm the cancelation of the job.   The Canceled job will then appear in the Results tab.     That is how a long running job can be canceled in a Private Gallery.
View full article
Adding files to Gallery App   Sometimes when uploading Apps or Macros the Gallery you may receive an error with a file extension referencing externals_...... You may also  select the workflow assets and the files are checked, but they are not loading to the gallery.   This often means the file cannot be found on the server side and as a result needs to be added to the workflow package and uploaded to with the app or macro.   Attaching the workflow assets can often be selected when exporting the workflow or adding them through the display asset management properties window within the input tool. Please see this Article for more information.   Similarly, you can also add assets within the events>>>Run command>>Assets tab.       If you add the assets through either of these methods when uploading to the Gallery, the server should be able to see the correct assets and execute without any externals errors.   Again if you are still experiencing any issues please reach out to Alteryx Support   Best,   Jordan Barker Client Services Support Engineer  
View full article
Question Is it possible to have multiple administrators for a Gallery Collection? Answer Yes, as of v10.1 we have added the ability to add additional administrators to Gallery Collections. In the past, the Collection owner was assigned as the sole administrator. In order to add another user as an administrator, the user must also be an Artisan to the Private Studio from which the app was shared. Please follow the steps below to add an administrator to a Collection:   In the Gallery, click on the Collections button. Click on the Collection you want to add the Administrator. Click on Users, look for the user, and then click on “Collection Admin”.     Once you've added the Admin permission , the user should now be able to add/update any app/workflow within the Collection.
View full article
Recently, we have had a number of questions regarding SSL certificates, how to install them, and how to configure Alteryx Server to use them. While the Alteryx Server Installation and Configuration Guide does cover enabling SSL for Alteryx Server, it doesn’t cover obtaining a certificate, or how to install that certificate so it can be used by the server.   There are a number of tools and methods you can use to obtain a SSL certificate to use with Alteryx Server.  In this article we will be focusing on using OpenSSL to create a Certificate Signing Request (CSR) to send to a Certificate Authority (CA), generating a self-signed certificate, installing the certificate, and configuring Alteryx Server to use the certificate.   Note: If you don’t have OpenSSL installed on your server you can download a precompiled Win32 or Win64 binary from https://slproweb.com/products/Win32OpenSSL.html. Please keep in mind that OpenSSL is not developed, or maintained by Alteryx. That we have no affiliation with the OpenSSL project, or the provider of this precompiled binary. As such feel free to use which ever implementation of OpenSSL you are comfortable with.   Creating a Certificate Signing Request with OpenSSL:   To generate a CSR, open an administrator command prompt on your server and navigate to the directory containing your OpenSSL.exe and configuration file. From there run the following command:   openssl.exe req -config openssl.cfg -out ServerName.csr -new -newkey rsa:2048 -nodes -keyout ServerName.key   This will prompt you to answer a number of questions related to your organization and the server. You can use the included a screenshot for your reference, but keep in mind the responses should be based on your organization and server information.     This command will create two files in the same directory with a .csr and .key extension. These files will need to be provided to your CA in order to have your certificate created. This can be either an internal CA, or a public CA such as; Verisign, GeoTrust, DigiCert, Entrust, StartCom, etc. The CA will provide you with a signed certificate in return as a .crt, .cer, .pem, or .pfx file.   Creating a Self-Signed Certificate with OpenSSL:   You can also use OpenSSL to generate a self-signed certificate. While this isn’t recommended for production environments there maybe a number of reasons why you would want to create one. Some possible reasons include dev or lab environments, and testing to confirm functionality before purchasing a certificate from a public CA. Regardless of your reason you can do so with the following procedure:   Open an administrator command prompt and navigate to your OpenSSL directory. Once there, run these commands:   openssl.exe req -config openssl.cfg -x509 -sha256 -nodes -days 365 -newkey rsa:2048 -keyout ServerName.key -out ServerName.crt openssl.exe pkcs12 -export -out ServerName.pfx -inkey ServerName.key -in ServerName.crt   The first command generates a signed certificate (.crt file) and private key (.key file). The second command creates a combined certificate and key file in a .pfx format from the generated certificate and key. Please keep in mind you will be asked the same or similar questions as you would if you were generating a CSR. Please reference the screenshots below:       Note: As previously stated we do not recommend using self-signed certificates in production environments.   Installing the Certificate:   Once we have received the signed certificate from the CA or generated a self-signed certificate we need to install it. To install the certificate we need to open a Microsoft Management Console (MMC) to access the Certificates snap-in by following these steps:   Click Start and then click Run. In the command line, type MMC and then click OK. In the Microsoft Management Console (MMC), on the File menu, click Add/Remove Snap-in. In the Add Remove Snap-in dialog box, click Add. In the Add Standalone Snap-in dialog box, select Certificates and then click Add. In the Certificates snap-in dialog box, select the Computer account radio button because the certificate needs to be made available to all users, and then click Next. In the Select Computer dialog box, leave the default Local computer: (the computer this console is running on) selected and then click Finish. In the Add Standalone Snap-in dialog box, click Close. In the Add/Remove Snap-in dialog box, click OK.   Next, we need to actually import the certificate. To do this:   Expand Certificates > Personal Right click on certificates under personal Select All Tasks > Import.     This will open the certificate import wizard.     Click Next       Browse to the certificate file provided by your CA, or the pfx file generated in the self-signing instructions Click Next   If you are using a self-signed certificate, or your CA issued a certificate that includes the private key you will be prompted for the password/phrase. Otherwise this step will be skipped by the import wizard.     Enter the password Check the box to mark this key as exportable Click Next   The next screen will ask to confirm where you want to place the certificate. This should have the Certificate store set to ‘Personal’ already.      Set the Certificate store to Personal if needed Click next On the next screen click Finished   If you are installing a self-signed certificate we need to repeat these steps in order to establish the local server as a trusted authority. To do this install the certificate a second time following the same steps as above. Except this time we are going to install it to the Trusted Root Certificate Authorities store instead of the Personal store. You can do this by expanding Trusted Root Certificate Authorities, right clicking on certificates, and choosing All Tasks > Import, or by changing the Certificate store at the end of the import wizard.       Configuring Alteryx Server to Use the Certificate:   At this point you can follow the detailed instructions in the Alteryx Server Installation and Configuration Guide to complete the configuration. Alternatively (and for completeness), you can continue with these simplified instructions.   First you need to collect the certificate thumbprint for the certificate you installed above. You can do this from MMC > Certificates > Personal > Certificates by right clicking on the installed certificate and choosing open. This will open a certificate dialog for the certificate you installed. From there, select the Details tab and find the Thumbprint field. Copy the value and remove all spaces from it (e.g. ‎74d4ca722e2954cd225f9b4697d2fc7f6747194c).     Next, you need to bind http port 443 to the certificate. To do so, open your administrator command prompt again. Then run the following command, making sure to replace the certhash with the thumbprint value you captured:   netsh http add sslcert ipport=0.0.0.0:443 certhash=‎74d4ca722e2954cd225f9b4697d2fc7f6747194c appid={eea9431a-a3d4-4c9b-9f9a-b83916c11c67}     To check that the binding is correct, you can run the following command:   netsh http show sslcert       Note: When renewing an expired or expiring certificate, you will need to delete the current binding (netsh http delete sslcert ipport=0.0.0.0:443), capture the thumbprint of the new certificate, and rebind the certificate using the instructions above.   For the final step, you will need to configure the Gallery service to use SSL. To do this open Alteryx System Settings and click Next until you reach Gallery > General. Once there find the Base Address section and check the box to Enable SSL. Then click Next, Finished, or Done as appropriate to apply the settings change and restart the Alteryx Service.     Note: The URL must also match the name the certificate was issued to. As such, if the certificate was issued to the server's fully qualified domain name (e.g. hostname.domain.tld), your URL needs to match this by using https://hostname.domain.tld/gallery/. If the certificate was issued to just the hostname, you would need to use https://hostname/gallery/. If the URL doesn’t match the certificate the service will fail to start properly.       Applicable versions: Alteryx Server 10.0 & 10.1 Credits:
View full article
Question Is it possible to allow users to publish an app/workflow to the Private Gallery but not allow users to actually run the app/workflow? Answer I received this question from a client that needs to do careful QA on apps before they can be pushed to the Production server.    This is possible through a manual process currently. When a workflow is published to the private gallery, the user who published it can edit the workflow settings to prevent the workflow from being able to run in the Gallery manually. This method requires the user to change the workflow settings for every workflow published that they do not want to be able to run.   The steps for this process are shown below.   1) Log in to your Private Gallery after publishing your workflow/app 2) Click on the Private Studio icon on the left side of the screen 3) Select the workflow/app you wish to change the settings for 4) Click the link for Workflow Settings 5) Deselect the option showing "This workflow may be run in the Gallery"     Note: Screen shots taken from 10.1.7.
View full article
As part of the upgrade from Alteryx Server 9.5 to 10.0+, the Mongo DB Alteryx Server uses for the persistence layer will be upgraded to MongoDB 3.0. During this process a backup of the existing database is created under the folder MongoDB_preAlteryx10 and the upgraded Database is created under the MongoDB_Alteryx10 folder. The existing persistence database, MongoDB, is not touched.     After completing the update, some users were unable to start AlteryxService (usually experienced as browsing to the local Alteryx Gallery returns an error page) because the configuration files were still pointing to the old Alteryx persistence database, MongoDB, instead of the upgraded one MongoDB_Alteryx10.   To get the service starting, the user must manually point to the MongoDB_Alteryx10 persistence directory in the Alteryx System Settings application.   Steps to get AlteryxService to start: First identify the correct folder where the persistence layer exists. You can check by launching the Alteryx System Settings application, and navigating to the Persistence Settings under Controller:       Copy the path shown under Data Folder up to Persistence (C:\ProgramData\Alteryx\Service\Persistence) and paste it in a File Explorer window; you should be able to see the different copies of the Persistence layer.     Double-click the MongoDB_Alteryx10 folder, copy the full path from the File Explorer bar and paste it in place of the existing path under Data Folder.           Follow through with the rest of the configuration steps in the Alteryx System Settings app and press Done at the last step. This should restart the service.     You can check if the service is running by opening the Task Manager and checking the status of AlteryxService under the Services Tab. You can attempt to restart the service for this windows as well by right-clicking on AlteryxService and selecting Start Service.     If you still can't get AlteryxService to start:   From the Start Menu, search for CMD, right-click and press Run As Administrator. Navigate to the location of the Alteryx installation by typing: cd "C:\ProgramFiles\Alteryx\bin" then pressing return (the part after cd depends on where you have Alteryx installed) Type: AlteryxService Test and press return. Once the command stops running, take a screenshot of the window and send it to support@alteryx.com; a Customer Support Engineer will reach out to you for further support.  
View full article
Is it possible to query the data on the "View Schedules" tab of the scheduler? This question has come up a few times recently, and the answer is yes you can but the method depends on whether you are using MongoDB (Server) or SQLite (Designer + Scheduler). Let's go over MongoDB (Server) first: First you'll need some information from your System Settings (Controller - Persistence section): You'll need the Host information, Username, and Password. You'll see two options for password, Admin and regular. For this you want to use the regular Password (which you can just copy/paste into your connector). Once you have this information, configure the MongoDB Input tool (Connectors toolset): The "Host" information goes in the Server input. Username and Password go in their respective boxes. The database you need to query is AlteryxService. The Collection drop down should auto populate with the tables you can pull from, however you may need to run the workflow once to refresh (you will get an error stating that Database and Collection must be specified). Once you've established your connection you can use the rest of the tool configurations to set up any other information you want such as record limits: You can find more information on the specifics of these options in the help file by clicking on the ? icon in the tool configurations. Next we’ll go over how to connect using SQLite (Designer + Scheduler): For this option it’s pretty straight forward. You’ll use your standard Input Data tool. Browse out to: ProgramData\Alteryx\Service\Persistance\AS_Schedules The file you are looking for is called “__TheData.sqlite” Parse the data With both methods you'll get a variety of information back including computer name, username, run dates, etc. There will also be a field called "ServiceData" that is a blob field with a binary object. This field contains additional information about the record you are viewing and can easily be parsed using the ServiceDataParser macro attached below. The ServiceDataParser.yxmc was created by Kory Cunningham and is necessary to make use of the additional field. The original macro is included in the Gallery Usage Report App available on the downloads page ( http://downloads.alteryx.com/downloads.html )  Note that in some cases you may encounter an error when trying to use the macro stating "This tool is not licensed". This is because the macro uses a generic tool that some older licenses don't enable. If you encounter this error, consult with our Fulfillment team to obtain an appropriate license.   Put it all together: The final step here is to join the information from the various Mongo tables back together (if pulling from multiple tables). The key table for this process is the Queue table (AS_Queue) as it holds all of the IDs necessary to join back to the other tables (AS_Results, AS_Schedules, AS_Applications) in order to get all the data together.   You'll need multiple Joins to make this work outlined below: 1) Join the Schedules Table to the Queue Table using the AS_Application_ID field. 2) Join the results of Step 1 to the AS_Results Table using the AS_Queue_ID field. 3) Join the results of Step 2 to the AS_Applications Table using the AS_Application_ID field and the Mongo_id field (from Mongo Input tool)   Note that in order to use the Mongo_id you'll need to parse it out to remove the unneeded information. You can do this using a simple RegEx expression within the RegEx tool: .*"(.*)".*   I've also attached a sample workflow detailing this process. Note that the workflow probably won't run until you update the credentials to match your own as it is set up for my instance of Mongo. You can use the workflow as a template for your own connections.   If you want to take this process a step further, take a look at this article. It will show you how ot use an Alteryx macro to accomplish this (downloadable from the Gallery) and also includes a link to show you how to build a Tableau dashboard to make the information easier to consume! All screen shots and directions are taken from Alteryx version 10.1.6   **Update for 11.0 release** In 11.0, the option to schedule workflows from the Gallery was added. I've updated the sample workflow to show how to bring those in and identify them separately. There's a bit of extra parsing necessary. Take a look at the "PullFromMongo_Updated_v11.yxzp" file attached.
View full article
For a shared server, the system owner/IT contact should set the memory to no more than (total memory-2G)/(Number of Users). This allows all users to run modules simultaneously without causing the system to go into virtual memory, which significantly slows processing.
View full article