Skip to main content

Aperture Data Studio troubleshooting

Looking for Aperture Data Studio v2? Go to our new site.

To find an answer or a solution, browse the topics or search the page (Ctrl+F or ⌘+F).

How do I limit memory usage?

The default memory settings assume that Data Studio is run on a dedicated (or largely dedicated) machine which isn't always the case. To ensure that not all available memory is allocated to Data Studio, you can adjust the maximum memory settings.

You can do this in the Aperture Data Studio Service 64bit.ini file which is in the root of the installation directory (by default, C:\Program Files\Experian\Aperture Data Studio <version>\Aperture Data Studio Service 64bit.ini). 

The following line controls memory allocation:

Virtual Machine Parameters=-Xms66:1000:16000P -Xmx66:1000:16000 

These default settings mean that Data Studio will use 66% of the total system memory that’s available, up to a maximum of 16 GB. 

-Xmx<value> This is the maximum amount of memory to be used. Example: to specify a fixed 24 GB for the application, enter: -Xms24g

-Xms<value> This is the initial amount of memory to use upon start up. For the best performance this should be the same as the Xmx value to avoid fragmentation of memory. Example: to specify that Data Studio uses only 8 GB at a maximum, enter: Virtual Machine Parameters=-Xms8G -Xmx8G 

How do I configure an ODBC connection? 

Download ODBC drivers

By default, we install both 32-bit and 64-bit drivers because an ODBC client running on a 64-bit OS may be both 32-bit or 64-bit.

After installing the ODBC drivers, you should be able to create a Data Source Name (DSN) for both 32-bit and 64-bit clients.

Set up the DSN

The 32-bit ODBC Administrator is found at %systemdrive%/Windows/SysWoW64/odbcad32.exe
The 64-bit ODBC Administrator is found at %systemdrive%/Windows/System32/odbcad32.exe

  1. Select the System DSN tab.
  2. Click Add.
  3. Choose Experian Aperture ODBC Driver.
  4. Fill in the Data Source Name field (e.g. Aperture ODBC server 64).

    We recommend that you distinguish between the 32-bit and 64-bit DSNs to avoid confusion.

  5. Fill in the Description, ODBC host (e.g. localhost) and the ODBC port (e.g. 7801).

Test the connection using Excel (Office 365 version)

  1. In Data Studio, go to the Workflow Designer and create a new workflow with a Snapshot step.
  2. In the step dialog, click Additional options and ensure that Publish to ODBC is enabled.
  3. Execute the workflow. You should get a confirmation message.
  4. Open Excel.
  5. Select the Data tab.
  6. Click Get Data and select From Other Sources then From ODBC. If you can't see this option, customize the ribbon to make Get External Data visible.
  7. From the Data source name (DSN) list select the Aperture ODBC server 64 (or whatever you called your DSN) and click OK. If you've used 64-bit client and you can't see the ODBC source, try steps 4-7 again with the 32-bit client.
  8. In the dialog that appears enter the Data Studio administrator username/password and click Connect. If you've entered the wrong credentials, go to Get Data > Data Source Settings… > and Clear permissions.
  9. Select a table from the list and click Load. Make sure that the list only contains workflow/snapshot names to which this user has read access.
  10. Getting Data message will appear, followed by the snapshot row/columns.
  11. Check that the following are correct: the column names, row count, and the cell data.
  12. Check that an audit message has been created for the ODBC session (if login audits have been enabled).

How do I upgrade ODBC drivers?

  1. Uninstall the old version of the ODBC drivers.
  2. Install the new version of the ODBC drivers.
  3. Remove the old System DSN in odbcad32.exe:
    - The 32-bit one is found at %systemdrive%/Windows/SysWoW64/odbcad32.exe
    - The 64-bit one is found at %systemdrive%/Windows/System32/odbcad32.exe
  4. Create a new System DSN in odbcad32.exe.

How do I add a custom JDBC driver? 

  1. Copy the driver .jar file you’d like to use to the drivers\jdbc folder within the database directory (by default C:\ApertureDataStudio\drivers\jdbc). Note that the Data Studio service doesn’t have to be stopped for your new driver to be picked up.
  2. In Data Studio, go to Data Explorer and Click here to create a new data source.
  3. Select JDBC as Data source type.
  4. Your newly added driver will appear in the DBMS list. All new drivers will appear in the list appended with Custom, for example 'Custom MySQL 5.1'.
  5. Select your driver and specify the connection details as appropriate.
  6. Click Test connection to check connectivity and Create to save changes.

How do I configure Apache Hadoop HDFS?

  1. In Data Studio, go to Data Explorer and Click here to create a new data source.
  2. Select Apache Hadoop HDFS as Data source type.
  3. Specify the following:
    - Hostname: the IP address or DNS name of the Primary NameNode of your Hadoop cluster.
    - Port: is the value of the property. Typically, you will find this in the Hadoop configuration file core-site.xml.
    - Username/Password: the Linux username/password on the Hadoop host machine.

    Note that your file access permissions will determine which files are visible to Data Studio.

    - Root directory: the starting directory for file discovery. If not specified, it will default to the root of the HDFS file system (“/”). 

    You should choose the root directory carefully since HDFS file systems may contain a huge number of files.

    To access all the files under your starting directory, enable the Include files in subdirectories option.

  4. Click Test connection to check connectivity and Create to save changes.

Driver's SQLAllocHandle on SQL_HANDLE_ENV failed

If you get this error while connecting to Excel or PowerBI, run these as administrator.

Windows could not start the Experian Aperture Data Studio Database Server {version} 64bit service on Local Computer

This error is most likely to occur when the JVM in which Data Studio runs is attempting to allocate more memory than is available on the system. 

The memory settings can be configured in the Aperture Data Studio Service 64bit.ini file which is in the root of the installation directory (by default, C:\Program Files\Experian\Aperture Data Studio <version>\Aperture Data Studio Service 64bit.ini). 

This line in the file controls the memory allocation:

Virtual Machine Parameters=-Xms66:1000:16000P -Xmx66:1000:16000 

By default, the Java Virtual Machine settings will use 66% of the total system memory that’s available, up to a maximum of 16 GB (from 24 available). This assumes that Data Studio is run on a dedicated, or largely dedicated box. 

If your environment isn't dedicated to Data Studio and has other applications running, it’s possible that this much memory can't be allocated. In this case, the VM parameters can be changed to specify an exact value for maximum memory used. For example, to allocate 8 GB RAM: Virtual Machine Parameters=-Xms8g -Xmx8g

If the service isn't starting after changing the memory setting, other possible causes are:

  • Port 7701 is already in use
  • Permissions issue when creating the Data Studio repository (by default, C:\ApertureDataStudio)

How do I install the Linux version of Data Studio?

View technical recommendations before installing. Note that your setup requirements will depend on the size of your data and Aperture Data Studio usage.

Installation pre-requisites:

  • A 64bit version of a compatible Linux operating system is used.
  • The latest version of 64bit Java 8 JDK is installed.
  • The server and the required port (default is 7701) is available to all client machines through all intermediate networks and firewalls. Other default ports that may need opening include:
    - 7801 for ODBC connections
    - 8080 for the Find duplicates server (if deployed separately) 

  • User limits for the dedicated user (default is ApertureDataStudio) are set to unlimited for each resource:
    - You can view your system’s limits by entering ulimit -a in the command shell.
    - It's critical that the application can open enough files simultaneously. Ensure this setting is set close to the operating system’s limit. For example, for RHEL/Centos set the hard limit to around 64000: when logged in as the dedicated user ulimit -Hn should give the result 64000.

Install Aperture Data Studio 1.6.0 for Linux

The supported platforms are Red Hat and CentOS. Note that we currently don't support installation in user-defined directories using the –prefix option.

The distribution exists as a .rpm file so you may use yum or rpm to install Data Studio. The installation directory created by the rpm is /home/experian/ApertureDataStudio/ApertureDataStudio_1.6.0.

$ sudo yum install ApertureDataStudio-1.6.0-1.el7.x86_64.rpm

The hierarchy of directories is created at installation and is owned by ApertureDataStudio:experian. The user (ApertureDataStudio) and group (experian) are created, if absent.

The directory and its children are created with permissions of 770, i.e. owner: rwe, group: rwe and all others no access. Also, two service files are created: the first is used to control the Aperture Data Studio server (ApertureDataStudio_1.6.0.service); the second for the Standardize service (Standardize_4.6.14.service).

The following are created:

  • A username ApertureDataStudio (marked as no-login).
  • A group experian.
  • A directory /home/experian/ApertureDataStudio.
  • All files with permissions 770.
  • All files owned by ApertureDataStudio:experian.
  • A service file /etc/systemd/system/ApertureDataStudio_1.6.0.service.
  • A service file /etc/systemd/system/Standardize_4.6.14.service.

To re-install Data Studio:

$ sudo yum reinstall ApertureDataStudio-1.6.0-1.el7.x86_64.rpm

Starting the server

Before you can use Data Studio you have to either start it as a service or run the executable directly in a terminal window.

Starting Aperture Data Studio directly

$ cd /home/experian/ApertureDataStudio/ApertureDataStudio_1.6.0
$ sudo java –Xms16g –Xmx16g –cp .:./pserver.jar:”./lib/*” com.experian.ServerMain STARTUP

Starting Aperture Data Studio as a service

# make the services known to the system
$ sudo systemctl daemon-reload

# create the symlinks
$ sudo systemctl enable ApertureDataStudio_1.6.0

# start the service
$ sudo systemctl start ApertureDataStudio_1.6.0

# Check the service status
$ sudo systemctl status –l ApertureDataStudio_1.6.0

Note that these services will restart on failure and at system boot time.

Tailoring the server properties files

The server will run out-of-the-box, however, you may prefer to relocate the server and the data directories to another partition/directory. Both of these locations may be changed by editing the file in /home/experian/ApertureDataStudio/ApertureDataStudio_1.6.0

The two properties are:

  • DirName.ROOT
  • DirName.DATA

You may create these directories yourself with the appropriate owner/permissions.

Additional file data sources may be specified in the file in /home/experian/ApertureDataStudio/ApertureDataStudio_1.6.0


Configuring data for Validate addresses step

  1. Place the Experian Batch data for the Validate addresses step in a directory of your choice.
  2. Edit /home/experian/ApertureDataStudio/addressValidate/runtime/qawserve.ini:
    • Add InstalledData=GBR,/home/experian/ApertureDataStudio/ApertureDataStudio_1.6.0/Batch
    • Add DataMappings=GBR,United Kingdom,GBR
  3. Add a valid Experian Batch licence using Data Studio: click on your username and select Update license.


Installing Standardize

# Install the prerequisites
$ sudo yum -y install lttng-ust libcurl openssl-libs krb5-libs libicu zlib

# make the services known to the system
$ sudo systemctl daemon-reload

# create the symlinks
$ sudo systemctl enable Standardize_4.6.14

# start the service
$ sudo systemctl start Standardize_4.6.14

# Check the service status
$ sudo systemctl status –l Standardize_4.6.14

Service 'Experian GDQ Standardize Server' (GdqStandardizeServer) failed to start. Verify that you have sufficient privileges to start system services.

To start the service:

  1. Search for services from the start menu or go to Control Panel > System and Security > Administrative Tools > Services.
  2. Locate the Experian GDQ Standardize Server, right-click and select Properties.
  3. Open the Log On tab.
  4. Select This account and enter NT AUTHORITY\NETWORK SERVICE as the account.
  5. Click Apply to save changes.
  6. Right-click on the Experian GDQ Standardize Server service and select Start.

Can I configure multiple columns?

Yes, when configuring data in the Data Explorer (if you're not in this view already, right-click on the source, select View data then Configure in the top menu).

Once in the configuration view, click Columns in the left-hand side menu and then Multi select. Choose the columns you want to edit, right-click and select the required action.

The data may need configuring

If you try to View data before it has been previewed and/or configured, a warning message will appear asking you to preview it first.

We recommend that you always preview data before loading it to ensure that the data we cache appears is as expected.

I have issues uploading Excel files

Due to the nature of the format, Excel files require more memory and processing power. If you have issues uploading a .xls or .xlsx file, try converting it to a .csv and then upload again.

My Metro 2 file hasn’t parsed correctly

In Data Explorer, right-click on the file and select Preview and configure. In the Data tab you will have the following options:

  • File is EBCDIC
  • File length is coded big-endian
  • Increase record length
  • File is packed

Different Metro 2 files may be encoded or packaged differently. These configuration options give you more control over the parsing process.

Validation rules cannot be saved/step options are greyed out (disabled)

Connecting the Validate step to a data source will prevent you from adding new rules. Connecting this step to the Union, Multi-View, Splice, Custom or Chart steps may cause your validation rules to be lost.

To avoid this, add the Transform step before the Validate one. 

Unable to read countries but the layouts are working in Experian Batch test harness

By default, the qaworld.ini contains all the address and component layouts used by each data set.

You shouldn't delete these layouts but you can make modifications as long as the layout continues to be valid (i.e. it works in the test harness).

If the qaworld.ini no longer contains address and component layouts, we recommend rolling back to the default version which can be found in addressValidate\templates.

Unable to read countries

Your Experian Batch isn't configured correctly.

To check, go to the addressValidate\runtime folder in your Data Studio installation (e.g. C:\ProgramData\Experian\addressValidate\runtime).

Show hidden files/folders has to be enabled for the ProgramData folder to be visible.

Using the Command  Prompt, run BATWV64.EXE (the Experian Batch API test harness). You should see the list of available address layouts. For Use layout number enter the number of the layout from the list that corresponds to a country you have configured. 

If you get an error, Experian Batch hasn't been configured correctly. Contact support for help.

Note that when configuring the TigerLine dataset for the USA, the TigerLineAPI= setting is not optional.

I can’t see workflow reports

Ensure you allow pop-ups in Chrome: click  on the right-hand side. Select Always allow pop-ups from http://localhost:7701 and click Done.

No export steps found

Workflows with more than one output have to include at least one export or script step to be executed:

  1. Go to Workflow  steps on the right-hand side.
  2. Drag and drop an Export step into the workflow and link to the relevant step.

I can’t edit an imported workflow

When importing a workflow file (.wfl) that references data not available in your environment, you will be prompted to manually map these tables.

The Map invalid workflow source/target tables dialog will list all the invalid source or target tables. Use the New table dropdown to map these to the appropriate table available in Aperture Data Studio.

You will be able to change this mapping later by re-connecting the workflow to a different source using the Workflow Designer.

Microsoft Active Directory in Aperture Data Studio 

Active Directory (AD) is Microsoft’s implementation of an LDAP server.

Note that Data Studio only uses AD’s authentication mechanism, not its authorization.

When you're using LDAP authentication and create a new user, you don't set a password as this is managed in LDAP itself. 

Data Studio administrator users will define which LDAP users have access to Data Studio by creating users in the normal way, and linking the Data Studio username to their LDAP username. 

The Data Studio server associates the Data Studio username and the AD username at the time a user logs in as the relevant AD username and password are sent to AD for authentication checks.

LDAP security 

A representation of the user’s password is stored in the LDAP server. The mechanism (i.e. algorithm) that is used to create this representation is well defined, although its implementation is not. For this reason, the most common security mechanism is SIMPLE. 

The SIMPLE mechanism expects you to authenticate by providing a username (DN or UPN) and a clear text password.

Note that Data Studio never stores this password - it's transmitted over a secure connection (using SSL) between the Data Studio server and the LDAP server.


Note that only administrators can update licenses. Find out about user roles

To enter your license key(s):

  1. Click on your username in the top-right corner.
  2. Select Update license.
  3. Click Request license. The page that opens will have your product update key(s) and instructions on how to request a new license.
  4. When you receive your license(s), paste/enter them in the Update license dialog click Apply. You can apply as many keys as necessary, one at a time.

If you’re applying an Experian Batch license, you will have to restart the service.

To find out details about your license (including what you’re entitled to use and the expiry dates):

  1. Click on your username in the top-right corner.
  2. Select About Aperture Data Studio. Your license details will be shown.
  3. To view more detailed information: Click here to see full license information.

License editions

Feature Standard Professional Enterprise
Rows per table  1 million  10 million Unlimited 
Number of data sources 10  100  Unlimited 
Database size  200 GB  3 TB  5 TB 
Shared workflow    Yes  Yes  
Script workflow steps    Yes   Yes  
Cloud connectors (AWS S3 and Azure Blob)   Yes   Yes  
SDK    Yes  Yes  
Data connections  JDBC  JDBC, Hadoop, S3, Azure  JDBC, Hadoop, S3, Azure 
Number of Consumer users  20  Unlimited 

Number of Designer and developer or Administrator users

Note that the default administrator user doesn’t count towards this limit.

1 20 

Each license edition can be supplemented with feature-specific licences at any point.

Can’t use a workflow step

You’re not licensed to use this workflow step. Here are the possible statuses:

Status Description
Active You're licensed to use the step (or licensing isn't required).
Invalid The license has expired.
Expiring The license will expire in less than 2 months.
Trial This step is in trial mode.
Inactive You're not licensed to use this step.
Disabled This step has been disabled by the administrator.

How do I add a SSL certificate?

Note that your certificate file has to be on the server machine.

  1. Go to Configuration > All server settings and enable Use Secure Sockets Layer (SSL).
  2. In All server settings find Server certificate.
  3. Enter the following details:
    • Key passphrase
    • Key file (This is the full path to the certificate’s key file. Don’t include quotation marks.)
    • Certificate file (The full path. If using a .pfx file, this should be the same path as the Key file.)
  4. Click Apply.
  5. It’s very likely that you will also want to update the server port to 443, the default port for HTTPS.

How do I configure LDAP (AD) authentication?

  1. Go to Configuration > All server settings and click LDAP properties.
  2. Click Enabled and specify the following:
    • LDAP server URL (e.g. ldaps://
    • Security (choose from the available security options)
  3. Click Apply to save your changes.

Debugging LDAP connectivity issues

You can use Microsoft’s LDP.exe tool to test LDAP connectivity:

  1. Create a connection: go to Connection > Connect. If successful, the details page will be open.
  2. Test that the user credentials: Connection > Bind. Select Bind with credentials as the type.

If the connection is successful but you can’t connect to Data Studio (using the same domain), contact support.

You can now assign this authentication method to your users. Find out about user management.

How do I reset the administrator password?

Note that these steps assume that Data Studio v1.3 is installed in the default location.

  1.  Stop the Data Studio service (Experian Aperture Data Studio Database Server), if running.
  2. On the server hosting Data Studio open the command line as administrator and enter:
    java -jar "C:\Program Files\Experian\Aperture Data Studio 1.3.0\pserver.jar" STARTUP RESETADMINPASSWORD

    Update this command to reflect the version of Data Studio you're using/custom file location, if not on v1.3/not using the default install location.

  3. This will start the Data Studio server in the command line and prompt you to enter a new password (in the command line console).
  4. Once the server has fully started up, you should be able to access the home screen (don't attempt to log in at this stage). Stop the command line server (Ctrl + C).
  5. Restart the service as usual. 
  6. Log in using the newly created password. You will be prompted to update it again via the UI for additional security.

How do I restart the Data Studio service?

The quickest way is to use Data Studio:

  1. Click on your username in the top-right corner.
  2. Select Restart service.
  3. Click Yes to confirm.
  4. You will be taken to the login page. 

    Note that the restart might take a minute.

  5. Log back in.


  1. Search for services from the start menu or go to Control Panel > System and Security > Administrative Tools > Services.
  2. Locate the Experian Aperture Data Studio Database Server service.
  3. Right-click on the service and select Start

    Note that the restart might take a minute.

  4. Log back into Data Studio.

How do I back up the Aperture Data Studio repository?

See step 1 in How do I upgrade to a new Data Studio version?

How do I upgrade to a new Data Studio version?

We strongly recommend that you don’t keep the old Data Studio version when upgrading to a newer one.

The recommended upgrade process consists of three parts:

  1. Backing up your current Data Studio repository.
  2. Uninstalling the old version.
  3. Installing the new one (run the executable as an administrator).

1. Back up your repository

a) Stop the service:

i) Search for services from the start menu or go to Control Panel > System and Security > Administrative Tools > Services.

ii) Locate the Experian Aperture Data Studio Database Server service.

iii) Right-click on the service and select Stop.

b) Back up:

Note that this may take some time.

Copy and save the following files/folders to a separate location: 

  • The Aperture Data Studio folder (by default, C:\ApertureDataStudio). This contains all your data, workflows and caches. You can choose to back up individual sub-folders as well:
    • import (if you have any files imported)
    • content (if you're using auto data tagging)
    • drivers (if you're using any custom JDBC drivers)
    • if you have snapshots: copy all the required ones (by default, C:\ApertureDataStudio\data\resource\table\workflow\{UUID}_{Snapshot Name})
    • sampledata folder (if you use sample data or tutorials).
  • Server properties file (by default, C:\Program Files\Experian\Aperture Data Studio {version}\ This contains all your settings defined in Configuration.
  • Filedatastores properties file (by default, C:\Program Files\Experian\Aperture Data Studio {version}\ Back this up if you have set up any data stores, use sample data or tutorials.
  • workflowTriggers.json file (by default, C:\Program Files\Experian\Aperture Data Studio {version}\workflowTriggers.json). Back this up if you have any workflow triggers defined.
  • Virtual Machine Parameters={memory usage} setting, if not using the default JVM setting (by default, C:\Program Files\Experian\Aperture Data Studio {version}\Aperture Data Studio Service 64bit.ini). 

  • If you have custom steps:
    • addons folder (by default, C:\Program Files\Experian\Aperture Data Studio {version}\addons)

  • If you are licensed for Experian Batch:
    • License key file (by default, C:\ProgramData\Experian\batchkeys.ini)
    • Qawserve file (by default, C:\ProgramData\Experian\addressValidate\runtime\qawserve.ini)
    • Qaworld file (by default, C:\ProgramData\Experian\addressValidate\runtime\qaworld.ini)

2. Uninstall the old version

a) Search for remove program from the start menu or go to Control Panel > Programs > Programs and Features.

b) Find Experian Aperture Data Studio.

c) Right-click, select Uninstall, then click Yes.

The uninstaller will delete:

  • C:\ProgramData\Experian\addressValidate
  • C:\Program Files\Experian\Aperture Data Studio {version} (includes custom steps, server settings, custom drivers, etc.)

The uninstaller will not touch:

  • C:\ProgramData\Experian (licenses for Data Studio and Experian Batch, might also contain other Experian files).
  • C:\ApertureDataStudio (contains workflows, users, import folders, etc.)


3. Install the new version

a) Stop the service, and replace the mandatory files noted above. Restart the service.

Note that it's not necessary to replace the repository itself if you are using it in the default location.

b) (optional) If your server had been configured to use a repository in a non-standard location:

 i) Stop the service

ii) Delete the newly created C:\ApertureDataStudio

iii) Replace your backed-up repository and file in their old locations

iv) Restart the service

c) Install the new version as usual. Get the latest Data Studio version.

If you're using a remote instance of the Find duplicates server, you may have to upgrade it as well. Firstly, check the release notes that the version of the server you're running is the latest. If not, install the latest Find duplicates server.

Clean install

If you want to install a new version on a machine that has/had Data Studio installed:

1. Uninstall any remaining instances of Data Studio.

2. Manually delete C:\ProgramData\Experianand C:\ApertureDataStudio.

Note that this will remove your existing license.

3. Install a new version as usual.

How do I change the database location?

By default, the database is installed on C:\ApertureDataStudio.

To change this, go to Configuration > All server settings > Database root and change the value. You will be prompted to restart Aperture Data Studio. 

All the old contents of this folder will be copied to the new location.

I’m getting UI issues

Try reloading the browser cache: Ctrl+F5.

The Aperture Data Studio application is not loading

Ensure the Windows service (Experian Aperture Data Studio Database Server) is running.

Search for services from the start menu or go to Control Panel > System and Security > Administrative Tools > Services.

I get a connection error

Check that the Windows service (Experian Aperture Data Studio Database Server) is running.

Search for services from the start menu or go to Control Panel > System and Security > Administrative Tools > Services.

A port is in use

Check that you're not using the default Data Studio ports: 7701 and 7801 (used by the web server and the ODBC, respectively).

To change these defaults, go to Configuration > Communication > and modify REST web server TCP/IP port and/or ODBC Port values.

How do I uninstall Aperture Data Studio?

See step 2 in How do I upgrade to a new Data Studio version?

Can’t find an answer or a solution?

Contact support