Skip to main content
Skip table of contents

ETL+ Installation Troubleshooting

ETL+ not starting or crashing.

ETL+ is not starting or is crashing on your computer:

Try these techniques in this order until the problem is resolved.

  1. Minimum System Requirements. Verify that your system meets the minimum system requirements:

  2. Run as Admin. Right-click ETL+ on Windows Explorer → Run as Admin. This might be needed when running ETL+ from Windows-protected folders.

  3. Remove hidden files in hidden folders.

    1. C:\ProgramData\DataSelf Corp

    2. C:\Users\<YourWinUserName>\AppData\Local\DataSelf_Corporation

  4. DataSelfWindowsService: If you need to remove/delete the DataSelfWindowsService manually:

    1. Run the Windows Command Line app with Admin rights.

    2. Then run on it:

CODE
sc stop DataSelfWindowsService
sc delete DataSelfWindowsService
  1. Change the options on the Metadata Server page if needed.

    1. Run ETL+ with the with with the -md parameter
      Example "C:\Program Files\DataSelf ETL Plus\DataSelf ETL Plus.exe" "-md"

    2. Enter the appropriate configuration values (see table below) on the Metadata Server page.

    3. Click Save.

  2. Antivirus. Check if your antivirus software (antivirus and firewall) is blocking ETL+ from running.

  3. Firewall. Check if your firewall is blocking ETL+ outbound connections.

image-20240815-210253.png

Metadata Server page

Configuration Values for the Metadata Server page

In most cases the values for the metadata server should be:

  • Server name = localhost

  • Authentication = Windows

  • Database name = etl_metadata

Exceptions: ETL+ applications run on DataSelf cloud server dw8

  1. .NET Repair. Check that your .NET is not corrupted (search on the internet for .NET Repair Tool specifically for your operating system).

Related Pages

Keywords:
Microsoft .NET Framework
Unhandled exception
System.ArgumentOutOfRangeException: InvalidArgument

v2023.07 ✅ ✅ v2022.08

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.