Skip to main content

Aperture Data Studio troubleshooting

How do I configure an ODBC connection?

Install 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

  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 From Other Sources. If you can't see this option, customize the ribbon to make Get External Data visible.
  7. Click From Data Connection Wizard.
  8. Select ODBC DSN from the list and click Next.
  9. Select the data source (e.g. Aperture ODBC server 64) and click Next.
  10. In the dialog that appears enter your Data Studio username/password.
  11. Select a table from the list and click Next. Make sure that the list only contains workflow/snapshot names to which this user has read access.
  12. Click Finish in the Save Data Connection File and Finish dialog.
  13. In the Import Data dialog select Table then click Next.
  14. Getting Data message will appear, followed by the snapshot row/columns.
  15. Check that the following are correct: the column names, row count, and the cell data.
  16. Check that an audit message has been created for the ODBC session (if login audits have been enabled). Find out about audits in Data Studio.

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.

Driver's SQLAllocHandle on SQL_HANDLE_ENV failed

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

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 fs.default.name 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.

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 installation. Note that your setup requirements will depend on the size of your data and Aperture Data Studio usage.

Install Aperture Data Studio 1.2 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.2.0.

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.2.0.service) and the Standardize service (Standardize_4.5.5.service).

The following are created:

  • A username “ApertureDataStudio” (marked as no-login).
  • A Group “experian”.
  • A directory “/home/experian/ApertureDataStudio/ApertureDataStudio_1.2.0".
  • All files with permissions 770.
  • All files owned by ApertureDataStudio:experian.
  • A service file /etc/systemd/system/ApertureDataStudio_1.2.0.service.
  • A service file /etc/systemd/system/Standardize_4.5.5.service.

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

[aperture@linux1 ~]$ sudo yum reinstall ApertureDataStudio-1.2.0-1.el7.x86_64.rpm
[sudo] password for aperture:
Loaded plugins: fastestmirror, langpacks
Examining ApertureDataStudio-1.2.0-1.el7.x86_64.rpm: ApertureDataStudio-1.2.0-1.el7.x86_64
Resolving Dependencies
--> Running transaction check
---> Package ApertureDataStudio.x86_64 0:1.2.0-1.el7 will be reinstalled
--> Finished Dependency Resolution

Dependencies Resolved

============================================================================================== Package               Arch      Version           Repository                              Size

==============================================================================================

Reinstalling:
ApertureDataStudio  x86_64     1.2.0-1.el7      /ApertureDataStudio-1.2.0-1.el7.x86_64   508 M

 

Transaction Summary
==============================================================================================
Reinstall  1 Package

Total size: 508 M
Installed size: 508 M
Is this ok [y/d/N]: y
Downloading packages:
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
  Installing : ApertureDataStudio-1.2.0-1.el7.x86_64       1/1
  Verifying  : ApertureDataStudio-1.2.0-1.el7.x86_64       1/1

Installed:
  ApertureDataStudio.x86_64 0:1.2.0-1.el7

Complete!
[aperture@linux1 ~]$

 

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.2.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.2.0

# start the service
$ sudo systemctl start ApertureDataStudio_1.2.0

# Check the service status
$ sudo systemctl status –l ApertureDataStudio_1.2.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 server.properties in /home/experian/ApertureDataStudio/ApertureDataStudio_1.2.0.

The two properties are:

  • DirName.ROOT
  • DirName.DATA

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

Additional dile data sources may be specified in the file filedatastores.properties in /home/experian/ApertureDataStudio/ApertureDataStudio_1.2.0.

Installing Experian Batch

  1. Create the directory /home/experian/ApertureDataStudio/ApertureDataStudio_1.2.0/Batch.
  2. Copy the GBR data mappings files to /home/experian/ApertureDataStudio/ApertureDataStudio_1.2.0/Batch.
  3. Edit /home/experian/ApertureDataStudio/ApertureDataStudio_1.2.0/qawserve.ini:
    • Add InstalledData=GBR,/home/experian/ApertureDataStudio/ApertureDataStudio_1.2.0/Batch
    • Add DataMappings=GBR,United Kingdom,GBR
  4. Copy qawserve.ini to /home/experian/ApertureDataStudio/ApertureDataStudio_1.2.0/addressValidate/qawserve.ini.
  5. Edit /home/experian/ApertureDataStudio/ApertureDataStudio_1.2.0/.experian/batchkeys.ini - add the Experian Batch licence key:
    $ chown –R ApertureDataStudio:experian /home/experian/ApertureDataStudio/ApertureDataStudio_1.2.0/

    Note that other Experian Batch .ini and .dat files can be found in /home/experian/ApertureDataStudio/ApertureDataStudio_1.2.0/.

  6. Restart the ApertureDataStudio server.
  7. Copy qaworld.ini from /home/experian/ApertureDataStudio/ApertureDataStudio_1.2.0/addressValidate/qaworld.ini to /home/experian/ApertureDataStudio/ApertureDataStudio_1.2.0/qaworld.ini:
    $ chown –R ApertureDataStudio:experian /home/experian/ApertureDataStudio/ApertureDataStudio_1.2.0/
  8. Restart the ApertureDataStudio server again.

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.5.5

# start the service
$ sudo systemctl start Standardize_4.5.5

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

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.

 

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

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.

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.

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.

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.

Alternatively:

  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?

1) Stop 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 Aperture Data Studio Database Server service.
  3. Right-click on the service and select Stop.

2) Back up:

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)
  • Server properties file (by default, C:\Program Files\Experian\Aperture Data Studio {version}\server.properties). This contains all your settings defined in Configuration.
  • Filedatastores properties file (by default, C:\Program Files\Experian\Aperture Data Studio {version}\filedatastores.properties). Back this up if you have set up any data stores, use sample data or tutorials.
  • sampledata folder (by default, C:\ApertureDataStudio\sampledata). Back this up if you use sample data or tutorials.
  • 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)

 3) Restore:

  1. Stop the Experian Aperture Data Studio Database Server service.
  2. Replace the current folders with the ones from your back up.
  3. Start the Experian Aperture Data Studio Database Server service. This is now your backed-up repository.

How do I upgrade to a new Data Studio version?

  1. Back up your Data Studio repository.
  2. Uninstall the old version.
  3. Run the new executable (as an administrator).

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.

How do I uninstall Aperture Data Studio?

  1. Search for remove program from the start menu or go to Control Panel > Programs > Programs and Features.
  2. Find Experian Aperture Data Studio.
  3. Right-click, select Uninstall, then click Yes.

Microsoft Active Directory in Aperture Data Studio 

Active Directory (AD) is Microsoft’s implementation of an LDAP server. Its underlying authentication mechanism is Kerberos.  

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

When you're using LDAP (or Kerberos) 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.

Licensing

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  10,000  100,000  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  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:

StatusDescription
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://organization.com:636)
    • 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.

 

Can’t find an answer or a solution?
Contact support